Key Takeaways
- An ops assessment maps where your team's hours actually go and which workflow leaks the most
- You walk away with a prioritized list and a scoped fix — whether or not you build anything
- It takes about 30 minutes; no prep is required, but 15 minutes of it doubles the value
- The best single input: one honest list of every repetitive task from last week
- A good assessment sometimes ends with 'don't automate this' — that answer is free too
What it is (and isn't)
An ops assessment is a 30-minute working session where we map how work actually moves through your business — where it enters, who touches it, which systems it passes through, and where the hours quietly disappear.
It is not a sales demo. There's no slide deck and nothing generic; we spend the time on your workflows. By the end, one of three things is true:
- There's an obvious, high-payback workflow to fix — and you get a scoped plan for it
- There's a fix, but it's not worth the cost yet — we tell you that plainly
- Your ops are actually fine — also worth knowing
All three outcomes are useful. Only one of them costs you anything, ever.
What we actually ask
The whole session runs on a handful of questions:
- Where does work enter? Calls, forms, email, walk-ins, referrals — and what happens in the first ten minutes after it arrives
- What gets typed twice? Any data that moves between two systems by way of human hands
- What depends on memory? Follow-ups, reminders, recalls, status updates that only happen if someone remembers
- What can nobody see? The question you can't answer without calling somebody
- What do you personally do that someone at half your rate — or a system — could?
You'll notice none of these are about software. Tools come last; the workflow comes first.
What you walk away with
| Deliverable | What it tells you |
|---|---|
| Workflow map | How the work really flows today, on one page |
| Leak list | Where the hours go, ranked by annual cost |
| First fix, scoped | What we'd build first, what it costs, payback estimate |
| Honest verdict | Build, buy, or leave it alone — with reasons |
The numbers behind our scoping come from a hundred-plus of these: Bohanon Dentistry's leak was front-desk phone tag and recall (10–15 hrs/week → 2–4). South Central's was coordination-by-phone (3–4 hrs/day → under 1). Auto Capital's was re-keying between systems (20–25 hrs/week → 3–5). Different industries, same method: find the biggest leak, fix that first.
How to prepare (15 minutes, optional)
You can show up with nothing and it works. But if you want the most out of the half hour:
1. Keep one day's interruption log. Every repetitive task you or your team touches, one line each. Don't clean it up — the mess is the data.
2. List your tools. Every system and spreadsheet in daily use. Note which ones "don't talk to each other."
3. Name the groan. The one task that makes someone visibly sigh. It's usually the right first target.
4. Know your rough numbers. What's an hour of your time worth? How many leads or jobs come in weekly? Payback math needs both.
Common questions
Will you try to sell me something? We'll show you what we'd build and what it costs. If the math doesn't clearly work in your favor, we say so — a bad-fit project costs us more than it costs you.
Do I need to be technical? No. If you can describe your week, that's the entire skill requirement.
What if we already have software? Almost everyone does. Most fixes connect what you own rather than replacing it.
Next steps
Book the assessment, or start with the one-day interruption log and see what it shows you on its own. Either way, the goal is the same: stop guessing where the hours go, and get a number you can act on.