The Anti-SaaS Manifesto: Stop Renting the Systems Your Business Runs On

Every month, your booking platform sends an invoice. Every month, you pay it. And every month, you own a little less of the system your business runs on.

That is not a software problem. It is an ownership problem.

SaaS made software easy to start. It also made it easy to never own anything you depend on. For tools at the edge of your business, that trade is fine. For the systems your revenue runs on, it quietly becomes a liability.

This is the Anti-SaaS Manifesto.

SaaS was a good idea

SaaS solved a real problem. Before it, software meant servers, installs, upgrades, and long procurement cycles. SaaS removed that friction: sign up, log in, start working.

For tools at the edge of your business, that is still the right choice. A SaaS form builder, a SaaS help desk, a SaaS analytics dashboard: rent them, and never think about them again.

SaaS is a great way to use software. It is a poor way to own a system.

Then renting became the business model

The problem is not the delivery model. It is what the delivery model became.

Modern SaaS is optimized to make leaving hard:

• Your data lives in their schema.
• Your workflows depend on their features.
• Your costs rise with your success, through seats and commissions.
• Your roadmap waits in their backlog.

None of this is accidental. Lock-in is not a side effect of SaaS. It is the SaaS business model. You did not buy a tool. You rented a dependency.

The quiet compromises

Every SaaS booking platform asks you to accept the same trades. They are small at first. They compound.

None of these break on day one. They break the day your business stops being average, and every growing business eventually does.

What this looks like in practice

Picture a clinic. It opens with one location, a few practitioners, and simple hours. SaaS booking is perfect: live in a day, cheap, done.

Then it grows. A second location with different hours. Practitioners who split their week between sites. Rooms and equipment that must never be double-booked. A rule that new patients need a longer first visit. An insurer integration. A report the finance team needs every month.

None of this is exotic. It is just what success looks like. And one by one, each requirement meets the same answer: the platform does not do that. So the team starts patching. A spreadsheet here. A manual override there. A booking rule now enforced by a person instead of the system.

The software still "works." The business just quietly slows down. That is the day SaaS stopped fitting, and no one sent a notification.

We are not anti-software. We are anti-rent.

This manifesto is not against software vendors, SaaS engineers, or the subscription invoice itself. It is against one specific thing: renting the systems your revenue depends on.

If a system is core (if it touches your bookings, your availability, your money), then it is not a feature you should rent. It is infrastructure you should own.

Renting your core is fine, until the rent decides your future.

When SaaS is still the right call

We will not pretend otherwise: most of the time, SaaS is the correct choice.

Rent SaaS when booking is not mission-critical, when your workflows are simple and unlikely to change, when volume is modest, and when speed matters more than control. A pilot, an early-stage product, a secondary channel: do not build infrastructure for those. Buy a subscription and move on.

Ownership earns its place only when booking is genuinely core: when it drives revenue directly, when operations depend on non-trivial rules, when other systems read your booking data, and when you intend to grow. Below that line, a manifesto is overkill. Above it, renting is the expensive option.

What we build instead

Timerise does not sell access to a platform. We design and build custom booking infrastructure, accelerated by AI, and we hand it over completely:

• You receive the code, not a login.
• You own the data and the schema.
• You control the logic and the roadmap.
• You pay once for the system, never a commission on your growth.

We are specific about what that means in practice:

• 6 to 8 weeks from kickoff to a system running in production.
• A fixed price, set by the complexity of your booking logic, not by hours billed.
• 0% commission and no recurring platform fees layered on top.
• 3 years of support included after handover, with the full source code and infrastructure transferred to you.

AI is what makes this practical. It removes the old excuse that custom is slow and expensive. As we argued in The End of SaaS Compromises, custom infrastructure can now ship in weeks, not months. And because the frontend is yours, you can keep extending it the way open-source components let you.

The principles

1. If a system is core to your revenue, it is infrastructure, not a feature to rent.
2. You should own the code, the data, and the logic. All three.
3. Growth must not raise your platform bill. No seat tax. No commissions.
4. Your workflows shape the system, never the other way around.
5. There is no lock-in. Leaving must always be possible, and cheap.
6. AI ends the trade-off. Custom is no longer slow, and no longer expensive.

The real question

The SaaS pitch always asks the same thing: how much does it cost per month? It is the wrong question. Ask this one instead: how much of our core business are we agreeing never to own?

When booking is core to what you do, ownership is not an upgrade. It is the only honest foundation.