Skip to content
Moduloa
← Journal
MOD-01 · Field notes

The bottleneck was never the machines

Research

Isembard is the best-funded live attempt at a distributed, software-run manufacturing network. It has capital, it has its own factory operating system, and it says it is turning orders away. What it cannot get fast enough is people willing to own a shop and run it, so it franchises, and it grows by converting machine shops that already exist.

2026-08-29 · Field notes · 5 min read · By

One of the claims on this site's register, P-24, says that a certified production network scales by conversion rather than construction: you do not build the factories, you upgrade the ones already standing. It is a comfortable thing to assert in 2026 because nobody has had to do it. Someone is now doing it in public, at some speed, and the instructive part is not that it works. It is which input ran out first.

The position

Capital, software, and more orders than it can take

Where Isembard is

Isembard is a London company founded in 2024 that makes precision components for aerospace, defense and energy. It raised USD 9 million in April 2025 and USD 50 million in March 2026, led by Union Square Ventures, on a stated plan of 25 factories by the end of this year, with Germany, France and Ukraine named as the next countries. Its own software, MasonOS, runs quoting, scheduling, supply chain, production and quality across the network.

In an interview published on 10 August, founder Alexander Fitzgerald put the company at 14 factories across the United Kingdom, the United States, France and Germany, with 66 employees, and named Anduril, Tekever, ARX Robotics and the UK government among its customers. On growth he was direct: "Demand is outstripping supply at the moment, so we are having to turn down orders now."

Read that as an input list. Capital, present. Factory software, shipping. Demand, in excess. Every constraint the usual argument reaches for is satisfied, and the company is still supply-limited.

The answer

The missing input is operators

Who owns the nodes

Isembard's answer is a franchise, launched in October 2025 and, as far as we can establish, the first application of the model to precision manufacturing for critical industries. Franchisees can start a site from scratch or, in the company's own words on its franchise page, transform an existing machine shop. They get MasonOS, an order pipeline, financing pathways and support toward ITAR, AS9100D and ISO accreditation. Setup runs to roughly three months.

The people it recruited are the finding. The first franchised site, Exeter, opened in September 2025 under Shaun Rowcliffe, then 22, previously a machine operator at a large UK defense manufacturer. The first US franchisee is Jonathan Foster, near St Louis: a cardiac surgery nurse for more than a decade who left healthcare after the pandemic when his business partner Robbie Crider suggested opening a machine shop, taught himself machining, started on a single CNC machine, and later converted that shop into an Isembard site of about 3,800 square feet. The US arm is run from Dallas by Justin Baucum, a former Army Special Forces operator. Fitzgerald's own list of franchisees runs to a former restaurant franchisee, a nurse, an engineer, a veteran and an investor.

None of that is a story about robots or about software. It is a story about how many people exist who will sign a lease, carry the machines on their own balance sheet, and learn to hold a tolerance. That population is the growth rate. It is also the input nobody in this field models.

The counting problem

Count the machines, not the factories

Three surfaces, three numbers

Checked on 29 August 2026, Isembard's homepage counter reads 8 beside the word Factories. Its locations page lists 14 site cards. Its franchise post says the company operates four. Three of the company's own surfaces, three different figures. This is ordinary marketing drift rather than anything sinister, and it is exactly why a site count is a poor unit.

The locations page is more useful because it publishes machines. Portsmouth carries 30. The London and Carrollton headquarters carry 10 each. Swindon carries 4. Every other listed site carries 2. Fourteen sites, 74 machines, and more than two thirds of the capacity sitting in three of them. On that page, a converted two-machine shop and a 30-machine plant each count as one factory, which means reaching 25 sites and multiplying capacity are not the same achievement and can be reported with the same number.

Capacity is the thing being routed, so site counts are the wrong denominator, and they are the number the whole field publishes. Machines, spindle hours, or qualified process families would each tell you something. A count of buildings tells you how many leases were signed.

The register

What this bears on, and what it does not settle

P-24, P-27, P-14

P-24 predicts that the network scales by conversion, not construction. Foster's shop and Rowcliffe's site are the mechanism running in the wild, funded, and inside a demand pipeline. That is the closest thing to a live trial of the conversion premise that we have found, and it is worth saying that the premise is holding up better than the schedule around it: the 25-factory target has about four months left on it.

P-27 is where this gets uncomfortable, in a useful way. That claim asks for a certified production process demonstrated moving between standardized cells owned by two different organizations, before 30 June 2027. A franchise is a third case the wording does not anticipate. The balance sheet is genuinely independent, since Foster owns his machines, and nothing else is: the brand, the demand, the operating system and the engineering standards are all Isembard's. Support toward accreditation is also help in earning your own certificate, which is a different act from carrying a qualification across an ownership boundary. Nothing here resolves P-27 and this note does not score it. It does suggest the claim treats ownership as binary when the market is producing a middle term.

P-14 gets quieter support. It predicts a new profession, the robot-era production technologist, spanning machines, software, quality and data in one role. A nurse and a 22-year-old machine operator running accredited nodes on a shared factory OS is roughly what the early version of that job looks like, and it arrived through a franchise manual rather than a training program.

What to watch

Four checkable things

Tests, not opinions

Whether the count reaches 25 by 31 December 2026, and on which of the company's three definitions. Whether Isembard ever publishes capacity rather than sites, which would be the first honest denominator in this layer. Whether a qualification is ever shown moving between two franchisee-owned shops without a fresh audit at the receiving end. And whether MasonOS ever runs in a factory that does not sell under the Isembard name, because that, not the franchise, is the moment a factory operating system becomes infrastructure instead of a brand.

The larger lesson is cheap to state and expensive to ignore. This site's argument has always been that the moat is the framework rather than the robots. Isembard is a reminder that the framework has a human layer in it. Standards, data and certification still have to be carried by somebody who owns the building, and the supply of those people is finite, unglamorous, and currently setting the pace for the most capitalized attempt at this in Europe.

Sources

What this is built on

Discussion

Add to this

Corrections, evidence, and disagreement are welcome. This is knowledge in the open. Anyone can read; sign in with GitHub only to post or react, and it appears here instantly.

Field notes are research, not decisions. They are dated, sourced, and open to correction. Republish this in full or in part under CC BY 4.0, with credit and a link back. · All journal entries →
Ask Datum