How We Work

Simple, transparent, no surprises

Five steps, the same on every build. The price is fixed before anything starts, and progress is visible every week.

01

Discovery call

Free, 30 minutes, no commitment. We walk one workflow end to end and write it down: the trigger, the systems it touches, and the decision sitting in the middle of it. That document is yours either way. If it is not a good match, we will say so on the call.

You get
One workflow written down: the trigger, the systems, the decision. Yours either way.
How long
30 minutes, free, no commitment.
02

Scope and proposal

A written scope with a fixed price: what is being built, what it costs, and when it will be done. Nothing starts until it is approved. No hourly billing surprises.

You get
A written scope and a fixed price to approve. What you sign off is a behaviour, not a feature list.
How long
Before any work begins.
03

Build

Two to four weeks for most projects, with weekly updates throughout. Progress is something you can look at, not a status colour.

You get
Weekly updates, and something you can look at rather than a status colour.
How long
2 to 4 weeks for most projects.
04

Launch and handoff

Deployment, monitoring, and a check that everything holds against real data. The first few weeks after launch are for the cases the test set did not contain.

You get
It live against your real data, monitored, with the first weeks of fixes part of the build.
How long
The first few weeks after launch.
05

Ongoing partnership

Ongoing work runs on an optional monthly retainer: new automations, changes to existing ones, and monitoring are all covered. You are not committed to it, and the code is yours either way.

You get
An optional monthly retainer. The code and the accounts stay in your name.
How long
Ongoing, and optional.

Not sure a build is the right answer at all? There is a separate front door: a paid, fixed-price assessment of one workflow that ends in a written recommendation you own, and which sometimes says do not build this. The discovery call is free either way.

Your side

What a project needs from you

Three things, kept deliberately small so the project does not become another item on your to-do list.

Access

Login credentials or API keys for the tools being connected. We tell you exactly what is needed upfront.

A point of contact

One person on your team who knows the workflow being automated. They do not need to be technical.

30 minutes per week

A quick check-in to review progress, answer questions, and confirm the right thing is being built.

Questions

Before the call

A question that is not here, asked in one line, gets answered in one.

Two to four weeks for most projects, with weekly updates throughout. Progress is something you can look at, not a status colour.

A written scope with a fixed price: what is being built, what it costs, and when it will be done. Nothing starts until it is approved. No hourly billing surprises.

Three things: access (login credentials or API keys for the tools being connected), a point of contact (one person who knows the workflow), and 30 minutes per week for a quick check-in.

There is a separate front door: a paid, fixed-price assessment of one workflow that ends in a written recommendation you own, and which sometimes says do not build this. The discovery call is free either way.

Step 01

Ready to start with a discovery call?

30 minutes, no commitment, and a written summary of the workflow either way.