What Happens in the 48 Hours Before Your Pipeline Goes Live

You need to give us four things. That is it.

Business name, address, and main phone number. Sounds obvious. We still see contractors hand us the wrong number — the one that rings to a personal cell nobody checks after 6pm. Make sure it is the number that takes incoming jobs.

Service categories and geographic radius. Tell us exactly what you offer and where. "Plumbing in Denver" works. "Plumbing, drain cleaning, and water heater installs within 25 miles of 80203" works better. The more specific you are, the more precisely we map your pipeline stages to job types that match your real ticket prices.

Calendar access. Google Calendar or whatever scheduling system you already use. We connect appointments directly so booked jobs appear without you logging into anything extra.

Your existing lead sources. Where do your jobs come from right now — Google, referrals, Angi, door hangers? List them all. We tag each source separately in the pipeline so you can see which ones are actually worth paying for.

Total time on your end: under 30 minutes to fill out the intake form we send after you sign. Most owners finish in 15. We do not start the 48-hour clock until that form comes back complete.

Once the intake form hits our inbox, the first eight hours are entirely our work.

We review your service categories and map your specific trade workflow to a pipeline stage sequence. This is not a generic setup copied from a template. A plumbing business needs stages built around emergency versus non-emergency, water heater versus leak versus drain. An HVAC contractor needs stages that separate system replacement quotes from tune-up calls. An electrical contractor needs stages that distinguish panel work from standard service calls.

In these first eight hours we:

• Define your pipeline stage sequence end-to-end — typically 6–9 stages depending on trade complexity
• Identify every automation trigger point: new lead in, call booked, quote sent, job won, job lost, job completed
• Select the custom field set appropriate to your trade — job type, estimated job value, property type, urgency flag
• Decide which lead sources feed into which entry points so tagging is consistent from day one

Nothing gets built in this block. This is the architecture phase — blueprint before concrete. Getting this wrong costs days of rework. Getting it right in hour two means the build phase runs clean.

By hour eight we have a documented pipeline map specific to your business and your trade.

This is where the actual build happens.

Pipeline stages. We create each stage with the exact name you will see in your pipeline view. For a plumbing contractor this might be: New Inquiry → Qualified → Estimate Scheduled → Estimate Sent → Job Won → Job Scheduled → Completed → Review Requested. Every stage has a defined entry condition and a defined exit trigger — nothing sits in limbo.

Custom fields. We add job-specific fields to every contact record: job type (emergency, standard, quote-only), estimated job value, property type (residential, commercial), preferred scheduling window, and lead source. These fields populate automatically based on how the lead came in and what information was captured on the inbound call.

Tag taxonomy. Tags tell you at a glance what you are looking at. We configure tags for trade category, lead source, urgency level, and pipeline position. Pull up any contact and see [Emergency] [Water Heater] [Google Ads] [New Lead] in under two seconds. No guessing, no digging through notes.

Automation sequences. Every stage transition triggers a sequence. New lead arrives: immediate SMS notification to you, simultaneous follow-up SMS to the lead. No response in 2 hours: second SMS fires automatically. Estimate scheduled: confirmation SMS plus calendar invite sent to the customer. Job won: booking confirmation plus 24-hour reminder. Job completed: review request SMS fires 4 hours post-completion.

These are not placeholder automations with generic text. Each one is written in language that fits home-service conversations, tested against quiet-hours rules, and wired to your specific pipeline stages.

By hour 24, the full pipeline is built. Nothing is live yet — that happens after QA.

We do not flip the switch until everything passes a live test.

In the final 24-hour block we push test leads through every entry point and verify that every automation fires correctly.

Entry point tests. A test lead enters through each source: inbound call, web form, click-to-call widget. We confirm the lead lands in the correct pipeline stage with the right tags and custom fields populated.

Automation timing tests. We verify that each SMS and email in the sequence fires at the correct interval, with the correct content, to the correct contact. A 2-hour follow-up should fire in 2 hours — not 20 minutes, not 4 hours.

Calendar sync confirmation. We book a test appointment and verify it appears in your connected calendar with full detail — time, job type, contact name, and phone number.

Edge case tests. Three scenarios we always run: an after-hours lead arriving at 11pm (does quiet-hours hold?), a duplicate contact submitting twice (does the system handle it cleanly rather than creating two records?), and a lead with no phone number captured (does the fallback sequence fire correctly?).

Every test is logged. If something breaks, we fix it before going live. If everything passes, we mark the pipeline live and send you the all-clear. You manage none of this testing process. You wait for the notification.

Day three is when you see it working.

The first thing you notice: your calendar has structure. Appointments do not just say "call from Dave" anymore. They say "HVAC Tune-Up — Residential — Referred by Google" with a confirmed time, the customer's phone number, and an address.

The second thing you notice: your phone is quieter, but your calendar is fuller. The AI Receptionist handled calls overnight. Some are booked as estimates. One asked about pricing and received an automatic response — you can follow up in the morning with full context already logged.

Your pipeline view shows every active lead by stage. New Inquiry has contacts in it. Estimate Scheduled has others. You did not manually move any of them. The automations moved them based on what happened in each conversation.

The first real test is an inbound lead arriving while you are under a crawl space. Your phone does not ring. The call is answered, the lead is qualified, the estimate is booked, and a confirmation SMS goes to the customer. You see the calendar event appear. That is the system doing exactly what it is supposed to do.

You are not watching dashboards. You are doing your job while the pipeline fills itself.

We do not hand you a login and disappear.

After go-live, we monitor automation health on a continuous basis. If an automation fails — a sequence stops firing, a stage transition breaks — we catch it and fix it before it costs you a booked job.

When you add a new service — say you start offering water softener installs alongside your core plumbing work — we update the pipeline stages, add the relevant custom fields, and write the new automation sequences. You tell us what changed. We handle the rest.

When edge cases appear that did not surface during testing — a lead type we have not seen before, a scheduling conflict pattern — we handle the exception and update the rules.

This is what done-for-you means. Not "here is the tool, good luck." The system runs on our watch so you can run your jobs.

See the full CRM and Pipeline Setup service — what is included and what it costs before you get on a call. When you are ready, book your setup call and go live in 48 hours.