How Ev Chapman Automates Collecting Testimonials for Her Business
Ev Chapman, a writer and creative entrepreneur who helps creators build, share and monetize their knowledge, explains how she reduced testimonial collection to a short, repeatable workflow for her courses and digital products.
Who is sharing the workflow
Chapman describes herself as a writer and creative entrepreneur. Her work centres on helping creators build, share and monetize their knowledge, including courses and digital products built with tools such as Notion and Tana. That product mix matters for testimonials: feedback needs to be gathered inside the learning experience and also surfaced on sales pages where future buyers decide.
The friction in the earlier setup
Before adopting a dedicated collection tool, Chapman assembled a workaround from separate pieces. A form gathered responses, an automation notified her when something new arrived, and she then had to move approved material onto a landing page or create a design in Canva. The chain was workable, but it involved many steps for a single testimonial. She says the effort likely reduced how many requests she made early on, because the process felt burdensome.
The streamlined workflow
The streamlined version changes where the work happens. A collection link sits inside each course, typically in a module toward the end. Customers open it, write their testimonial, and Chapman receives an email notification. She reviews the submission, approves it, and sends it to the wall. Because the wall is embedded, approved testimonials appear wherever that embed is placed without rebuilding each page.
Where requests and displays sit
For courses, the request lives in a late module so learners encounter it after completing the main material. For products, Chapman sends an email roughly a week after purchase. Widgets on landing pages then display the approved testimonials. The pattern separates two jobs: asking at the right moment, and displaying proof where it supports a purchase decision.
What she values in the setup
Chapman highlights ease of setup, including getting the system working with a Notion website, as a practical advantage. She also values being able to contact a creator directly to request new features, and she describes the price point as suitable for independent creators. Those are her reported preferences, not independently verified product claims.
A checklist for simplifying your own process
A useful takeaway is to audit the path from request to display before adding more tools. Ask: Can the customer submit without leaving the course? Does the owner get notified without polling a form? Is approval a single decision? Does an approved item update every display automatically? If any answer is no, that step is a candidate for simplification. Chapman also notes that visitors sometimes ask her what she uses after seeing testimonials on her site, a reminder that visible proof can generate peer interest as well as buyer confidence.
| Stage | Earlier approach | Streamlined approach |
|---|---|---|
| Collection | Form as a separate step | Collection link inside the course or product flow |
| Notification | Separate automation to alert the owner | Email notification when a testimonial arrives |
| Approval and display | Manual update to landing page or new design in Canva | Approve once and send to an embedded wall that updates everywhere it is embedded |
| Follow-up for products | Not described as a timed email | Email about a week after purchase |
Based on Chapman's interview account; not an independent product comparison.
Frequently asked questions
When should a course creator ask for a testimonial?
Place a collection link inside the course near the end, and for standalone products send the request by email about a week after purchase. That timing puts the ask after the customer has had time to use what they bought.
What happens after a customer submits a testimonial?
Review each submission, approve the ones you want to publish, and send them to the wall. With an embedded wall, approved items update in every place where that embed is used, so you do not need to rebuild landing-page graphics for each new entry.
Why did the manual setup discourage testimonial requests?
The earlier setup required a form, a separate automation for notifications, and manual design work for the landing page. Each extra step made collecting feedback feel like a hassle, which can discourage early requests.
Did the testimonial display prompt questions from other creators?
Chapman reports that people sometimes ask what she uses after hearing her mention it or seeing it on her website, which suggests the display itself can prompt peer interest.