Staging before live
We build in a separate test setup or with test records first, so nothing touches your real customers, books or calendar until it's ready.
- Home
- Process
Process · How we work
Our AI automation process, step by step.
Every project starts with a free discovery call and a workflow audit, and nothing gets built until you've read a written scope and agreed to it. Here is what happens at each stage of our AI automation process, what we need from you, and what you get back.
The five steps
From first call to running system.
Each step has a clear purpose and a clear output. You always know what's happening, what we're waiting on and what comes next.
- 01
Discovery call
A conversation, by video or in person around Wilmington, about how your business runs, which tasks eat the most time and what you'd most like to stop doing. We ask a lot of questions, and we tell you plainly whether we think automation is a good fit.
- We need from you
- Time with the person who knows the day-to-day work best, and a rough idea of the tasks that frustrate your team.
- You receive
- An honest read on whether an audit makes sense and, if it does, a short list of the workflows we'll look at.
- 02
Workflow audit
We sit with the people who do the work and watch tasks happen the way they really happen. We list every tool, hand-off and exception, including the ones nobody wrote down, and note how often each task comes up and how long it takes.
- We need from you
- Access to the people doing the work, a view of the tools they use (a screen share is fine) and a few real examples, like emails, forms or invoices. You can remove sensitive details first.
- You receive
- A written map of your current workflows, a ranked list of opportunities with the estimated hours each one costs, a recommended first project and a written scope for it.
- 03
Custom build
We build the agents and automations around your process, connected to the tools you already use and set up in accounts your business controls. Everything is built and tested in a staging setup first, and we show you progress on real examples as we go.
- We need from you
- Someone who can grant access to the systems involved, decisions on the rules (what counts as urgent, who approves what) and honest feedback on test results.
- You receive
- A working system that has been tested against your real work, with exception paths and approval steps already in place.
- 04
Launch & training
New systems run alongside your team before they take over. We compare results, fix what needs fixing and only switch over when the people who rely on it trust the output. Then we train everyone who will use it.
- We need from you
- Time for your team to learn the new workflow, and one person who will own it day to day.
- You receive
- Plain-English documentation of what runs, when and why, a short guide for handling flagged items, training for your team and a list of every account the system uses, all owned by you.
- 05
Ongoing support
Software changes. Vendors update their apps, your team grows and your process shifts. We keep an eye on what's running, fix problems early, adjust rules as your business changes and build the next item on your list when you're ready.
- We need from you
- A heads-up when your process, tools or team change, so the automations change with them.
- You receive
- Monitoring, fixes, regular check-ins on what's working and an updated list of what's worth automating next.
The workflow audit
What a workflow audit gives you.
The audit is the most important step in the process. It turns "we're always busy" into a specific, written list of where the hours go and what to do about them.
How we decide what to automate first- A map of your workflows
- Each repetitive process written out step by step: who does it, which tools it touches, where information gets re-typed and where things tend to stall or go wrong.
- Ranked opportunities
- Every automation opportunity we find, ranked by the time it costs, how often it causes mistakes and how hard it is to automate. Each one comes with an estimate of the hours it takes up each week.
- A recommended first project
- The one project we'd start with and why. Usually it's something frequent, predictable and painful, where you'll see the difference quickly.
- A written scope
- What would be built, which systems it connects, where a person approves the work, what's out of scope and how we'll know it's working. Pricing is quoted in writing alongside it.
- What not to automate
- Tasks that are too rare, too variable or too dependent on judgment. Knowing what to leave alone is as useful as knowing what to change.
You keep the audit findings whether or not you hire us to build anything.
Audit findings
What the audit turns up.
Most of what we find isn't dramatic. It's the quote request that three people touch before anyone replies, the customer re-typed into two systems, the tracker someone rebuilds every Friday.
Each finding is written down with the steps involved and the time it costs, so the decision about what to build first is based on your real week, not a guess.
Illustrative example. Your findings depend on your business.
Building safely
How we build safely.
An automation that's wrong some of the time is worse than no automation. These safeguards are part of every AI agent and workflow automation we build, not optional extras.
Tested on real examples
We test with the messy emails, odd forms and edge cases your business actually gets, not tidy samples. Then the system runs alongside your team before it takes over.
Human approval where it matters
You decide which actions need a person's OK, like sending a reply to a client or changing an invoice. Anything unusual is flagged instead of guessed at.
Only the access it needs
Each automation gets permission to the systems and actions its job requires, through accounts you control. If it only needs to read a mailbox, it can't send from it.
Everything is logged
Every action is recorded: what came in, what the system did and why. If someone asks "what happened to that order?", there's an answer.
A way back
Every launch has a rollback plan. If something misbehaves, we can switch it off and your team returns to the old way of working while we fix it.
Handling sensitive records? Ask about private and local AI, which keeps data on hardware you control.
Engagement shapes
Three ways to work together.
The audit points toward one of these. Whichever fits, the scope, timeline and price are agreed in writing before any work begins.
one-off project
One workflow, done well
A single, clearly scoped automation, like quote intake or invoice processing. We build it, launch it, train your team and hand it over. A good way to see how we work before committing to more.
phased roadmap
Several projects, in order
When the audit turns up several opportunities, we sequence them so each phase pays off before the next one starts. You can pause between phases and reprioritize as you learn what works.
ongoing support
Support and improvement
For businesses that want someone keeping an eye on things: monitoring, fixes when a vendor changes something, rule adjustments as you grow and new automations added over time.
How long does the workflow audit take?
It depends on how many workflows and people are involved. A small team with one problem area takes less time than a business with several locations and departments. We agree what the audit will cover on the discovery call, so you know what to expect before it starts.
Is the workflow audit really free?
Yes. The discovery call and the workflow audit cost nothing, and you keep the written findings whether or not you hire us to build anything. Pricing for a build depends on its scope and is quoted in writing after the audit.
Do we have to give you access to all of our systems?
No. For the audit we mostly need to watch the work being done, often over a screen share. For a build, access is limited to the systems that project touches, granted through accounts you control, and you can remove it at any time.
What if the audit shows automation isn't worth it?
Then we'll tell you. Some tasks happen too rarely, change too often or need too much judgment to automate well. The audit says that just as plainly as it says where the time is going.
Can we start with something small?
Yes, and we usually recommend it. Starting with one well-defined workflow lets your team see how it runs and build trust in it. The ranked list from the audit makes it easier to decide what comes next.
Free workflow audit
Start with step one: a conversation.
Tell us how your business runs and where the time goes. We'll tell you honestly whether an audit makes sense, and if it does, what it will cover. No cost, no obligation.
or email tom@columbusinnovate.com