What we found
Sometimes the answer isn't AI.
Troy S. is a manufacturer's rep for specialty building products. The assessment found one job quietly eating his week. The fix had nothing to do with AI.
- The job
- Substitution requests
- Before
- 30 to 60 min each, by hand
- Now
- About 5 min to review
- Back in his week
- Roughly 7.5 hrs
- The fix
- Process automation
What was leaking
A substitution request is an ordinary part of the job. A contractor has a specific product written into the spec and wants to swap it for something else. Sometimes the specified item is on backorder. Sometimes there's an equivalent that costs less. Either way, somebody has to answer.
Answering means building a package. The two products laid out side by side. The specs that have to match. The data sheets. And the case for why the swap holds up, because an architect or an engineer is going to read it and decide.
Troy built that package by hand. Every time. Thirty to sixty minutes of pulling the same kinds of documents into the same shape, request after request.
So most simply didn't get done.
That's the real cost. Not the hour. Every request that sat in his inbox because he didn't have an hour that day.
What the assessment found
We didn't start with a tool. We started with his week and asked where the time actually went.
The substitution request came up right away. Once we walked through one, the job split cleanly in two.
One half is judgment. Is this swap genuinely equivalent? Will it get accepted? Is this something Troy wants his name on? That half is Troy, and it should stay Troy.
The other half is assembly. Pulling the same documents. Laying out the same comparison. Formatting the same package the same way. That half doesn't need a person, and it doesn't need AI either. It needs the steps to happen in order without somebody doing them by hand.
That's a boring answer. It's also the right one.
What got fixed
The assembly half now runs on its own. The judgment half didn't move.
| Step | Before | After |
|---|---|---|
| Pull the specs and data sheets | By hand, every request | Runs on its own |
| Lay the two products side by side | By hand, every request | Runs on its own |
| Format the package | By hand, every request | Runs on its own |
| Decide whether the swap holds up | Troy | Troy |
| Time per request | 30 to 60 min | About 5 min to review |
The package now arrives already built. Troy reads it, decides, and sends it. About five minutes. Roughly 7.5 hours back every week.
The requests that used to sit now get answered. That part never shows up in an hours number, and it's probably the bigger half.
The point
None of this was AI.
That matters, because the reason to run an assessment isn't to end up with AI. It's to find out which jobs in your week are costing you, and then to pick the right fix for each one. Sometimes the right fix is AI. Often it's a form, a template, or a set of steps that run in order without you standing over them.
If the only thing somebody sells is AI, every finding is going to look like AI. I'd rather hand you the boring answer when the boring answer is the one that works.
The assessment reads your week the same way it read Troy's. Which jobs, which fix, what it costs.
The substitution package
- Assemble the package by hand this one · 30 to 60 min
- Answer the ones still sitting this one · every week
Start
Your week has 5 hours hiding in it.
One call, one report, one walkthrough. $999, refunded in full if the report doesn't show you a path to 5 or more hours a week.
Report in 3 business days, walkthrough the day after.