Our approach
Evidence first. Then software.
We treat every engagement as a question to answer with evidence: where does the work actually leak, what is worth building, and did it work? Software is how we answer it.
How an engagement runs
Four steps, repeated.
The same loop for an internal tool, an AI agent or a funnel. Each pass makes one workflow better and tells us what to do next.
-
01
Map the work
We sit with the people who do the work and map where time, leads and money leak. The output is a written scope, not a slide deck.
You get: Workflow map, measures, written scope
-
02
Build one workflow first
We build the workflow that costs the most and release it as soon as it works, while a wrong assumption is still cheap to fix.
You get: Working software in your team’s hands
-
03
Measure it in use
We agree the measures up front and check them against real use, so the next decision is made on evidence rather than opinion.
You get: A review of what changed, in numbers
-
04
Extend the same system
Once the first workflow earns its place, the next one builds on it. One system that grows, not a pile of tools.
You get: The next workflow, on the same foundation
Why we work this way
Big launches hide expensive mistakes.
Most software projects fail quietly. The scope is written before anyone watches the work being done, the launch arrives months later, and by then the assumptions inside it are expensive to change.
We run our own products, so we pay for our own wrong guesses. That is why every engagement starts with the people who do the work, ships one workflow early and is judged by numbers agreed before a line of code is written.
Engagements
Three shapes of work.
Most clients start with a scoping sprint, decide on the evidence, and move to a build and then to running and improving it with us.
-
01
Scoping sprint
A short, fixed piece of work to map one workflow and decide what is worth building.
- Interviews with the people who do the work
- A written scope and system design
- A fixed scope for the first build
-
02
Build
The first workflow designed, built and released, then extended in small, scoped steps.
- Working releases from early on
- Weekly progress you can use
- Documentation and handover
-
03
Run & improve
An ongoing engagement to keep the system running, measured and getting better.
- Monitoring, fixes and updates
- New workflows as the business changes
- A regular review of what the numbers say
What you own
Everything we build is yours.
No lock-in by design. If you ever want another team to run it, they can.
-
The code
In a repository you control, from the first commit.
-
The data
In databases and accounts in your name, exportable at any time.
-
The accounts
Hosting, AI providers and tools billed to and owned by you.
-
The knowledge
Documentation good enough for another team to take over.
Working together
A rhythm built for busy operators.
Engagements fit around a business that still has to run. This is what working with us looks like week to week.
-
One accountable lead
A senior lead owns your engagement from scope to release. You always know who to ask, and they know the whole system.
-
A weekly working session
Thirty minutes each week on what shipped, what we learned and what comes next, with working software rather than status slides.
-
Measures you can see
The numbers agreed in scoping are tracked in the open, so progress is judged by what changed in the business.
-
Security from day one
Roles, permissions and audit history in the first release, hosted in accounts you control, to your security requirements.
Principles
What we hold ourselves to.
-
01
We run what we build
We build and operate software products of our own, so we know what it costs to keep software working after launch, not just to ship it.
-
02
Evidence over opinion
We decide what to build from how the work actually happens, and judge it by measures agreed before we start.
-
03
Plain about fit
If the answer is a spreadsheet, a template or software you can buy, we will say so. Custom work has to earn its place.
-
04
You own it
Code, data and accounts belong to you, documented well enough that another team could take over.
Working theses
What we believe, until the evidence says otherwise.
Positions we hold from building for clients and running our own products. We revise them when the work proves us wrong.
-
Thesis 01
Fewer tools that agree beat more tools that don’t.
Most businesses don’t need more software. They need the software they have to share one version of the truth.
-
Thesis 02
AI earns its place one checkable task at a time.
Use it where the work repeats and a person can check the result. Widen what it may do only as it proves itself.
-
Thesis 03
A funnel is a system, not a campaign.
Leads are lost in the gaps between tools. Fix the system and every campaign lands on something that works.
Plain about fit
When we are not the right firm.
We take on a small number of engagements at a time, so we would rather say no early than late.
- You need a brochure website and nothing behind it.
- You want the lowest hourly rate for a fixed list of features.
- The problem is standard and software you can buy already solves it.
- Nobody on your side can give the work an hour a week.
Start a project
Start with a scoping sprint.
Tell us the workflow or the part of your funnel that costs the most. A partner replies within one business day.
Start with one workflow.
Tell us the work that costs your team the most. The first step is a scoping sprint, and you decide on the evidence.
Or write to us at [email protected]