Sales
Tracks the lead until the job is won or lost.
Build the process around how home-service work actually moves, from a new lead and on-site bid through deposit, scheduling, job progress, final payment, review, and later reactivation. Enciu Consulting connects those steps so the team can see what needs attention instead of relying on memory or scattered notes.
The stages below are starting points. Final stage names and handoff rules are reviewed with the business before anything is automated.
Tracks the lead until the job is won or lost.
Tracks the job after the sale through completion and payment.
Gives completed customers a defined place for later follow-up.
Home-service businesses move between calls, site visits, estimates, materials, scheduled jobs, payment checkpoints, and follow-up. Clear status changes make the next action visible instead of leaving it in someone’s memory.
Each new lead needs a clear starting stage, source, owner, and approved follow-up path so it can move toward a call or bid without a separate note.
Bid Scheduled and Bid Sent should mean different things. The CRM can show which estimate still needs a visit, which has already been delivered, and which customer is waiting on the next sales action.
The fulfillment process can separate deposit status, material-payment status, and final payment so those financial checkpoints are visible instead of being buried inside messages or accounting notes.
Job Booked, Materials Ordered, Scheduled, In Progress, Needs Site Revisit, and Punch List stages give the team a more specific picture of what is preventing completion.
Completed does not have to mean the opportunity disappears. Final payment and review checkpoints keep the next customer step visible before the record is archived.
A past-customer process can hold completed contacts for approved seasonal check-ins, maintenance reminders, referral requests, or reactivation work.
The exact package controls what is included. These are the major system responsibilities that can be connected around the home-service lifecycle.
Website forms, phone conversations, booking activity, imported contacts, and other approved sources can create or update the CRM record with source information attached.
Separate sales and fulfillment pipelines keep open bids apart from active jobs while preserving a defined handoff when the work is sold.
Consultation or on-site bid calendars can use business availability, travel buffers, reminders, two-way calendar sync, and CRM attribution.
Stripe, branded estimates, invoices, and payment links can be configured so deposit, material-payment, and final-payment steps fit the fulfillment process.
Approved stage changes can trigger tasks, internal notifications, follow-up, invoice actions, review requests, or other workflow steps included in the build.
Completed jobs can move into review follow-up and later into a past-customer process for appropriate maintenance, referral, seasonal, or re-engagement campaigns.
This example shows how the stages can connect. It is a working model, not a universal template, and the final build is adjusted to the client's real sales and job-delivery process.
The contact starts in New Lead with source and job details attached.
The on-site visit or consultation is booked and logged against the lead.
The estimate is sent, the deposit checkpoint is tracked, and a won job hands into fulfillment.
Material payment, ordering, scheduling, and job status live in the fulfillment pipeline.
Completion, final payment, and review request are separate stages before archiving.
The completed customer can move to a nurture process for approved reactivation or repeat-business outreach.
The industry page shows the operating model. These service pages explain the individual implementation work in more detail.
We map the actual process before deciding which stages, fields, calendars, payment steps, or workflows belong in HighLevel.
We review how leads arrive, how bids are scheduled, what information is collected, how deposits and materials are handled, how jobs are scheduled, what happens when a revisit is needed, and how completed customers are handled today.
The build plan defines the pipelines, stages, custom fields, calendars, payment checkpoints, imported data, approved workflows, business-texting requirements, website work, testing, and package limits before configuration begins.
Representative contacts are moved through the included lead sources, sales stages, fulfillment stages, booking actions, payments, workflow triggers, and handoffs. The goal is to verify that the configured system behaves the way the documented process says it should.
The handoff covers where new leads appear, how to update opportunities, how to manage active jobs, how to send estimates or invoices when included, how bookings connect to records, and what the included workflows do. Ongoing support follows the active scope and monthly subscription terms.
For one defined lead follow-up gap, the Lead Follow Up System is $1,500 to set up, plus $300 per month beginning at launch. Work involving multiple pipelines, payments, migrations, websites, integrations, or additional systems receives a custom quote after the system review. Usage and third-party charges are separate.
These answers focus on bids, job pipelines, field scheduling, deposits, existing customer data, and repeat-customer follow-up.
The operating model is useful for service businesses that move from a lead or inquiry into a bid, estimate, consultation, or scheduled job, then through fulfillment and payment. The final stages are changed to match the specific trade and business process rather than forcing every company into the same labels.
Not every business does. A second Fulfillment pipeline is useful when the work after the sale has enough distinct stages, such as deposit, materials, scheduling, active work, site revisits, punch-list work, final payment, and closeout. A second pipeline can be included in a custom implementation when the client process requires it.
Yes. The calendar setup can include consultation or on-site bid scheduling, business availability, travel or buffer time, reminders, two-way Google Calendar sync, and CRM attribution. The exact calendar structure is confirmed during the build plan.
They can be represented as separate operational checkpoints. When Payments & Invoicing is included, the build can configure Stripe, branded estimates and invoices, payment links, and approved workflow actions around those stages.
Yes, when Data Import & Cleanup is included. The current process covers cleaning names, phones, emails, addresses, and available job-history fields, formatting the data, importing it into HighLevel, checking the source and import counts, and spot-checking records for accuracy.
A custom implementation can add a Past Customer Nurture pipeline. Completed customers can move into an approved follow-up process for review, referral, seasonal, maintenance, or reactivation activity. The cadence and messages are finalized with the client before those workflows are built.
No. The stages shown on this page are starting points from the current home-service build scope. We review and change them to match the client's real process before automations or handoff rules are tied to those stages.
Bring the spreadsheet, CRM, estimate process, calendar, or notes you use today. We will review how a customer moves from first inquiry through the completed job and identify which GoHighLevel setup fits the process and package.
Review My Home Service System