Process

How we work, and what it is like to work with us

No mystery, no jargon, no disappearing for six weeks. Here is exactly what happens from the first call to the final handover.

Step by step

From first call to handover

The same structure serves a new build and a rescue. What differs is the assessment stage: discovery for something new, an audit for something that already exists.

  1. Introductory call

    Thirty minutes, free. You describe the situation; we ask questions. You leave knowing whether we can help and what a sensible first step would be.

    No cost, no obligation
  2. Assessment

    Discovery workshops for a new project, or a code and infrastructure audit for an existing one. The output is a written document you keep.

    Fixed price
  3. Proposal

    Scope, approach, timeline, team, cost and risks, in plain English. We say what we are uncertain about rather than hiding it in a contingency.

    A few days
  4. Delivery cycles

    Two-week cycles. Each begins with agreed priorities and ends with a demo of working software and a short written update covering progress and spend.

    Repeating
  5. Launch

    A rehearsed release with monitoring, backups and a rollback plan in place before the switch is flipped.

    Planned window
  6. Handover or ongoing support

    Documentation, credentials and a walkthrough for whoever takes it on — your team, ours, or someone else.

    Your choice

Ways to engage

Three commercial models, chosen to fit the work

Fixed price

For audits, discovery, and projects with a clear and stable scope. You know the cost before we start, and changes are agreed in writing.

Monthly budget

For evolving products and rescue work where the scope emerges as we go. An agreed monthly ceiling, two-week checkpoints, and the freedom to stop or change direction.

Support retainer

For live software. A predictable monthly fee covering updates, monitoring, fixes and a block of improvement time.

Working principles

Promises we are happy to be held to

You own everything

Code, designs, documentation, cloud accounts and domains are in your name from the start. If we part ways, you lose nothing.

No surprises on cost

You see spend against budget every two weeks. If something is going to take longer, you hear it when we know — not at the end.

Bad news travels fast

When we find a problem, you hear about it that day, with options. Clients can handle difficult facts; what they can't handle is finding out late.

Senior people do the work

The engineer you speak to on the first call is the kind of engineer who works on your project. We don't sell with seniors and deliver with juniors.

Plain English

Reports and updates are written for the person paying the bill. If you need a glossary to read our update, we have failed.

Built to be handed over

We work as if another team will inherit the project tomorrow. That is what makes software maintainable — including by us.

Staying in touch

What communication looks like

A shared channel

Day-to-day questions in a shared chat or by email, answered by the engineers themselves.

A staging site

Always available, always current. Try the software yourself whenever you like.

A fortnightly update

Done, next, blocked, and spend against budget — in one page.

A demo every cycle

Thirty minutes to see progress, ask questions and change priorities.

Start with a thirty-minute call

No slides, no sales pitch. Just a useful conversation about your project.