No shape yet
A product worth building, but no architecture, no roadmap, and no honest read on whether the first version is buildable in the time you have.
From a raw idea, a service delivered by hand, or a system that has drifted, to a concrete, buildable plan with the hard choices made on the page. Product and service design, feasibility, architecture, and roadmap, read through an operator’s lens rather than an investor’s. Shape works as a project of its own and as the first half of a Build. The hand-off point is clean: ready to build.
You have an idea worth building, or a system that has drifted far enough that nobody can say what it should do next. The team can ship, but the shape is missing: which architecture, which sequence, which trade-offs you are actually signing up for. Without that, you either over-build for problems you do not have, or you pour months into a direction you will have to undo.
A product worth building, but no architecture, no roadmap, and no honest read on whether the first version is buildable in the time you have.
Something your team delivers manually today, a consultation, an inspection, a membership, that could reach many more customers as a digital product, with no clear picture yet of what that product is.
Something that grew feature by feature until the original design no longer holds, and every change costs more than it should.
A decision big enough that getting it wrong sets you back a year. You need the trade-offs laid out, not a vendor’s pitch.
An honest read on whether the idea survives contact with reality: the technical risks, the unknowns worth de-risking first, and the rough cost in time and people. If the answer is no, you hear it now, not after the build.
The system laid out: components, boundaries, data, the build-vs-buy calls, the failure modes. For a system that has drifted, a review of where it will help you and where it will hurt, with a migration path that does not stop the world.
We map how the service works today and how it should work, who does what, and what the product has to carry. Scope is cut to a first version that earns its keep. A roadmap then sequences the work so the risky parts come early and the team is never blocked waiting on a decision.
An operator’s read, not a verdict for a buyer: what to do about the product in front of you, written to be built from rather than filed.
A Software-as-a-Medical-Device platform taken from concept to a buildable system, where the architecture carried the EU MDR, IEC 62304, and ISO 13485 burden from day one rather than having it bolted on later.
Decades-old flower-auction trading flows turned into a concrete plan for a modern multi-sided marketplace, then built. Product strategy and platform architecture, with McKinsey Design.
A checkout-free convenience-store concept for Albert Heijn, scoped from idea into a working digital-store experience that became a public Ahold Delhaize launch. With McKinsey Design.
€8,000-15,000
One to two weeks. We test your idea or service with the people who would use it, then write down the concept, the architecture, and a roadmap. If a product already exists, a Diagnostic from €6,000 reads it instead.
€18,000-28,000
Two to three weeks, one defined deliverable: an architecture and migration plan, a de-risking spike or proof of concept, or a scoped roadmap ready to hand to the team.
All figures are indicative, net of VAT, and scoped per engagement. A bigger build is scoped from the Shape work that precedes it. See the full engagement model →
A short call to figure out what would actually help, and whether a Shape phase or a Diagnostic is the right first step. If it isn’t, we’ll say so.