What if you find we should not build it?

We tell you. About a third of our discoveries end with a recommendation to buy something off the shelf or do nothing. We charge fixed price so we can stay honest about that.

Do we own the deliverables?

Yes. The architecture, the plan, the SOW, all of it is yours. We have no IP claim and we encourage you to use it with any vendor.

Two to three people typically. A senior engineer or architect, a product or design lead, and an embedded subject matter expert if the domain calls for it.

ENGAGEMENT · DISCOVERY SPRINT

Two weeks to a plan you can actually execute.

Stakeholder interviews, a real architecture proposal, and a delivery plan you can hand to any vendor. You walk away with a plan even if you do not hire us.

Start a project See pricing

DURATION

Two weeks, fixed

PRICING

Fixed price

BEST FOR

When this is the right shape.

Boards that need a credible plan before approving a budget.
Teams that have a fuzzy brief and need it sharpened.
Anyone who has been burned by vendors quoting before they listened.
Founders pre Series A who want a 6 month plan, not just hand waving.

NOT FOR

When you should pick something else.

Projects where the requirements are already locked and you just need execution. Skip to fixed scope build.
Existing platforms where the question is operational, not strategic. Talk to us about an architecture audit instead.

WHAT YOU GET

Deliverables, in plain English.

01
Architecture proposal with diagrams, decisions, and trade offs noted.
02
Risk register with the three risks worth taking seriously now.
03
Milestone plan covering scope, sequence, and a realistic timeline.
04
Build versus buy assessment for any third party components.
05
Statement of Work ready for legal review or another vendor's bid.

HOW IT RUNS

The process, week by week.

1
Day 1 to 3: stakeholder interviews
We talk to product, engineering, ops, sales, and one customer if you can give us access. We listen more than we present.
2
Day 4 to 6: technical discovery
Code walk through (if it exists), architecture review, integration map, data flow review, and a security baseline.
3
Day 7 to 9: synthesis
Architecture proposal, milestone plan, risk register, and the call we recommend (build vs buy, rewrite vs strangler, in house vs vendor).
4
Day 10: delivery and review
Three hour readout with your team. Written SOW shared the same day. You leave with a plan, regardless of next step.

FAQ

Questions buyers ask first.

What if you find we should not build it?: We tell you. About a third of our discoveries end with a recommendation to buy something off the shelf or do nothing. We charge fixed price so we can stay honest about that.
Do we own the deliverables?: Yes. The architecture, the plan, the SOW, all of it is yours. We have no IP claim and we encourage you to use it with any vendor.
How big is the team?: Two to three people typically. A senior engineer or architect, a product or design lead, and an embedded subject matter expert if the domain calls for it.

OTHER ENGAGEMENT MODELS

EMBEDDED SQUAD

A senior team that joins your standup, not your inbox.

FIXED SCOPE BUILD

Defined scope, defined price, defined date.

LONG HAUL PARTNERSHIP

Year on year ownership of platforms that matter.

GET STARTED

Ready to kick off a discovery sprint? Let's talk.

A 30 minute scoping call. SOW within a week. First sprint inside a month, or your discovery is on us.

Book a scoping call See pricing