He demoted his SaaS to sell a service and 4x'd revenue in 12 months

Source note Episode guide Original audio

Summary

This The SaaS Podcast episode features Omer Khan interviewing Farzad Rashidi about how Responna moved from self-serve outreach SaaS into a done-for-you AI Visibility Service. The story links a SaaS growth plateau, customer execution limits, outcome-priced work, publisher relationships, and Generative Engine Optimization into one operating case. Its core lesson is that Responna did not abandon software; it redirected software, AI, and workflow design toward delivering the customer-visible outcome.

Key Claims

  • Responna began as an internal tool at Visme for finding websites, backlinks, collaborations, and brand mentions, then launched as a standalone product in 2019.
  • The SaaS product plateaued because churn caught up with new sales; customers liked the tool but often lacked time, people, writing capacity, and publisher follow-through.
  • A marketing-agency customer resisted an $800 monthly software subscription but accepted a much larger pay-per-result arrangement once Responna offered to do the work.
  • The first service version was delivered manually with a spreadsheet and internal operator, then expanded into a client portal, publisher portal, and back-end order/delivery system.
  • Responna reports that the customer grew from roughly $7,000-$8,000 per month to about $65,000-$70,000 per month, and that company revenue grew fivefold over the prior 12 months.
  • Farzad frames the model as productized service rather than an ordinary agency: pricing, volume discounts, add-ons, publisher operations, and delivery options are structured so work can move through an assembly-line process.
  • The AI visibility method starts by testing target buyer prompts in tools such as ChatGPT, Claude, Google AI Overviews, and Gemini, then identifying which third-party pages are being cited.
  • Farzad argues that directly pitching already cited sites has very low yield, so Responna uses Lookalike Publisher Outreach to find similar publishers with authority and relevant keyword profiles.
  • The service creates fresh third-party content that resembles already cited pages, places the client brand prominently, and tries to move the brand into the citation pool over time.
  • Responna’s moat is presented as a combination of software, AI automation, process design, aggregated demand, proprietary publisher data, and a Publisher Relationship Moat.

Key Quotes

“service as software” - market frame Omer uses for AI-native services.

“not magic” - Farzad’s caveat that AI visibility work can be done manually in-house.

“less than a 1% success rate” - Farzad’s estimate for directly pitching already cited sites.

Connections

Contradictions

  • No direct contradiction with existing wiki content. The episode reinforces the wiki’s Service As Software and Result As A Service threads with a concrete SaaS-to-service pivot, while adding a sharper distinction between AI search analytics and done-for-you AI visibility delivery.
  • The source adds a useful tension to Generative Engine Optimization: optimization is not only prompt testing and measurement, but may require third-party publisher supply, fresh content, and off-page SEO work that resembles older link-building systems.