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.
Bookings, payments and reviews — and nothing else — live fast enough to raise on traction.
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
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.
APPROACH
ARCHITECTURE
Availability, holds and confirmed bookings with transactional integrity — a hold expires or converts, never both. Double-booking is prevented at the database level.
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.
Every step — search, view, hold, book, pay, review — emits events into a simple table with a dashboard on top.
DECISIONS
None of them test the core hypothesis, and each would cost launch time.
TRADE-OFFThe first version looks thinner than the vision.
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.
Funnel numbers are the fundraising asset, and retrofitting analytics loses the earliest cohort.
TRADE-OFFBuild time that produces no user-facing feature.
STACK
SIMILAR PROBLEM?
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 →