For COOs, CFOs and operating partners · logistics, distribution, manufacturing, construction, dealer and multi-location groups · Florida first

Which process eats the most hours?

Name it. In 7 days I'll tell you whether AI can take it, what it saves and what it costs. In 30 days it runs in your systems — owned by your team, with the controls your CFO and auditor will ask about.

Which one are you?

Three situations. Each has a different first move.

Owner-led company

"Show me the number before I sign anything."

First move: 7-day Check on the process that eats the most hours; you decide on the Build with the saving in front of you.

PE-backed portco

"The 100-day plan has an AI line. Who owns it?"

First move: 30-day Build on one back-office process, number agreed on day one — then the same playbook in the next portco.

Multi-location group

"Twelve locations do the same task twelve ways."

First move: Build it once at one location, measure it, roll it out with Agent Care.

Across a portfolio

The portfolio company pays and owns the build; the operating partner sponsors it. Same day-one number, same scorecard, then the same playbook in the next company.

Where to start

Workloads for operating companies.

  1. Invoice intake and AP exceptions

    CFO, finance shared services

    Reads invoices and statements, matches them to POs and receipts, and routes only the exceptions to a person.

  2. Order exceptions and customer email

    Customer service, order desk

    Sorts what arrives, drafts the routine replies, and hands the exceptions to a person with the facts attached.

  3. Freight and carrier invoice reconciliation

    Logistics, distribution

    Matches carrier invoices to shipments and rate agreements, and flags the lines that don't add up.

  4. Warranty and service admin

    Dealer groups

    Checks claims for completeness against the manufacturer's rules and drafts the submission for a person to approve.

  5. Scheduling and dispatch notes

    Field service, construction

    Turns calls, emails and photos into structured job notes and a draft schedule a dispatcher confirms.

How we work together

Know → Prove → Run.

Know · 7 days

7-day AI Readiness Check

Which process eats the most hours, which to automate first, and what it saves. For regulated firms, the list of AI already running — vendor features included — with an owner next to each item. One page and a 30-minute walkthrough.

  • You send the system list and vendor contracts in the first 48 hours.

$4,500 · 7 days · credited in full to a Build or a Governance Setup within 90 days

Book a call
Run · monthly

Agent Care or a part-time AI lead (fractional CAIO)

Agent Care — from $3,500/month. We keep your agents running, fix what drifts, and ship the next small change.

Part-time AI lead — from $8k/month, one day a week. Someone senior who owns your AI program, vendor reviews and board reporting.

3-month initial term, then monthly

Book a call

Several AI initiatives, or a board or lender asking? Governance Setup — fixed fee, scoped on a call.

For the CFO signing off

  • One number, agreed on day one and written into the statement of work.
  • Read on day 30 from your own systems — not from my slides.
  • If the number we agree on day one isn't hit on day 30, up to 30% of the Build fee isn't invoiced.

Payback is worked from your baseline on the call; I don't quote projected savings before I've seen the process.

Worked example

What this looked like before.

From a program I led in a previous role. Client name withheld.

Sales-operations automation — national services company

What it did
60+ workflows on low-code tools for the sales organization — the reports and hand-offs people were doing by hand.
Who signed off
Each workflow had a named owner in sales ops before it went live.
How it was measured
Hours returned to the sales team, tracked per workflow.

What makes it stick

Four things every build leaves behind.

In 2025, 42% of companies abandoned most of their AI initiatives (S&P Global). These four are why a build doesn't join them.

Named owner and trained operators

Someone on your side owns it, and the people who use it are trained before go-live.

Decision log and an off switch

Every decision is logged, and anyone with the authority can stop it.

The paperwork your auditor asks for

Written while we build, not after.

30-day warranty

What breaks in the first month, I fix.

We're not regulated. Why the controls? Because the agent has to survive your CFO's month-end, your auditor and the next system upgrade. The controls are a few hours inside a 30-day build; leaving them out is how pilots die in month three.

Questions operators ask

Straight answers.

We tried a pilot and it died.

Most die from the three reasons on the home page — no owner, no explanation, no number. The build fixes those on purpose.

Whose systems?

Yours. It runs in your tenant, on your keys; nothing leaves.

Who builds it?

I lead every build and write the controls. Vetted developers do parts of the engineering under my review. It runs in your tenant, on your keys.

What if the day-30 number isn't hit?

If the number we agree on day one isn't hit on day 30, up to 30% of the Build fee isn't invoiced. The number and how it's measured go in the statement of work.

We're about 200 people. Is this sized for us?

Yes. One workflow, one integration, 30 days — that's the size.

We're an accounting, law or wealth firm.

Same approach, sized to you. Client data stays in your tenant, your cloud and your API keys; nothing leaves.

We have twelve locations. What do locations 2–12 get?

The same build, configured for each site, with that site's owner trained and the same day-30 number read per location. The rollout runs under Agent Care, one location at a time, in the order you choose.

Next step

Thirty minutes. Bring the process that eats the most hours.

I'll tell you whether it's a 7-day Check, a 30-day Build, or not worth your money yet.