Sample report · Generated by the real engine

See the report before you ask for one.

Most "free audits" are a sales call wearing a costume. Ours is a scored report — so here's one, in full. These are example answers from a composite small business (not a real client), run through the same rubric that scores yours. Nothing below is mocked up.

The example answers

Team size
2–5 people
Repetitive work
15–30 hours/week
Data lives in
Spreadsheets
AI use today
Tried ChatGPT a few times
Current tools
QuickBooks, Gmail, an estimating spreadsheet

Their biggest bottleneck, in their words

“Re-typing job details from emails into our estimating spreadsheet, then chasing the owner for sign-off on every quote before it goes out.”

AI-readiness score

71

/ 100

Ready to start — one focused workflow

Repetitive workload

17/20

15–30 hours/week of repetitive work is squarely in payback territory — typically 6–12 months to recoup a build.

Data accessibility

12/20

Spreadsheets are automatable, but fragile. Expect part of any build to formalize them into something with structure.

Team AI adoption

12/20

You've experimented — good. The gap between trying ChatGPT and trusting a production workflow is exactly what a focused build closes.

Scale of return

14/20

At 2–5 people, one automated workflow often returns a full headcount-day per week.

Problem clarity

16/20

You can name the bottleneck. The audit call sharpens it into measurable scope.

What to automate first

The quote pipeline — specifically the email-to-spreadsheet step. The automated version: job request emails land in a shared inbox, AI extracts the job details (address, scope, materials mentioned, urgency) into your estimating spreadsheet's exact columns, and drafts the quote from your past pricing. A human — probably the owner — still reviews every quote before it goes out. That review step stays. The re-typing disappears.

What it would cost

This maps to one focused automation: $8K–$25K to build, 4–8 weeks, $40–$300/month to run. Not a platform, not a system — one workflow done completely. At 15–30 hours/week of repetitive work, businesses like yours typically recoup the build inside the first year. The spreadsheet fragility (the lowest-scoring dimension above) gets formalized as part of the build rather than as a separate project.

The next 90 days

1. For two weeks, tally every hour spent re-typing or chasing sign-offs — you'll want the real number, not the felt one.

2. Pick the single spreadsheet that would become the system of record, and stop forking copies of it.

3. Put the team on a $25–$30/seat AI tool now — the build lands faster in teams that already trust the tools.

4. Bring all of it to the free 30-minute review call. The report is the agenda; you leave with a scoped plan or a clear "not yet."

Scores are computed on a fixed rubric from self-reported answers — the same rubric for every business, every time. They're a starting point for the review call, not a quote. This sample uses example answers and is regenerated from the live scoring engine whenever the site is built.

Your numbers will be different.

Nine questions, three minutes, and this exact report — scored on your workload, your data, your bottleneck — lands in your inbox. And if the honest answer is "don't build yet," it says so.

Get my report

Can AI help?

What's the task your team does manually every day?

Tell us in plain words. We'll ask a couple of questions, then tell you honestly whether it's worth automating — no sales pitch.