How we work

A clear path from first idea to dependable software.

Structured enough to be reliable, flexible enough to move. Each project is scoped to the problem, with four phases and working software you can see along the way.

  1. 1DiscoverDefine the business goal, user need, risk, and success criteria.
  2. 2ShapeTurn the goal into a clear product scope and technical direction.
  3. 3BuildDevelop in visible increments with working software and feedback.
  4. 4SupportMonitor, learn, maintain, and evolve what has been delivered.

Before phase one

How a project begins.

No forms and no sales scripts. A short email is the first step.

  1. 1

    You write to us

    A few lines about what you want to achieve and who will use it. The Contact page lists what helps.

  2. 2

    We reply with questions

    We ask what we need to understand the problem, and tell you honestly if we think we are not the right fit.

  3. 3

    We agree the next step

    Together we settle scope and cost before work begins, and then the Discover phase starts.

The four phases

What happens, phase by phase.

For each phase: what we do, what we ask of you, and what you have in hand afterwards.

  1. Phase 1 of 4

    Discover

    Agree on the problem before anything is built.

    Define the business goal, user need, risk, and success criteria.

    What we do

    • Talk through the problem, the people who use it, and the constraints
    • Review the tools, data, and processes already in place
    • Name the risks early and agree what success looks like

    What we ask of you

    • A conversation with the people who know the problem best
    • Access to examples: current tools, documents, or sample data
    • Someone who can make decisions on your side

    What you get

    • A short written summary of goals and success criteria
    • A list of assumptions and open questions
    • A clear view of whether new software is the right answer
  2. Phase 2 of 4

    Shape

    Turn the goal into a scope you can read.

    Turn the goal into a clear product scope and technical direction.

    What we do

    • Define the smallest first version that is genuinely useful
    • Sketch the main flows and the system architecture
    • Choose technology that fits the team who will run it

    What we ask of you

    • Feedback on the scope and the prototype, in writing or in a call
    • Decisions on what is in the first version and what is not
    • Introductions to whoever owns the systems we must connect to

    What you get

    • A scope written in plain language
    • Flow diagrams or a clickable prototype
    • A recommended build plan with the trade-offs explained
  3. Phase 3 of 4

    Build

    Working software, in steps you can see.

    Develop in visible increments with working software and feedback.

    What we do

    • Build in small increments, each one usable on its own
    • Show working software regularly and adjust to what we learn together
    • Test, secure, and document as we go, not at the end

    What we ask of you

    • A named contact who can answer questions quickly
    • Feedback on each increment while it is still easy to change
    • Test accounts or sandbox access for the systems we connect to

    What you get

    • Working software you can try along the way
    • Decisions made together, with the reasons written down
    • A release that has been tested before it reaches users
  4. Phase 4 of 4

    Support

    Keep what was delivered working and improving.

    Monitor, learn, maintain, and evolve what has been delivered.

    What we do

    • Launch with monitoring so problems are noticed early
    • Fix issues and answer questions after release
    • Use real usage to decide what to improve next

    What we ask of you

    • Reports of anything that does not behave as expected
    • Your view on what matters most to improve next
    • A decision on how much ongoing help you want, if any

    What you get

    • Handover notes so the software can be operated and understood
    • Ongoing maintenance and improvement if you want it
    • A direct line to the people who built it

Working together

How we keep a project visible.

You should never have to wonder where a project stands.

Written first

Goals, scope, and decisions are written down in plain language, so everyone can check what was agreed.

Working software, not slides

Progress is shown as software you can open and try, at regular points through the build.

Decisions with reasons

When we choose one approach over another, we record why. Months later, that record is worth more than anyone remembers.

Remote and focused

We work remotely, with email as the main channel and calls when a conversation is faster than a thread.

The common thread

Visibility, early validation, deliberate iteration.

Three habits that run through all four phases, whatever the size of the project.

Visibility

You can see progress in working software, not only in status reports.

Early validation

We test the riskiest assumptions first, before they become expensive.

Deliberate iteration

Every round of changes has a reason, so the product gets better instead of just bigger.

Common questions

Before we start.

How does a project start?
Send us a short description of what you want to achieve. We reply by email, ask the questions that matter, and suggest a sensible next step.
Do you work remotely?
Yes. Our operating model is remote-first and designed for focused collaboration with customers and partners.
How is cost decided?
It depends on scope. We agree on scope and cost with you before work begins, so both sides know what to expect.
What if we are not sure what we need yet?
That is a normal place to start. The Discover phase exists for exactly this: we help you work out the problem, the options, and whether new software is the right answer at all.
Can we change direction once work has started?
Yes. Because we build in small, usable increments, what we learn from each one can change the next. We write the change down, so scope never moves by accident.
Will we understand what you have built?
That is the aim. We document as we go and hand over notes written for the people who will run the software, not only for the people who wrote it.
Do you keep supporting a project after launch?
If you want us to. Support is its own phase: monitoring, fixes, and improvements guided by real use. You can also take what we built and run it yourselves.

Start a conversation

Ready to talk through your project?

Tell us what you are trying to achieve. We will respond by email.