Packages without price tags
Testimonials on Service Packages Pages
Your packages page lists three tiers of service and a “Get a quote” button where a price would be. Visitors cannot compare numbers, so they are asking two other questions: which package is for someone like me, and will the quote be fair? Generic praise answers neither. Answer four questions about your page to see which proof goes where.
- Proof that helps visitors pick a package
- Quotes that take the fear out of “request a quote”
- Where each one sits on a page with no prices
The problem, solved
Why packages pages struggle with proof, and how StoryProof fills each slot
Visitors cannot tell which package suits them
Three tier names and a list of inclusions mean little to a buyer. They want to see someone like them who picked a tier and was glad.
With StoryProof: Tag each testimonial with the package the client bought, then build a small widget per package from its tag.
People are scared of the quote
No price on the page makes some visitors assume it is expensive or that the quote will be a sales pitch. They leave rather than ask.
With StoryProof: From Pro, a multi-step form can ask several questions, so one can be about the quoting process itself. Put those answers beside the quote button.
Nobody believes the top tier is worth it
The full service package looks like an upsell. Without someone who chose it explaining why, visitors drop to the cheapest.
With StoryProof: Ask clients on the top package to say why in their own words, by video, audio or text, through one collection link.
Four widgets on one page feels heavy
A widget under each package plus one by the button means several embeds, and nobody wants to add a script four times.
With StoryProof: The embed.js script can load once per page and fills every StoryProof widget div on it. How many widgets you can have depends on your plan.
Flip the switch to see how StoryProof handles each one.
Placement picker
What should your packages page lead with?
Answer for the packages page as it stands today.
Your answers are scored in your browser only.
Each slot on the page, and the testimonial it needs
Live preview
A single focused quote under a package
The working Quote Spotlight layout with sample testimonials from stock personas, not StoryProof customers.
We put the review wall under our pricing table and prospects quote the reviews back to us on calls.
In StoryProof
Fill every slot on the packages page
Step 1 of 4
Tag what you already have by package
Go through the library and tag each testimonial with the package that client bought. Untagged ones show where the gaps are.
Step 2 of 4
Ask for the missing angles
From Pro, add a question about package choice and one about the quote process to a multi-step form, and send it to clients on each package.
Step 3 of 4
Build one widget per slot
One widget per package from its tag, plus one for the quote button with the process quotes.
Step 4 of 4
Embed them with one script
Place each widget div in its slot and load embed.js once on the page.
Before you start
What the picker cannot tell you
What this does not cover, and what to check on your side. Better to know now than after launch.
- 01
Check any price a client mentions
If a client mentions what they paid, check you are happy for that figure to be public before you approve it.
- 02
It does not know your conversion data
If you can measure where visitors leave the page, that beats the picker’s rules.
- 03
A small library cannot fill every slot
If a package has no testimonial yet, leave its slot empty rather than borrowing a quote from another package.
- 04
Placement on other pages is covered elsewhere
Homepages, product pages and thank-you pages are covered in our guide to where testimonials go on a website.
FAQ
Questions people ask
Short answers to what usually comes up next.
Should a packages page show testimonials if it has no prices?
Yes, and they matter more. Without prices, proof is one of the few things helping visitors choose a package and decide to ask for a quote.
How many testimonials per package?
One short one is usually enough under each package. More than that pushes the inclusions and the button out of view.
Is it fine for a testimonial to mention what the client paid?
Only if the client agreed and you are comfortable with that number being public. On a page that hides prices, a quoted figure can undercut your quotes.
What if clients do not know which package they bought?
You do. Tag their testimonial from your own records rather than asking them.
Still have a question? Ask the StoryProof team or book a demo.
Proof for every package, even without a price
Tag testimonials by package, build a widget for each slot, and load them all with one script.
Last updated 2026-11-07.