Proof for the process
Testimonials on How It Works Pages
A how it works page walks visitors through your process in three to five steps. Somewhere in there is the step they do not believe: setup in a day, a designer who gets it first time, a claim that is handled for you. That is where a customer’s word does the most. Answer four questions about your process to see which testimonial pattern fits the page.
- Proof at the step visitors doubt
- Or one customer’s story across every step
- Questions that get step specific answers
The problem, solved
Why process pages lack proof, and how StoryProof attaches it to steps
Nobody believes step two
“We handle the migration for you” is the step every visitor doubts, and the page offers nothing but your word for it.
With StoryProof: Tag testimonials by the step they talk about, then build a small widget from the “migration” tag and place it beside that step.
Our testimonials never mention a step
Customers praise the result, not the onboarding call or the first draft. You have nothing that speaks to the process.
With StoryProof: From Pro, a multi-step form asks several questions in one sitting, so one can ask what a particular step was like.
Step quotes from strangers feel disjointed
Five different people at five steps reads like a collage. Some processes are better shown through one customer from start to finish.
With StoryProof: Ask one customer to talk through their experience step by step, by video, audio note or text, through a single collection link.
Video beside every step is too much
A video next to each step makes the page slow and noisy, and most visitors only want a sentence.
With StoryProof: Mix formats. Audio notes play in widgets alongside written testimonials, so a short voice clip can sit beside one step and text beside the rest.
Five widgets means five scripts
One widget per step sounds tidy until someone pastes the same script five times into the page.
With StoryProof: The embed.js script can load once per page and fill every StoryProof widget div on it.
Flip the switch to see how StoryProof handles each one.
Placement picker
Which testimonial pattern suits your how it works page?
Answer for the process your page describes.
Answers are scored in your browser only.
Live preview
One story told along the process
The working Timeline layout with sample testimonials from stock personas, not StoryProof customers.
Review from Google“We put the review wall under our pricing table and prospects quote the reviews back to us on calls.”
Review from Trustpilot“StoryProof made collecting and showing real customer video reviews effortless for us.”
Review from G2“The widget looks native on our site. Nobody can tell it is embedded.”
Review from Google“Collecting video reviews used to be the hardest part. Now it takes one link.”
Prompts
Questions that get answers about a step
Ask about the step you need proof for, not about the whole experience.
The step visitors doubt
- Before you started, what did you expect this part to be like?
- What actually happened at this stage?
- How much of your time did it take?
Leave out
- Was the migration easy? (invites a yes and nothing more)
A customer who went through everything
- Walk us through your first week with us.
- Which step mattered most, looking back?
- What would you tell someone about to start step one?
In StoryProof
Put proof beside the steps
Step 1 of 4
Tag testimonials by step
Read your library and tag each testimonial with the step it mentions, if any. The empty tags are your collection list.
Step 2 of 4
Ask about the missing steps
From Pro, add one question per step to a multi-step form. Customers can answer by video, audio or text.
Step 3 of 4
Build a widget for each slot
One per doubted step, or one after the last step, chosen from the matching tag.
Step 4 of 4
Embed with a single script
Place each widget div beside its step and load embed.js once for the page.
Before you start
What this plan does not settle
What this does not cover, and what to check on your side. Better to know now than after launch.
- 01
Proof cannot fix a confusing process
If visitors do not understand a step, rewrite the step. A testimonial beside an unclear explanation does not clear it up.
- 02
Old quotes can describe an old process
A testimonial about a step you have since changed is misleading. Retire it when the step changes.
- 03
Keep the steps readable
Proof beside every step can bury the process. If the page feels crowded, keep only the quote at the most doubted step.
- 04
Other page types are covered elsewhere
Homepages, product pages and thank-you pages are in our guide to where testimonials go on a website.
FAQ
Questions people ask
Short answers to what usually comes up next.
Should a how it works page have testimonials at all?
Usually yes, but few. One quote at the step visitors doubt often does more than a block of general praise at the bottom.
Where exactly should the testimonial go?
Beside or just under the step it talks about, so the visitor reads the claim and the proof together.
Can one customer’s story replace the steps?
No. Keep your steps as the explanation and use the story alongside them. Visitors still need the plain version of what happens.
What if no testimonial mentions a particular step?
Ask recent customers about that step specifically. Until you have one, leave the step without proof rather than using a quote about something else.
Still have a question? Ask the StoryProof team or book a demo.
Proof at the step that needs it
Tag testimonials by step, place a widget beside each one, and load them all with one script.
Last updated 2026-11-07.