Turning a mission into a Malt client case: the complete method

The fatal mistake: trying to collect info for your client case 3 months after the mission ends. By then, your client has moved on, the numbers have shifted, your contribution is diluted in other actions.

Rule 1 — Frame measurement at kickoff. In your proposal or kickoff, define the 3-5 KPIs you'll track together. The client provides them, but you frame them. E.g.: 'We'll track: overall organic traffic, positions on the 10 target keywords, conversion rate on pillar pages, qualified leads attributed to SEO.'

Rule 2 — Document continuously. Create a shared doc (Notion, Google Doc) where you note week by week: key decisions, before/after numbers, difficulties overcome, client feedback. At the end of the mission, you have everything at hand.

Rule 3 — Formalize the 'commercial reference' clause in the contract. Add a line to your quote or contract: 'The provider may cite the mission as a commercial reference (company name, context, aggregated results) unless explicitly stated otherwise.' 95% of clients sign without a fuss.

Impact: applied systematically, you recover 100% of the data you need to build a powerful client case, without having to 'beg' at the end. The client case writes itself as the mission progresses.

Regardless of your profession, these 5 categories of KPI provide material for a powerful Malt client case.

KPI 1 — Direct business impact. Revenue generated, revenue saved, additional margin, qualified leads, deals closed. It's the KPI that speaks to the executive. E.g. dev: 'Feature that generated +€45k of recurring revenue in 3 months.' E.g. SEO: '+€280k/year of revenue attributed to organic traffic.' E.g. designer: 'New checkout flow, conversion +18%.'

KPI 2 — Operational impact. Time saved, shortened cycle, adoption, error reduction. It's the KPI that speaks to the COO or teams. E.g.: 'Client onboarding shortened from 3h to 20 min.', 'Product shipping cycle 6 weeks → 3 weeks.', 'Dev team adoption 100% in 2 months.'

KPI 3 — Quality/satisfaction impact. NPS, user satisfaction, quality score, retention rate. Especially useful in UX/design/product. E.g.: 'User NPS +25 points post-redesign.', 'CSAT support score 4.2 → 4.8.'

KPI 4 — Technical impact. Performance, uptime, code quality score, test coverage. Useful in dev/data/DevOps. E.g.: 'Time-to-load 3.2s → 1.1s.', 'Lighthouse Performance 42 → 96.', 'Uptime 99.2% → 99.98%.'

KPI 5 — Organizational impact. Enabled recruitment, team training, skill transfer, delivered doc. Useful in consulting/training. E.g.: 'Internal team trained, 3 junior devs autonomous in 2 months.', '40-page technical doc delivered, no longer need my support.'

Tip: capture at least 3 KPIs per mission, in at least 2 different categories. This gives you a multi-dimensional client case that speaks to every decision-maker (biz, ops, technical).

The end of the mission is your last moment of collection. After that, you lose access and attention. Do these 4 actions systematically.

Action 1 — Official closing session (30-45 min). Organize a closing call with the decision-maker (not just your operational contact). Goal: recap of deliverables, final numbers, feedback. Take notes. Record the call (with permission) to capture key phrases.

Action 2 — Formal request for the written testimonial. During the closing call, directly formulate: 'Would you be up for writing a short testimonial, 2-3 lines, that I can use on my Malt profile? I can prepare a draft for you to validate if it saves you time.' 70% accept. If you offer to prepare a draft, it rises to 90%.

Action 3 — Capture the final numbers. During the call, explicitly request the final KPIs: 'On the 3 KPIs we framed at the start, what are the consolidated numbers?'. Note everything. If the client doesn't have them in mind, offer to have them sent within 7 days.

Action 4 — Malt review request. Within 48h post-close, send a Malt message to the client requesting an official review on the platform. Do it while the client is still 'warm' on your work. Beyond 2 weeks, the response rate drops by 80%.

Malt post-mission message template: 'Thanks for this collaboration [first name]! Can you leave me a quick review on Malt (2 min max)? It's very important for my profile and it helps me land the next missions. Thanks in advance!'

With this ritual applied systematically, you recover 4-5 client cases + 4-5 reviews + 4-5 written testimonials per year. Your profile becomes a machine that convinces.

A 'it was great, I recommend' testimonial doesn't convert. A precise testimonial with context and result = signature. Here's how to get the right format.

Method 1 — The draft to validate (the most effective). Write a first draft yourself based on what you know about the client, send it for validation. 'Here's a testimonial draft, tell me what you'd change.' 90% of clients accept with 0-2 minor modifications. You gain in quality AND you save them time.

