SaaS · Bookings & operations / Design & development
BookingFlow
From the first request to event day.
Visit the websiteOne workspace brings together the event request, quote, payments and team instructions. Flo helps turn incoming emails into structured files. The platform is currently available as a private beta.
The project in practice
Role, team
& technical choices.
Design a product, then grow it as a team of two.
My contribution
I started the project in late 2025 and built its first full-stack version: business workflows, data, interfaces, documents and deployment. I continue to develop it alongside the venues.
Team & collaboration
Abdel-Samade joined me in 2026. His experience strengthens our design, review and reliability practices; we now evolve the product together.
Today
3 pilot venuesThe beta manages real private-event files, quotes and payments for events worth several thousand euros.
Two concrete
choices.
Keep the agreed price
Every booking and quote stores a copy of its rates. Changing a package tomorrow cannot alter the price accepted today.
Count a deposit only once
Stripe can resend the same confirmation. A database constraint and transaction prevent a payment from being counted twice.
- Next.js
- TypeScript
- tRPC
- Prisma
- Neon
- Better Auth
- Stripe
- Resend
A team dinner, from email to service.
Consider a private-event request for 42 people. The date arrives by email, the guest count changes and dietary requirements are added. The challenge is keeping one shared version of the file until event day.
- 01
Prepare
Flo extracts information from the request and highlights what is still missing.
- 02
Validate
The restaurant checks the information before continuing with the file and quote.
- 03
Hand over
The team receives an operational sheet built from the file, without client-facing prices.
Enlarge Recover the thread of the request.
Email, quote and last-minute changes should not tell three different stories. The demo first shows this scattered information, then brings it into one file to review. Assistance prepares the work; the person managing the event keeps control.
Public demo · example data, not a real client file.
Enlarge The right information for the right team.
The kitchen needs quantities and dietary requirements; front-of-house needs seating and timing. The team sheet brings those instructions together without exposing prices. Here, one document connects 42 covers, room setup and the service plan.
Public-site preview · fictional event.