N 03 · Technical leadership
Platform Consulting .
For the decision you can't afford to get wrong. We research your case, weigh the options against real delivery experience, and hand you a report you can act on.
- First meeting
- ~1–5 days in
- Preliminary findings
- 1–2 weeks in
- You pay from
- Signing
- Full report
- 2–4 weeks
¶03 / The service
Judgement, in writing.
Some decisions are too expensive to guess: migrate or rebuild, which stack to bet on, build or buy. We dig into your case — codebase, team, constraints, market — and weigh the options against real delivery experience.
What you get is a recommendation with its reasoning shown: trade-offs costed, risks named, a phased roadmap attached. A report you can circulate, argue with, and act on — not a vague opinion in a slide deck.
Independent, then invested.
The recommendation is independent — we're not reverse-engineering it from a build we'd like to sell you. If off-the-shelf wins, the report says so.
But we don't vanish after the hand-off either. If the roadmap calls for building, we can build it; if your team takes it in-house, we stay a phone call away.
¶How it works
From first note to ∞
The process.
The research starts before the contract does. By the time anyone asks you to pay, you've already seen how we think.
Today
You contact us.
The decision on your desk, in a paragraph. Migrate or rebuild, this stack or that, build or buy — whatever fork you're standing at.
~1–5 days later
Meeting one — the question.
What hangs on the decision, the constraints around it, who needs convincing. Then we start the research — reading your code, your numbers, your market. Unpaid, on purpose.
1–2 weeks later
Meeting two — preliminary findings.
What we've learned so far and where it points, plus a proposal for the full engagement: scope, timeline, price. You see how we think before you spend anything.
A couple of days later
You decide.
Continue, and we go deep. Or keep the preliminary findings with our compliments and stop — you owe us nothing either way.
2–4 weeks
The report lands.
Options weighed with trade-offs and costs, a clear recommendation, a phased roadmap. Written to be argued with, precise enough to budget against — and presented to whoever needs convincing.
Afterwards, if you want
We help you execute.
Build it with you, embed engineers alongside your team, or hand over cleanly and stay a phone call away. The report stands on its own either way.
If the preliminary findings don't earn it —
don't sign. Keep them, use them, share them internally; no invoice follows. We'd rather lose an engagement than argue you into one — a report is only worth something if you trust the people who wrote it.
¶ — Your exact case
The overview ends here.
The specifics depend on you.
What you just read is the default shape. The decision on your desk, what's already on the table, who has to sign off — each answer bends the engagement.
The quiz takes two minutes and plays the engagement out for your exact case — what we'd research, how deep the report goes, and what you'd hold in hand at the end.
Two minutes — your answers are saved as you go, and we read them before we reply.
It asks about things like —
What decision are you facing?
Migrate or rebuild, stack choice, build versus buy — the question sets the research.
What's already on the table?
A legacy codebase, competing proposals, a deadline — what we weigh the options against.
Who needs convincing?
A board, a co-founder, your own engineers — it shapes the report and the walkthrough.
¶Fit
Who it's for.
- ◇
Leadership facing a fork in the road
Migrate or rebuild, monolith or services, this stack or that one. The wrong call costs years — you want the reasoning, not just an answer.
- ◇
CTOs choosing foundations
You're about to commit budget and headcount to a platform decision, and you want it stress-tested by people who've shipped on those foundations.
- ◇
Teams weighing build versus buy
Off-the-shelf covers 80% and the last 20% is your actual business. You need someone to draw that line honestly.
Probably not, if —
You already know what to build and need it built.
See Custom Web DevelopmentYou need hands in the codebase this month, not a report.
See Embedded EngineersYou want a rubber stamp on a decision already made. We'll tell you what we actually think — that's the product.
¶Case studies
In preparation
Case studies for this engagement are being prepared.
We work under NDA more often than not — happy to walk you through relevant examples on a call.
¶ — Next step
The first meeting
costs you nothing.
A short note is enough — we'll come back within one business day with specific questions and a couple of times that work.
Two minutes, a dozen questions — it makes the first meeting count.