How an engagement runs

A written trail from discovery through support.

  1. Discovery

    We map the system, users, constraints, risks and what “done” means commercially — not just technically.

  2. Planning

    Scope, architecture, milestones, environments and support assumptions become a written proposal you can challenge.

  3. Design

    Flows, data shapes and interface decisions are settled early enough that build work does not invent them mid-sprint.

  4. Development

    We build in your repositories with reviews, environments and the operational hooks the system will need in production.

  5. Testing

    Functionality, regressions and release checks happen before traffic — including restore and deploy rehearsals where they matter.

  6. Deployment

    Launch includes monitoring, backups, certificates and an escalation path already agreed — not bolted on afterwards.

  7. Support

    We stay on for incidents, improvements and monthly written reporting under the coverage window you contracted.

Before you commit

What your proposal will define

We do not publish fixed prices. Risk, traffic, infrastructure and support needs differ every time, so the commercial and technical terms are written down before any work starts.

Timeline and milestones
Phase dates, what lands in each milestone, and what must be true before the next phase begins.
Architecture
How the system is structured, where it runs, and which decisions are deliberate versus open.
Deliverables
Source, environments, documentation, runbooks and anything else you receive at each stage.
Cost breakdown
What is in scope, what is out of scope, and how change requests are priced — without surprise retainers hiding in the fine print.
Deployment plan
How releases happen, how they roll back, and what is monitored from day one.
Support and coverage
The hours your support actually covers, acknowledgement expectations, and who it escalates to.
Ownership
Whose accounts hold infrastructure and credentials. Our default is that you own both.
Reporting and exit
Written summaries on an agreed cadence, and what handover looks like if you take the work elsewhere.