"We build and run business systems" is a sentence. This is what it means in practice, step by step, in the order it happens, with what you see at each stage and what you decide. It is written so that a company considering a build knows what it is agreeing to before the first call, and so that the first call can be about your business rather than about us.
Stage 1: the discovery call
A video or phone call, free, usually forty-five minutes. We ask what your team does by hand today, in order: where a request or an order or a lead comes in, who touches it, where it waits, what breaks, and what the person doing it would rather be doing. We ask to see the sheet, the group chat or the inbox where it lives now. We do not pitch; we listen and take notes, and at the end we say whether we think a system is the right answer, and roughly what shape it would take.
Sometimes the honest answer is "one workflow, and a freelancer would be cheaper", and we say so; the freelancer versus company guide is the comparison we use.
Stage 2: the blueprint
Within a few days you receive a written document:
- The process as it is, in a diagram, with the places it breaks marked.
- The process as it will run, with each automated step, each point where a person decides, and each tool connected.
- What is in scope and what is not. The things we deliberately leave for a second stage are listed, so the first stage is finishable.
- The price of the build and the monthly plan it runs on afterwards.
- The timeline, in stages, with what your team will be able to use after each.
- What we need from you: access to the tools, the message wording, the person who will test.
You approve the blueprint, change it, or decline. Nothing is built before this document is agreed, and nothing is invoiced before it is approved.
Stage 3: the build, in stages
A private n8n instance is provisioned for the system: its own container, database schema, credentials and subdomain. If the system uses WhatsApp, the API instance is provisioned beside it. Then the build follows the blueprint's stages, usually the one with the most visible effect first: the first reply to a lead, the order confirmation, the reminder.
You see each stage as it is finished, with real data from your tools, and your team tries it before the next stage starts. Wording is yours: every message a customer or an employee receives is written in a settings sheet you can read and edit.
Stage 4: testing with your team
Before anything is switched on for customers, the people who will live with the system run it: the receptionist sends the test booking, the salesperson receives the test lead, the finance lead approves the test invoice. What they find is fixed; what they want changed is changed if it is in scope, and listed for the second stage if it is not. The security page describes what the instance is at this point: isolated, backed up, monitored.
Stage 5: the switch-on
Workflows are activated one at a time, lowest-traffic first, and we watch the first real executions with you. For a system that replaces a manual routine, the manual routine keeps running in parallel for a few days, so a mistake is caught by comparison rather than by a customer. Then it stops, and the system is the way it is done.
Stage 6: the months after
The system runs on a monthly plan: hosting, updates, backups, automated monitoring and a named engineer who built it and answers your messages. In the first month we review the numbers the system produces with you (reply times, no-shows, overdue invoices, whatever it measures) and adjust the timings and wording. After that, changes to the process are scoped and quoted as small pieces of work, done by someone who already knows the system; a second stage from the blueprint is the usual first one.
You own the workflows. If you leave, they export from n8n in a form that runs anywhere, and the migration guide describes the export.
What the company brings, and what we bring
You bring: the knowledge of how the work is done and why, access to the tools, the wording of the messages, and one person who will test and later own the relationship with the system.
We bring: the design, the build, the instance, the running, and the honesty to say when something should not be automated.
Starting
The discovery call is booked from the consultation page. The solutions pages show, for each kind of team, what the blueprint tends to contain.