Use testimonials to show what a client says about working with you. Use case studies to explain the situation, your contribution and the evidence available about the result. Together, they can help a visitor assess whether your experience is relevant to their own needs.
Start with evidence you are allowed to publish. A strong-looking quote or logo is not useful if it is inaccurate, out of context or presented without the required permission.
Give each type of evidence a clear purpose
A testimonial is someone’s account of an experience. A case study is a structured account of work. Neither should be stretched beyond what it supports. A compliment about communication does not establish that you doubled revenue, and a photograph of a workshop does not establish that participants secured jobs.
| Evidence | Useful for showing | What it does not establish by itself |
|---|---|---|
| Approved client quote | The client’s stated experience | Results the client did not mention |
| Project screenshot | An interface or deliverable | Sales, traffic or enquiry growth |
| Documented project description | Scope, decisions and work delivered | Measured impact without supporting records |
| Verified outcome data | A defined result over a stated period | That your work was its only cause |
Collect testimonials with specific questions
Ask what the client needed, what part of the engagement was useful and what they would tell someone considering similar work. Give them space to answer in their own words. Do not write a glowing claim and pressure them to approve it.
Confirm the wording, attribution and intended use. A private WhatsApp message is not automatically a website testimonial. If you shorten a quote, preserve its meaning and obtain approval for any substantive edit. Keep a record of the agreed version.
Where a client requests anonymity, agree what details can still be shared. “A client” provides limited context, but confidentiality should not be traded for a more impressive testimonial. Do not invent a name or job title to fill the gap.
Build a case study around a decision
A useful case study answers: who needed help, what was difficult, what work you did, why you made the main decisions and what can be demonstrated afterwards. Include limitations where they matter.
The structure does not require a dramatic transformation story. Some projects are valuable because they organise information, replace an unreliable process or give staff a maintainable system. Describe that work precisely.
- Set out the relevant client context.
- Describe the problem or brief.
- Identify your role and any delivery partners.
- Explain the main work and decisions.
- Show the deliverables and supported outcomes.
- Offer a next step for readers with a similar requirement.
What the BIUC case study demonstrates
My public BIUC Industrial Services case study identifies the sector, website work delivered through Techmita and the need to organise several technical capabilities. It describes dedicated service information, corporate content and contact destinations.
That supports a practical discussion about structuring a specialist business website. It does not provide verified enquiry growth or revenue figures. Keeping that boundary clear lets the example do useful work without becoming an unsupported performance claim.
You can see other documented work in my project portfolio. Each example should be assessed for the kind of evidence it actually contains.
Place evidence near the question it answers
A visitor on a service page may want to know whether you have handled a similar requirement. A relevant project link near that section is more helpful than a wall of unrelated logos at the bottom of the homepage.
Use a short summary on the service page and link to the full account. Explain the relevance: for example, “See how several industrial service areas were organised into dedicated website destinations.” The reader then knows why the link is there.
My content development support can help turn approved project material into useful website evidence, while website development addresses its structure and presentation.
Review evidence as the business changes
Check that the project is still described accurately, the client attribution remains appropriate and any outcome period is stated. If the live client website changes after handover, a dated screenshot can distinguish your delivered work from its current version.
Do not silently alter a historical case study to imply that you built later features. Explain the scope of your involvement. If a result has several possible causes, describe the association and available evidence rather than claiming sole credit.
Frequently asked questions
What if I have no impressive numbers?
Explain the brief, decisions and deliverables. A clear account of real work can help buyers assess fit even when outcome data was not collected or cannot be shared.
Can I use a client’s logo because I worked with them?
Confirm the permission and any brand-use conditions. A logo should not imply an endorsement, partnership or scope of work beyond what was agreed.
Should every testimonial include a photograph?
Only when the person has authorised that use and the photograph adds useful context. Accurate wording and attribution matter more than decorative presentation.
Make your evidence easier to assess
Choose a few relevant projects, gather the approved source material and state exactly what each one demonstrates. That gives prospective clients something concrete to review before starting a conversation.
Discuss your next step
If you would like help applying this to your organisation, share a short description of your situation and the decision you need to make.





