I built a multi-tenant booking SaaS template for agencies — here's what I learned
Hey IH,
I've been quietly building SlotKit for the past few months —
booking infrastructure for agencies that build client platforms.
The idea came from a simple frustration: every time an
agency client needed booking functionality, someone had
to rebuild the same infrastructure from scratch.
This isn't a starter kit. It's the booking infrastructure
layer agencies deploy per client — multi-tenancy,
availability engine, race conditions, Stripe, email
confirmations — production-ready from day one.
SlotKit packages all of that into a Next.js 15 template:
- Multi-tenant architecture (one codebase, unlimited clients)
- 5 vertical presets (salon, clinic, fitness, professional, restaurant)
- Stripe Checkout built-in
- Booking reminders via Vercel Cron
- Availability exceptions for holidays and closures
It's live on Gumroad at $149/$299/$499 depending on the license tier.
Current status: launched 3 weeks ago, still in early distribution.
Zero sales so far — being honest here. Working on content marketing
and community presence to get the first few customers.
Happy to share more about the technical decisions or the go-to-market
approach. And always open to feedback on the product or positioning.
slotkit.dev if you want to check it out.
This is a useful agency wedge because the pain is very specific. Booking looks simple from the outside, but multi-tenancy, availability logic, Stripe, reminders, race conditions, and vertical-specific flows are exactly the kind of plumbing agencies keep rebuilding without getting paid extra for it.
The positioning I would tighten is around “agency booking infrastructure,” not just a SaaS template. That makes it feel less like another starter kit and more like the layer an agency can use to ship booking products faster across multiple client types.
One thing I’d pressure-test early is the naming frame. SlotKit is clear, but it also sounds very template/toolkit-like. If the product becomes a serious booking infrastructure layer for agencies, the brand may need to feel broader than slots and templates.
Xevoa .com would fit that direction better because it feels more like a modern workflow/platform brand, while still leaving room for scheduling, availability, payments, reminders, agency client portals, and broader service-business operations.
The "agency booking infrastructure" framing is sharp
I've been using "template" as a shortcut but you're right that it undersells the actual scope.
A template implies copy-paste; what agencies actually need is a production layer they can deploy and customize per client without rebuilding core logic each time.
On the brand point
noted, though I think the tighter focus is an asset at this stage. Broader platform brands are harder to explain to a cold audience. When you're pre-traction, specific beats flexible.
What's your experience with the agency side
do you work with them directly or more on the tooling layer?
That’s fair. At pre-traction stage, specific usually does beat flexible.
My angle is more on the positioning/tooling layer than running an agency directly. I usually look at where the product is being framed too small for the buyer’s real reason to pay.
For SlotKit, I would not make the first message broad. “Agency booking infrastructure” is still specific enough. It just makes the value feel more durable than “template.”
The agency buyer probably does not care that it is a cleaner starter kit. They care that they can sell booking systems faster, avoid rebuilding the same plumbing, and protect margin on client projects.
So I’d keep the wedge narrow, but make the outcome bigger:
“Ship client-ready booking systems without rebuilding scheduling, payments, reminders, and tenant logic every time.”
That feels more sellable to agencies than “booking template.”
Happy to think through the agency positioning privately if useful.
"Ship client-ready booking systems without rebuilding scheduling, payments, reminders, and tenant logic every time" — that's a cleaner frame than what I have on the landing page right now. The outcome is more concrete and the agency buyer sees themselves in it immediately.
I'll test that angle in the next content piece and see how it lands. Open to continuing the conversation — feel free to reach out directly
Sounds good.
Drop your email and I’ll send over a tighter version. The useful part here is mapping the agency positioning, landing page promise, and first content angle properly instead of crowding the thread.