Hospitality & F&B
Live in production — seven cities booking through one system
Timeline
1 week to production
Scope
Booking platform · staff console · email layer · website concept
Industry
Hospitality & F&B
Stack
Next.js, React, TypeScript, PostgreSQL, AWS
Outcome
Live in production — seven cities booking through one system
Before Itqan
Seven restaurants, and every booking lived in a phone call or a DM. Nobody could see the whole day, and nobody could change a rule without asking a developer.
Seven brunch restaurants across Sweden, and every table booked by phone or Instagram DM. No shared view of who was coming, no way to cap a sitting before the kitchen drowned, and every "can we cancel?" was a call someone had to answer mid-service. The chain needed real booking infrastructure — and owning it, not renting a per-cover SaaS that charges for every guest.
The bridge
After
Live at boka.lemongarden.se on the client's own AWS — no per-booking fees, ever. Guests book, reschedule and cancel themselves through signed email links; the kitchen sees exact covers per 90-minute seating; every location has its own login and inbox routing. Overbooking is impossible by design (capacity is checked atomically at write time), and every release passes a multi-model security review before deploy.
What we shipped
The website concept
Alongside the platform we designed a full website concept for the chain: hand-drawn lemon branches that sketch themselves in as you scroll, postage-stamp buttons, wavy awning bands and a city marquee. Pitched with an interactive live demo — shown here as designed.
Restaurant booking SaaS charges per cover, forever, for what is essentially a calendar with rules. We built Lemon Garden the opposite deal: a system they own outright, on their own server, where the owner changes the rules from a console instead of calling a developer. Demo on day one, production in a week — then we let their real service weeks tell us what to build next.
