Edition Two — Bespoke operating systems

Your business has outgrown its software.

Edition Two designs, builds and evolves bespoke software and operating systems for established businesses.
You bring the operational problem — the spreadsheets, the workarounds, the person holding it together. We work out what the software should do, then build it and keep building it.

Not another app to add to the pile — the software your business would have designed for itself.

Show us your business See how it happens

A 30-minute call with the founder — pick a time that suits you. Nothing to prepare beyond bringing the person who knows how the operation works.

Edition OneOne order. Six systems. Sarah copies it between them.

Built for

Manufacturers, specialist distributors, healthcare groups, construction, logistics, multi-site operators. Established companies, typically £1m–£50m$1m–$50m in revenue.

And once it is built

AskAsk the business a question in plain words and get an answer from its own records.
CanvasAsk for the workspace your team needs, and have it made from the same records.
ConnectKeep every tool — portal, reports, AI — reading one shared understanding of the business.
See the three

Built in the real world

Three systems we actually built, for three established businesses: a healthcare clinic, a mid-market manufacturer and a seventeen-instructor driving school. Client names are withheld on this page. Read the work

Edition One

A typical company2011

Someone bought a CRM. Sales lives in it.

2014

Finance chose an accounting package. Sarah copies the invoice numbers from one to the other.

2016

A developer built a quoting tool. He left in 2019. Nobody else knows how it works.

2018

Operations started "the master spreadsheet". It now has 31 tabs and one person who understands it.

2020

The WhatsApp groups began; half the decisions now live in them. Then a second spreadsheet — to check the first one against the accounts.

2024

The monthly report is exported by hand. It takes two days.

Look at Sarah

Your people are doing work your software should be doing.

Copying. Checking another system. Remembering the rule. Updating the sheet. Messaging the driver. Reconciling two numbers that should have matched.

Edition Two

The copying, checking and chasing become software. Sarah goes back to running operations.

Nobody designed this. It accumulated.

Your business has become more sophisticated than the software running it.

Your software doesn't connect the business.
Your people do.

People shouldn't have to behave like APIs.

Edition One

Sales has one version of Mason Industrial. Finance has another. The ERP has a third. Sarah reconciles them.

Redesign

The ERP stays. Accounting keeps its books but shares the customer. The spreadsheets go. The rules Sarah used to remember are built into the system.

Edition Two

Now the quote, the order, the invoice and the history all belong to the same customer. One version of the truth.

That is what we mean by customer state: one record every system reads and writes.

The problem isn't that you need another piece of software.

It's that nobody ever designed the technological version of your company.

Edition Two

The deliberate redesign.

Your business shouldn't have to become more generic so your software can understand it.

What we actually build

We build the software your company is currently improvising.

Bespoke business software: the customer records, quoting, orders, jobs, stock, calls, invoices, portals and reports your people are running today through spreadsheets, inboxes and memory — designed as one system, around how your company actually works.

One example systemA specialist manufacturer. One customer, one order, one system — from the first call to the invoice, everyone sees the same customer. Yours would look different; that is the point.

What stays, what goes

The shape depends on the company. That is why nobody could sell it to you off the shelf.

ERP · orders and stock: Kept. It does its job; the new system reads and writes it.
Accounts package: Kept and connected. It keeps the books; it stops being where the customer lives.
Quoting tool · master spreadsheet · reconciliation sheet: Replaced. Quoting is rebuilt on the customer's real terms and stock; the checking by hand goes.
Customer record · orders · production · despatch · portal · rules: Built. One record every part of the operation reads, invoices connected to the orders they bill, the rules Sarah used to remember built in.

Off-the-shelf software begins with its own definition of a customer, an order or a job. Edition Two begins with yours. Every business has its own idea of what those things are — what belongs to them, what must never be lost, what should make a person act. Ours starts by writing that down: the things that matter to your company, how they relate, and what the system must know about each one. Engineers call this a data model, or an ontology. You can call it the shape of your business. It is the first thing we design and the last thing we compromise.

What a specialist manufacturer's system has to understand, for example:

