How it works
Three parts: understand, build, hand over.
A project starts with how your business works today and ends with one tested workflow you've been walked through. Scope and price are agreed before any of it begins.
Understand the current work
We go through how inquiries reach you now, what happens to each one, and which tools are already in play — the form, the inbox, the phone, the spreadsheet, whatever you use for scheduling.
What you have afterAn agreed scope: the workflow to build, the tools it touches, and the price.
Build one useful workflow
I connect those tools so the details land in one place, the right person gets told, and the next step is set up. We start with the one workflow that takes the most repetitive work off your plate.
What you have afterA working workflow, built around the tools you already use.
Test it and hand it over
We run real inquiries through it, including the awkward ones, and fix what doesn't hold up. Then I walk you through how it works, where it hands back to you, and how to change it.
What you have afterA tested workflow, a walkthrough, and an agreed plan for any ongoing support.
Someone requests an estimate. Here's what happens next.
Illustrative workflow — adapted to your business.
The customer sends a request.
They fill out your website form with their contact information and the work they need.
The details reach you.
The request is saved in your customer records, and you receive a notification.
The customer gets a confirmation.
An acknowledgment explains the next step using wording you've approved.
An unanswered request gets flagged.
If it still needs attention, a reminder prompts you to follow up.
You decide what to quote and which jobs to take. The automation handles the repeated steps around those decisions.
What's in scope
One workflow, named in writing, with the tools it touches listed — not a standing arrangement to automate whatever comes up. What a workflow can do depends partly on what those tools allow, so the scope says what will be connected and how.
Testing and the handover
Before anything goes live we run inquiries through it, including the ones that don't follow the happy path: missing phone number, duplicate submission, someone replying to the confirmation. Then I walk you through what it does, where it stops, and how to change the parts you'll want to change.
Where a person stays in the loop
Quotes, scheduling judgment and anything a customer would expect a human to decide stay with you. Automation is for the predictable parts either side of those decisions.
Support afterwards
Agreed at the end of the project, in writing, with whatever it costs stated. Nothing is billed for on the assumption you wanted it.
What moves the price
- How many places an inquiry can arrive from
- Which tools the workflow has to connect to, and what they allow
- How many services, locations, or crews it has to account for
- Whether existing customer records need tidying up first
- How much ongoing support you want afterwards
Projects are scoped around the workflow, tools, and support needed. You'll get the scope and price before work begins.
Fair questions
Do I have to change the software I use?
Usually not. The point is to connect what you already run. If a tool genuinely can't do what the workflow needs — no way to get data in or out — I'll tell you that rather than working around it badly.
How long does a project take?
It depends on how many tools are involved and how quickly we can test against real inquiries. You'll get a realistic estimate with the scope, before work starts, rather than a number picked to sound good.
What happens if something breaks later?
That's what the support arrangement is for, and we agree it at the end of the project instead of leaving it vague. Some workflows need nothing; some are worth checking on.
Will it send things to my customers without me seeing them?
Only what you've approved, and only where you want it. Anything that needs a judgment call stays with you — the workflow's job is to make sure it lands in front of you with the details attached.
Do I own what gets built?
The accounts and the data are yours wherever the tools allow it. Some pieces sit inside third-party platforms you subscribe to, and I'll be specific about which ones those are so nothing about ownership is a surprise later.
Want to see whether there's a workflow worth building?
Tell me how inquiries reach you now and what happens to them. I'll follow up to arrange a conversation.