A finished project can look impressive and still tell a prospective customer very little about the work behind it.
Photographs show what was produced. A website screenshot shows the design. A list of deliverables shows the scope. Those details can help someone assess parts of the result, but they may leave the reason for the engagement unexplained.
What was happening in the business? Why did this work make sense? Which decisions mattered? What changed afterward?
A case study has room to answer those questions. For a service business, that context is valuable because prospective customers are often evaluating judgment as well as execution. They want to understand whether the team has handled a situation relevant to theirs.
Begin Before the Deliverable
Describe the situation that made the work necessary. It might involve growth, a change in services, customer misunderstanding, a process that no longer fits, or a capability the company’s presentation fails to show.
The initial request and the issue behind it may be different. A company could ask for a website because its inquiries are poorly suited to the work it wants. The assessment may reveal that its service descriptions and examples are attracting a different audience from the one leadership intends to reach.
That context explains why the recommendation involved more than design.
Keep it specific and proportionate. You do not need to describe the entire business history. You also do not need to make the situation sound worse than it was. Identify the relevant facts and what the engagement was intended to improve.
If the case will be published, agree on which information can be shared. An internal diagnosis may contain details the customer is not comfortable making public. Resolve that before turning it into the opening of a marketing story.
Show the Reasoning People Cannot See in the Finished Work
The decisions are often the most informative part of a case study.
Why was the work sequenced that way? Why did the team emphasize one service? What was preserved? What recommendation changed after learning more about the company?
Choose the decisions that explain the approach. You do not need a diary of every meeting.
For a website engagement, a revised structure might help customers understand distinct services. For brand work, retaining a familiar name while changing the identity might preserve useful recognition. For an operational engagement, clarifying responsibility might need to precede the implementation of a system.
Explaining those connections lets a reader see what informed the work. It also helps avoid a case study in which every project is described using the same words: strategy, design, launch, success.
The reader should be able to tell why this recommendation belonged to this situation.
Separate What Was Completed From What Improved
A launch establishes completion. It does not establish every business result the company hopes to achieve.
A useful case study distinguishes among:
- The work delivered. What was created, introduced, or implemented?
- The change observed. What is different in how customers or the team understand and use it?
- The business result supported by evidence. What can be measured or otherwise substantiated, and over what period?
You may have strong information in one area and limited information in another. Present that accurately.
For example, a company might be able to confirm that its team can now update important information without a recurring workaround. That is a meaningful operational improvement. It should not be translated into a revenue claim unless the business has evidence for that result too.
If an engagement is recent, explain what can be observed so far. There may not yet be enough information to assess its longer-term effect.
Be Precise With Financial Results
At Re3, we want evidence of the value our work contributes. Financial results can be part of that picture when the customer can provide appropriate information and agrees to share it.
The figure needs a clear meaning. Is it revenue, profit, an increase in average project value, or another measure? What period does it cover? What was happening before the work began?
Also consider what else changed. Staffing, pricing, sales activity, delivery capacity, and market conditions can all influence a result. If several changes contributed, the case study should account for that rather than assign the entire improvement to one project.
The explanation can still be persuasive. In fact, it gives the reader more to evaluate. A specific result with context is more useful than an impressive percentage whose basis is unclear.
You do not need to wait until every effect can be measured to document the work. You need to be clear about the evidence available and what it supports.
Include the Customer’s Experience
The customer may notice something your team would not think to mention. A decision became easier. Staff stopped giving different explanations of a service. A new piece of work is being used in a way the team did not anticipate.
Ask about those changes. Use approved wording, and keep the comment in the context needed to understand it. A general compliment can support confidence in the relationship, while a specific observation can help substantiate a particular improvement.
Questions about what remains difficult are useful too. They may belong in a future recommendation or an improvement to the process. The published case study should be accurate, and the discussion behind it can help the business learn.
Collect the Information While the Work Is Happening
Trying to reconstruct the starting point months later can leave important detail missing. Identify useful evidence early, clarify what the engagement is intended to support, and agree on an appropriate time to review it.
Keep the significant decisions and the reason for them. Record what was delivered. Ask the customer what changed once there has been enough time to use the work.
That creates material for a case study with real substance. It also gives the business a better basis for evaluating its own recommendations.
A prospective customer should finish the case understanding the situation, the reasoning, and the evidence of improvement. The finished work matters. The explanation makes it possible to assess more of what went into it.
