MX.0 UK 2026 runs December 1-2 in Sheffield. Siemens, AstraZeneca and Gousto are on the agenda, talking digital transformation, AI-ready operations and in-house MES development. One session puts a number on the stakes: a single factory production stop can cost up to $2 million. If you sell into manufacturing, that number is your entire pitch.
Why this conference matters more than the badge count
Most manufacturing conferences are a trade-show floor with a keynote bolted on. MX.0 is different in one specific way: the speakers are operators, not vendors. Siemens sends people who run plants. AstraZeneca sends people who own the compliance layer. Gousto sends people who scale food production under margin pressure.
That matters because the buying committee for industrial software is small and senior. You are not selling to a manager who needs to build consensus over six weeks. You are selling to someone who has already been told to fix a line, cut a shift, or replace a legacy MES that nobody wants to touch.
The $2 million per halt figure is the useful part. It reframes every conversation. You are not selling software. You are selling avoided downtime, and the buyer already has a number in their head that is bigger than your annual contract.
What separates MX.0 from the usual industrial calendar is that each speaker represents a different failure mode, and each failure mode maps to a different sales motion. Siemens is the integration problem: brownfield sites, mixed-vintage equipment, and the political cost of ripping out a control layer that still works. AstraZeneca is the validation problem: every change to a regulated process carries documentation overhead, so the buyer is not asking whether your tool works but whether it survives an audit trail. Gousto is the throughput problem: perishable inventory, tight delivery windows, and a margin structure that punishes overproduction as hard as underproduction.
Read the agenda as a segmentation exercise rather than a content lineup. The compliance buyer at AstraZeneca will not sign off on the same proof you would send to a Gousto operations lead, and neither will respond to the downtime framing in the same way. The regulated buyer needs to see change control and traceability. The food-production buyer needs to see yield and waste reduction inside a single shift cycle. Siemens sits closer to the infrastructure layer, where the objection is rarely budget and almost always disruption risk.
For a small team, that is the practical takeaway. One conference, three distinct buyer profiles, three different opening lines. The badge count is irrelevant. The room is small enough that the right twenty conversations beat a booth and a swag budget.
The three buyer profiles you'll actually meet
We've run outbound into UK manufacturing for long enough to know the room splits roughly three ways. Each one needs a different email, and each one punishes the wrong pitch in a different way.
- The Siemens-shaped buyer. Large enterprise, long procurement, existing MES or SCADA stack. They are not replacing anything this quarter. They are looking for a wedge — a pilot, a single line, a proof point they can take to a group-level committee. Sell the pilot, not the platform. The mistake here is treating interest as intent. A warm reply from this buyer often means they are gathering options for a decision that will be made by people you will never meet, on a timeline you cannot influence. Your job is to make the pilot cheap to approve and easy to defend upward.
- The AstraZeneca-shaped buyer. Regulated, audit-heavy, terrified of anything that touches data lineage. They will ask about validation before they ask about features. If your product cannot survive a CSV or GxP conversation, do not waste the meeting. Note that this buyer rarely says no outright — they go quiet, because saying yes requires evidence you have not supplied. Come with a validation approach, a data-flow diagram, and a clear answer on where your system sits relative to their quality management framework. Anything less reads as risk.
- The Gousto-shaped buyer. High-volume, low-margin, fast-moving. They want throughput and they want it this quarter. They will tolerate rough edges if the ROI lands inside 90 days. This is where a solo founder can actually close. Their procurement is short, their decision-maker is often in the room, and their tolerance for a half-built product is higher than their tolerance for a slow one. Lead with the number, not the roadmap.
If you are a two-person team, ignore the first two and go hard at the third. The enterprise buyers at MX.0 are worth a conversation, not a pipeline. Treat them as intelligence-gathering: what they tell you about their constraints will sharpen the pitch that actually closes.
In-house MES development is the quiet signal
The agenda item that should make you sit up is in-house MES development. That is a phrase manufacturers use when they have given up on off-the-shelf and started building their own. It sounds like a threat to software vendors. It is actually the opposite.
Every company building its own MES has hit the wall where the internal team cannot keep up with the roadmap. They have a working prototype, a frustrated engineering lead, and a CFO asking why they are paying three salaries to maintain something a vendor could host. That is your opening.
What makes this signal durable rather than a one-off is the compliance layer underneath it. An in-house MES is rarely just a scheduling tool — it becomes the system of record for batch genealogy, deviation handling, and audit trails. The moment a manufacturer pursues certification or supplies a regulated customer, those workflows have to satisfy an external auditor, not just an internal operator. That is precisely where homegrown builds stall: the original developer understood the shop floor, but nobody scoped the validation and traceability requirements that arrive eighteen months later. The result is a system that works in production and fails in an audit, which is a far more urgent buying trigger than a missing feature.
It also explains who is actually in the room. A manufacturer still writing requirements documents is months from a decision and will treat any vendor conversation as research. A manufacturer already maintaining a half-finished internal build has sunk cost, a deadline, and an internal champion who now needs an exit that does not look like a retreat. That champion is the person to reach before the conference, not after.
We saw the same pattern in the factory downtime cost breakdown for MX.0 Sheffield — the buyers who show up to these sessions are the ones already mid-project, not the ones still writing requirements docs.
How to work the room without wasting the trip
Two days in Sheffield is not cheap once you add travel, hotel and the opportunity cost of not being on calls. Treat it like a pipeline sprint, not a networking event.
Before you go, pull the speaker list and the sponsor list. Cross-reference against your ICP. You will find maybe 15 names worth a real conversation. Build a one-line brief for each: what they run, what they said publicly in the last six months, and the single question you want to ask them.
At the event, skip the keynote Q&A. Stand near the coffee, not the stage. The best conversations happen in the ten minutes after a session ends, when the speaker is trying to leave and someone asks a specific question about their plant.
After the event, send the follow-up within 24 hours. Not a template. Reference the specific thing they said. If you cannot remember what they said, you did not listen hard enough.
One caveat: if you are running outbound to manufacturing buyers, your deliverability has to be clean before you send a single MX.0 follow-up. The DMARC changes Google and Microsoft pushed through hit industrial domains hard, and a bounced follow-up to a Siemens procurement lead is worse than no follow-up at all.
What we'd do with a ticket to MX.0
We would not try to sell on the floor. We would book three coffees, one dinner, and one follow-up call for the week after. That is a realistic return on two days.
The reason is structural, not temperamental. A room like MX.0 is built around panels and keynotes, which means the people worth meeting are on stage, in transit between sessions, or surrounded by vendors who all want the same ten minutes. The agenda itself tells you where the useful conversations sit. Siemens will be talking about automation and the integration of operational technology with IT — the kind of deployment where the buying committee spans engineering, security, and finance, and where nobody signs anything on the strength of a badge scan. AstraZeneca brings the regulated end of the spectrum: validated processes, audit trails, and change control that make procurement cycles long and reference checks decisive. Gousto represents the opposite pressure — high-volume, low-margin, consumer-facing manufacturing where the constraint is throughput and the tolerance for a bad integration is close to zero.
Those three contexts do not share a pitch. They share a shape of problem: a process owner who has already been burned by a tool that promised more than it delivered. That is why the pre-event list matters more than the event. We would build it around the specific operational pain each company has publicly signalled, not around job titles, and we would score for who is likely to be in the room versus who merely appears on the attendee app.
The rest of the pipeline comes from the list you build before you arrive. If you want to see how MiraReach handles the prospect scoring and the personalised first line for a room like this, give MiraReach a try. It will not book the meeting for you. It will make sure the email that gets you there does not sound like everyone else's.
— Mira