Review templates
New Customer Welcome & First Success
A first conversion has occurred.
KPI: First-success rate or proxy; first-to-second purchase/booking rate.
View template →Review Generation
There is a legitimate signal that the customer has successfully experienced value.
KPI: Review request conversion rate; review volume/quality monitoring as appropriate.
View template →12-Month Commercial & Customer Moment Calendar
Annual intake layer. It is not a send calendar; it identifies legitimate reasons communication may be needed.
View template →Launch Countdown Workback
Back-plan material launches from the customer-facing date rather than discovering dependencies at the end.
View template →First-Success Support
First purchase/service milestone.
KPI: Success proxy; support request rate; subsequent conversion.
View template →Review Request
Qualifying successful experience.
KPI: Review conversion rate.
View template →90-Day Growth OS Install
When installing the broader connected system rather than a single campaign.
View template →Satisfied Customer → Advocate
Maps how a satisfied customer becomes a reviewer, referrer, and long-term advocate.
View template →Ask For Review
[Thank/recognize successful experience]. [Ask for an honest review]. [Direct destination/link].
View template →Barrier → Response Starter Matrix
A quick-reference matrix that matches common customer barriers — awareness, trust, price, effort — to the right type of response.
View template →LDG Offer Ladder Quick-Start
An 8-level offer ladder, from plain value communication up to monetary discounts, so you reach for the weakest offer that will still work.
View template →Lifecycle Health Scorecard
Reviews core lifecycle metrics — conversion, repeat rate, at-risk recovery, VIP retention — against your own baseline, not a universal benchmark.
View template →Customer Experience Risk Scorecard
Flags customer-experience risk — poor timing, excessive frequency, contradictory messages — before a send goes out.
View template →Evidence & Standardization Scorecard
Decides whether a test result is strong enough to become a standard template or whether it should stay client-specific.
View template →