01Workflow mapping sessions
A 75-minute session per workflow with the people who run it. We draw each step in their words, lane by lane, and mark it person only, AI assist or AI with a person's approval.
All servicesWhere to start
AI workflow discovery sprints for New Hampshire businesses
One or two weeks to find the work AI should take on, before you build anything.
For owners and managers who want a straight answer before spending on AI. T10 spends one to two weeks with the people who do the work, maps each workflow in their own words, and measures the hours each step takes. You get a short list of opportunities ranked by the hours they free up and the risk involved, with the first one scoped and quoted.
Discuss your AI plans
A sprint, start to finish
Five AI ideas, mapped, measured and ranked.
A concept film of a sprint we could run for an 18-person cabinet shop. The team's ideas go on a two-week plan. The quote-request workflow is mapped with the people who run it, each step with its hours per week and how much of it AI should do. The ideas are ranked by hours and risk, and the readout names the first build and what stays with the owner. The company, people and hours are made up.
Example workflows01 
02
03
Small enough to prove on real work.
0102Opportunities ranked by hours and risk
Each step gets the hours per week it takes, how often it goes wrong and what's at stake if an AI gets it wrong. The best few become opportunities, each with the systems it would touch.
03A readout for leadership
One meeting and one short document: the ranked list, the first build scoped and quoted, the training that would help and what to leave alone. The maps and the handoff pack are yours to take to any builder.
How an engagement works
Four steps, and you see it work before you commit.
- 01
Kickoff
After a free planning call, a one-hour kickoff to pick the two to five workflows and the people we should talk to.
- 02
Map the work
Mapping sessions on site or by video, one per workflow, with the people who do it. Each step gets a mode and its hours per week.
- 03
Score and rank
We score each opportunity on hours, error rate and risk, check which systems it would touch, and draft the first build.
- 04
Readout
A meeting with leadership to walk through the ranked list and the first step, quoted. You keep the maps and the handoff pack.
A good first engagement
What we look for before recommending an engagement.
- Leadership wants to use AI but can't say where it would help first
- Several teams have ideas and no fair way to compare them
- A budget decision needs a written case behind it
- The people who do the work can give us a few hours each
Questions
AI workflow discovery sprint: straight answers.
How long does a sprint take?
One week covers two or three workflows. Two weeks covers up to five, or one workflow that runs across several sites or teams.
Do you calculate ROI?
We measure what the decision rests on: the hours each step takes per week, how often it goes wrong and what's at risk. Owners usually put their own labor rate on those hours. We keep dollar figures out of the maps so the case rests on numbers your team agrees with.
Who needs to be involved?
One leader who owns the decision, and the people who do each workflow for about 75 minutes each. Nobody needs to know anything about AI.
Do we have to buy a build afterward?
No. The readout and the handoff pack are yours, and any builder can work from them. Some clients start with AI Cowork training instead, or decide the best move is to leave a workflow alone.
Is this a technical assessment?
No. It's written for leadership, in plain language. We do note how each system can be reached (an API, a web portal or nothing at all), because that decides what can be built.
How much does a discovery sprint cost?
The first 30-minute planning call is free. The sprint is a fixed price, quoted before it starts, based on how many workflows and sites it covers.
Related services
New Boston · Statewide