Every project is scoped to your case.
We do not sell packages off a shelf. Every project starts with a conversation about your workflow. We agree the scope, the cost and how we will know it worked, in writing, before any work begins.
Talk, scope, agree, build.
A free 30-minute call
You describe the workflow. We ask about volume, tools and where it goes wrong, and tell you plainly whether automation is worth it.
A written scope
We look closely at the process and the systems involved, then write down what we would build, what we would leave alone and what it would take. For a larger problem that look may be its own short step. We say which on the call.
A price you agree to
The cost comes from that scope, so you can weigh it against the hours it saves. Nothing is built until you have agreed it.
Build, then optionally run
We build and launch one workflow. If you want us to keep it running, monitoring and repairs are agreed separately and stay optional.
Six things decide the size of a project.
Steps and systems
How many steps the workflow has and how many tools it has to talk to.
Documents and data
How consistent your documents and records are, and how much cleaning they need first.
Rules or judgment
How much is plain rules and how much needs AI to read, sort or draft.
Control and approvals
Who must approve what, and how much has to be logged and reviewable.
Hosting and security
Where data must live, how long it is kept and who is allowed to see it.
Volume and support
How much work flows through it, and how much ongoing care you want.
What you get in writing.
One document, in plain language, that you can read, question and change before you agree to anything.
- What is automated, and what is not
- The systems and access we need from you
- Where a person approves, and the limits that trigger it
- What happens when something fails, and who is told
- The timeline
- The cost, and what ongoing management covers if you choose it
- How the system is handed over, so you can run it without us