Should You Put a Testimonial on Your Product's Empty-State Screen?

The empty state is the most underrated screen in your product. It's the first thing a new user sees after they sign up and before they've done anything — no projects, no data, no history, just a blank panel and a prompt. Most teams treat it as a place to put a friendly illustration and a "Create your first thing" button. But it's also the exact moment a user is deciding whether this product is worth the effort of filling up. That makes it a surprisingly good place for a testimonial — if you use the right one.

The question isn't "can you put a testimonial here?" You can put a testimonial almost anywhere. The question is whether this screen, with this user in this frame of mind, is served by proof. Often it is. Sometimes it badly isn't. Let's separate the two.

Why an empty state is a proof moment, not just a blank screen

Think about what's actually happening psychologically. The user has committed just enough to sign up, but they haven't experienced any value yet. They're staring at nothing, and the small voice that shows up at every empty state is asking: is this going to be worth it? This is the activation cliff — the point where a large share of signups quietly wander off and never return.

A testimonial answers that voice directly. It says: someone like you filled this same empty screen, and here's what they got on the other side. It reframes the emptiness from "this product does nothing" to "this product is waiting for you to start." That reframe is the whole job.

An illustration can't do this. A clever line of microcopy can soften the blank, but it can't provide evidence. A testimonial can — which is why, on the right empty state, it outperforms the friendly-robot cartoon that occupies most of them.

When it works well

Not every empty state is equal. Testimonials earn their place on the ones with high stakes and high hesitation:

• The first-run empty state, where the user has done nothing yet and needs a reason to invest the first ten minutes. This is the single best slot.
• Empty states that require real work to fill — importing data, connecting an integration, inviting a team. The bigger the ask, the more a proof point pays for the effort. A testimonial from someone who says the setup was worth it directly offsets the friction.
• Empty states for a feature the user hasn't tried yet. When they open a section for the first time — reports, automations, a second workspace — a one-line quote about what that feature did for someone else is a nudge toward trying it.

In all three, the testimonial you choose should be about outcome after setup, not generic praise. "Once I imported my customers, I had my first report in five minutes" beats "Great product, love it." The first tells them the empty screen is a short distance from value. The second just clutters it.

When to leave it out

Proof is not free — it costs attention, and an empty state's primary job is to get the user to do the one thing. Skip the testimonial when:

• The empty state is transient and low-stakes. An empty search result, an empty notifications tray, an inbox-zero state — these aren't decision moments. A testimonial there is noise. The user isn't deciding whether to stay; they just cleared their list.
• The call to action is already crisp and the user is already moving. If your data shows people fill this state fast without hesitation, adding proof only slows them down. Don't fix activation that isn't broken.
• It would compete with the primary action. If the testimonial is loud enough to pull the eye away from the "Create" button, you've traded activation for reassurance. The button wins. The proof supports it, quietly, underneath — never above.

The rule of thumb: put a testimonial on an empty state that a user might abandon, not on one they'll clear in passing.

How to place it without cluttering the screen

An empty state lives or dies on clarity, so the testimonial has to stay subordinate to the action. A few practical rules:

1. Keep the hierarchy: headline, primary action, then proof. The testimonial is the third thing the eye lands on, not the first. It reassures the user who hesitated after reading the CTA — it doesn't shout over it.
2. Use one short quote, not a carousel. An empty state is a focus moment. A rotating wall of testimonials turns a clean screen into a landing page and buries the one action you want. One line, one name, one role.
3. Make the quote match the task in front of them. If the CTA is "Import your contacts," the proof should be about what importing contacts unlocked for someone — not about your pricing or your support team. Relevance is what makes it feel like guidance instead of marketing.
4. Attribute it like a real person. Name, role, and company (or a photo) turn a slogan into a witness. An anonymous quote on an empty state reads as filler and does the opposite of building trust.

The deeper principle

An empty state is a fork in the road: the user either invests the first bit of effort or drifts away. Everything on that screen should reduce the perceived cost of investing or raise the perceived reward. A testimonial, placed right, does the second — it's a short message from someone who already walked the path saying it led somewhere good.

So the answer to the question is: yes, on the empty states that matter — the first run, the effortful setup, the untried feature — and no on the trivial ones. Put your proof where a user might quit, keep it beneath the action, and make it speak to the exact task they're being asked to do. Done that way, an empty state stops being a dead end and becomes the quiet start of activation.