One line of work, eight stages.
A lead enters, the team works it, it becomes a customer, the work becomes a project, pricing becomes a proposal, the homeowner signs, and the record keeps everything that happened along the way.
Lead lands
A Facebook Lead Ad submission arrives and routes to the correct workspace by connected Page. Calls and referrals are entered once, with source captured.
Team works it
Staff review, contact and qualify the lead. Follow-ups, assignments and every touch stay on the record instead of in someone's head.
Relationship forms
The lead becomes a client, with contacts, company and property linked into the structure the real customer actually has.
Project opens
The opportunity moves through the stages your business defines, and each stage change is recorded historically.
Estimate built
Sections, line items and saved templates produce the scope and totals without rebuilding the same job from scratch.
Proposal sent
Options, attachments and templates go out to the homeowner. Send history is tracked, so a failed send is reconciled rather than repeated.
Homeowner signs
The customer reviews on a page built for them and accepts, with acceptance and signature evidence stored on the proposal.
Job runs
Job details and cost items sit under the project, and notifications push the events the team needs to act on.
Every stage leaves evidence
The activity timeline is not a feature you turn on. It fills itself as the work happens, which is the difference between remembering a job and being able to prove it.
| Stage | What the system records |
|---|---|
| Intake | Source, intake state (received, processing, created, failed, rejected), routing decision, workspace |
| Qualify | Lead events, status changes, follow-ups, assignment |
| Convert | Relationship links between client, contacts, company and property |
| Pipeline | Stage changes with history, related activity on the project |
| Price | Estimate sections, line items, totals and the template used |
| Issue | Proposal options, attachments, send history and delivery outcome |
| Accept | Homeowner review, acceptance and signature evidence |
| Execute | Job details, job cost items, operational and automation events |
The failure cases are handled, not hidden
Most of the damage in a contractor's software stack happens in the gaps: a lead that never arrived, a proposal sent twice, a retry that duplicated a record. These are the parts we built on purpose.
A lead fails to import
The intake event is recorded with its failure state and can be retried or replayed. The original event is not thrown away.
A Page connection breaks
Connections report as active, revoked, error or expired, so a dead integration surfaces instead of quietly costing you a month of leads.
A proposal email is ambiguous
Send history is tracked and reconciled rather than blindly re-fired, so the customer doesn't get the same proposal twice.
Two people act at once
Safeguards protect against duplicate processing and conflicting operations on the same record.
A workspace closes
Closure blocks future activity and safely shuts down connected systems, including disabling the Facebook Page integration when appropriate.
You want out
Data export and account closure are controls inside the product, not a support ticket and a two-week wait.
Bring a live lead to the walkthrough
Connect your Page, take one real inquiry from intake to a sent proposal, and look at the activity record it leaves behind. Twenty minutes, no slides.