Recommended draft structure: 1. Client context (1 sentence) 2. Problem before intervention (1 sentence) 3. What you did / how you worked (1-2 sentences) 4. Concrete result (1 sentence with number if possible) 5. Recommendation (1 sentence)

Sample draft: 'Levan joined our team as senior SEO consultant to recover our organic traffic in freefall after a failed technical migration. He conducted a precise audit, prioritized critical fixes, and delivered 3 structured work streams over 4 months. Result: traffic recovered to +12% vs baseline, 15 keywords in Google top 3. Autonomous, methodical, results-oriented: I recommend without hesitation. — Marie D., CMO EdTech Scale-up'

Method 2 — Guided questions. If the client prefers to write themselves, send them 4 short questions: 1. What was your initial need? 2. Why did you choose this freelancer? 3. How did the mission go? 4. What were the results?

The client responds in 5 minutes, you can reformat into a clean testimonial for validation.

Mistake to avoid: asking for a vague testimonial like 'can you write a few words?'. You'll receive unusable filler.

Classic question: 'How do I know if the result comes from my mission or other parallel actions?'. Here's how to handle it.

Case 1 — Assumed partial attribution. If you know other actions contributed, formulate the result as partial attribution. 'Revenue generated: +€45k/month (of which approximately 60% attributed to my SEO work stream, according to client analytics).' This honesty reassures senior clients.

Case 2 — Proxy numbers. If the business KPI is too far, use proxy numbers close to your action. E.g. dev: instead of 'revenue +18%', say 'Performance improved 3x, bounce rate -44% on impacted pages'.

Case 3 — Concrete qualitative numbers. When the number doesn't exist, replace with concrete operational. '3 new features delivered on date', 'Team autonomous on the topic in 6 weeks', '45-page reference doc delivered'. These are quantified facts that prove the scope of work.

Case 4 — Relative comparison. If you have no absolute number, compare to a baseline. 'Best quarter of company growth according to the CEO', 'Best client onboarding ever measured according to the CSM', 'Feature generating the most engagement in the last 3 years according to the product team'.

What you must never do: invent a number. On Malt, you can be challenged on a call by a prospect 'how did you measure this +180%?'. If you can't answer, you're burned.

Safety rule: always add the implicit source. 'According to client measurements', 'From the client's GA4 dashboard', 'Confirmed by the client's CFO'. It protects you and adds credibility.

Here's the Notion template I use for all my missions and that I have my coaching clients adopt. It saves you 3-4h of retrospective collection on each mission.

Section 1 — Client context (filled at kickoff) - Company name, sector, size, stage - Budget decision-maker, operational contact - Context: why they contacted you, what problem - Baseline: numbers before intervention (the 3-5 KPIs we'll track)

Section 2 — Mission framing (filled week 1) - SMART objectives (3 max) - Measurement KPIs defined - Planned deliverables + dates - Commercial reference clause validated? (yes/no)

Section 3 — Logbook (filled each week, 10 min) - Week X: key decisions, progress, blockers, client feedback - Numbers to date on KPIs - Anecdotes / key moments (useful for the case study)

Section 4 — Mission review (filled at closure) - Final KPIs vs baseline - Deliverables actually delivered - Client feedback (verbatim if possible) - What worked well / what I'd do differently

Section 5 — Commercial assets (filled post-mission) - Written testimonial (validated) - Malt review requested and received - Case study written (STAR-R) - Authorized visuals (screenshots, logos)

Keep this doc for each mission. After 3-4 missions, you have a reproducible system that gives you quality client cases without superhuman effort.

A well-collected client case isn't a single asset: it's multi-format raw material. Each case can feed 4 different supports.

Format 1 — Malt case study (STAR-R 500-700 words). The main format, on your Malt profile, at the top of the portfolio. See dedicated guide.

Format 2 — Short portfolio project (150-250 words). Condensed version of the same case, for other platforms (personal site, LinkedIn) or to complete your other short Malt projects.

Format 3 — Narrative LinkedIn post (300-500 words). Tell the case in 1st person with narrative tension: 'The client called me in panic. -35% of organic traffic in 6 months. Here's how we recovered.' Format that engages massively on LinkedIn and brings you prospects.

Format 4 — Snippet for sales call (30 sec oral). The spoken version to bring out in sales calls: 'On my last project similar to yours, EdTech scale-up context, they had dropped 35% of traffic, we recovered to +12% in 4 months. That's the type of result we can aim for here too.'

Multiplier ROI: 1 well-collected client case = 4 formats = multi-platform presence + ready sales pitch. For 2h of collection, you generate weeks of content.

Tip: always write the Malt case study first (the longest and most structured format). The other formats are deduced by condensation or reformulation, in 20-30 min each. Massive time savings.