BookMeUp
Book anything — events, tables, courts, studios, appointments. One catalog, one click.
- Kind
- Concept · Booking marketplace
- Year
- 2026
- Role
- Positioning, UI design, Motion, Build
- Built with
- Next.js, GSAP, Supabase

The growth problem
Breadth is the product and breadth is the problem. Nobody books a padel court through a site that also sells dentist appointments — not unless it first proves the model underneath is sound.
What the design does
Positioning
Turns the breadth into the thesis instead of apologising for it. The claim isn't "we have everything", it's that every category runs on one record — a title, a moment, a place, a capacity — and a booking system stops being domain-specific the second you stop hard-coding the domain.
The path
Substitutes mechanism for social proof. With no bookings yet there's no crowd to point at, so the site explains exactly how it works: server-side sessions in an HttpOnly cookie, a unique constraint that makes double-booking impossible however fast you click, and no admin signup route at all. Confidence from showing the engineering rather than claiming traction.
The feeling
A systems register — dark ground, monospace, geometric category glyphs, a build version stamped in the footer. It reads as infrastructure rather than a startup landing page, which is the right register for something asking to hold your calendar.
Try it here
The live product, running in the page.