Pipeline stages that fit trades
SaaS pipeline jargon does not land on a shop floor. Name stages the way your team already talks:
- Inquiry — call, web form, referral, repeat customer.
- Qualify — fit, geography, timeline, rough budget band.
- Estimate / site visit — scope documented enough to price.
- Proposal out — number in the customer’s hands with clear expiry.
- Follow-up — bounded sequence, not infinite nagging.
- Booked — deposit or schedule confirmed; job number assigned.
- Handed to ops — dispatch has what sales promised.
If you cannot point to where a lead sits on that list without asking three people, you have a pipeline problem—not a marketing problem.
Qualification without being rude
Qualifying is not gatekeeping. It protects both sides: your crew’s calendar and the customer’s expectations.
Questions that work in construction and HVAC:
- Timeline — “When do you need this done?” surfaces emergencies vs shopping.
- Geography — honest about travel and crew assignment.
- Scope — “What does done look like?” reduces change-order fights later.
- Budget band — not interrogration; “Are we in the ballpark of X–Y for this scope?”
Document answers in one place—CRM field, shared sheet, or portal note—so the owner is not re-asking on every callback.
Follow-up that feels human
Referrals built your reputation because you sound like a local shop, not a call center. Follow-up should match that.
What we see work:
- Bounded sequences — e.g. day 2, day 5, day 10 after proposal; then stop.
- One owner per stage — estimator sends update; owner joins only on exceptions.
- Stop rules — no answer after three touches → nurture list or close lost; protects brand.
Automation can remind; it should not replace judgment on a $40k commercial bid. The owner’s voice stays on the deals that need it.
Handoff to delivery
The ops lead should trust the job packet in one read: scope, access, materials risk, customer temperament, what was promised on price and timing.
One paragraph from sales to dispatch beats a CRM full of fields nobody opens. If marketing ran a promotion, ops needs that in the handoff—not discovered on site.
Customer status after booking ties to Status Updates Without the Phone Tag—same promise, visible through the job.
Owner role vs team role
| Usually owner-only | Team can own |
|---|---|
| Major commercial bids, key relationships, pricing exceptions | Qualify, schedule visits, send proposals, routine follow-up |
| Strategic “yes/no” on fit | CRM hygiene, stage updates, handoff packet |
If every row in the right column still lands on you, structure is lagging—see When Growth Outruns Structure for the ten-decision diagnostic.
Pipeline design is not about squeezing more leads. It is about consistent follow-through without the owner carrying every open estimate in their head.
What happens next
Pipeline design is part of partnership—we map yours in the first working sessions: stages, owners, follow-up rules, and handoff to ops. No personality transplant required.
We partner with construction and HVAC owner-operators—typically roughly 30 to 150 employees—who want operations, systems, and growth in one relationship. See Proof for what we have shipped.