Fifteen years building SaaS across European scale-ups, including the unicorn Brevo, compressed into two words. Malith Gamage bootstrapped Zapdigits, a client-reporting tool for marketing agencies, and his survival advice is not a framework. It is do not die. Stay alive three or four years and you are fine. Everything else in this episode is the operational discipline that makes that possible.

• Survival is the strategy, not a precondition for one. No in-house hires, infrastructure scaled only when needed, and a year of AWS credits used as a cash-flow cushion.
• White labelling sits on every plan, not the top tier. Agencies have to look more put-together than a client’s internal marketing team, so branding is the product rather than an upsell.
• He ships AI visibility reporting and openly doubts it. Ask the same question five times and get five answers pulled from five places.
• Domain authority did not predict who got cited. His own unpromoted, zero-authority domain was the source models pulled from, while the promoted one was not.
• A lifetime deal run as a feedback engine. The value was buyers who kept sending feature requests, not the one-off revenue.

• Do not die
• Your AI is only as smart as your schema
• Shipping a feature he does not fully trust
• White labelling, and a lifetime deal as a feedback engine
• Chapters and timestamps
• People, ideas and sources mentioned
• Questions this episode answers
• Go deeper

Some main advice is don’t die. Like as long as you can stay for like three, four years alive, then you’re good.

Unromantic, and more useful than most strategy. The failure mode for a bootstrapped tool is almost never being out-competed on features. It is running out of runway during the years when nothing is visibly working.

So the discipline is structural: no in-house hires, infrastructure scaled only when demand actually arrives, and a year of cloud credits treated as a cash-flow buffer rather than free compute to burn.

Your AI is smart as your schema. As long as you give the correct data and the correct description, then you will get good answers back.

He draws the parallel to MCP without prompting, and it is the reason he pipes context in before asking anything: pull the Analytics data first, describe it properly, then ask the question. The quality ceiling is set at the data-description step, not at the model.

I don’t even know sometimes if you ask the same question five times you get five different answers they pull out from five different places.

Zapdigits aggregates brand visibility across several models and averages it into a score for agency clients. He will t...