If you run a web agency long enough, the same thought shows up. What if instead of building sites for clients one at a time, I owned the platform that builds and hosts them, and ran my whole business on my own thing. That is the pull toward building a website builder SaaS. The mistake is thinking you have to write the entire thing from a blank screen.
The 80% that is not your idea.
A website builder platform is a huge amount of software, and most of it is not the part that makes yours special. Multi-tenant accounts so each client is separate. A visual editor. A deploy pipeline. Hosting. User roles and permissions. Billing. Domains and SSL. All of that is table stakes, its the same in every platform, and building it from nothing is where people sink a year or two and quietly give up.
Your edge is not the deploy pipeline. Your edge is how you build sites, the presets you use, the way you work with clients, the specific slice that is yours. Everything under that is plumbing you should not be laying by hand.
Building the generic platform from scratch is spending a year rebuilding things that already exist, so you can finally reach the starting line other people started from.
The shortcut, start from a platform you own.
The version that actually works is to start from a multi-tenant site platform whose code you own, and shape it into your product. You get the accounts, the editor, the hosting pipeline, and the roles already built, and you spend your time on the parts that make it yours instead of on auth and tenancy.
That is literally why Seedly Sites exists. I did not want to sell sites one at a time forever, and I did not want to spend two years building a platform from zero to stop doing that. So the platform is the thing you own and run as your own website builder, for your clients, under your brand. You start at your edge, not at the plumbing.
Make it something yours.
Explore Seedly's software and the guides to help you get started.
Explore the codebasesThe honest catch.
Owning and running a platform is more than owning a folder of client sites. You take on the responsibility of running the thing, and you inherit the structure of whatever you start from, so it matters that the foundation is actually good. But that trade beats the alternative of building the whole platform yourself, by a wide margin, unless your idea is so unusual that no existing platform fits it. For most agencies, it is not that unusual. It is the same platform with your way of working on top.
Where to actually start.
You can build a website builder SaaS without writing the boring 80% yourself. Start from a platform you own, and put your months into the part that is actually your product. The build-or-buy call in general is in SaaS boilerplate vs building from scratch, and the agency-into-product version is in turning your agency into a SaaS.
Start at your edge, not the plumbing.
