Services — Forward-deployed engineering

A forward-deployed engineer, not an agency.

The term is military: a unit stationed on the front line rather than back at headquarters. Applied to engineering it means the same thing. We work inside your systems, with your data and your constraints, instead of advising from a safe distance — then build it with the people who will live with it.

01 — Three jobs, one person

Not a client portal

The work splits three ways, and a larger firm would put a different person in each seat. Something is lost at every handoff between them, so here they are the same person.

  • The consultant

    Find the real problem

    Earn enough trust that people tell you what is actually wrong. It is rarely what the brief says, and you cannot get to it in a procurement meeting.

  • The product manager

    Decide what is worth building

    Separate signal from noise and cut the rest. Most of the value in an engagement sits in what does not get built.

  • The engineer

    Build it and ship it

    Hands on keyboard, in your repository, against your real data. The person in the first meeting is the person writing the code.

How that works in practice

  • We work in your tools

    Your Slack, your board, your repository. You see the work as it happens rather than in a fortnightly status call.

  • We talk to the people doing the job

    Warehouse staff, support, ops. The person who knows why the spreadsheet has a hidden column usually knows where the problem is.

  • Handover starts in week one

    Code in your accounts, documentation as we go, your engineers in the pull requests. There's no cliff at the end because there's nothing left to hand over.

02 — What we've built

Client names under NDA

Agentic supply chain

Agentic supply chain management

A supply chain management platform built from scratch. Client under NDA.

Label generation platform

Carrier APIs · backend integration

Shipping label generation built from the ground up, wired into carrier APIs and existing backend systems.

Some of the work is under NDA and some of it is infrastructure nobody outside the business would recognise. If you want to know whether we've solved something like your problem before, ask directly and we'll tell you what we're allowed to.

All 6 engagements

03 — Where we're useful

First store to full stack

  • Systems that don't talk

    Carrier APIs, ERPs, POS, warehouse systems. The integration work nobody wants to own.

  • Operations held together by memory

    The process that works because one person remembers it. Turned into software before they leave.

  • AI that has to survive production

    Putting AI into a business that already works. Different problem from building an AI product, and a harder one.

  • Marketplace and channel integration

    Mirakl, Linnworks, ShipStation. Getting your own site and the channels you sell through to agree on stock.

  • Custom platforms

    When nothing off the shelf fits the way you actually work, and bending your business to the software costs more.

  • E-commerce and storefronts

    Shopify through to fully custom. A first store, or a fifth replatform that has to go right.

04 — This isn't for you if

Better to find out here than three weeks in.

  1. You want a fixed spec built to the letter

    We'll question it. That's the job you're paying for.

  2. You need six people starting Monday

    We're small on purpose. Scale is the one thing we can't sell you.

  3. The decision is already made

    If you want hands rather than judgement, there are cheaper hands.

  4. We can't reach the people doing the work

    Embedding is the method. Without access it's just guessing at a distance.

Tell us the case. We'll tell you if it's ours.

Discovery is free — you get a written proposal either way