A good enquiry, then silence
A new enquiry comes in: a property manager who has just taken over three buildings, a school that has been told by its insurer to sort out water hygiene, a hotel whose contractor has let them down. It arrives by phone, web form or email, and the person who takes it writes a few notes.
Then it needs more information: how many buildings, what kind of systems, whether there is a current risk assessment. Often it needs a site survey before you can price. The notes go to the director, who is busy. The survey is booked eventually. The proposal is written in Word from an old one. By the time it goes out, the client has signed with someone who replied first.
Where the handoffs break
| Step | Owner | What goes wrong |
|---|---|---|
| Enquiry received | Whoever answered | Key details not asked |
| Qualification | Director or sales | Waits for a call back |
| Site survey | Engineer or assessor | Booked late, findings on paper |
| Proposal | Director | Written from scratch, delayed |
| Follow-up | Nobody in particular | Not done |
Each step is small. The problem is that nothing moves an enquiry to the next step, so enquiries wait wherever they were last touched.
What stalled enquiries cost
New contracts are the lifeblood of a service business, and every stalled enquiry is work you could have won. Slow proposals also say something to a prospective client about how you will respond once they are a customer. And directors spend evenings writing proposals that could be largely assembled.
An enquiry pipeline with the steps built in
- Enquiries from your website, email and phone are logged in one pipeline, with a structured form that asks what you need: building types, number of sites, current arrangements, reason for enquiry, timescale.
- Each enquiry has an owner and a next step with a date, so nothing waits without someone knowing.
- Where a survey is needed, it is booked from the pipeline into the right person's diary, with the details the surveyor needs.
- The surveyor records findings on a tablet form: assets, sites, access, observations. These feed the proposal directly.
- The proposal is assembled from your templates: scope per site, task frequencies, pricing from your price model, and standard terms. The director reviews and adjusts.
- Follow-up reminders prompt the owner at sensible points, with a draft note ready, until the enquiry is won, lost or parked with a reason.
If you use HubSpot or another CRM, we can build the pipeline inside it. If you do not, a simple pipeline built for your process is often enough.
Enquiries that move
Every enquiry has a visible status and an owner. Directors see the pipeline at a glance and spend their time on judgement and pricing, not layout. Surveys produce proposal-ready data. Prospective clients get a timely, professional proposal, and polite follow-ups that do not rely on anyone's memory.
Take a property manager with three office buildings. The enquiry form captures building details and the fact that there is no current risk assessment. The owner books a survey. The surveyor's findings list the systems and outlets. The proposal assembles a risk assessment for each building and monthly monitoring, priced from your model, and the director adds a note about access that the property manager mentioned. The follow-up prompt a week later reminds the owner to call.
Win and loss reasons, recorded for every enquiry, also show you over time where you are losing work: price, speed, scope or something else.
Checklist for your sales process
- Enquiries are noted on paper or in someone's inbox.
- Proposals are written from scratch or copied from old ones.
- Survey findings are retyped into proposals.
- Nobody follows up proposals consistently.
- You have lost enquiries to competitors who replied first.