A website, and the enquiry pipeline behind it
Enquiries from the site arrive as records, not emails to forward.
Website · CRM · automation
- Client
- Add client
- Sector
- Professional services
- Year
- Add year
- Role
- Design, build and automation
02What changed
Before, and after.
- 01
Before: Enquiries in a shared inbox
Now: Each enquiry arrives as a record
- 02
Before: Forwarded to whoever was free
Now: Assigned to the right person automatically
- 03
Before: Website and CRM from two suppliers
Now: One build, front to back
03How it’s wired
Where it sits in the system.
On the site·Headline
A homepage that says what the firm does in one line.
On the site·Enquiry button
An enquiry form that asks what sales needs to know.
In the system·Contacts
Each enquiry lands as a contact, checked for duplicates.
In the system·Pipeline
A deal opens at the first stage, with the enquiry attached.
In the system·Automation
The right person is assigned, and a reply is drafted.
04The work
How it came together.
Where it started
The website sent enquiries to a shared inbox. Someone forwarded each one on, someone else added it to the CRM, and some were never answered.
What I built
The site and the pipeline were designed together. The form asks what sales needs, and each enquiry arrives in the CRM as a contact and a deal, assigned to the right person with a reply drafted.
05Outcome
What it changed.
- Time to first reply
- Add a measured figure
- Enquiries left unanswered
- Add a measured figure
Built with
- Next.js
- CRM
- Automation platform
06Next project
Contact
Want something like this?
Or write directly: andrewamir41@gmail.com