The AI Tools Assessment
A structured review of your operation that ends in a specific, costed, sequenced plan — not a strategy document full of possibilities. You'll know which tools, what they cost each month, how long each takes to stand up, and what order to do them in.
Nobody should buy a build they haven't seen the case for.
Most AI projects fail before they start, because the scope was guessed at. Someone sold a chatbot before anyone checked whether the chatbot was the bottleneck.
The assessment exists so the build decision gets made with real information — what the work costs you today, which fixes are genuinely worth doing, and which ones aren't.
You keep it
The document is yours regardless of what you do next. Nothing ties it to hiring us for the build.
Fixed fee
Quoted before we start, scoped to your systems and team. No hourly surprise.
Real numbers
Named tools with actual monthly pricing, not "contact sales for enterprise licensing."
Honest scoring
Including what we recommend skipping, and what you can handle yourself without us.
What's inside
Every assessment follows the same structure, whatever the industry. Seven sections, built to be acted on rather than admired.
Executive summary
The core problem stated plainly, the operational outcome we're aiming at, and the hours realistically in play. Written so someone who wasn't in the room can follow it.
Opportunity scoring
Everything we find, weighed against what it costs to fix and what it returns. Priority stops being a matter of opinion and becomes something you can point at.
Quick wins
The short list worth doing first — each specific pain paired with the specific thing that resolves it. This is usually where the first reclaimed hours come from.
Recommended solutions
Named tools and builds, with real monthly cost, honest setup time, and what each one gives back. Where the right answer is something we don't build, we name that too.
Engagement timeline
A phased sequence built around your operating calendar. Disruptive work lands in your quiet months, never in the weeks that pay for the year.
Financial impact
Estimated return stated net of what the tools actually cost — because a number that ignores the subscription line isn't a real number.
Open questions
What we still need to confirm before anything can be quoted precisely, and why each one matters. It's how you can tell the figures were reasoned rather than generated.
The patterns we find most often.
Different industries, same underlying shape: a person doing work a system should handle. These are composite illustrations of common findings, not any single client's engagement.
Proposals rebuilt from scratch every time, because the last one lives in someone's sent folder rather than in a system.
Generate drafts from existing client records and past work, so the starting point is 80% done instead of blank.
Jobs booked by phone and text, then re-entered by hand into scheduling and invoicing — twice, sometimes three times.
A single intake path that captures the job once and pushes it everywhere it needs to go.
Front-desk staff answering the same twenty questions all day, while intake paperwork waits and appointments run behind.
Handle the routine questions and pre-visit intake automatically, so staff time goes to the people physically in front of them.
Two systems holding two versions of stock, reconciled weekly by a person with a spreadsheet and a good memory.
Connect the systems directly where a full migration would be too risky, so the reconciliation stops being someone's job.
No clean answer to "which location is actually carrying us," because the reporting requires three exports and a manual merge.
One consolidated view across locations that's current without anyone assembling it.
One person understands how everything fits together, and that person has no time left in their week.
Move what's in their head into systems and documentation, so the business stops depending on their availability.
How an assessment runs.
Light on your calendar by design. The work happens on our side; your team's involvement is concentrated into a few focused sessions.
Discovery call
Free, no obligation. We learn what you run on, where the friction is, and whether an assessment is even the right next step. You leave with a scope and a fixed price.
Embedded review
We work through your systems and sit with the people doing the work. Read-only access where possible, scheduled around your operation rather than interrupting it.
Walkthrough & handoff
We present the finished assessment live, answer questions, and hand it over. Building with us is a separate decision you make afterwards, document already in hand.
What people ask before committing.
Why pay for an assessment instead of going straight to a build?
You can go straight to a build — plenty of firms will quote one. The risk is that the scope gets guessed at, and you find out mid-project that the expensive piece wasn't the bottleneck. The assessment is inexpensive relative to a misdirected build.
What if it tells us to do nothing?
Then it saved you considerably more than it cost. Sometimes the honest answer is "your process is fine, spend the money elsewhere," and we'd rather say that than manufacture a project.
Do we have to build with you afterwards?
No. The document names specific tools, real costs, and a sequence — deliberately detailed enough that your own team or another firm could execute it. We'd like to build it, but nothing obligates you.
Does this only work for certain industries?
The structure holds across industries because the underlying problem does: disconnected systems and a person filling the gap. What changes is which systems and which gap — that's what the review is for.
How much of our time does it take?
Typically a kickoff conversation, a few short sessions with the people who actually do the work, and access to your systems. We shape the schedule around your operating calendar.
What does it cost?
A fixed fee, quoted on the discovery call once we know how many systems, locations, and people are in scope. You'll have the number before you commit to anything.
Is our data safe?
We work with read-only access wherever it's technically possible, and we'll sign an NDA before the discovery call if you'd prefer. Anything we take away is limited to what's needed to write the assessment.
Find out what an assessment would cover.
Talk with our team. We'll walk through your systems, give you an honest read on whether an assessment makes sense, and a fixed price if it does.