Kudobox

For saas

The testimonial that survives your next release

Software changes every few weeks. A testimonial praising a screen you have since removed reads as out of date to exactly the person you were trying to convince.

No password. You get a private dashboard link right after this — bookmark it, that's your login.

Why it is hard here specifically

Most SaaS testimonials are about features, and features are the part of a product with the shortest life. The ones that keep working are about the problem the customer had — which does not change when you redesign the settings page.

What Kudobox does about it

  1. Ask about the problem, not the screen

    “What were you doing before this?” ages well. “I love the new dashboard” does not survive the redesign.

  2. Show the company, never their logo

    The companies layout sets the names your customers typed as text. A logo would say that company endorsed you, which is not what one employee's testimonial means.

  3. Read them out through the API

    If your marketing site is your own code, the widget is optional: the API hands them back as JSON, already filtered to what may be published.

  4. Watch the language change

    What your customers keep saying, read back as prose, is where you find out they describe your product in words you have never used on your own site.

The questions worth asking

Copy these into your form and change them to sound like you. Each one is written to produce a sentence you could actually publish — which is the whole difference between a testimonial and a compliment.

  1. What were you using before, and what made you stop?
  2. What was the moment you knew this was going to work?
  3. What does your week look like now that it did not before?
  4. Who else on your team uses it, and for what?
  5. What nearly stopped you signing up?
  6. What would you tell somebody comparing us with the obvious alternative?

The limit, said plainly

No report here will produce a figure your customers did not give you. If you need “40% faster onboarding” on your page, it has to come from a customer who said it.

Your customers already wrote the words

Send one link and their words arrive here instead — with the date, with the permission, and read for risk before you publish.

Everything it does