Five phases. No black box.
You should know what is being solved, what is being built, and what needs a decision from you. Everything below is what we actually do, and where we cannot give you a number yet, it says so.
What actually happens, in order.
We do not invent clients, metrics, integrations, capabilities or prices. Where two sources disagree, we keep the conservative one and say there is a conflict. Where a product demo uses stand-in data, we write down which figures are real and which are not. That rule is why parts of this page tell you what we are not going to claim.
Understand
A conversation, at no cost. Longer if the workflow crosses several teams.
Work out what is actually going wrong, before anyone talks about technology.
What happens
- We walk the workflow as it runs today, including the parts done by hand.
- We find where work waits, gets re-entered, or quietly drops.
- We agree what a good outcome looks like in your terms, not in features.
What you get
- A written description of the workflow as it actually is
- The specific points where it costs you time or work
- What we would be trying to change, stated plainly
Before the next phase
We both agree the problem is described correctly. If we cannot, there is nothing worth building yet.
Scope
Depends on scope. We will tell you how long the scoping itself will take before we start it.
Turn the problem into a system on paper, with a price attached.
What happens
- We decide what is automated, what stays manual, and where a person has to approve.
- We list what it has to connect to, and what data has to move between them.
- We choose deterministic logic where a number has to be defensible, and AI only where it removes real work.
What you get
- What we would build, and what it connects to
- What it takes to run once it exists
- What it costs
Before the next phase
You have a written scope and a price before any build starts.
Build
Depends on scope. The productised automation service for trades goes live in days; a platform build does not.
Ship it into production, in working pieces rather than one reveal at the end.
What happens
- We build the parts that carry the most risk first, so problems surface early.
- Integrations are wired with retries and alerts, so a failure is visible rather than silent.
- Where AI drafts something a customer will see, a person approves it before it sends.
What you get
- Working software you can use, not a prototype
- The integrations connected and running
- The approval points you asked for, in place
Before the next phase
It does the job on real work, not on sample data.
Wire
Runs alongside the build rather than after it.
Connect it to the tools you already pay for, so nothing fails silently.
What happens
- We wire in the comms, calendar, payments, storage, CRM and AI platforms the work touches.
- Every step gets a retry and an alert.
- Every action the system takes is written to a log.
What you get
- One system instead of five tabs and a group chat
- Retries and alerts on every step
- The named list of what your system is wired into
Before the next phase
No step carries real work until it has a retry and an alert on it.
Run
Ongoing, for as long as you want us running it.
We operate it. This is the part most studios do not do.
What happens
- AI drafts and automates. A person signs off before anything reaches your customer.
- We monitor it and act when something needs attention.
- We keep changing it as the business changes.
What you get
- A system somebody is actually responsible for
- Reporting on what it did, in plain English
- Changes made as they are needed
Before the next phase
There is no handover cliff. We do not build it and leave.
What has to pass before anything ships.
Tooling catches what tooling can catch, and a person decides the rest. These eight run on our own work, including on this website, which is the only reason they are worth listing.
Types
TypeScript in strict mode, including unchecked index access. The build fails rather than shipping a guess.
Lint
ESLint across the whole surface, including the React rules that catch cascading renders.
Build
A production build has to compile and prerender every page before anything goes out.
Viewports
Checked at nine widths from 320px to 1920px, looking for overflow and clipped text.
Contrast
Text contrast measured against its real background, not eyeballed. AA or it changes.
Keyboard
Every control reached and operated without a mouse, with focus visible the whole way.
Reduced motion
The site is used with reduced motion on, and has to still make sense with nothing moving.
Human review
Tooling catches what tooling can catch. A person still decides whether it is right.
What we are not going to claim
Plenty of studios publish a methodology full of things nobody has written down. These are the questions we would rather answer properly on a call than invent on a web page.
- Fixed timelines for custom work. Scope decides it, so we scope it first.
- A published day rate. Studio work is quoted per project.
- Certifications we do not hold.
- A support SLA. Ask us what response you need and we will tell you if we can meet it.
- Who owns the intellectual property in your build. That belongs in a written agreement, not a marketing page.
Have something that needs building?
Tell us the problem. We will work out what the system has to do.