Product: Grades, specifications, tolerances, finishes, variants — not "SKU".
Customer: Contract terms, price lists, rebates and what they usually order. Logic that differs by account.
Quoting: Built from real capacity, stock and lead times — often by phone, by someone who knows the customer.
Order: One order that knows its own state across production, despatch and invoicing.
History: Years of buying patterns, exceptions and complaints. Currently in people's heads.

A clinic's system has to understand patients, treatment plans and follow-ups instead; a driving school's, learners, instructors, postcodes and availability. The components — CRM, quoting, portals, operations platforms, job and inventory management, automation, reporting, AI agents, telephony, integrations, legacy modernisation — are chosen per business and designed as one thing.

How we work

You bring the problem. We work out the system with you — and you watch it take shape.

Who you work with

The founder and the senior engineers who build your system.

The people you speak to are the people doing the work — from the first conversation to the last chapter.

How it is organised

Ninety-day chapters, with the minimum deliverables agreed in writing at the start of each.

What you see

Working software from the first month, shipped every week — not a reveal at the end.

The Edition Two guarantee

If the agreed minimum isn't delivered by the end of a chapter, billing stops until it is.

What that makes possible

Once the business is properly connected, you can ask it, shape it and build on it.

The system holds the whole business as one connected set of records — customers, orders, quotes, stock, people, rules. That is what makes the three things below possible. None of them is a separate product; they are what your system can do once it exists.

One scenario, followed through

The manufacturer's owner asks which customers are quietly buying less. They look into one. They turn what they found into a workspace the sales team runs from — and because the workspace, the ERP and the customer portal all read the same business layer, an update in one reaches the others without anyone copying it.

01AskAsk the business a questionWhich customers are quietly buying less — and an answer traced to the records
02CanvasAsk for the workspace you needAn account-review workspace, made from the answer
03ConnectKeep everything reading one businessAn update reaches every surface without re-keying; a new tool joins in one step

The three demonstrations run on the example manufacturer, with invented records. What they show is what the systems we build do.

01 / 03AskIllustrative

What one model makes possibleAsk the business a question

Ask the business a question.

The question

A commercial question, asked in plain words.

Today: an export from the ERP, a spreadsheet, and an afternoon — if anyone thinks to ask at all.

What the system does

An answer you can trace back to the records.

“Buying less” is defined once, with you — then the answer is calculated from your own orders, invoices and quotes.

The answer

Six accounts. Which ones, by how much, and what is still open with them.

A calculated figure, not an estimate — and where to look next.

The investigation

Calder & Finch: a slower rhythm, not one late order.

Seven orders last year, four this year, the same size each time; the last was two months ago and a quote has sat unanswered for 27 days. Whether the volume went elsewhere or their demand fell, the records can't say — so the next step is a call, not a conclusion.

The answerIllustrative

6 accounts−£113k on the twelve months before · of 286 that ordered in both years

Account	Change	Orders	Owner
Calder & Finch	−41% −£34k	7 → 4	R. Cole
Okoro Fabrication	−28% −£17k	8 → 5	R. Cole
Vale Composites	−19% −£10k	6 → 6	M. Adeyemi
Brightwater Marine	−15% −£21k	4 → 3	M. Adeyemi
Pennine Tooling	−12% −£12k	4 → 4	J. Harris
Hartwell Engineering	−9% −£19k	4 → 4	J. Harris

How the system reads the question

“Buying less” is defined once, with you: among accounts that ordered in both of the last two years, invoiced value down by more than 5% on the twelve months before. That runs as a query against the records, so the figures are calculated, not estimated.

Look into it

Three follow-ups the owner might ask next. Each answer is drawn from the records beside it.

The last twelve months

18311bracket setJul£12,500
182403mm sheet · 40Apr£12,600
18140bracket setJan£12,000
179883mm sheet · 40Oct£12,500
4 orders£49,600

The twelve months before

17610bracket setSept 25£11,400
175883mm sheet · 40Aug 25£12,200
17415bracket setJun 25£11,700
172605mm sheet · 20Apr 25£11,800
171023mm sheet · 40Feb 25£12,600
16944bracket setDec 24£11,900
168103mm sheet · 40Oct 24£12,400
7 orders£84,000

Open quotes

Q-08623mm sheet · 40£12,80027 days open · no reply to two chasers

Account owner

R. Cole

What the evidence suggests

