Skip to content
Process

Four stages, no surprises.

The same sequence whether the engagement runs six weeks or a year. Predictability is a feature.

  1. 01

    Technical discovery

    Week 1

    We read the code, trace the hot paths, and talk to the people who get called when it breaks. You get a written assessment of what is actually in the way — including the parts you did not ask about.

    You receive: Assessment + risk register

  2. 02

    Architecture & plan

    Week 2

    Target architecture, build sequence, delivery plan, and a fixed commercial shape. Enough detail to decide with your eyes open, and cheap enough to walk away from.

    You receive: Architecture notes + sequenced roadmap

  3. 03

    Build in increments

    Weeks 3–14

    Two-week increments, each deployed behind a flag and demonstrable in your environment. You see running software, not slides about running software.

    You receive: Deployed increments + CI

  4. 04

    Handover & support

    Ongoing

    Runbooks, architecture decision records, and a walkthrough with the engineers who will own it next. After launch we stay available on an agreed support window, sized to how much of it you want to run yourself.

    You receive: Runbooks + SLOs + support window

What we commit to.

Fixed scope, fixed price

The plan stage produces a number. That number does not move unless you change the scope, and we tell you what a change costs before it starts.

Your repo from commit one

Everything lands in your version control and your cloud accounts. There is no staging ground we control and you cannot see.

Weekly written updates

What shipped, what slipped, what we are worried about. In writing, every Friday, whether or not there is good news.

An exit that works

Runbooks, ADRs, and a pairing period. We consider the engagement successful when your team stops needing to call us.

Engagements

Tell us what is breaking.

Send the problem, not a polished brief. An engineer reads every enquiry and replies within two working days with a real technical opinion — including when the honest answer is that you do not need us.

Start a projectcorp@codeaex.com
  • Reply from an engineer, not a salesperson
  • Fixed scope and price before any build starts
  • Your code, your cloud, your repo — from day one