A System to Produce Case Studies: How to Document Client Results in LATAM 2026

The most valuable marketing asset for selling services is a documented result from a real client, and almost everyone produces them by accident — one every eighteen months, whenever they happen to remember. The problem isn't that your clients lack results. It's that nobody captured the starting point, and without that number the case can no longer be built.
Case Study vs Testimonial: Which One Actually Sells
A testimonial says you're good. A case study shows the before, the process and the after. The difference isn't length — it's function. A testimonial confirms an opinion; a case demonstrates a mechanism.
|
|
Testimonial |
Case study |
|---|---|---|
|
What it communicates |
That the client was satisfied |
What changed, how, and over what period |
|
What the prospect thinks |
"Good for them" |
"That's exactly my problem" |
|
Verifiable |
No |
Yes, with a starting point and an end point |
|
Useful for |
Reinforcing trust late in the funnel |
Starting the conversation in the first place |
|
Requires |
Asking for it |
Having measured it from day one |
That last row decides everything. A testimonial can be requested at any time; a case study only exists if someone wrote down where the client stood when they started. Which means producing case studies isn't a marketing task — it's an onboarding task.
The Data You Have to Capture Before You Start
If a client arrives, you work together for six months, and then you ask "where were you before?", the answer will be an approximate memory. And an approximate number can't be published.
What to record in the first week of work:
- The metric you're going to move, chosen with the client and written with its unit: new clients per month, monthly revenue, appointments booked per week, cost per lead
- The current value of that metric, with the date
- The problem in the client's own words, verbatim, without you rephrasing it — this quote is what opens the case later
- The stated goal and the timeframe they expect
- Preliminary permission, asked casually: if we get a good result, would you be willing to let us tell the story?
That last point changes the economics of the whole process. Asking at the start, when nothing is at stake and the client is enthusiastic, gets a very different answer than asking at the end, when it sounds like you're requesting a favor.
How to record it without building a complicated system
You don't need custom fields or integrations. In the ASIO CRM, the client record has notes, tags and an assigned owner — that's enough if you use a fixed convention:
- When the sale closes, write a short block in the record's notes with the five items above, always in the same order and with the date
- Add a tag like base-captured so you can later filter who has a starting point and who doesn't
- If the client gave preliminary permission, add a second tag: preliminary-consent
- Store the onboarding document in the Drive connected to your account, linked to the client record
What matters is the convention, not the tool. A notes block with a fixed format is searchable and sufficient; an elaborate system nobody fills in is worth nothing.
The Three Moments to Ask for the Case
The same client produces three different cases depending on when you ask. These aren't alternatives — they're three assets with different uses.
|
Moment |
What it captures |
What it's for |
|---|---|---|
|
First visible result |
The emotion of the initial change, the most spontaneous quote |
Short content, ads, posts |
|
End of the engagement |
The full process, what was done and why |
Sales page, commercial proposal |
|
Six months later |
Whether the result held, and what happened to the business |
The most persuasive case for high-ticket |
The first visible result is the easiest moment and the most neglected. When a client messages you "hey, I closed two this week" — that's the material. Ask right there, in that same conversation, before it becomes normal. A one-minute voice note describing what happened is worth more than an interview scheduled three months later.
The end of the engagement is when you have the complete arc and the client has perspective. That's the moment for the formal interview.
Six months later is the one almost nobody does and the one that sells hardest in high-ticket services, because it answers the prospect's real objection: does this hold up once the consultant is gone?
If you use ASIO Messages, the reminder for the six-month follow-up can be scheduled into the flow at closing, so it doesn't depend on you remembering.
The Case Structure That Converts
Five blocks, always in the same order. This is the template:
|
Block |
What goes inside |
Where it comes from |
|---|---|---|
|
Starting situation |
The problem in the client's verbatim words, plus the starting number with its date |
Onboarding notes + interview |
|
Why they were stuck |
What they had tried before and why it didn't work |
Interview |
|
What was done |
The two or three concrete decisions that moved the needle — not the full task list |
Your own project notes |
|
Result |
The end number, in the same unit and measured the same way as the starting one |
Closing notes |
|
Timeframe |
How much time passed between the two numbers |
Dates on the two records |
Two rules about this structure. First: the "what was done" block should hold two or three decisions, not fifteen steps. A case that lists everything you did reads like a status report; one that names the two decisions that mattered reads like judgment — and judgment is what the prospect is buying.
Second: the end number has to be measured the same way as the starting one. If you counted "new clients per month" at the start and "pipeline opportunities" at the end, the case isn't comparable, and an attentive prospect will notice.
The 20-Minute Interview That Produces the Material
Schedule the interview with a Calendly link so you don't lose time coordinating, record it with permission, and ask exactly these questions in this order:
- "Before we started working together, how would you describe the situation? Tell me like you'd tell a friend."
- "What had you tried before that, and why didn't it quite work?"
- "When was the moment you noticed something was changing? What exactly happened?"
- "Of everything we did, what would you say moved the needle most?"
- "What would you say to someone who's today where you were six months ago?"
Question 1 produces the quote that opens the case. Question 2 is the one most people skip and the most valuable: it establishes that the problem was genuinely hard, which is what makes the result credible. Question 4 usually gets you a different answer than the one you would have given — and the client's version is the one to use.
Twenty minutes is enough. If the interview runs to forty, the extra material rarely makes it into the final case.
After the interview, write the result and the main quote into the client record's notes while it's fresh, and add a case-ready tag. That tag is what later lets you see at a glance how many cases you have available.
Consent, Confidentiality, and What to Do When the Client Won't Appear
The preliminary permission you got during onboarding isn't final approval. Before publishing, you need sign-off on the actual text.
The process that works: send the finished draft and ask for approval of what's written, not permission in the abstract. It's far easier to say yes to a text that already exists and that the client can correct than to authorize something they haven't seen.
Keep that approval in writing — a message saying "yes, publish it" is enough for most cases, and for corporate clients a signed document filed in your account's connected Drive is worth the extra step.
When the client won't authorize their name, the case still works. You have three levels of anonymity:
- Sector and region: "an HR consultancy in Guadalajara"
- Profile only: "a business coach with six years of experience serving SMB clients"
- Structure only: the problem, the decisions and the timeframe, without the exact figure — replacing the number with the type of change ("went from depending on referrals to having a predictable channel")
The third level loses force, but it's still infinitely better than having nothing. And it's the right format when the client operates in a niche so small that sector and region already identify them.
What you never do: publish an anonymized case and then, in a sales conversation, reveal whose it was. If you accepted anonymity, it holds in private too.
From One Case to Five Assets, and the No-Exaggeration Rule
A well-documented case isn't an article — it's raw material for five formats:
- The long page: all five blocks, with the verbatim quotes. This is what you link from a proposal
- The short video: just question 3 from the interview, the moment the client noticed the change
- The carousel: one template block per card, in order
- The ad paragraph: starting situation and result, in two lines
- The objection response: the "what they had tried before" block is your best answer when a prospect says they've already tried something similar
And the rule that holds all of it together: never exaggerate, never round up, never merge two clients into one "representative" case. A modest, verifiable case sells better than a spectacular one the prospect doesn't believe.
The services market in LATAM is saturated with inflated promises, and the prospect who reaches your case already distrusts by default. A contained result, with the real timeframe and an honest starting point, does something no big number can: it sounds true. And if the number is verifiable, you can defend it on a call — which is exactly where the sale closes.
Ready to Get More Clients?
At Asio, we teach you to implement these strategies step by step through the Mastery program — combining Meta Ads and conversational automation so you get more appointments and close more sales, without relying on manual messages.


