A website with a booking system that fits how you actually work.
Not a scheduling widget bolted onto a template. A site built for your business, with a request or booking flow that asks your questions, in your order, under your rules — and a dashboard you run yourself. You own all of it: the code, the data, the domain.
Why the off-the-shelf booking tools stop working
Calendly, Squarespace Scheduling, Acuity and the rest are good at one thing: someone picks a slot from a calendar. That works when every appointment is basically the same appointment.
It stops working the moment your booking has a shape:
- The job needs a conversation before a date can be set — a quote, a consultation, a look at reference images.
- You need to see what someone wants before you agree to a time.
- Your intake questions don't fit in a plugin's three fields, so they end up in email anyway.
- Your policies — deposits, cancellation windows, minimums, travel — live somewhere nobody reads.
- You want to screen out the enquiries that were never going to be a fit, without a phone call.
At that point the widget becomes a second inbox. Everything real still happens in your messages, and you're paying monthly for the privilege.
What "built for you" actually means
The request flow
- Your questions, in the order that makes sense for your work
- Branching — different service, different questions
- File and image uploads attached to the request
- Required fields for the things you can't quote without
- Your terms stated on the page, before the form
The dashboard
- A pipeline: new, talking, booked, passed
- Everything one client sent on one screen
- Private notes only you see
- Calendar sync, so a booked date is a booked date
- Pages, prices and photos you edit yourself
It's a real demo, not a mockup. Open the dashboard and click through it — move a request across the pipeline, open a card, read what came in. No signup, nothing to install, nothing you can break that matters.
Built for it, so far
The system is the same underneath; the questions and the pages are shaped around the trade.
Tattoo studios →
Reference images, placement and size, style, artist routing, flash pages, deposit and reschedule policy stated up front.
Private chefs →
Date and headcount, location, dietary restrictions that can't be skipped, budget range, and menus you edit yourself each season.
Those are the two I've built end to end, so those are the two I'll show you. The pattern — a request that needs real information before a date gets set — is the same for photographers, event planners, stylists, trainers, mobile services, studios of most kinds. If your booking has a shape, it's the same problem.
And if it doesn't — if you need a straight, well-built site with no portal behind it — I do those too, and I'll say so rather than selling you a dashboard you'd never open.
What it's built on
Next.js and Supabase — a modern framework and a Postgres database. Not a page builder, not a stack of plugins that break when one of them updates.
- Fast. Static where it can be, dynamic where it has to be.
- Yours. The code is yours. The database is yours. Your domain is registered in your name, on your card — not mine.
- Portable. Take the handover for $400 and everything moves to your own accounts and keeps running without me. Nothing is built to trap you.
- Backed up. On the care plan, nightly, with a restore I've actually tested — an untested backup isn't a backup.
What it does, and what it doesn't do yet
Today
- Custom request and inquiry flows with uploads
- Admin dashboard with a pipeline and client history
- Calendar sync
- Pages, prices, galleries and posts you edit yourself
- Email notifications when something lands
Not yet
- Taking deposits or payments by card on the site
- Memberships, class packs and subscriptions
- Multi-location scheduling across sites
- Invoicing and accounting
I'd rather tell you that now than after you've paid. I built the back end, so any of those can be built — it just changes the quote, and you'd see that number before anything starts.
How a build goes
- 1. A call, and a fixed quote
- You tell me how bookings reach you now and what you're tired of doing by hand. I write down the scope and the number. Nothing starts until you've seen both.
- 2. Design, then build
- Layouts and copy first, so you're reacting to something real rather than describing it. Then the site and the request flow get built.
- 3. You use it before it's live
- You send yourself test requests and move them around the dashboard. If a question is wrong or in the wrong place, that's what this stage is for.
- 4. Launch, and then it's yours
- Domain, hosting, and a walkthrough of everything you can change yourself. Then either the care plan, or the handover — your call, and you can switch later.
Four to six weeks for a full build, three rounds of changes included. Faster is sometimes possible; I'll tell you honestly whether it is, and whether it costs more.
What it costs
Every project gets a fixed quote in writing before anything starts. Full pricing and what's included →
Common questions
- Isn't a custom booking system overkill for a small business?
- If a calendar widget covers you, use one — it's cheaper and I'll say so. This is for when the widget has become a second inbox and the real work still happens in your DMs.
- What are the ongoing costs if I run it myself?
- Hosting and the database, on your own accounts. Small — on the order of tens of dollars a month at the scale most single-operator businesses run at. I'll show you the actual numbers for your setup before you decide, not after.
- Can I move to another developer later?
- Yes, and the handover exists so that's a normal thing to do rather than a fight. Standard framework, standard database, code in your repo. Any competent developer can pick it up.
- What if something breaks at 9pm on a Saturday?
- On the care plan, that's mine to fix — the site and the booking system are monitored, and I'd usually know before you do. Off the plan, it's yours, which is the honest trade for not paying monthly.
- Do you only build booking sites?
- No. Static sites, revamps, and straightforward brochure sites too. The booking system is the thing I'm best at, not the only thing I do.
Tell me how booking works for you now
What you sell, how people reach you, and what you keep retyping. I'll tell you straight whether a custom system is worth it for you — including if the answer is no.
Start a project