What we build

Seven services, on the same practices.

What each one is, what it takes, and what you keep. Every service has its own page with the method, the deliverables and the questions buyers ask.

  1. We know what we want to build. We are less sure anyone needs it.

    Product discovery

    Jobs to be done, story mapping, and a scope you can defend.

    The most expensive software is the software nobody needed. We find the smallest release that proves the idea, map every step of the job it replaces, and write down what stays out and why, so the first version ships in weeks and teaches you something.

    Length
    Two weeks to start
    Price
    Fixed, known before we start
    You leave with
    A story map and a written first release
    Afterwards
    Discovery runs alongside every release
  2. Every release is a weekend nobody wants to work.

    Web development

    React and Node platforms built for continuous delivery from the first commit.

    Web platforms that deploy on demand, with tests that catch real bugs, architecture that tells the next engineer where things belong, and a code health score at every milestone. Fast now, and still fast in year three.

    Stack
    React, Next.js, Node and TypeScript
    First release
    Weeks, not months
    Measured by
    Code health score and DORA metrics
    Deploys
    On demand, in your cloud
  3. The app is always a release behind the website.

    Mobile development

    Native iOS and Android, one codebase where it makes sense.

    Mobile apps on the same continuous delivery pipeline as the web, with crash and performance monitoring from launch day, and the same views your web users get, in the hand of a plant head or a house hunter.

    Default
    React Native, native where a feature needs it
    Fixes
    Over the air, within the hour
    Store accounts
    Yours, from the first build
    Existing apps
    Diagnosed and stabilised first
  4. The old system makes the money, so we cannot switch it off.

    Legacy modernisation

    Rebuild without stopping the business.

    A legacy platform is usually the one making the money, so it cannot pause. We lock the current behaviour with tests, replace it in small verified cycles, and keep the old system serving users until the new one is proven, with the health score showing the improvement sprint by sprint.

    Starts with
    A diagnosis on read only access
    Rewrite or refactor
    The diagnosis decides
    Your roadmap
    Features keep shipping, no freeze
    Progress
    Before and after scores, sprint by sprint
  5. We find out about outages from our customers.

    Platform and DevOps

    CI/CD, observability and infrastructure that is ready for the day the traffic arrives.

    Pipelines with quality gates, monitoring that wakes someone up before a customer notices, and infrastructure built for the peak rather than the average. Open source first, so you own it and can run it.

    Clouds
    AWS, GCP, Azure or on premise
    Measured by
    DORA metrics
    Handover
    Runbooks your team can take over
    Existing pipelines
    Diagnosed, then fixed
  6. Our developers ship faster with Cursor, and we break more than we used to.

    AI-assisted delivery

    AI is already writing your code. This is the gate it writes inside.

    Google’s DORA study of AI-assisted teams found the pattern: throughput up, stability down. Code arrives faster than review, testing and deployment can absorb it. The roadmap moves and the release calendar slips in the same quarter. We put the gates in first, then roll the tools out behind them, so your team keeps the speed and you get the evidence that the code still holds.

    Length
    Six to twelve weeks
    Format
    Pairing on real tickets, not training
    Baseline
    Your four DORA numbers, before and after
    We step back
    When the numbers hold without us
  7. AI made our developers faster. It did not make the code better.

    Practices coaching

    Coaching your engineers in TDD and continuous delivery until they run it.

    AI makes every developer faster at producing code. It does not make the code better. This is for a team that does not have the practices underneath yet. We pair with your engineers on your codebase, set up the delivery platform on your repositories, and leave when the health score and DORA metrics are yours to hold.

    Format
    Pairing on real work, not training
    Our side
    One to three engineers
    Length
    Typically two to three quarters
    Step back
    When the metrics hold without us

How an engagement starts

With a number, not a proposal.

Whichever service you need, the first step is a measurement.

  1. 01

    A diagnosis in thirty minutes

    Connect your repository, read only. You get a code health score, DORA metrics and a ranked list of what is slowing delivery. No agents to install, no changes to your code.

  2. 02

    Or a discovery sprint

    For a new product: two weeks to map the jobs, the story map and the thinnest first release, with a written scope you can take to your board.

  3. 03

    Then the team you need

    From two engineers coaching your team to a full product team that owns discovery and delivery. Every tier runs on the same platform and reports the same numbers.

Whichever way in, you own the code, the tests, the pipeline and the documentation, and we hand over when your team is ready to run it.

Held every day since 2012

Six practices under every service.

AI makes every developer faster at producing code. These are what make the code worth keeping, and our delivery platform scores the codebase against them after every push.

The practices in full
  • Test driven development

    The test first, then just enough code to pass it. A mistake is caught in seconds, not three weeks later in production.

  • Clean architecture

    Business logic at the centre, infrastructure at the edges. The next engineer, and the next AI agent, knows where things belong.

  • Small batches

    One scenario, one change, one commit. The blast radius of any mistake stays small, and the feedback comes back the same day.

  • Specifications first

    Acceptance criteria readable by the people who asked for the feature, agreed before the code, checked after it.

  • Continuous delivery

    A pipeline with quality gates, and releases that happen when a change is ready rather than on a date.

  • DORA metrics

    Lead time, deployment frequency, change failure rate and time to restore, reported at every milestone.

Ways to work with us

Pick the shape that fits.

The practices, the delivery platform and the numbers reported to you stay the same whichever you choose.

  • Dedicated engineers

    Team extension · time and materials, monthly

    Our engineers join your team on your backlog from the first week, and bring the practices with them.

  • Project delivery

    Fixed scope · fixed price per milestone

    A defined build with a written scope. Discovery first, then milestones with working software and a score at each.

  • Dedicated product team

    Managed team · monthly retainer

    A full team that owns discovery and delivery end to end. You set the outcomes and see the numbers.

  • Practices coaching

    Coaching · time boxed

    We pair with your engineers on your codebase and step back when the numbers hold without us.

Questions

What buyers ask us first.

Product discovery

We already know what we want to build.
Then discovery is short and it confirms the scope, ranks the risks, and gets the analytics in place. It rarely takes the full two weeks in that case.More on product discovery

Web development

What is a code health score?
A score out of ten across architecture, complexity, maintainability and test effectiveness, measured by our platform after every push. You see the same number we do.More on web development

Mobile development

Can you take over our existing app?
Yes. We start with a diagnosis, stabilise the release process, and ship the next feature before touching anything structural.More on mobile development

Legacy modernisation

Rewrite or refactor?
The diagnosis decides. Most systems are better refactored in place with a safety net; a few are cheaper to replace. We show you the numbers and say which.More on legacy modernisation

Platform and DevOps

Can you fix a pipeline someone else built?
Yes. A diagnosis of the pipeline is part of the thirty minute repository diagnosis. Slow, flaky or gate free pipelines are the most common finding.More on platform and DevOps

Practices coaching

Our developers already use AI tools. Why do we need this?
Because AI amplifies whatever is already there. With discipline it makes a team faster; without it the codebase degrades faster than review can keep up. Enablement is the discipline part.More on practices coaching

What clients say

In their words.

01 / 04

Life Insurance Direct
Before Metricsense, checking calls was a manual process: we selected files for review. Now the platform analyses every call, and we review by risk. It has identified customer experiences we would not have picked up before, and it lets us scale our quality assurance program without increasing headcount, with our team still the human in the loop. It helps us protect our customers, our business and our agents.

Russell Cain

Founder and CEO, Life Insurance Direct

Start with a diagnosis

Connect your repository and see your code health score in thirty minutes.

Read only access, no agents to install, no changes to your code. Or tell us about the product you need built.

See AI engineering