< Applications open — three slots remaining >
Help us build the thing you actually need.
We take on a small number of design partners each year. You bring a real operational problem, real assets and honest feedback. We build against it, and you get the result before anyone else does.
< The trade >
This only works if it goes both ways.
A design partnership is not a discount and it is not a pilot with better branding. It is a working arrangement with obligations on both sides, and it is worth being blunt about what those are.
What you get
What we ask
- Direct influence over the roadmap. Your problem shapes what gets built, in what order.
Access to real assets and real operational data. Sanitised is fine, synthetic is not.
- Early access to capability before general release, and to features built specifically for your case.
Time from people who know the work. Usually a technical lead and an operational lead, a few hours a month.
- Preferential commercial terms, held for the life of the partnership.
Honest feedback, including when something does not work. Polite feedback is worse than useless.
- Named involvement in the resulting capability, if you want it. Some partners do, some do not.
Willingness to be a reference for other operators once the work stands up.
< Current partners >
Two live. Both building something that did not exist before.
Each partnership is anchored to one capability area. What gets built for them becomes part of the platform for everyone.
< Live / Asset inspection >
EKSS
Working with us on inspection at scale, and specifically on the problem of turning a capture into a finding an engineer will act on rather than a folder someone has to review.
The work has shaped how MAYNE handles defect location, scoring and comparison between inspection cycles. Much of what is now standard in the inspection workflow started as a requirement from this partnership.
< Live / Continuous monitoring >
Offshore Windfarm Operator
Working with us on persistent monitoring of remote and offshore assets, where the cost and weather-dependency of sending people is the constraint that shapes everything else.
The partnership has driven how MAYNE handles baselines, thresholds and alert confidence, and the principle that an alert nobody trusts gets muted within a month.
< Open now >
Three slots for the coming year.
We keep the number small deliberately. A design partnership only works if the engineering team can give it real attention, and that does not scale.
< Slot 01 / Open >
Survey and mapping
An operator with a large linear estate and a survey programme that is not producing comparable data year to year. Rail, water, highways or utilities.
< Slot 02 / Open >
Detection and tracking
A site or estate with a persistent unauthorised access or incursion problem, and the appetite to treat it as a data problem rather than a fence problem.
< Slot 03 / Open >
Open brief
Something we have not thought of. If you hold assets, have a problem you cannot currently solve, and can articulate why existing tools fail, we want to hear it.
< How It Works >
Four stages, about twelve weeks to first output.
No procurement cycle, no discovery phase that produces a deck. The first thing you see is working software running on your own data.
Apply
A short form and a conversation. We are looking for the problem, not a specification. If you already know exactly what you want built, you probably want a supplier rather than a partner.
Week 0
Scope
A working session with our engineering and operations teams. We agree what success looks like, what data is available, and what we are each committing.
Weeks 1–2
Build
We build against your problem with your people in the loop. Fortnightly reviews, working software rather than progress decks.
Weeks 3–12
Run
The capability goes into service on your assets. The partnership continues, and what was built for you becomes part of the platform for everyone.
Ongoing
< Who this suits >
Be honest with yourself before applying.
A good fit
Not a good fit
- You own or operate assets and carry the consequence when they fail
You are procuring on a fixed specification against a fixed date
- You have a problem your current tools do not solve
You want a discount on something that already exists
- You can commit named people, not just a budget line
The only person available is a procurement contact
- You can share real data, even if it needs sanitising first
Data access is not achievable within the timescale
- You are comfortable being early, including the parts that are rough
You need production-grade certainty from day one
The ones people ask before applying.
Need more information? Reach out to discuss your specific situation.
Does it cost anything?
Who owns what gets built?
Do we have to be named publicly?
What if it does not work?
How many do you take on?
Can defence organisations apply?
Tell us what you cannot
currently solve.
Not a specification, not a tender. The problem, in your own words, and why the tools you have do not deal with it.