Four steps, and you approve the second one.
The whole thing costs you about two to three hours of your own time. Most of the fear about projects like this is really a fear of being drawn into months of meetings, so here is the honest version.
- 01
Call
Thirty minutes. We map where the time is going. No pitch deck.
What we do
We ask what happens today, step by step, including the parts done by hand and the parts people work around. Then we say which of it is worth automating. Sometimes the answer is none of it.
What you do
Thirty minutes, and a willingness to describe the boring version of the work rather than the tidy version.
- 02
Scope
A written plan, a fixed price, a delivery date. You approve it before anything is built.
What we do
A written plan: what gets built, what it will and won't do, what happens when it fails, a fixed price, and a delivery date. No hourly drift afterwards.
What you do
An hour or so reading the scope and telling us where it's wrong. You approve it before anything is built.
- 03
Build
Usually two to four weeks. You see it running before it goes live.
What we do
We build and test the agreed workflow, including its key exceptions and records. You see it working on representative data before anything is switched on.
What you do
Access to the systems involved, and roughly an hour to look at it running before it goes live.
- 04
Handover
You receive the code, setup notes, credentials, and agreed operating instructions.
What we do
We hand over the agreed code, configuration, credentials, and documentation. Maintenance or post-launch support is discussed separately if the workflow needs it.
What you do
Review the handover and confirm that your team can access the agreed accounts and operating notes.