Riti set out to make hosting a small event, a workshop, a yoga class, a gallery night, as easy as booking a table, for hosts and space owners across Norway, Sweden, and Denmark. That meant three different groups on one platform: people renting out physical spaces, people running events in them, and people attending. We designed and built the product with Pankaj: the space marketplace, the event layer on top of it, and the Stripe Connect payment flows connecting both.
The core decision that shaped everything else: one unified account. Nobody signs up as a 'host' or an 'attendee'. Anybody can attend, then host, then rent out a space, all from the same login, without a separate account or a support ticket to unlock it.
Riti: One Account, Three Roles, and a Payments Model That Had to Get the Split Right Every Time
The challenge
Most marketplaces pick a role at signup and build the whole product around that choice. Riti couldn't, because the same person books a yoga studio on Tuesday and hosts a workshop in one on Friday. We had to design an account model where hosting is a capability you unlock by acting, not an identity you commit to on day one, without the product feeling like two different apps stitched together.
Underneath that sat a harder problem: money. Space vendors earn 90% of a booking with Riti keeping 10%. Hosts keep 100% of ticket revenue. Neither is paid until 24 hours after the event or booking actually happens, and space bookings are approval-first, a vendor has to say yes before a card is ever charged. Every one of those rules had to hold up exactly, across three countries, with no escrow layer to fall back on if something went wrong.
Our approach
We designed a single dashboard that reads by mode, not by role: switch to Host mode and event tools appear, switch back and it's discovery and bookings, but it's the same account, the same login, the same profile underneath. First-time hosting triggers a lightweight profile step and a Stripe Connect prompt, only when it's actually needed, not upfront for everyone.
For space bookings, we built the full approval-first flow: a request goes to the vendor before any charge happens, the vendor approves or rejects, and only then does the attendee see a 'Pay now' step. If nobody pays, the request auto-expires and the slot reopens. That sequencing (request, approve, pay, hold, payout) had to be airtight, because there's no escrow account absorbing a mistake if it isn't.
On the trust side, every new space listing lands in an admin review queue before it's visible to the public, and admins can suspend a space or a vendor without deleting anything underneath it, existing bookings stay intact even if a listing gets pulled. We paired that with in-app notifications for every state change (approved, rejected, paid, cancelled) so nobody has to guess where their booking or listing stands.
“DreamLaunch helped us bring Riti to life, a platform built to connect people with unforgettable experiences across cities. From the event discovery flow to creative spaces and workshop listings, every detail was designed with real intention. They understood our vision from day one and delivered something we're genuinely proud of.”
Pankaj
Founder, Riti
