How Zylzio runs on Zylzio

Every tool this studio runs on, we built. The website you're reading. The scheduler that booked your call. The CRM that remembered your name. The proposal you signed, the portal you log into, the invoice you paid. One codebase. One Next.js and Supabase app, deployed once, doing all of it.

That's not a flex. It's the whole pitch. Let me show you.

What's actually in there

Start at the front. The marketing site is a handful of pages with our brand baked into the CSS. No page builder, no theme, no plugin stack to babysit. When we want to change something, we change it. It deploys in about a minute.

Behind the contact form sits a small CRM. Every inquiry becomes a lead with a timeline: when they wrote, what they said, when they booked a call. The scheduler is ours too — it knows our hours, sends confirmations and reminders, and quietly moves the lead forward in the pipeline. Nobody retypes anything.

When a project looks real, we write the proposal in the same system. The prospect gets a private link. We can see when they open it. They accept by signing their name right on the page — no PDF attachments, no “did you get my email?” Then one click turns the accepted proposal into a project: client record, kickoff checklist, deposit invoice, all created together.

From there the client lives in the portal. Progress updates, weekly previews to approve, files to download, messages, invoices they can pay online or print. Every Friday a digest goes out summarizing what moved. We log our hours against each project, so we always know what a fixed price actually cost us.

Why bother?

The honest answer: we tried the usual stack first. A CRM here, a scheduling tool there, a proposal service, an invoicing app, a shared folder for files. Each one fine alone. Together, a mess. Data lived in five places. Statuses drifted. Monthly fees stacked up for features we barely touched.

Owning the stack fixes the seams. A booked call and a paid invoice land in the same database, so the timeline of a client relationship is one query, not an archaeology project. When something annoys us, we fix it that afternoon. When a client asks for something — say, a printable invoice — we ship it instead of waiting on a vendor's roadmap.

And it keeps us sharp. This is the work we sell. Running our own business on software we wrote is the most honest test environment there is. Every rough edge we feel, we fix before a client ever feels one like it.

The pitch, plainly

Here's where this stops being about us. What we did for ourselves is exactly what we build for clients: one system, owned outright, shaped around how the business actually works.

When we build for you, you keep everything. The code, the data, the database, the deploy. No license that expires. No per-seat pricing that punishes you for hiring. No platform that sunsets a feature you depend on. If we disappeared tomorrow, your system would keep running and any competent developer could pick it up — because it's plain, boring, well-documented code on infrastructure you control.

Most small businesses don't need more software. They need less of it, doing more, in one place. That's the thing we make.

What we buy instead of build

Owning the stack doesn't mean building everything. That would be vanity, not engineering. We draw the line at problems where being wrong is expensive and someone else is world-class:

Stripe moves the money. Card payments, subscriptions, the billing portal where clients manage their own care plans. We will never store a card number, and neither should you.

Resend delivers the email. Getting mail into inboxes instead of spam folders is a dark art with full-time practitioners. We write the emails; it gets them there.

Vercel and Supabaserun the thing. Hosting, the database, auth, backups. Rented infrastructure, owned application. If we ever need to move, it's Postgres and a Node app — the most portable combination in the business.

The rule is simple: build what makes the business different, buy what makes it the same as everyone else. Payments, email delivery, and hosting are the same for everybody. How you run your projects is not.

The takeaway

Software you own compounds. Every small improvement stays improved. Small afternoons spent fixing our own annoyances keep adding up to a system no off-the-shelf tool matches — because it wasn't built for an average business. It was built for this one.

Yours could work the same way. If that sounds worth a conversation, book a call. The scheduler you'll use is the one from paragraph one.