Opportunity assessment
A plan you can take into the room.
Two to four weeks. We talk to the people who do the work, look at the systems and the data, and give you a ranked list of what to automate, what it would cost, and what to leave alone. Fixed price, credited against a pilot.
What happens
How an engagement runs.
- Week 1
Interviews and a walk-through
We come on site. We sit with eight to twelve people across the business, from the owner to the person who keys the invoices, and watch how work actually moves. We also meet your IT or security lead.
- Week 2
Systems, data and constraints
We inventory every system and where its data lives, what has an API and what doesn't, and the security, compliance and contract constraints that shape what is possible. You get a written data map.
- Weeks 3–4 (folded into week 2 for smaller companies)
The roadmap and the readout
A ranked list of candidate workflows scored on time saved, risk and effort, with a cost for each. The first pilot scoped and priced. A one-hour readout with your leadership team, and the deck to reuse.
Deliverables
What's in the roadmap.
-
A ranked list of workflows.
Usually eight to fifteen candidates, scored on hours saved, error cost, risk and effort. The top three in detail.
-
A data and systems map.
Every system, what it holds, what talks to what, and what has to change before AI can use it.
-
A security and compliance review.
Which providers and regions you can use, what data may never leave, and what your IT team needs in writing.
-
Costs and a timeline.
A price for each of the top three and a 12-month sequence that fits your budget.
-
A draft AI use policy.
One page your team can actually read, covering approved tools, what not to paste anywhere, and who to ask.
-
The first pilot, scoped.
Fixed scope, fixed price, start date. If you go ahead within 90 days the assessment fee comes off the pilot.
Pricing
Fixed price. Two sizes.
Under 100 people
$9,500
2 weeks
100 people and up
$18,500
3–4 weeks
Credited in full against a pilot that starts within 90 days.
Both include the on-site visit for companies within a day's drive of Kansas City. Further afield, we do the interviews remotely and travel for the readout.
Who runs it
The same people who run the assessment build the pilot.
Nothing gets handed to a junior team after the sale.
Meet the senior team →Questions we get asked
Something else? Book a call and ask.
Who needs to be involved from our side?
A sponsor who can make decisions, your IT or systems lead for two hours, and eight to twelve people for 45-minute interviews. We work around their schedules.
Do we need to prepare anything?
A list of your systems and who owns each. We take it from there.
What if the answer is "not yet"?
Then the roadmap says so, and what would need to change first. About one in five assessments ends with 'fix the data first' or 'buy this off-the-shelf tool'. You still get the map and the policy.
Can our IT team or an outside security firm review your findings?
Yes, and we encourage it. The data map and security review are written to be handed over.
Is the assessment really credited against a pilot?
Yes, in full, for a pilot that starts within 90 days of the readout.
Can you do this remotely?
Yes. We prefer one day on site for the walk-through because you learn more watching than asking, but every step works remotely.
Keep reading
Let's start early.
Thirty minutes to talk about what your team does by hand and which systems it lives in. We'll tell you whether an assessment is the right first step or whether something smaller would do.
Not ready to talk? Take the 5-minute readiness check