Sheet 05 / 07 · How we work

How an engagement runs, so you know what you’re buying.

Seven steps, from a free 30‑minute conversation to a handover you could walk away from. Read them before you call: they tell you what you’re buying, and whether it’s what you want.

Seven steps, start to finish

From a free conversation to a handover you could leave at, then a support plan only if you want one.

  1. Conversation

    30 minutes, free. What’s broken, what it’s costing you, and whether this is the right firm for it.

  2. Assessment

    A written audit of your current state: what exists, what’s wrong, what it would take. Credited against the build if you proceed.

  3. Proposal

    Fixed fee, fixed scope, a date, and the risks named rather than discovered later.

  4. Build

    A working preview from the first week. Weekly written updates. One consolidated round of feedback per milestone. Why both matter.

  5. Cutover

    Tested with live data before the switch, monitored after, with a documented rollback.

  6. Handover

    Code, accounts, credentials and documentation transferred to you. You could leave at this point and be fine. The exit terms.

  7. Ongoing

    A support plan, or nothing at all. Both are acceptable outcomes. See the monthly plans.

Two commitments

Both are about the build: what you see while it happens, and how your feedback reaches us.

A preview from week one, not a reveal at the end.

You see the real thing as it’s built. Problems surface while they’re still cheap.

Feedback consolidated per milestone.

Your comments are collected in one place, rather than arriving by text over several days. It is the single biggest factor in whether a fixed timeline holds, so we say it upfront: a shared expectation now, not a complaint later.

The exit terms, in full

Every engagement, at every price, includes all of it. None of it is an upsell.

Code
The complete source code, in a repository you own.
Accounts
Every account — hosting, database, domain, email — in your own name from day one.
Data
All content and data in standard, portable formats.
Documentation
Written documentation of how the system is built, deployed and maintained.
Transition
Thirty days of transition support at no charge if you ever leave, including working directly with whoever takes over.
  • No exit fee.
  • No data-release charge.
  • No notice period beyond the 30 days on a support plan.

Monthly plans attached to a build start with a 12‑month initial term, then run month-to-month with 30 days’ notice. See the monthly plans.

The day-one test

If we disappeared tomorrow, could someone else keep your systems running?

That has to be yes on day one — and the documentation exists to make sure it is.

It’s why the handover transfers code, accounts, credentials and documentation to you, and why you could leave at that point and be fine.

Step 01 is a free 30‑minute conversation.

What’s broken, what it’s costing you, and whether this is the right firm for it. If it is, step 02 is a written assessment, credited against the build if you proceed.

Book the conversation