Beginner4 min readFreelance & Solopreneur AI

Portfolio case evidence, not hype

Write case studies from permissioned evidence: problem, constraints, what you delivered, and what you can prove. Do not let AI invent metrics, testimonials, or client logos. A freelance portfolio workflow that treats claims like advertising claims.

What you should be able to do

A case writeup is only as strong as the evidence you can show and the permission you have. Use AI to organize facts you already verified. Delete any metric, quote, or logo the model invented.

Saved only in this browser.
In this article

Before entering any real client information into AI, confirm authorization for the exact tool, account, data category and purpose. A paraphrase can still be confidential. Permission to publish a finished case or send a client email does not necessarily permit uploading the underlying evidence or thread to an AI provider. Use fictional or non-sensitive placeholder material in general chat; keep the actual record private otherwise.

Portfolio pages fail in two opposite ways: they are so vague they persuade no one, or they are so punchy they overclaim. AI makes the second failure cheaper. Ask for “a case study that sounds impressive” and the draft may add percentages, quotes or comparative language that the evidence does not support.

Freelancers sell trust. Invented proof burns it twice - once with the prospect who checks, and again with the past client who recognizes their project dressed in fiction.

Match each public claim to evidence

The US FTC advertising guidance requires advertising claims to be truthful and supported. Its legal scope is US-specific; use the rules for the actual audience and business. Editorially, keep each metric, quotation and comparison tied to evidence and permission rather than relying on how persuasive it sounds.

Evidence pack before prose

Gather, offline:

  • Client permission to describe the work in the form required by the agreement; check whether any public mention is restricted
  • One-sentence problem statement in your words
  • Constraints (timeline, stack, brand rules)
  • Deliverables actually shipped
  • Outcomes you can prove (screenshots, analytics exports you are allowed to share, before/after artifacts)
  • What you will anonymize (company name, revenue, personal data)

If permission is missing, stop. Write a hypothetical process sample labeled as illustrative instead of a fake case.

Strip personal data about the client’s customers and staff. Anonymize competitively sensitive figures unless permission explicitly covers them. Do not paste full contracts into a consumer model to “extract a case study.”

Workflow

Step 1: Fill an evidence sheet yourself

Use the fields in the portfolio evidence checklist. No AI yet.

Step 2: Structure-only generation

Using only the evidence sheet below, draft a 200-300 word case
writeup with sections: Context, Constraints, What I delivered,
Evidence of outcome, Limits / what this does not prove.
Do not invent metrics, quotes, logos, awards, or client names.
If evidence is missing for a section, write "not evidenced" instead
of filling it.

Evidence sheet:
[evidence authorized for this exact environment, or fictional practice sheet]

Step 3: Invention audit

Highlight every number, comparative (“3x”, “industry-leading”), and quotation. Each highlight needs a source in the evidence sheet or it goes.

Step 4: Permission audit

Confirm the public version matches what the client allowed: named vs anonymized, metrics yes/no, screenshots yes/no.

Step 5: Authorship accountability

You remain the accountable author of the portfolio claim (keep your name on AI-assisted work). If AI helped polish, that does not reduce your duty to substantiate.

Keep a private “evidence” folder per case (permission email + screenshots). The public page should be regenerable from that folder without opening a chat history.

Anonymized cases still need evidence

Anonymizing the client name does not license invented metrics. “A Series B SaaS company” with a fabricated conversion lift is still a false claim. Anonymization protects identity; it does not create proof. If you lack measurable outcomes, write about process quality, constraints handled, and artifacts you can show.

When NDAs block public cases

Some NDAs forbid public mention entirely. Options that stay honest:

  • Ask for a narrow written exception (anonymized, no metrics)
  • Use a labeled illustrative walkthrough of your method with fictional data clearly marked
  • Request a private reference call instead of a public page

Do not “approximate” a forbidden case until it becomes unrecognizable fiction presented as fact.

Validation and fallback

Validation: every claim maps to a file in the evidence folder.

Fallback: publish a process breakdown (“how I approach X”) with no client story until permission and proof exist.

Tie this to proposal drafts so sales decks reuse only the same permissioned proof, not a second, looser narrative.

Publish the result you can actually support

Invented evidence folder: six dated, signed-off page designs, a delivery receipt covering those six designs and permission to show cropped screenshots. It contains no analytics and no testimonial. Supported copy: “I designed and delivered six pages within the agreed scope; these screenshots show the approved layouts.” Unsupported copy: “The redesign doubled sales and delighted every customer.”

A useful case can explain the constraints, design decisions and artifacts without claiming an unmeasured commercial result. Check that screenshots themselves contain no client or third-party information beyond the permission granted. Keep separate records for provider-input authorization and public-use permission.

An invented folder of six signed-off designs, their delivery receipt and cropped-screenshot permission, compared with supported delivery copy and unsupported sales and satisfaction claims.
The evidence supports delivered work and approved layouts. It supplies no analytics or testimonial for a commercial-outcome claim. Open the full-size diagram.

Read next

Continue through the same learning path with the next practical articles.