LDN 51.5072° N
Recommendations
don't ship. Operators do.
Forward deployed engineering for maritime and B2B software. An operator in the room deciding what gets built, an engineering team that builds it, and something running in production when we leave.
DIAGNOSIS / 01
Activity is rising.
Decision quality isn't.
420 organisations were active in maritime AI last year, up from 276. The budget is committed. The distance between buying it and trusting it is the work.
The interface doesn't.
WHO / 02
You're not buying a method. You're hiring the operator who has run it.
Lucid is led by Leigh Steed-Middleton, a product and technology executive who rewires operating spines rather than tweaking products. Across five years at Sedna he put product, engineering, marketing and customer success under one system: recurring revenue grew 10× at roughly 58% CAGR, six acquisitions were integrated, and the customer base passed 700 organisations.
Structure where there's noise, velocity where there's friction, accountability where there's ambiguity. The operator you meet stays on the work. Behind them, a small engineering team — so the seat ships, rather than writing a plan somebody else has to resource.
Read the background ↗MODES / 03
Two modes. The second is what makes the first ship.
The same people who run the model, holding the keyboard.
We take the seat.
Fractional CPTO / COO — and we take the seat inside the work. Customer calls, the roadmap, the architecture, the hiring. What we decide, our engineers build.
Practice ↗We build the thing.
Some problems don't need advice. Lucid incubates and operates its own software, and takes build work where the product is the point rather than a deliverable. The same capacity sits behind the seat, which is why an engagement can end with something running — and why it costs what it does.
Evidence ↗| Mode | What we own | Shape | Status |
|---|---|---|---|
| Fractional CPTO | Product, engineering, architecture, technical hiring | Ongoing, part-week | OPEN |
| Fractional COO | Operating cadence, delivery, spend, cross-functional flow | Ongoing, part-week | OPEN |
| Operating review | Written assessment of the model, and the plan we then run | Fixed scope | OPEN |
| Build | Software designed, built and run by our team | Project or embedded | OPEN |
PROOF
“There is a noteworthy difference between simply connecting systems and confirmingTHETIUS & DANELEC · THE GREAT INTEGRATION · 2026
they actually support decision-making.”
Confirming it is the job we take.
METHOD / 04
How an engagement runs.
Four phases. The last one is the point — we're building something that keeps running without us.
FIT / 05
Who we work with.
What we install is written down. What we build is running.
An engagement leaves a record on purpose. The operating review, the decision log, the architecture position, the hiring plan — documents your board can read and your team can run from. Where we build, it leaves the software too: running in your estate, with the people who own it named. If it only lived in our heads, we didn't do the work.
EVIDENCE / 07
Six on the record: four engagements, and two products we build and own. Three live, three in build. We publish work at the point it's real, not at the point it's announced.
WRITING — THE PUBLICATION
Notes from inside the machine.
Operating models, product organisations, and the unglamorous mechanics of shipping software. Written by the operator doing the work, sent when there's something worth sending.
The one in progress is here for the same reason the ledger shows what is still building.
Forty-five minutes. Bring the constraint.
Tell us where the model is bending. We'll say what we'd do, and whether we're the right people to do it.