Discuss your project

How we work

You should never have to ask
how it is going.

Outsourced development usually fails in one specific way: the client finds out late. Everything below exists to make that structurally difficult, and to make leaving us easy if it happens anyway.

The shape of a project

Four stages,
four things you keep.

Each stage ends with an artefact in your hands, so leaving after any one of them costs you nothing.

  1. 01

    Week one

    Scope it in a week

    A short paid discovery: we map the workflow with the people who do it, agree what version one must do, and hand back a fixed scope, price and date. If you take that document to another team instead, it still works.

    You keep01 / 04

    The plan.

    • Scope
    • Estimate
    • Risks
  2. 02

    Every week after

    Build in weekly slices

    Every week ends with a deployment you can open, a written update on what moved, and the plan for the next one. Priorities can change on Monday; they should not be a surprise in month three.

    You keep02 / 04

    The product.

    • Working build
    • Weekly update
    • Next plan
  3. 03

    At launch

    Ship, then measure

    We instrument the thing we built — how often it is used, where it fails, how long the job now takes — so the question ‘did this help?’ has an answer that is not a feeling.

    You keep03 / 04

    The numbers.

    • Dashboards
    • Error reporting
  4. 04

    Afterwards

    Run it, or hand it over

    Your repository, your cloud accounts, your data, from the first commit. We can stay on for maintenance and on-call, or write the handover documentation and step back. Both are normal endings.

    You keep04 / 04

    The keys.

    • The code
    • The accounts
    • The docs

How every project ends

Something real has to move.And the record has to agree.

A lime cube taken from a white shelf, with one slot now empty, beside a linked panel that shows the same empty slot and the lime item.

Engagement models

Three ways to work with us

Communication

What a normal week looks like

Mon

Tue

Wed

Thu

Fri

DavFops

Plan in the channel

Build

Deploy + written update

Call, only if a decision needs one

You

One person who decides

Access and test data

An answer within two days

Click through the build

What we promise

Four lines in every contract.

Service agreement · extract

  1. The price is fixed before we build.
  2. You see working software every Friday.
  3. The code, data and accounts are yours from day one.
  4. You can leave at any point and take everything with you.

Limits

Things we will not do

  • We do not take on work we have not done before and learn on your budget. If it is new to us, we say so and price the risk down, or pass.
  • We do not staff a project with juniors after the sales call. The people on the call are the people building it.
  • We do not hold your infrastructure. Accounts, domains and repositories are yours from the first day.
  • We do not bill for a surprise. Scope changes are agreed in writing before they are worked on.

Your next move

Start with a discovery week

The smallest useful commitment. At the end you have a scope, a price and a date — and no obligation to spend either with us.

Discuss your project