How It Works
From One Workflow to a System You Own
We design, build, deploy and manage AI automation on infrastructure you own. Every project follows the same steps, so you know what happens next and what you sign off along the way.
The Steps
Free Process Audit
We start with a free, no-obligation process audit of one workflow: what starts it, who does each step, which systems it touches, and where it goes wrong. Nothing is built at this stage.
Requirements You Sign Off
Before we build, you sign off a plain-language summary of your requirements: what the system will do, what it will not do, and what stays with a person. Nothing is built until you agree.
Your Infrastructure
Your AI runs on infrastructure you own: your own cloud account or VPS. You open and pay for the cloud account yourself. You create least-privilege accounts for us, and you can revoke our access at any time.
Pre-flight Audit
Before any deployment we run a pre-flight audit of your hardware or cloud account. It confirms that the system has the resources, access and settings it needs before anything goes live. Problems found at this stage are cheap to fix; the same problems found after launch are not.
Staged Rollout
We roll out in stages, and every change has a rollback plan. Each stage is checked with real work before the next one begins, and the team can see exactly what changed. If a stage does not behave as expected, it is reversed.
Handover
At handover you receive the architecture, runbooks, recovery steps and a credential transfer plan. Those documents describe how the system is built, how to run it day to day and how to recover it if something fails. Whoever runs it next has what they need.
Managed Service (Optional)
Managed service includes monitoring, incident handling, updates and a monthly report. It is optional. Some businesses prefer to run the system themselves after handover, others prefer ongoing support, and either choice leaves the system on your infrastructure.
Who Does What
Clear lines from the start make the project easier to run and easier to hand over. Everyone knows which decisions are theirs, who approves changes and who to call when something needs attention. That clarity matters most when something unexpected happens.
Design, Build and Manage
- Map the workflow with your team
- Write the plain-language requirements
- Build and test against your real examples
- Run the pre-flight audit and the staged rollout
- Monitoring, incident handling, updates and a monthly report, if you choose the managed service
Ownership and Approval
- The cloud account or VPS it runs on, and its bill
- Your business data and workflows
- The accounts you create for us, which you can revoke at any time
- Approval of anything that reaches a customer or a prospect
- The system itself, if you leave
What You See Along the Way
Before the Build
A plain-language summary of what the system will do, what it will not do and what stays with a person. Nothing is built until it has been read and signed off. Any later change to the scope is written down the same way.
During Rollout
Each stage is described before it starts, together with its rollback plan. You can see what is changing, when, and how it would be reversed. Progress is measured against the requirements you signed off.
Every Month
A log of our access to your systems, and with the managed service, a monthly report. The log shows which systems were accessed and when. The report covers how the system performed, any incidents and any changes made.
At Handover
The architecture, runbooks, recovery steps and credential transfer plan. Together they let your own team, or another supplier, run and recover the system without depending on the original builder. Credentials move to your control in a planned, documented way.
Guide
What You Do at Each Stage, and What to Expect
Before the Audit: Pick One Workflow
Choose one piece of work that repeats often and annoys people. Write it down as it really happens today, including the shortcuts and exceptions, and note roughly how often it happens and how long it takes. Bring the person who does the work, not only the person who manages it, and a few real examples: sample messages, forms, statements or call notes, with personal details removed if you prefer.
During the Audit
The conversation walks through the workflow step by step: what starts it, where the information comes from, which systems it passes through, who decides what, where it waits and where it goes wrong. The aim is an honest picture, including the parts that should stay manual. Sometimes the right answer is a simpler process rather than automation, and that is a useful result too.
Reading the Requirements Summary
Before anything is built you receive a plain-language summary to sign off. Read it as a promise of behaviour: what the system will do, what it will not do, what it hands to a person, and how you will know it is working. If a sentence is unclear, ask for it to be rewritten. Anything missing from the summary should be assumed not to be included.
Preparing Your Infrastructure
The system runs on an account in your name. You open it, you pay for it, and you create limited accounts for the people who build and support it. Keep a list of those accounts and what each can do, so access can be reviewed or withdrawn at any time. A pre-flight check of the account happens before anything is deployed, so problems surface early.
During Rollout
Rollout starts small: one team, one branch, one type of request, or the new system running alongside the old process. Watch the results and the list of cases handed to people. Expect adjustments in the first weeks; that is the rollout doing its job. Widen the rollout only when the results are steady.
At Handover
Handover is the point where you can run, change or move the system without depending on its builder. Check that you can find the documentation, that you know how to switch the system off and fall back to the manual process, and that every account and credential is in your name.
After Go-live
Decide who in your business owns the system: who reads its reports, who approves its actions, who updates the information it works from. Review it monthly for the first few months. Most improvements come from what the first real weeks reveal.
Start with the Audit
We start with a free, no-obligation process audit of one workflow. It looks at how the work is done today, where time is lost and which parts should stay with a person. The result is a clear picture of whether automation makes sense, and where to begin.
Book a Free Process Audit