RADICALROADMAP

We design and build custom software, automations and AI implementations.

scroll

What we build

What you need, when you need it.

  1. 01

    Custom software

    Applications built around how the business actually works, instead of a business reshaped to fit software somebody else designed.

  2. 02

    Automation

    The repetitive work that quietly eats hours every week: data moving between systems, reports assembled by hand, the same message sent for the hundredth time.

  3. 03

    AI implementation

    Used where it genuinely streamlines a workflow, and deliberately left out where it does not. The measure is fewer manual steps, not more technology.

  4. 04

    Technical consultation

    Sometimes you don't need a project, you need an experienced pair of hands for a few weeks. We'll sit with your team, work out the architecture, or take the thing that's stuck off your plate.

Complexity

You bring the problem. We deliver something simple.

Most of the difficulty in a business is not that anything is missing. It's the fact that the work is scattered across tools, inboxes, and in people's heads, with no single source of truth.

Approach

We work out the problem before we quote the solution.

Before we build anything, we get to know the problem and the people who have it — how the work runs today, where it breaks down, and what the people on the other end of it actually need. Understood properly, most problems turn out to be narrower than they first appear. That is what lets us build the right thing instead of the large thing.

EngagementNorthwind Logistics12 weeks
  1. Discovery
  2. Research
  3. Requirements
  4. Prototype
  5. Refine
  6. Deliver
Discoveryweek 1Nine interviews, four sites, no slides
Orders arrive by emailthree people re-key themPricing lives in a spreadsheetone copy per branchNobody owns the exceptionsthey queue up quietlyMonth-end takes four daysthe real cost
Ops, finance, and the two people doing it
Researchweeks 2–3We go and count it
Hours lost each week, by step
  • 61%of order handling time is re-entry
  • 2systems disagree on price
  • 1 in 9orders needs a human call
Requirementsweek 4Agreed before anything is built
  • Read orders from email and attachmentsmust
  • One price list, one source of truthmust
  • Hold anything priced over the POmust
  • Write back to the ledger nightlyshould
  • Branch-level reportinglater
Signed offops and finance, togetheragreed
Prototypeweeks 5–7In their hands in week five
Refineweeks 8–10Three rounds, two weeks apart
  • “Show the held ones first”done
  • “We price by branch, not by region”done
  • “Email me the exceptions at seven”done
r1r2r3Nothing shipped that they had not used
DeliveredliveWeek 12
4 dayssaved every month-end
98.6%of orders handled without a person
1price list, everywhere
Handover, documentation, and a team that runs itshipped
  1. 01

    Understand your problem

    A short call about how the work runs today, where it stalls, and what it costs you when it does.

  2. 02

    Research before building

    For a product you intend to sell, that means market and competitive research first, so the thing that gets built has somewhere to land.

  3. 03

    Design for outcomes

    We size the build against what it actually saves or earns. If that number does not work, we say so.

  4. 04

    Build in the open

    You see working software early and often, and you talk to the people building it, start to finish.

Platforms

Software on any screen or device.

We have spent years designing for every size of screen, from a phone held in one hand to a monitor on a desk. Each platform has its own conventions, and we know them well enough to build something that belongs there — a genuinely native experience rather than one layout stretched to fit.

Northwind Operations
Overview
Open jobs24
This week£18.2k
Held3
Throughput
QueueSite surveyTuesdayParts orderawaitingInvoice 4471heldCallbackThursday

Who we are

You'll work directly with us.

Lane Fries

Product engineering

10 years across billing and payments, messaging and automation, and shipping native apps end to end. Built the invoicing, payments and automated messaging that a field service company now runs on, from an empty repository to the software its customers use every day.

LinkedIn

Eric Swann

Architecture and AI strategy

30 years across financial services, developer tooling and open source. Principal engineer leading a six-engineer team, author of open-source developer tooling, and the person who built a company's AI engineering strategy from evaluation through to production.

LinkedIn

Jason Moore

Product and creative direction

20 years running product and design teams, taking software from an idea to a business. The research and positioning work that decides what is worth building at all.

LinkedIn

Start with the problem.

A short call about the actual problem is enough to start.

Start a project