Blueforge

Four stages, in the same order every time.

The names come from the forge, and the work is plain engineering. Each stage ends with something you can inspect before the next one starts.

  1. 1

    Assay

    A smith tests the metal before it goes near the fire.

    We examine what you have: systems, data, team and constraints.

    Two to four weeks on site and in your systems. We read the code, query the data and talk to the people who use it. You get a written assessment and a fixed-scope plan. If the plan is 'don't build this', we say that.

    You receive

    • Written assessment
    • Architecture proposal
    • Fixed-scope plan and budget

  2. 2

    Forge

    Heat and hammer. The shape gets made here.

    We build in two-week increments, with a working release at the end of each one.

    Your team sees a working release every two weeks, in an environment that mirrors production. Every trade-off goes into the decision log as it is made.

    You receive

    • Working release every two weeks
    • Test suite that grows with the code
    • Decision log

  3. 3

    Temper

    Hardened steel is brittle. Tempering is what makes it tough.

    We harden the system before launch: load, security, failure and recovery.

    It's the easiest stage to cut when a deadline is close, and we don't cut it. We load-test, run a security review, break things on purpose and rehearse the recovery. Launch happens when the system passes, and the pass criteria are agreed in advance.

    You receive

    • Load and failure test results
    • Security review
    • Runbooks and rehearsed recovery

  4. 4

    Service

    A good tool gets maintained. It stays in use for decades.

    We run and maintain what we built, or hand it to your team with everything they need.

    Choose a service agreement with agreed response times, or a full handover. Either way the code, the accounts and the documentation are yours from the first day.

    You receive

    • Service agreement or full handover
    • Monitoring and monthly health report
    • Quarterly improvement plan

Bring us the system you can't afford to get wrong.

Talk to an engineer

30 minutes. Bring the problem, and we'll tell you whether we're the right shop for it.