The assessment answers that. It's the first step in every project we take on, and it's paid. Here's what happens during one and what you have when it's over.
It starts with the people who do the work
We begin with interviews. First the owner or operations lead who called us, then the people who do the job every day, like the estimator or the person who keys in invoices. They know where the time goes, and they usually know where the workarounds are hiding.
We ask how a piece of work arrives, who touches it and where it sits waiting. A process that looks simple on paper often has six handoffs and a spreadsheet nobody mentions until the second conversation.
Then we look at real data
Descriptions only go so far, so we ask for real examples: up to about 25 of the orders, forms, invoices or drawings your team handles. We look at how messy they are and which systems they have to end up in.
A lot of automation ideas live or die here. A form that arrives the same way every time is easy to read automatically. Fifty suppliers who each send a different layout is a bigger project, and it's better to learn that in the first week than the third month.
We build small working demos
Before we recommend anything, we build two small demos against your real data. They're rough on purpose. Each one answers a single question: does this approach work on your documents and your systems?
Your team sees their own examples go through, which tells them more than any slide about what's possible. It also gives them something concrete to push back on.
You get a written roadmap
The assessment ends with a written roadmap. It lists the workflows we looked at and scores each one on how doable it is, how soon it would pay off and how risky it is to connect to your systems. Then it lays out what we'd build first and roughly what it would take.
Sometimes the answer is AI. Sometimes it's a better form or a change in who does what. The roadmap says which in plain language, so you can act on it whether or not you hire us for the next step. If automation isn't worth it for you, the roadmap says that too, and you keep it.
Why we charge for it
A free scoping call can't look at real data, so any estimate that comes out of it is a guess. Charging for the assessment lets us spend real time with your people and your files before anyone commits to a bigger project. It also keeps the recommendation honest, because you're paying for an answer, and sometimes that answer is "don't build this."
What comes after
If the roadmap shows a project worth doing, the next step is a pilot build: one workflow, for a fixed fee, built against your real systems and put into daily use. After that, some clients move to monthly support for maintenance and new work. Plenty stop after the pilot, and that's fine with us.
Is this a fit for your company?
The assessment works best for companies of about 25 to 1,500 people where an owner or operations leader can point to work that eats hours every week. You don't need a technical team or a solution in mind before we talk.