Bootstrapping a dev SaaS as a non-tech founder with Frank Lämmer @ fortrabbit

saas.unbound is a podcast for and about founders who are working on scaling inspiring products that people love, brought to you by https://saas.group/, a serial acquirer of B2B SaaS companies.

In episode #2 of season 6, Anna Nadeina talks with Frank Lämmer, co-founder of fortrabbit, a managed, Platform as a Service (PaaS) cloud hosting provider specifically for PHP developers.

Building a developer-focused SaaS without being a technical founder sounds risky on paper — and it often is. Frank Lämmer’s story with fortrabbit is full of scrappy pivots, co-founder tensions, niche wins, and everyday operational realities that many founders don’t talk about. He co-founded a managed Platform as a Service dedicated to PHP developers and, after more than a decade, remains deeply involved in product, brand, and support while the company stays bootstrapped.

From graffiti writer to founder

Frank’s background is not the typical software founder arc. He grew up in West Berlin, spent a long youth doing graffiti, and slowly moved into graphic design and web projects. That visual and communication experience became his contribution to the founding team: marketing, brand, customer communication, and business operations.

The technical work came from his co-founders, especially the early “genius” DevOps engineer who built the initial infrastructure. The team started as an agency, tired of client-driven roadmaps, and wanted to create a product they controlled — fortrabbit was the result: secure like Fort Knox, fast like a rabbit, a managed cloud hosting service for PHP.

Why a PHP-focused PaaS?

The team was solving their own problem. Heroku was a model for developer experience in the Ruby community, but PHP still powered a huge share of web apps. PHP 7’s improvements revived interest and momentum. The founders saw a clear product-market fit in offering developer-friendly hosting for PHP apps and focused on building something the developer community would actually want to use.

Brand voice: human over gloss

Frank’s approach to communication is deliberately human and accessible. He treats the company like a person — open, readable, and friendly. That’s not a contrived marketing tactic; it’s how they talk to each other internally and how they built the product. Still, Frank recognizes that technical content attracts developers most, so fortrabbit balances a human tone with deep technical resources and documentation.

Co-founder friction and the importance of exit clauses

One of the most instructive parts of the story is how co-founder disagreements nearly derailed the company. Early on, opposing visions and financial strain led key founders to leave. The fallout forced a hard lesson: make exit strategies explicit from day one.

“If you do something in the contract or even in a handshake deal, be clear about exit strategy.”

Practical takeaways: define veto powers, set clear buyout terms, and plan governance for situations when a founder wants out. Those details aren’t glamorous but they stop small conflicts from becoming company-ending problems.

Navigating market shocks: when partners become competitors

Finding a niche community can be powerful, but it can also be fragile. fortrabbit found initial traction in the Laravel community and later in Craft CMS. When platform creators or popular frameworks decide to build their own hosting, smaller hosts can suddenly lose a steady acquisition channel. Frank experienced this twice: conferences became expensive and less targeted, and platform maintainers eventually offered their own hosting.

The lesson here is twofold: diversify acquisition channels and avoid over-reliance on sponsorships or partnerships that can be reversed by the partner’s changing priorities.

Hiring, remote work, and keeping culture

Hiring for a small bootstrapped tech company brings its own tradeoffs. fortrabbit moved from a Berlin-centric team to a remote-first model and recruited internationally. Frank emphasizes a team approach to hiring — technical interviews are led by engineers, while he focuses on cultural fit and communication.

He also highlights the reality that small companies can’t always compete on salary with big tech. The match that works best is someone willing to accept slightly lower pay for greater impact, autonomy, and variety. Screening can be noisy in today’s AI-assisted hiring landscape, so Frank looks for genuine signals: tailored applications, evidence of deep interest, and real craftsmanship.

Bootstrapped by choice? Not always

fortrabbit stayed bootstrapped — but not always by choice. The team applied to accelerators and VCs but failed to secure funding at critical moments. That forced them to learn persistence through adversity. Frank argues that long-term product knowledge, built over 13 years of serving a niche market, is a strength that probably would not have survived a high-pressure VC timeline.

He embraces lifestyle entrepreneurship: modest growth, autonomy, and the ability to manage work around life rather than vice versa. That’s not an argument against growth, but a recognition that for some founders the tradeoffs of VC-backed scaling aren’t worth it.

Operational realities: support, bureaucracy, and profit

Running a hosting business is support-intensive. fortrabbit’s product requires deep technical operations, first-line human support, and constant attention. Frank admits they don’t run like a tidy, high-margin SaaS that an acqui-hirer might want; they’re hands-on, bespoke, and customer-focused.

Local bureaucracy can also be a drain. Shareholder changes, employment law, and healthcare rules in Europe can complicate founder transitions and compensation. Frank’s point is practical: expect administrative friction and budget time to manage it.

Wins, failures, and what mattered most

Biggest wins:

• Deep product knowledge in a specific niche after many years of iteration.
• A loyal community and long-term team members who stayed through ups and downs.
• Creating a product customers rely on while keeping full control over direction.

Biggest failures and ongoing struggles:

• Initial architectural choices that required costly rewrites.
• Dependence on partner ecosystems that later built their own hosting.
• Co-founder misalignment that could have been mitigated with clearer contracts.

Practical hacks and advice for founders

Frank shared simple, actionable ideas that other founders can use immediately:

1. Write explicit exit clauses. Have buyout terms, veto rules, and governance spelled out early, even for friendly teams.
2. Diversify acquisition channels. Don’t rely on sponsorships or partnerships as your sole growth lever; they can evaporate overnight.
3. Be realistic about hiring constraints. Small teams must sell impact and autonomy to attract talent, not just salary.
4. Protect your time and mental space. Encourage real holidays, disconnects, and boundaries for the team. Founders can set the tone by modeling it.
5. Keep customer support human. Developer-focused products still need human-first support and clear documentation to build trust.