Team planning
Monthly Testimonial Collection Plan Template
Most teams ask for testimonials in bursts: a flurry before a launch, then silence for months. A monthly rhythm gives a steadier supply. Work out how many requests you need, then pick a start date to get a dated month.
- A dated month of requests from one start day
- Batches sized to your request email allowance
- A review slot before the next month begins
The problem, solved
Why monthly collection stalls, and how StoryProof keeps the rhythm
We never know how many to ask
Without a target, someone sends twenty requests one week and none for the next six, and the homepage carousel still shows last year’s quotes.
With StoryProof: Your plan sets a monthly ceiling on request emails, which gives the batch size a hard upper edge. Review request emails per month: Free 10, Starter 100, Pro unlimited.
Every batch starts with hunting for names
If building the list takes an afternoon, the batch slips to next week, then next month.
With StoryProof: Contacts and smart lists are on every plan, so the people for this month’s batch can be kept ready inside StoryProof.
Reminders eat the second half of the month
Chasing each non-reply by hand turns a one-hour task into a daily chore, and it is the first thing dropped when work gets busy.
With StoryProof: From Pro, the follow-ups automation sends a reminder three days after a request and a last email four days later, and stops for anyone who has replied.
Answers pile up without a review slot
A good month of collection is wasted if the submissions sit unread until the next quarter.
With StoryProof: Everything lands in the approval queue first, so one fixed review slot at the end of the month clears the batch before anything goes public.
Nobody looks back at last month
Without a look back, the same batch size is repeated whether it worked or not.
With StoryProof: An analytics dashboard is included on every plan, so the month-end review has a place to start.
Flip the switch to see how StoryProof handles each one.
Work backwards from the goal
Plug in your own numbers. The reply share comes from your last few months, not from a benchmark.
Timeline
Your month, dated
Choose the first working day of the month. The plan places two request batches, the reminders, a review slot and the look back.
Day 0
Build this month’s list
Pick customers who reached a result since the last batch. Drop anyone asked in the last few months.
Day +1
Send batch one
About half of this month’s requests. Keep the rest back so the allowance covers batch two.
Day +4
First reminders go out
Three days after batch one. If you have the follow-ups automation, it sends these for you.
Day +8
Last reminders for batch one
Four days after the first reminder, then stop chasing this group.
Day +12
Send batch two
Adjust its size: if batch one replied well, you may need fewer requests than planned.
Day +15
Reminders for batch two
Same rhythm as batch one, so nobody is chased twice in a week.
Day +24
Review and approve
One sitting to read, tag and approve or reject everything that came in.
Day +27
Look back and size next month
Count requests sent and usable testimonials received. Update the reply share in the table above.
Dates are worked out in your browser. Nothing is saved.
How a filled-in plan reads
Illustrative plan, not a real customer
A small B2B team wants {goal} new testimonials this month to refresh its pricing page and two landing pages.
Last quarter roughly one request in {n} became a usable testimonial, so it plans {requests} requests, split into two batches.
It checks that number against its plan’s monthly request emails before sending, and keeps a few back for customers who reach a milestone mid-month.
- Batches
- Two, eleven days apart
- Reminders
- Automated, stop on reply
- Review slot
- Day 24, one hour
In StoryProof
Run the month in StoryProof
- You will need
- A StoryProof workspace
- A goal for the month and last month’s reply share, if you have one
- 1
Keep a ready list of candidates
Add customers as contacts when they reach a result, and group them in a smart list for the next batch.
- 2
Check the batch against your allowance
Review request emails per month: Free 10, Starter 100, Pro unlimited.
- 3
Send each batch by email
StoryProof sends requests by email only, so plan any phone or in-person asks separately and share the link yourself.
- 4
Let reminders run on their own
From Pro, follow-ups wait three days, remind, wait four more days and send a final note, skipping anyone who unsubscribed.
- 5
Clear the queue in one sitting
Nothing goes live until it is approved, so a single monthly review keeps the library tidy.
What happens next: After two or three months your reply share settles, and the plan becomes a ten-minute job on the first working day.
Before you start
Where the plan needs your judgement
The allowance is a ceiling, not a target
Sending the maximum to customers who have not reached a result yet produces polite, thin answers.
Reply shares change
A new audience or a new question will answer differently. Treat last month’s share as a starting guess.
Quiet months happen
If few customers hit a milestone this month, ask fewer people rather than padding the list.
Hand-shared links are outside the plan
Links you post or print bring replies the schedule cannot predict. Count them in the look back, not the forecast.
FAQ
Questions people ask
Short answers to what usually comes up next.
How many testimonials should we ask for each month?
Start from the number of spots you need to fill or refresh, then divide by the share of requests that usually become usable. That gives a request count rooted in your own results.
Is one big batch better than two smaller ones?
Two batches let you adjust mid-month. If the first replies well, the second can be smaller, and the review work does not all land on one day.
Should the same customer be asked every month?
No. Leave a gap of several months, and ask again only after something new has happened for them, such as a renewal or a new result.
What if our plan’s email allowance is smaller than the request count?
Ask the customers with the clearest results first and share the collection link by hand for the rest, or move to a plan with a larger allowance.
Still have a question? Ask the StoryProof team or book a demo.
Put next month on a schedule
Keep a candidate list, send requests in batches and let reminders run themselves.
Last updated 2026-11-05.