A decline in frequency, not one late order. Last year they ordered seven times, roughly every eight weeks; this year four times, roughly every thirteen weeks, at the same order size. The gap since their last order is unusual only against the old rhythm.

What stays uncertain

Whether the volume went to another supplier or their own demand fell. The open quote — Q-0862, 27 days without a reply to two chasers — is the only current signal, and silence is not a decision.

A sensible next step

R. Cole calls about Q-0862 and asks the question directly, before anyone treats the account as lost.

02 / 03CanvasIllustrative

What one model makes possibleAsk for the workspace you need

Ask for the workspace you need.

The request

A workspace that didn't exist a minute ago, asked for in a sentence.

The declining accounts, their order trend, the quotes still open, who owns each account, what to do this week.

What the system does

It makes the workspace from the same records.

The customers, orders and quotes the rest of the business runs on, with the same permissions. Save it; share it with the team.

The second request

Ask again, and it reorganises.

Grouped by account owner, each salesperson sees the accounts they should call this week. The expensive part of software was never the screen — it was making the screen true, and that part is done.

ACCOUNT REVIEW · BUYING LESSEXAMPLE WORKSPACE

Open an account to see the records behind its row. Group or filter the view; the records don't change, the surface does.

Account	Change	Orders	Open quotes	Owner	Follow-up
Calder & Finch	−41% −£34k	7 → 4	1 · £13k	R. Cole	Call about Q-0862 and ask directly
Okoro Fabrication	−28% −£17k	8 → 5	2 · £18k	R. Cole	Chase the two open quotes
Vale Composites	−19% −£10k	6 → 6	—	M. Adeyemi	Review the last three orders with them
Brightwater Marine	−15% −£21k	4 → 3	1 · £34k	M. Adeyemi	Confirm the September slot
Pennine Tooling	−12% −£12k	4 → 4	—	J. Harris	Price review due · contract renews in November
Hartwell Engineering	−9% −£19k	4 → 4	—	J. Harris	No action · within normal variation

03 / 03ConnectIllustrative

What one model makes possibleKeep everything reading one business

Keep everything reading one business.

Before

Every tool wired straight into every other.

ERP to CRM, CRM to the spreadsheet, the portal to whichever export someone could reach. Each link knows the mess underneath — and breaks when it changes.

What we build

One business layer, underneath everything.

The systems worth keeping connect into it once. The workspace, the customer portal, reporting and an AI assistant read from it. Nobody has to copy updates between them.

What that means

An update, seen where it matters.

An order is despatched in the ERP. The account-review workspace and the customer's portal show it — nobody re-keyed it, nobody had to be told.

What that protects

Change a system underneath. Add a tool on top.

The old CRM goes and the surfaces above carry on. A mobile app joins with one connection — to the layer, not to every system behind it.

01One connected business
02Answers
03Workspaces
04Every tool

In that order — each one is possible because of the one before it

Ask: a language model handles the question — what is being asked, which records it concerns, how to explain the result. The figures come from definitions we write down with you and your finance team: what counts as revenue, what a declining account is, what an order at risk is. Those definitions run as queries against the records, so a number in an answer is the same number the business reports, not a model's estimate. Where something has no definition yet, the system says so rather than guessing.

Canvas: a workspace is a view over the same records — the same customers, quotes and orders, with the same permissions — laid out for one team's job. Because the entities, relationships and rules already exist, most views, dashboards and many workflow surfaces can be generated and adapted quickly, then filtered, saved or shared. Not every feature is a view; a new process still needs designing. The claim is narrower and more useful: the truth underneath already exists, so the surface is cheap.

Connect: the business layer is a stable, versioned contract over the records — the entities, permissions, business rules and the integrations to the systems beneath. Portals, internal tools, reporting, AI agents and partner systems connect to the contract, not to the ERP or the CRM directly. When a system underneath is replaced, we change the mapping behind the contract; what sits above keeps working. It does not make integration free — each connection is designed, and a system without an API takes real work — but it stops every new tool relearning the history.

Real client work

Three businesses. Three systems we actually built.

Client names are withheld on this page; the companies, the systems and the outcomes are real. We will walk you through any of them in conversation.

01Healthcare clinicReal client · anonymised

