All Services
Pre-Development · Marketplace Strategy & Planning

Marketplace strategy that survives contact with users.

Before a single line of code, we pressure-test your marketplace idea against the two-sided economics, the supply story, and the wedge. Two to three weeks of structured discovery, validation, branding, and prototyping , so the marketplace you build is the one worth building.

See the Full Process
Why Pre-Development Exists

Marketplaces fail at the planning stage, not the coding stage.

A marketplace is not a product with users. It is two products with two sets of users, who need to find each other, trust each other, and exchange value, usually money. Get the wedge wrong and no amount of code will save you. Get it right and the build becomes a known problem with known answers.

01

Supply comes before demand.

If your supply side will not show up reliably and at margin, the marketplace does not exist. We model this first, with you, on a whiteboard, well before launch.

02

The wedge is rarely what founders think.

"Etsy for X" is a category, not a wedge. We help you find the specific use case, geography, and behaviour where you can win in the first ninety days.

03

The cheapest code is the code you do not write.

Every Pre-Development sprint cuts the build scope by twenty to forty percent. That is weeks of timeline and tens of thousands of dollars you keep.

What Is Included

Four deliverables that decide whether your marketplace is worth building.

Each one stands alone. Together they replace the first three months of guessing.

01

Marketplace Strategy

Define the foundation: core model, target users, value proposition, and the realistic path from cold-start to liquidity.

We map your marketplace against the four critical questions every two-sided platform must answer before code is written. Who is the constrained side, supply or demand? What is the unit economic that has to work? Where does the cold-start break, and how do we get past it? What does the same user do twelve months later that makes the platform compound?

Key deliverables
  • Marketplace strategy document: the operating thesis, written down
  • Monetization model and unit-economics forecast
  • Cold-start plan with named first-twenty supply
  • Competitive analysis and positioning summary
  • Wedge brief: who, where, behaviour, why now
02

Branding & Design

Build a brand both sides of your marketplace can trust on first visit.

Marketplace branding is not consumer branding. Both sides have to feel safe transacting through you, and the visual system has to do that work without a single line of marketing copy. We run a collaborative brand sprint, then ship a working landing page and design system you can use for fundraising, hiring, and supply outreach immediately.

Key deliverables
  • Collaborative brand exploration and brainstorming sprint
  • Two to three branded landing-page directions
  • Finalized landing page with conversion analytics wired in
  • Logo files, type system, color tokens, base components
  • Brand guidelines document: short, opinionated, and useful
03

Mocks & Prototyping

See the marketplace in motion before development begins.

A real interactive prototype lets you watch users hit your core flow before a single backend route exists. We wireframe the supply onboarding, the search-and-match path, the booking or transaction flow, and the post-transaction loop. Then we click through with five real users, change what we learned, and only then commit to the build.

Key deliverables
  • Wireframes for the four core marketplace flows
  • Interactive prototype in Figma or equivalent
  • Five-user usability test with synthesized findings
  • Annotated edits and a build-ready mock set
  • A documented list of what we cut and why
04

User Journey Mapping

Understand both sides of your marketplace as the same map, not two disconnected funnels.

Most journey maps stop at "user signs up." Marketplace journeys do not. We map supply and demand on the same surface, identify the eight to twelve moments that decide whether someone returns, and tag each one with the trust, friction, and motivation factors that drive it. The output is a sheet your engineering team can build against and your marketing team can target against. No translation required.

Key deliverables
  • Detailed personas across three growth phases (cold start, fit, scale)
  • Side-by-side supply and demand journey map
  • Trigger, friction, and trust events tagged at every step
  • Conversion-critical touchpoint framework
  • Optimization recommendations prioritized by leverage
How Pre-Development Runs

Two to three weeks. Three working sessions a week. One written thesis at the end.

Week 1

Discovery and economic modelling

Two working sessions to map your marketplace, the constrained side, and the unit economics. We end the week with a written thesis you either agree with or change.

Week 2

Brand sprint and validation prototype

Parallel tracks. Brand exploration on one side, clickable prototype on the other. By Friday you have something to show partners, supply, and investors.

Week 3

User tests, journey map, build brief

Five users. Real reactions. We translate what we heard into a build brief with cut scope, sequenced milestones, and a defensible budget.

How AI Fits Into Pre-Development

The thinking is human. The grunt work is not.

Pre-Development is a strategy phase, which means it is the phase where AI helps least and senior judgment matters most. We are honest about both.

