Process

How it works

Four steps, each with a stop point. A 20-minute call, an audit, one capped pilot inside the tools you already use, then support or an agreed stop.

Call → Audit → Pilot → Support

Step 1 of 4

Call

You tell me what's taking up your team's time. I ask about calls, scheduling, paperwork and follow-up, and which tools you already pay for.

You leave with · a clear yes or no on whether an assessment is worth it

Step 2 of 4

Audit

I learn how your business runs and walk through the workflows you pick, from first contact through delivery, billing and follow-up.

You leave with · a ranked list of bottlenecks with effort estimates

Step 3 of 4

Pilot

You choose a useful first project. I configure your existing tools first, then build targeted automations within the agreed scope, tested with your team before they go live.

You leave with · working automations in accounts you own

Step 4 of 4

Support

I test with your team, document what I built, and we agree on next steps, or stop.

You leave with · documentation your team can run without me

In order

What a pilot looks like

Illustrative. The schedule and the hour cap are set in the scope document.

01 · MappingSessions with you and the people who do the work. A written list of every handoff, from first contact through billing and follow-up.

02 · RankingBottlenecks ranked with effort estimates. You pick the first project. Scope and hour cap agreed in writing.

03 · First buildYour existing tools configured first. The first automation drafted and tested with one person on your team.

04 · TestingFixes from testing. A second pass with everyone who touches the workflow.

05 · Go liveRunning in accounts you own. Documentation drafted in plain language.

06 · HandoffA handoff session with your team. Next steps agreed, or an agreed stop.

What I commit to

How engagements are scoped

Scope is defined up front. We agree in writing on specific workflows and deliverables before work begins.
Hours are capped. Scope changes are discussed and agreed first.
No unlimited development. This isn't an open-ended build or on-call IT service.
You keep control. Automations live in, or connect to, accounts you own, and are documented for your team.

Said plainly

What I don't promise

No guarantees of results. I don't promise specific revenue, lead or time-savings outcomes.
No compliance guarantees. I don't provide legal, tax, regulatory, licensing or data-privacy advice or certification.
Results depend on your business. Results depend on your workflows, tools, data and team adoption.

FAQ

Questions owners ask before a call

Do I need to buy new software?

Usually not. I get more out of your existing CRM, scheduling, phone, email, document and accounting tools before adding anything new. If something new is genuinely needed, it goes in the scope document first.

Who owns what gets built?

You do. Automations live in, or connect to, accounts you own, and are documented for your team.

What if it doesn't work for us?

Every automation is tested with your team before it goes live, and the engagement has a stop point built in. I don't promise specific revenue, lead or time-savings outcomes; results depend on your workflows, tools, data and team adoption.

How much of my team's time does this take?

Mapping sessions with the people who do the work, then short testing rounds with the same people. The scope document sets the hours, including yours.

See it on one trade · HVAC, the full breakdown

Start with the 20-minute call

Tell me what's taking up your team's time.

Find out where AI can help

Start with a 20-minute discovery call. No prep, no pitch deck.