The problem: The customer journey was split across systems — lead, enquiry, booking, appointment and case each started the patient again.
The system: Commercial operating system — first enquiry to completed case, one continuous patient record.
The outcome: +24% year-on-year growth

The clinic's commercial operation ran the length of the patient journey — lead, enquiry, conversation, booking, appointment, case — and each stage had its own tool, process or person. An enquiry wasn't one persistent record travelling through the clinic; it was a series of handoffs, with manual follow-up and context lost at every join.

Edition Two rebuilt the operating layer across the whole pathway: one system in which the clinic understands the same person continuously from first contact to treatment. Acquisition, conversation, appointment state and commercial progression became one connected model. The clinic subsequently grew around 24% year on year.

02Mid-market manufacturerReal client · anonymised

The problem: Management could not see the business as one coherent customer system — the history was there, the patterns were not visible.
The system: Customer & management system — the commercial history of every account, held as one evolving relationship.
The outcome: Management can see the company: declining accounts, stalled quotes, salesperson patterns, repeat behaviour.

An established manufacturer with customers, salespeople, operational processes and years of commercial history — held in systems that never joined into one model of the business. Questions that should have been easy were hard: where opportunities get stuck, which accounts are quietly declining, whether individual salespeople behave differently, what the company knows collectively that no single manager can see.

Edition Two rebuilt the operating system around a far richer idea of customer state: not a contact record with transactions attached, but an evolving representation of the relationship. Once every customer was held that way, patterns became visible across salespeople, customers, time and operations. Isolated anecdotes became management information. The system didn't digitise the operation; it made the operation legible.

0317-instructor driving schoolReal client · anonymised

The problem: The operating system was one person's head — every enquiry picked up, matched and booked by hand.
The system: Enquiry & allocation system — telephony built from the ground up, AI enquiry handling around the clock, the matching rules written down, one record per learner.
The outcome: No longer depends on one person: calls route themselves; the person manages exceptions.

One person answered every enquiry, worked out what the learner needed and where they were, knew which instructors could serve them and when, booked them, assigned them by hand and remembered what happened next. That person was the CRM, the call centre, the routing engine, the allocation algorithm and the institutional memory.

Edition Two rebuilt that logic as infrastructure: telephony built from the ground up, AI handling enquiries around the clock, the informal reasoning behind who gets which learner codified as assignment rules, a customer-state layer that knows where every learner is and what happens next — and the whole workflow connected. The knowledge that ran the company stopped being tribal and became infrastructure.

Records shown inside the three systems below — customer names, figures, postcodes — are illustrative. The clients, the systems and the outcomes are real.

Practical questions

The things people ask before they get in touch.

No. Sometimes it means keeping the ERP you have and building the missing system around it. Sometimes it means replacing the CRM with one that understands your customers properly. Sometimes it means connecting quoting, orders, telephony, a customer portal, reporting and AI into one piece of software. In the Design step we decide, with you, what should stay, what should connect, what should be replaced and what needs to be built.

AI is part of it, not the point. The language model handles the question — what is being asked, which parts of the model it concerns, how to explain the result. The numbers come from definitions we write down with you and your finance team and that run as queries against your own records, so a figure in an answer is the same figure the business reports. Where something has no definition yet, the system says so rather than guessing.

Who this is for

Not for everyone. Deliberately.

Manufacturers, specialist distributors, healthcare groups, construction, logistics, multi-site operators. Established companies, typically £1m–£50m$1m–$50m in revenue.

Edition Two tends to work when

Established company, not a startup
Operations more complicated than the software understands
Off-the-shelf gets you 80% of the way — and the 20% matters
You suspect there is a dramatically better way to run this

Probably not for you if

Shopify, HubSpot or Xero already solve it
You want the cheapest development resource
You know exactly what to build and need tickets executed

Every company has an operating system.

Most just didn't design theirs.

The first edition happened by accident. The second one doesn't have to.

Start here

Show us how your business works.

Show us the strange bits — the spreadsheets, the workarounds, the legacy software, the processes nobody has quite managed to fix. We'll tell you where we'd start.

Show us your business

A 30-minute call with the founder — pick a time that suits you. Nothing to prepare beyond bringing the person who knows how the operation works.

You'll speak directly with the founder. Bring whoever actually knows how the operation works — the person who runs the spreadsheet is usually more useful than the org chart.