Skip to content

How a SaaS Portfolio Operator Collects Testimonials Across Multiple Companies

A founder running several product-led SaaS businesses needs a repeatable way to turn satisfied users into proof that helps free users upgrade. This guide explains the workflow used across a portfolio: collect text and video testimonials in context, display them consistently, and use critical feedback separately for improvement.

Why testimonials matter for product-led SaaS

Danny Chu previously built and exited a startup and now helps run a portfolio of SaaS companies with partners. For product-led businesses, testimonials serve two purposes: they reassure prospects, and they give existing free users a reason to move to a paid plan. The same collection system can be repeated for each company instead of rebuilding forms and display pages from scratch.

The gap between a rating and a testimonial

The team first relied on NPS submissions. Those ratings were strong, but a high score did not turn into a completed testimonial when customers were sent to a separate form. That distinction matters: a rating measures likelihood to recommend, while a testimonial is a publishable statement that needs its own clear request and format.

A repeatable collection and display workflow

After switching, collection pages were placed throughout onboarding, on websites, and inside the product. Customers could submit text or video testimonials through a dedicated page. Approved responses were then shown through a wall of fame and testimonial widgets for each portfolio company. Examples linked in the interview include ScreenshotAPI, ColdDM and Inlytics.

Portfolio testimonial checklist

Use this checklist for each product in a portfolio:

  • Create one collection page per company so responses stay attributable.
  • Put the request in onboarding, in-app moments and on the website.
  • Offer both text and video formats.
  • Route negative comments to the product team for improvement, not to the public wall.
  • Publish approved testimonials on a wall and embed selected items with widgets.
  • Invite strong contributors to expand a short quote into a detailed customer story.
  • Reuse the same process for every portfolio company to keep operations consistent.

How the proof was reused

The operator reported that testimonials supported conversion and sign-ups, including movement from free use to paid use. Short testimonials were also used as starting points for longer customer stories on the blog, intended to support organic traffic. The main practical advantage was simplicity: one interface handled the workflow instead of combining several complex tools.

Testimonial workflow at a glance
StageWhat happensPurpose
CollectText and video submissions through dedicated pages in onboarding, in-app and website locationsReduce friction after a positive experience
ReviewSeparate publishable praise from critical feedbackUse criticism for product improvement
DisplayWall of fame and widgets for each companyProvide consistent social proof
ExpandTurn selected testimonials into detailed customer storiesSupport blog content and organic discovery

Workflow summary based on the interview account; product availability must be confirmed by the owner.

Frequently asked questions

Why did a high NPS score not lead to testimonials?

A high score signals willingness to recommend, but it does not automatically produce a usable public quote. The gap described here was between receiving a strong rating and getting the same person to complete a separate testimonial form. Closing that gap requires a direct, low-friction testimonial step at the moment of enthusiasm.

Where should a testimonial collection page be placed?

Place the collection link or page where customers already complete onboarding, inside the product, and on the website, so the request appears in context rather than as a disconnected form. Collect text and video in the same workflow, then reuse approved items on a wall of fame and through widgets.

What should you do with negative testimonials?

Use negative feedback privately to identify product or service improvements, while publishing only testimonials you have permission to display. That separation lets critical comments improve operations without turning a public wall into a complaint channel.

How can short testimonials become longer content?

Invite a willing customer to expand a short testimonial into a fuller story for the blog. That longer format can support organic discovery, while the original short quote remains available for product pages and widgets.