Retainer offer and acquisition review tutorial
A week 4 tutorial for test repeatability through one inspectable output.
When this is the right output
Use this when one case exists and you need to decide whether to keep selling the service.
Prepare before you start
- One case or sample that can be shown
- A second target-user batch or distribution channel
- A decision rule for continuing, narrowing, or stopping next month
Public case breakdown
How Stellantis &You UK used Make for aftersales messaging
The aftersales team was overloaded by phone and in-person communication. In Make's case, intent and sentiment classification routed ordinary messages to automation and subtle dissatisfaction signals to human follow-up.
Source
Make customer care success story47,000+ messages analyzed and 18,000+ handled automatically over 12 months
It did not start as a huge system
Classify first
The workflow judges intent and sentiment before attempting any response.
Keep human boundaries
Negative, ambiguous, and risky messages are escalated to people.
Track outcomes
The team measures handled volume, escalation, and customer feedback instead of showing only a workflow diagram.
What to copy
Sell saved time, not the diagram
Clients buy less repeated work and fewer missed issues, not the automation canvas.
Automate low-risk work first
Classification, sorting, notification, and logging are safer first steps than full auto-replies.
Price from before-after evidence
Record manual time and post-automation time before quoting a pilot.
Build a small version
Collect 20 historical messages
Pick one niche such as clinics, training firms, or local services.
Create 3 labels
Use only no reply needed, needs human, possible churn.
Run 5 reviewed tests
Let AI classify, review manually, then calculate accuracy and time saved.
Do not promise fully automated support first. Message triage and human alerts are easier pilots to sell.
Build the first version
Package the case
Turn the strongest result into a case your target users can understand.
Prepare a second batch
Choose a similar audience or channel instead of changing direction.
Run distribution
Use the same case to test hooks, channels, or outreach.
Make the decision
Use pilots, payments, subscribers, bookings, or clear needs to decide next month.
Copy-ready templates
Case opening
I used [method] to help [audience] handle [problem] and produce [result]. Now I am testing whether it fits similar cases.
Second-batch outreach
I just finished a small case close to your situation and would like to know whether it could solve [problem] for your team too.
How to decide the next step
Continue when
- The second batch creates 2 pilot or paid intents
- Someone discusses a retainer or ongoing service
- You can explain acquisition cost and next step
Change direction when
- The second batch creates no clear demand.
- The case only convinces the original customer.
- You still cannot name the acquisition source.
Return to the result after you finish this output
In week four, use the case to reach a second batch and test repeatable acquisition or retainers.