Our SaaS MVP had traction, the question was how to scale it without a rewrite

I’m running a SaaS product that started as a fairly lean MVP. That was the right call early on because we needed to validate demand and get real users into the product quickly.

The problem showed up once usage grew, of course. Features that used to be straightforward started taking longer. We also had to think more seriously about tenant isolation, permissions, deployment, backups, and, basically, whether the current setup would hold up as more customers joined.

So I wanted to audit the product and look at how tenants are separated and which parts of the codebase create repeated maintenance work. I needed to know if the infrastructure can scale without a lot of manual intervention. I was looking at SaaS development partners for that stage, and went for Redwerk eventually (their SaaS development offer includes modernizing and scaling existing products). So they reviewed the current architecture, improved areas that were becoming difficult to maintain, and strengthened tenant separation and cloud infrastructure where the product needed it. I have to hand it to them, they explained the tradeoffs super clearly and we learned which changes affect reliability now, which ones can wait, and what each improvement buys us operationally.

Be aware, at that point, the work touches the whole product. You need someone who can look at the entire system carefully and improve the parts that are slowing growth.

The best advice I can offer after all this - deal with architecture problems while the product is still manageable. If every new customer creates another exception, well, the cleanup will be much harder.