Prerender’s Second Act: What Changed After Acquisition

Todd built Prerender over a weekend. By the time he sold it, it was serving pre-rendered pages to crawlers for over 100,000 businesses. That gap between “thing I hacked together” and “real company with a second life” is worth understanding if you’re sitting on something similar.

Most acquisition stories are about the deal. This one is about what came after. The liquidity event matters but for Prerender, it was almost secondary. The real unlock was operational: infrastructure costs slashed by 80%, a team that absorbed the support load, and a founder who could exit cleanly without being the single point of failure anymore.

That’s a different story than the one most bootstrapped founders imagine when they think about selling.

The wedge was urgent, and that made everything easier

Google would hit an Angular site and see a blank page. Rankings tanked. Founders panicked. Todd’s fix was blunt but effective: render the page in a headless browser, snapshot it, serve that to the crawlers. Simple, unglamorous, and exactly what people needed.

What made it stick wasn’t the idea. It was the timing of when it showed up. Prerender landed when teams had already shipped a major front-end release and had no good rollback option. In that situation, you don’t want a roadmap. You want the bleeding to stop. Google has long flagged JavaScript heavy sites as a crawling challenge dynamic rendering (serving static HTML to bots) has been a recommended workaround in Google’s own documentation for years. Prerender was that fix in product form.

Two things Todd did early that bootstrapped founders tend to delay: he charged from day one, and he made the setup trivial. One line of code. No headless browser to manage yourself. No infrastructure to babysit. If your SEO is on fire, friction is your enemy and he removed it.

Urgency is a distribution channel. It’s easy to underestimate how much of a product’s early growth comes from showing up when the pain is unbearable.

The bootstrap trap, in its purest form

Todd ran Prerender solo to around $2M ARR. Then he brought his brother in. But even then, the day was mostly technical support. All day, every day.

This is the pattern that’s hard to see when you’re inside it. The product works. The margins are real. The demand is real. But you’ve quietly become the system. Every customer that needs help needs you. Every outage, every weird crawl behaviour, every edge case it routes back to the founder.

You’re not running a business. You’re running a support operation with a product attached.

Research from the Indie Hackers community consistently shows that founder burnout and support overload are among the top reasons bootstrapped SaaS founders consider exits not a bad product or weak revenue, but the weight of being the only one who can fix anything. Todd was at around $2.5M ARR when saas.group reached out. The business was healthy. The founder was tired.

That’s the real trigger most acquisition conversations never name.

Why the process actually worked

Todd had talked to buyers before. The pattern he didn’t like: “this becomes a feature inside our bigger product.” His thing would get absorbed, rebranded, eventually forgotten. That’s not an exit. That’s a slow shutdown with a cheque attached.

With saas.group, the expectation was different. He shared the number he’d take. The answer was essentially: yes. No penny-pinching. No drawn-out negotiation. No pressure tactics.

The other piece that mattered and this is underrated was flexibility around his involvement. Todd didn’t want to stick around long-term. He didn’t have to. The deal structure made it possible to leave cleanly, without obligations dragging on.

saas.group’s commitment was equally clear: Prerender would stay standalone. Not absorbed into another product. Not rebranded into irrelevance. A real business, run properly, with the infrastructure and team it had never had under a solo founder model.

This is what we mean when we say the process should fit the founder, not the other way around. Some founders want to stay involved. Some want a clean break. Both are valid and the structure should make room for that from day one.

What actually changed after the acquisition

The most concrete operational win wasn’t headcount or product velocity. It was infrastructure.

Before the acquisition, Prerender was running on AWS at roughly $1M per year. After the transition, that setup got reworked. Costs dropped to around $200K annually. That’s $800K back in margin not a small-print efficiency gain, but a structural shift. The difference between “we can’t hire” and “we can invest.”

That saving didn’t come from financial engineering. It came from operational expertise knowing how to run cloud infrastructure at scale, which a solo founder building a product on weekends simply isn’t positioned to optimise.

Beyond infrastructure: the team grew, support coverage improved, and the founder bottleneck was gone. Every hard question no longer had to route back to Todd.

And the market kept expanding in a way nobody fully anticipated. Prerender was built to solve a specific problem: search engines couldn’t parse JavaScript, so it served them pre-rendered HTML instead. That same core insight now maps directly to AI crawlers. GPTBot, ClaudeBot, and similar agents preferentially index server rendered HTML the same format Prerender has been producing for years. The original product thesis hasn’t just aged well. It’s found a second, much bigger wave.

That second act wouldn’t have been possible under a solo founder model. It needed the operational foundation that only arrived after the acquisition.

What bootstrapped founders can take from this

A few things stand out from how Prerender’s story played out.

Urgency is a distribution channel. Prerender didn’t need a sales team because it showed up exactly when the pain was unbearable. If your product fixes something urgent and removes something broken, charging early and keeping onboarding simple isn’t aggressive. It’s smart.

Notice when support becomes the job. If you’re the one fielding every hard question, you’re not running a business you’re running a support operation with a product attached. That’s sustainable up to a point. Then it stops being sustainable fast. The signal is easy to miss when revenue is growing. Pay attention to it anyway.

The right acquisition removes bottlenecks. The liquidity is one part of the outcome. For Prerender, the real unlock was: infrastructure got lean, a team took over operations, and the product found a second act it couldn’t have had with one person at the centre of everything. That’s not just an exit. That’s what a good operator does with a business you built.

Deal structure matters more than founders expect. “Who acquires you” and “how the deal is structured” will shape what happens next more than the number on the cheque. An acquirer who wants to absorb your product is a different outcome than one who commits to keeping it standalone. Both will offer you money. Only one gives your work a real future.

The honest question isn’t “should I sell?” It’s simpler: is the next step more hustle, or is it removing the bottleneck so the business can outgrow you? Sometimes the answer is the former. Sometimes it’s the latter. Prerender’s story shows what the latter looks like in practice a product that got a real team, leaner infrastructure, and a second market it wasn’t built to serve but was perfectly positioned for.

Todd’s work didn’t get absorbed or forgotten. It got a second act.
If you’re curious what that kind of transition looks like in practice, we’re happy to talk.