Elicon
← ALL REFERENCE ENGAGEMENTS
REFERENCE ENGAGEMENT
Marketplace

Marketplace MVP for an Early-Stage Founder

Bookings, payments and reviews — and nothing else — live fast enough to raise on traction.

  • Next.js
  • Node
  • Postgres
  • Stripe Connect

Reference engagements illustrate how Elicon would approach a project of this kind — the problem, the architecture and the decisions. They are examples, not accounts of past client work.

THE SITUATION

The problem.

An early-stage founder who needs a two-sided marketplace live fast enough to raise on traction rather than slides. The engagement cuts scope to bookings, payments and reviews, runs everything else as a manual process behind an admin panel, and instruments the funnel from the first day.

The founder needs real usage data quickly, and every extra feature delays it.

  • ·The product vision includes far more than is needed to test the core hypothesis.
  • ·Investors want funnel data, which only exists if it is collected from the start.

APPROACH

How we'd run it.

  1. 01Cut scope to bookings, payments and reviews; everything else is a manual workflow at first.
  2. 02Use Stripe Connect for provider payouts instead of a custom ledger.
  3. 03Sync provider calendars so availability stays accurate.
  4. 04Instrument every funnel step from day one.

ARCHITECTURE

What gets built.

Booking core

Availability, holds and confirmed bookings with transactional integrity — a hold expires or converts, never both. Double-booking is prevented at the database level.

Payments via Stripe Connect

Connected accounts for providers, platform fee at capture, payouts and identity checks handled by Stripe. No custom ledger and no money held in ambiguous states.

Funnel instrumentation

Every step — search, view, hold, book, pay, review — emits events into a simple table with a dashboard on top.

DECISIONS

The trade-offs.

Cut messaging, packages, subscriptions and loyalty entirely

None of them test the core hypothesis, and each would cost launch time.

TRADE-OFFThe first version looks thinner than the vision.

Manual processes behind an admin panel instead of automation

At low volume, manual vetting is fast and teaches the founder what the automated rules should be.

TRADE-OFFIt does not scale, and the threshold where it stops working is written down up front.

Instrumentation on day one

Funnel numbers are the fundraising asset, and retrofitting analytics loses the earliest cohort.

TRADE-OFFBuild time that produces no user-facing feature.

STACK

Typical stack.

APPLICATION
Next.jsTypeScriptNodeTailwind
DATA
PostgresTransactional holdsEvent table + dashboard
PAYMENTS
Stripe ConnectPlatform feesAutomated payoutsKYC via Stripe
INTEGRATIONS
Google Calendar two-wayiCal import

SIMILAR PROBLEM?

Tell us what you're dealing with.

One conversation with an engineer is usually enough to tell whether this is a few weeks of work, a few months, or something you shouldn't build at all.

Talk to an engineer →