What AI does in Pre-Development
  • Synthesizes competitive research and pulls structured data from public marketplaces
  • Drafts persona variants, journey-map skeletons, and brand-direction starting points
  • Generates wireframe iterations against a written spec, ten in the time it took to draw one
  • Transcribes and clusters user-test feedback into themes
  • Renders prototype variants overnight so the next session has something to react to
What humans always do
  • Decide which side of the marketplace is constrained, and stake the strategy on it
  • Sit across from you and tell you when the wedge is wrong
  • Run user tests, interpret silence and body language, choose what to change
  • Make the unit-economics call: is this margin-real, or are we faking it
  • Sign their name to the written thesis at the end of the engagement

The senior thinking is not negotiable. The speed is what is new.

Who Pre-Development Is For

If three of these are true, this is the right starting point.

  • You have a marketplace idea but have not validated it with real supply or real demand yet.
  • You are about to spend more than fifty thousand dollars on a build, and you want to know whether the spec is right first.
  • You are a non-technical founder and you do not have a co-founder who has shipped a marketplace before.
  • You are raising soon and the deck would land harder with real research, real numbers, and a real prototype.
  • You are willing to kill the idea if the numbers do not survive the work.
When To Skip This

Pre-Development is the wrong call if any of these is true.

  • You already have a live marketplace and a real liquidity problem . Go look at Grow instead.
  • You are looking for a logo and a deck. We can refer you out , that is not what this engagement is.
  • You want to be told the idea is good. We will tell you what is true, which is not the same.
  • The marketplace is a side feature inside a larger product. The work is real, but it lives in a different conversation.
Pre-Development FAQ

What founders ask before they hire us.

Pre-Development is intentionally priced to be the cheapest expensive thing you do. A typical engagement runs two to three weeks of focused work and is fixed-price by milestone. The exact number depends on the marketplace category, the depth of validation needed, and whether branding is in scope. We quote on the discovery call once we understand which of the four deliverables you actually need.
Two to three weeks of calendar time, run as three working sessions a week with structured homework in between. Two weeks is enough when the founder already has supply-side relationships and a clear thesis. Three weeks is typical when we are doing the brand sprint and the prototype in parallel. We do not run engagements longer than four weeks . Past that, you are stalling, not planning.
A prototype is clickable, not transactable. It exists to test whether the core flow makes sense to real users, and it is built in two to three days. An MVP transacts real money between real users. A prototype belongs in pre-development. An MVP belongs in the build phase. Skipping the prototype and going straight to MVP is the single most expensive mistake we see non-technical founders make.
Rarely, and only when the founder already has a written strategy we can read. Marketplace branding without a wedge produces a beautiful logo on a marketplace nobody returns to. If you have done the strategy work elsewhere, send it over before the discovery call and we will tell you whether it is enough to start design from.
Three things, in order. First, model the unit economics on the constrained side (usually supply) and see whether the take rate survives realistic willingness-to-pay. Second, get five real prospective supply-side users to react to a clickable prototype and a one-page offer. Third, run a cold-start test: can you, the founder, manually hand-deliver the first ten transactions in a week. If any of those three fail, the marketplace is not ready to be built. That is what pre-development buys you: the ability to find out for the cost of three weeks instead of three months.
A written marketplace strategy document with the operating thesis, monetization model, and cold-start plan. A finalized landing page with a working brand system. A clickable prototype of the four core flows. A side-by-side supply and demand journey map. A build brief with cut scope and a defensible budget. Plus a clear yes-or-no on whether to build, and if no, what the next experiment should be.
Yes, and it is one of the most common reasons founders engage with us at this stage. The strategy document, unit-economics model, branded landing page, and clickable prototype are exactly the artefacts a seed-stage investor expects to see. About a third of our pre-development clients use the work product directly inside their pitch deck. We do not write the deck, but we make most of it true.
We do shorter pre-development engagements scoped as marketplace strategy reviews, usually one week. They focus on the parts of the four deliverables you have not done, typically the unit economics and the journey map, and end with a written set of recommendations against your existing roadmap. Tell us where you are on the discovery call and we will tell you whether a review is enough or whether the gaps are big enough to justify the full engagement.

Decide what to build before you build it.

Thirty minutes with Darren. We will tell you whether your marketplace is worth building, and what the next ninety days should look like.

30 minutes · No obligation · Walk away with a clearer marketplace