How we work

We start with
the smallest system that helps.

This is how a project runs, from the first call to your team running the system without us.

Book a free audit
A marble statue of a bearded philosopher in a blue apron cupping a seedling in a small orange pot, beside the words “Start small.” on an orange ground, with a Slack logo tile.

Signal

Find the thing worth fixing.

We start with what you want to achieve, the last time the work was actually done, and the people who did it. From that we find the one problem or opportunity that matters most.

We start with
What you want to achieve and a recent example of the work.
You receive
A map of how the work runs, the one thing to fix first and a suggested scope.
Your involvement
The person who owns the process walks us through it and helps set a starting point to measure against.
Ready when
We agree what needs to change and whether we know enough to scope a build.

System

Design it, build it, test it.

We agree what comes out, what data it needs, who decides what and who owns it. Then we build the smallest version that helps and test it on real work, including the awkward cases most likely to break it.

We start with
An agreed problem, access to the sources and real examples to test with.
You receive
A working system, with checks, a record of each run and a written note of what it does not do.
Your involvement
Your team confirms access, approves the design and reviews what comes out.
Ready when
The normal path and the important failure cases both pass the tests we agreed.

Shipped

Put it into real use.

We connect the system to your live tools and train the people who will use it. Running it, checking it, recovering it and changing it are all part of the handover.

We start with
An accepted build and the people who will own it.
You receive
A working system, written guidance and a clear handover.
Your involvement
Your team practises the everyday use, the reviews and what to do when something fails.
Ready when
Someone on your team can run it, spot a failure and knows who to call.

Compound

See what it changed, then improve it.

We compare the result with where you started. We fix anything that keeps failing, improve the flow and only expand when the evidence and your team's capacity support it.

We start with
Run records, feedback from the people using it and the measures we agreed.
You receive
A ranked list of improvements and the evidence to decide the next step.
Your involvement
The owner reviews what it is worth, how much it is used and what has changed.
Ready when
Every change has a reason, an owner and a way to check it helped.
A marble statue of Mercury in an orange courier jacket holding out a ring of keys with a blue box under one arm, beside the word “Yours.” on a blue ground, with GitHub and Notion logo tiles.

What the
handover includes.

You should be able to run the system without us. The handover includes:

  • What each step and each number means
  • The tests it has to pass and the cases we checked
  • Who owns each account, each data source and the day-to-day running
  • What to do when it fails and how to change it safely
Read the build guide

Ways to
work together.

Who owns
what.

It stays yours

Wherever we can, accounts, data, files and exports stay in your name. We agree what access we need, who approves the important actions and what you get at handover.

Support is agreed up front

Monitoring, response times and ongoing changes are agreed for each project. A build does not come with round-the-clock cover. New sources, channels and requests go through an agreed change process.

Security and data

Questions people ask.

Do we need a diagnostic first?

Only when we need a closer look before we can scope the build properly. If the goal, the inputs and the limits are already clear, we can scope a build straight away.

Do you work with our existing tools?

Usually, yes. We check what access, data quality and connection options you have during the first stage. A tool being listed in our directory means we can talk about it, not that every workflow with it is possible.

Explore integrations
How do we agree what success means?

We agree what success looks like before we build. That can include the quality of the output, how reliable it is, how much review it needs and the decision it supports. We measure business impact against where you started rather than promise it in advance.

Who needs to be involved?

Someone who owns the result, the people who do the work and whoever can approve the access we need. Your team helps define the flow, reviews real outputs and decides who runs it afterwards.

Can we operate the system ourselves?

Yes, if you want to. We agree ownership, documentation, training and how you export everything as part of the scope. We can stay involved where the system or the team needs it.