Skip to content

How we work

Simple to start, easy to end

You pay for the weeks you use, and everything we build is yours.

From first call to handover

  1. 01

    Intro call

    Thirty minutes on your problem, constraints and timeline. No pitch deck.

  2. 02

    Scoped proposal

    Within three working days: the outcome, who works on it, how long, and the price.

  3. 03

    Kick-off

    The right engineers join your tools and your stand-ups, usually within two weeks.

  4. 04

    Delivery and handover

    Regular demos, written decisions, and a handover your team can run without us.

Four ways to engage

Skills join for the weeks they are needed. Mix models as the work changes.

Advisory retainer

A fixed number of hours each month with a named senior engineer. Cancel with 30 days notice.

Fixed-scope sprint

A set price for a defined outcome and end date. Easiest to approve and to compare.

Embedded squad

Two to five engineers working inside your roadmap and tools, month to month after an initial term.

Build and transfer

We build it, document it, and train or help hire the team that takes it over.

One quarter, five engagements. Each starts when needed and ends when done.

Weeks

Sprints with a price and an end date

The most common way to start. A defined outcome, a set price, and a date you can plan around.

  • Production-readiness review

    2 weeks

    A ranked list of risks with fixes sized and sequenced.

  • Cloud cost audit

    4 weeks

    Savings identified, the first ones already shipped.

  • Kafka or event-driven migration

    8 weeks

    A working pipeline in production and a team that can run it.

  • MVP build

    8 to 16 weeks

    A launched product, clean code and documentation, handed over.

Tell us what needs to exist by next quarter

Thirty minutes on your problem, constraints and timeline. A scoped proposal within three working days.