The buyer can see that you understand their market, buying motion, and constraints.
Cold email proof supports a cold email offer more directly than proof from an unrelated channel.
Match the result to the prospect's actual objective instead of choosing the largest number.
Use recency as the tie-breaker after the proof is relevant, not before.
A prospect asking for recent work is not requesting an archive. They are asking whether your claim is safe enough to investigate.
This happened recently in our own outbound: a prospect asked to see work relevant to a boutique business. The wrong answer would have been a list of every campaign, screenshot, article, and client result we could find. The useful answer is a short Google Doc built for that decision.
Treat the document as a private sales page. It should show that you understood the request, select the most comparable proof, explain the transformation, offer one useful insight about the prospect's situation, and make the next step almost frictionless.
Ink Persuasion operating rule: when the same industry and the same outbound mechanism exist in one case study, lead with it. Use the closest result next. Freshness matters, but relevance matters first.
Why a link dump weakens strong proof
A shared folder pushes the work of interpretation onto the buyer. They must decide which example resembles them, what changed, which parts you controlled, and whether the result is even relevant. More assets can create more uncertainty.
A focused page answers those questions before the buyer has to ask:
- Why is this example relevant to my company?
- What was the starting point?
- What did you actually change?
- What evidence supports the result?
- Which parts are comparable and which are not?
- What would the next step look like for us?
The page does not need aggressive persuasion. It needs enough structure for the buyer to understand the proof quickly and accurately.
For a concrete example, our Prolux cold email case study pairs six original Instantly screenshots with the audience, outreach approach, and metric definition. The 55 recorded campaign opportunities are presented with their limits, so a prospect can understand exactly what the evidence supports.
The exact response I would send
When a prospect asks for recent work, acknowledge the request and tell them why the example you selected is relevant. Do not make them open a link before they understand the connection.
Absolutely. I pulled together one short document for you. I chose this example because it is the closest match on [industry, outbound mechanism, or desired result]. Inside, you will see the starting point, what changed, the evidence behind the result, and one idea I would apply to your situation. Here is the document: [view-only Google Doc link] If the approach looks relevant, reply with the part you want me to unpack and I will map it to your outbound system.
The message is short because the document carries the proof. The document is focused because its job is to earn one next decision, not to display every piece of work the agency has completed.
Use a four-part rule to select proof
1. Same industry
Industry fit reduces the number of assumptions a buyer must make. The offer, audience, buying committee, sales cycle, regulations, and language may be closer to their own situation.
2. Same outbound mechanism
If you are selling a cold email system, cold email proof is stronger than an unrelated paid-media result. A different mechanism may demonstrate general competence, but it does not answer whether you can deliver the mechanism being proposed.
3. Closest result
Choose the transformation that resembles the buyer's desired outcome. A smaller, directly comparable result can be more persuasive than a dramatic figure with a different offer, market, or operating model.
4. Freshest credible example
Recent proof can show that the process still works under current conditions. Use it after relevance. A fresh but unrelated case study is not automatically the best answer.
When no example matches all four dimensions, say what is comparable and what is not. Do not stretch one client's result into a guarantee for another.
Build the Google Doc like a sales page
Lead with a relevant observation
The most valuable part of the document may be the first paragraph that is not about you. Review the prospect's market, current outreach, website, positioning, or visible sales path. Add one concrete observation they can use even if they do not hire you.
That changes the frame from "here is our portfolio" to "here is evidence that we understand the decision in front of you." Keep the observation specific and source-bound. Do not manufacture a diagnosis from a quick glance.
Show transformation, not only output
A campaign screenshot proves that a dashboard existed. It does not explain why the work mattered. Use a simple transformation structure:
Before: the operating problem and constraint Change: the work, mechanism, and decisions we controlled After: the verified result or improved operating state Evidence: screenshot, report, source link, and date Boundary: what the evidence does not prove
Ink Persuasion's $390K cold email pipeline case study and $4M consulting pipeline case study are useful because they preserve the mechanism and source evidence. The LinkedIn content case study belongs in a LinkedIn conversation, not as substitute proof for a cold email delivery claim.
Make the next step extremely easy
Do not end the document with several competing asks. Choose the next decision that matches the prospect's current level of commitment.
- Ask them to reply with the one part of the example they want unpacked.
- Offer a small sample built around their market.
- Suggest a 15-minute review of the gap you identified.
- Give two narrow scheduling options or one booking link.
- State exactly what you need from them before the next step.
The lower the cognitive load, the easier it is for the buyer to continue. The goal is not to hide the sales process. It is to remove avoidable work from it.
Share the document deliberately
Google Drive supports viewer, commenter, and editor access. Viewer access is usually enough for a proof document. Use commenter access only when feedback inside the document is useful. Avoid editor access unless collaboration is required.
Check the link from a signed-out or separate test session before sending it. Confirm the exact asset, permissions, visible owner information, links, screenshots, and mobile layout. Publishing a Doc to the web makes it broadly public, so do not use that setting for private client proof or confidential screenshots.
Common mistakes
- Sending the biggest result when it is not the closest result.
- Using proof from a different channel without explaining the difference.
- Sharing screenshots without dates, context, or metric definitions.
- Presenting modeled pipeline as booked revenue.
- Exposing client names or private data without permission.
- Making the document about the agency instead of the prospect's decision.
- Ending with a vague "let me know what you think" instead of one clear action.
Frequently asked questions
What should I send when a prospect asks for work samples?
Send a short, tailored proof page with the closest relevant case study, the starting problem, the work performed, the transformation, source evidence, one useful insight for the prospect, and one easy next step.
Should I send several case studies?
Only when each one answers a different material question. Lead with the closest industry and mechanism match. Add a second example only when it closes a specific proof gap.
Does the newest case study always win?
No. The same industry, same mechanism, and closest result are usually more important. Recency is a useful tie-breaker.
Should the Google Doc be public?
Use the narrowest access that still lets the prospect read it. A normal view-only link is often enough. Do not publish confidential proof to the open web.
A practical sales case study template
Keep the document short enough to scan in one sitting. Replace every bracketed line with facts you can support, remove sections that do not help this prospect, and keep the strongest evidence close to the result it proves.
Why this example is relevant: [industry, mechanism, or goal match] Starting point: [verified problem, constraint, and baseline] What changed: [work performed and decisions controlled] Transformation: [verified result or improved operating state] Evidence: [dated screenshot, report, link, or source note] What transfers to your situation: [useful, bounded insight] What does not transfer automatically: [important limitation] Next step: [one easy decision or action]
This format gives the buyer the context needed to evaluate the proof without turning the page into a long portfolio. It also keeps the boundary between a comparable result and a promised result visible.
Sources
Want something like this done for your outbound system?