Five modules. Pick what applies to your business.
The list is intentionally short. Every module is specified end to end (fixed scope, fixed price, tested rollback), not a brochure entry. Most businesses start with one. None start with all five. The intake response will tell you which one to ship first, and which one to skip.
We don’t rebuild what you already pay for. We build around it.
QuickBooks sends three invoice reminders on every plan it sells. Jobber sends two more, if you’re on Connect or above. Selling you a fourth would be a waste of your money. Neither one knows what the other did. Neither knows a customer is disputing the bill, or already promised to pay Friday, or that a commercial account on net-60 shouldn’t get the same nudge as a $300 repair.
That gap is the job. We switch on everything your software already includes, then build the layer it cannot have: the part that reads both systems, knows who not to chase, escalates when it should, and tells you what actually changed. Your existing tools become the first layer, not the only one.
Pushing work down onto software you already own isn’t us being modest. It’s cheaper to run. Every reminder QuickBooks sends for free is one we don’t send over Twilio, which is your monthly bill, not ours. And it’s one less thing that can break after we hand it over.
So the first thing we do is go through what you already pay for and write down, line by line, what it covers and what it doesn’t. You get that page whether or not you hire us. Sometimes it says configuration and a data cleanup close the gap on their own: a $1,500–4,000 job instead of a $4,000–9,000 one. We would rather sell you that than a build you didn’t need.
Index.
-
invoice-chaser
The overdue invoice you hate chasing, followed up in your voice until it's paid. jump ↓module · 1-2w
-
friday-digest
The Friday email you never get around to writing, generated from systems you already pay for. jump ↓module · 3-7d
-
estimate-drafts
Drafts in your voice, built from your own historical examples. jump ↓module · 1-2w
-
schedule-keeper
The invisible tax on small businesses. Reschedule logic, dispatch, no-show recovery. jump ↓module · 1-3w
-
phone-desk
The phone keeps ringing after you close. We answer, qualify, book. jump ↓module · 2-4w
The overdue invoice you hate chasing. Now it chases itself, in your voice.
Sold as the Revenue Recovery Sprint, because the automation is only the last part. First we baseline what you’re actually owed, fix the invoice data that breaks follow-up, and switch on the reminders your software already includes. Then we build the escalation those tools can’t do. Runs off the same invoice status friday-digest already reads: the unpaid ones over 60 days. When a job goes unpaid, it follows up by text and email in your voice, on a schedule that escalates gently: a friendly nudge, then a check-in, then the offer of a payment plan, then one last notice. It stops the second the invoice is paid. It never sounds like a collections agency, because it sounds like you.
- escalating follow-up by text and email: friendly first, firmer only if it has to be
- triggered off invoice status in jobber or quickbooks, the same data friday-digest reads
- always in your voice: your greeting, your wording, your sign-off. you approve the sequence once
- offers a payment plan on its own, and stops the moment the invoice is marked paid
- disputed or do-not-contact invoices route back to you, never chased
- handoff: runs on twilio and your own email, billed in your name, nothing new to log into
what we measure, at kickoff and again at 30 / 60 / 90 days
- dollars overdue, and the invoice count past 30, 60, and 90 days
- average days to pay, calculated the same way every time
- invoices never sent, or sitting in the wrong status (usually the biggest surprise)
- hours you and your office staff spend chasing
- dollars paid after the new sequence: reported as associated with, never caused by. There is no control group and we will not pretend otherwise
what this is not
- not debt collection: no legal demands, no credit reporting, no collections representation
- no guaranteed recovery. Anyone promising you one is guessing
- nobody gets contacted when consent, contact data, or account status is unclear
Sample data from a fictional business, not a client result. An example escalating follow-up on a $3,180 invoice 62 days past due: a friendly day-3 nudge, a day-14 check-in offering to split it into two payments, and a day-30 final notice, all in the owner's voice. The sequence stops the moment the customer pays.
The Friday email you never get around to writing. Now it writes itself.
Pulled from systems you already pay for (QuickBooks, Stripe, your field-service software, your booking tool) and stitched into one email or one dashboard, in the language you actually use. No new logins, no "we'll need read access to your database."
- weekly owner digest, sent friday 5pm: the one report you'll actually read
- revenue / hours / unpaid invoices aging / appointments / utilization
- QuickBooks, Stripe, Square, and your FSM: pick what you already run
- owner-only and manager-only versions, scoped per role
- "why did this number move?" answered in a paragraph, not a chart legend
- handoff: standard email; nothing to log into
Sample data from a fictional business, not a client result. An example weekly digest email: revenue of $48,210 (up 14 percent), 87 jobs booked, 4 no-shows, and a note that three quotes over $4,000 are still open.
Pick a week. Run the digest.
Three fictional weeks at Cedar Ridge Mechanical, the same fictional shop as the sms demo further down the page. Pick one and run it; the weekly owner email composes itself from that week's numbers. Every week is pre-written, nothing is generated live, and no AI runs here.
Drafts in your voice. Built from your own historical examples.
Written from your own proposals, your own emails, your own social posts: your best prior work goes in front of the model every time it drafts, so the output sounds like you and not like a chatbot. You approve every send. Nothing goes to a customer without you reading it first.
- proposal & invoice drafts, populated from job data, tuned to your tone
- customer email drafts (estimate follow-ups, reschedule notes, late-payment nudges)
- marketing email: monthly newsletter, seasonal promos, drafted from your prior best
- social posts drafted in a consistent voice for instagram, facebook, or google; written for you to post, not posted for you
- tone safeguards: your forbidden-words list, your disclaimer rules, your brand spelling
- handoff: drafts land in your gmail / outlook drafts folder. you press send.
Sample data from a fictional business, not a client result. An example proposal draft: three paragraphs of scope, seven line items, a $6,840 total, pulled from prior similar quotes and held for the owner's review before send.
Stop hand-rebuilding the calendar every Monday morning.
Scheduling is the invisible tax on small businesses. Every cancellation triggers a hand-rebuild of the day. We automate the boring half so your front desk handles the half that actually needs a human.
- cancellation → waitlist re-fill, automatic and same-day
- missed-appointment recovery: the opening goes back out to the waitlist automatically, so nobody has to remember to do it
- reminder sequences that respect channel preference (text vs email vs voice)
- dispatch suggestions by zip and availability, built on the fields your FSM already carries, not on certifications and job history it doesn’t track
- customer records: remove duplicates, fix formatting, fill in the fields your team always skips
- handoff: built around the calendar you already run; switching tools is never the starting assumption
Answer the phone after you close. Triage it. Route it. Put it on the calendar.
For shops whose calls need real triage, routing, and escalation: not just an answering bot. After-hours inbound (calls, texts, web forms) gets answered in your voice, qualified against the questions you'd ask yourself, and either booked to your real calendar or escalated to a human with the full context.
use the cheap option instead when
- you mostly need messages taken and standard appointments booked
- every call gets handled the same way, whoever is calling
- you’re already on Jobber Plus: its AI Receptionist is included, and we will tell you so
- a $29–249/mo subscription (Jobber Receptionist, Housecall Pro CSR AI, Goodcall) covers it
use phone-desk when at least two of these are true
- emergency vs. non-emergency has to be triaged, and getting it wrong costs you
- routing depends on technician, territory, certification, or who’s on call
- booking has to respect real capacity, not just an open calendar slot
- commercial accounts or service agreements get different treatment
- your existing number has to forward, with a defined failover when something breaks
- a human has to be reachable inside a defined window, with the context handed over
- after-hours chat & web-form intake, 24/7
- two-way SMS that respects opt-out and STOP keywords
- AI phone agent for shops with high call volume (books to your calendar, transfers when it can't)
- review-reply assistant that drafts in your tone, you approve before send
- spam & lead-form filter (no more "we noticed your website" emails reaching you)
- handoff: full transcript + customer record into your CRM, every time
what this is not
- not a subscription you should buy first. If a $29–249/mo receptionist covers your calls (Jobber’s is $29/mo and free on Plus; Housecall Pro and Goodcall have their own), that is what we will tell you to switch on, and we will not quote you a build instead. This module earns its price on the conditions above, not on answering the phone
- no response-time promise. We would rather say nothing than publish a speed we have not measured on a real shop’s traffic
- outbound texting cannot start on day one. Carriers require your business to be registered before a single message leaves, and that queue is not ours to speed up
Sample data from a fictional business, not a client result. An example after-hours SMS intake: a customer texts about a dead AC, the desk qualifies the job, offers two slots, and books a weekend visit into the CRM.
Play the customer. See what the desk does.
A scripted walk-through of an after-hours text to a fictional Cobb County shop. You pick the customer's lines; the desk answers with canned, pre-written replies. This is a demo, not the live product responding, and no AI is involved.
How engagements are priced.
Every engagement is fixed-scope, fixed-price. The free intake response includes a preliminary range; the fixed price comes after we've seen the work up close. There is no monthly retainer; you pay for what we ship, and the run cost (a small monthly to cover hosting and the software it runs on) is billed in your name to your accounts. If we don't have a build worth doing, we don't invoice you to keep looking.
Builds run $2,000–18,000 depending on the module. Below that sits a $1,500–4,000 cleanup and configuration engagement for shops whose real problem is messy data and unconfigured software rather than missing software. It stands on its own: there is no credit toward a bigger build, and no upgrade we are steering you toward.
The windows above are build time, not time-to-live. Every engagement then runs a pilot week beside your existing process, a cutover, and seven days of burn-in where we are reachable for real breakage. Plan on a couple of weeks past the build before it is yours and we are gone. That tail is the part that makes the rollback proven instead of promised, and we would rather you counted on it than discovered it.
One honest note on the build windows above. Anything that sends a text (the invoice follow-up, the reminders, the after-hours desk) cannot send its first one until the carriers approve your business for messaging. That registration happens on your account, it is required by law and by every US carrier, and the wait is theirs, not ours. The build windows are build time. We start that paperwork on day one and tell you where it stands, but we don’t control the queue and won’t pretend the calendar ignores it.