This blog runs on software I built. Here's why that's both exciting and terrifying.
April 10, 2026Every developer has, at some point, thought: I should build my own version of that.
For me, that thought came while I was trying to set up appointment scheduling for my beautiful wife - a nail artist who was drowning in DMs, trying to manually coordinate bookings, no-shows, and reminders every single day. I looked at the existing tools. They were either too complex, too expensive, or too ugly. So I did what developers do.
I built my own.
That project became Timelish — an all-in-one appointment scheduling platform for small businesses. And this blog you're reading right now? It's built on top of it. Which means every post I publish here is, in a small way, a live demo of the very product I'm writing about.
That's the thing I want to explore in this space: what it actually looks like to build a SaaS from scratch, make real engineering decisions under real constraints, and ship something people depend on.
Why appointment scheduling?
It's not a glamorous problem. Nobody's going to write a TechCrunch headline about calendar software. But that's exactly why it interested me.
The businesses that need this most — nail artists, personal trainers, tutors, therapists, consultants - are not developers. They're not going to configure webhooks or read API documentation. They need something that works the way email works: you just open it and go.
The market had solutions, but most of them fell into two camps: tools built for enterprises (powerful, complicated, expensive) and tools built for the lowest common denominator (simple, but you hit the ceiling fast). Nobody was building something that was genuinely easy and genuinely capable.
So the engineering challenge became: how do you build a product with the surface area of something simple, but the depth to actually handle real business needs?
How did Timelish get started?
At first, it started as a very simple web app written using Next.js - a single instance that you can install as a Docker container for yourself. No fancy drag and drop, no admin panel, no calendar connection. Nothing. It was a very simple app - read YAML config for booking settings, MDX defined pages, simple ICS link to read the calendar (which quickly became a big problem - you are basically reading the whole list of calendar events, which would take up a few seconds after a few months), simple email with ICS file attached to automatically save the appointment to calendar and block the time.
How was it hosted? Simple. Just a Docker container running at my homelab using Dynamic DNS to point the domain to my home. Internet cut off? No bookings.
It was that simple.
But then I started to build features that my wife needed - the ability to confirm/decline appointments, set up a schedule, appointment reminders, taking deposits - this used to be a big problem for my wife, who had just started, and constantly had people not showing up to the appointments and going no-contact, etc.
So I started building.
What Timelish actually does now
At its core, Timelish gives a small business owner three things:
- A booking website they can set up in about five minutes - drag, drop, publish. No designers, no agencies, no waiting. Clients get a link, they pick a time, done.
- An automated layer that handles everything that usually falls through the cracks. Confirmation emails. SMS reminders. Follow-ups. The kind of work that used to eat up Sunday evenings, answering messages that could have been a booking link.
- A payment layer so businesses can collect deposits or full payments at the time of booking. This alone cuts no-show rates dramatically - when someone has skin in the game, they show up.
The main features that are already in place:
- Connect with Google Calendar, Outlook, Google Meet, Zoom, and PayPal. Everything stays in sync. Need video meetings? That's supported too!
- Create beautiful pages or nice email templates with an easy-to-use drag-n-drop builder (I am really proud of this one specifically - who knows how many hours I spent creating, optimizing, and verifying it).
- Create gift card designs with another visual drag-and-drop editor and sell them to boost your revenue.
- Write blog posts and publish them (hey, that's what we are doing here!)
- Create intake, contact, or other forms - and collect responses.
- Appointments and waitlist - your clients can book or add themselves to the waitlist directly
- User and customer notifications - email or SMS to keep both parties up-to-date on their schedule
- Cancellations and reschedules - allow your users to manage their appointments and collect fees if required. Or do it yourself!
- Smart schedule - reduce downtime between bookings, so you can maximize your profits. Get full control over your day. (Again, my wife was a very big contributing factor - she hated it when customers booked hours apart and made her just sit and wait around for the next appointment)
- And many more…
The part that keeps me honest
Here's the thing about building a product and then building your public writing platform on top of it: you can't fake it.
If Timelish has a reliability problem, my wife's business goes down too. If the booking flow breaks, her flow breaks too. No appointments to be made, no money in our budget. If I make a bad architectural decision, I live with it in production every day - not just in some staging environment I rarely look at.
That accountability is uncomfortable in the best way. It forces me to care about the parts of the product that don't show up in a demo: the edge cases, the error handling, the performance under weird conditions.
I think this is actually the right way to eat your own dog food. Not a toy internal tool that nobody depends on, but a real public surface that real people interact with.
What I'll write about here
This blog is where I'll work through the decisions behind Timelish - technical and otherwise.
Some posts will be deeply technical: the architecture choices, the tradeoffs, the things I got wrong the first time. Some will be about the product side: how to figure out what to build when your users can't articulate what they need. Some will probably just be honest postmortems of things that broke in ways I didn't anticipate.
I'm not going to pretend this is a finished, polished product I'm writing retrospectively about. Timelish is still pre-launch - we're collecting a waitlist right now. So you're getting the live version of this story, not the highlight reel after the fact.
That's either the most interesting version of a founder blog or a future source of personal embarrassment. Possibly both.
Want to try Timelish? We're launching soon. Join the waitlist at timelish.com — early members get up to 40% off.