WhatsApp us
Websites

A Useful Agency Case Study Does Not Need an Invented Revenue Number

Build a useful case study from the brief, delivered work, role and visible outcome. Show real videos and websites without inventing financial results.

Colleagues discussing work during an office meeting.
Photo: Ivan S / Pexels
Share

A quicker read

Summarize with AI

Five key points. Three practical next steps. Choose your assistant, then paste the copied article into your new chat.

Preview the summary request

You choose what to send. AI summaries can miss details; use the full article for context.

A real video, website or campaign asset is evidence of delivered work. It does not need an invented revenue figure to become useful in an agency case study. Explain the brief, your role, what was produced and what a buyer can inspect. Add commercial results only when the underlying records support the claim.

This approach is useful for Dubai businesses commissioning a website or portfolio section, particularly when strong creative work exists but customer revenue data is unavailable. The page can demonstrate delivery quality without pretending to establish a financial outcome.

Match the claim to the evidence

Evidence available Claim it can reasonably support What it does not establish by itself
Published film The visible production, presentation and editing work Sales or lead growth
Live website or dated screenshots The design and implemented features shown A conversion uplift without comparison data
Approved client statement The client's stated experience Every possible performance claim
Delivery records The agreed outputs and documented timing The customer's financial return
Reconciled performance records A defined result within the recorded period and method A guarantee that another client will repeat it

Use a five-part project page

Start with a short project summary: customer or project identity where approved, the service delivered and your role. Then explain the brief in the customer's terms. Describe the constraint or decision that shaped the work. Show the actual output with captions. Finish with the observable outcome and any supported measurement, keeping those categories distinct.

For an illustrative presenter-led video project, the case could explain the product question, approved script, speaker choice, filming setup and final edits. Embed the film or link to a stable viewing destination. A caption can identify what the production team delivered. None of that requires claiming that the video increased the client's revenue.

Attribute the work precisely

Identify whether your team handled strategy, filming, editing, design, development or distribution. If the client supplied the concept or another partner delivered part of the work, reflect that accurately. A clear contribution is more credible than a broad claim to have created everything.

Confirm that the customer identity, assets and statements can be published for the intended use. Remove confidential information from screenshots and working documents. If the customer cannot be named, describe the project at an appropriate level without creating a misleading impression of a public endorsement.

Start from the work that a buyer can actually inspect

Choose a real output and identify the service it demonstrates. That could be a published video, an implemented website, a set of approved creative assets or a documented campaign setup. The first question is what the work shows, not which impressive number can be attached to it. A buyer considering production can learn from the framing, presentation, sound and edit of an actual film even when the agency does not have the client’s sales records.

For example, LunaSol’s video page lets prospective buyers inspect published video work. A project explanation can connect an example to the production decisions and delivered scope. The presence of a film is already useful evidence of the visible work. Missing revenue attribution should limit a revenue claim, not erase the value of the film itself.

Interview the person who knows the delivery

A short factual interview often provides better case-study material than a generic success-story questionnaire. Ask what the customer needed, what the team was responsible for, which constraint affected the work and what was actually delivered. Use the output and available records to check the answer. The writer should leave with a specific account of the project rather than a collection of adjectives about collaboration.

Ask for decisions that a new buyer would find useful. Why was a particular format chosen? What information needed to appear in the first part of the video? Which website function mattered to the receiving team? What did the client supply? These answers explain expertise through the work itself. They are more informative than an unsupported claim that the project transformed the business.

Keep unknowns specific. If the exact delivery date is unavailable, do not invent one. If the team knows the work and role but has no revenue data, publish the supportable delivery explanation. If a client statement has not been approved for public use, omit that statement while using the material that can be shown. The whole case does not need to become a vague list of pending evidence.

Use a project structure that works without financial results

Project summary

State the service, type of work and your team’s role in a few direct sentences. Identify the customer or project only to the extent approved for publication. Put the actual output near the summary so a buyer can inspect it early. A long introduction about the industry can wait if it does not help explain this project.

Brief and constraint

Explain what the customer asked for and the practical condition that shaped the delivery. A limited filming window, a need for several output formats or a website handoff to an existing internal tool can be meaningful context. Use the real constraint. Do not invent a dramatic crisis to give the story a more impressive before-and-after structure.

Work and decisions

Describe what the team did and why it mattered to the brief. Be concrete about the activity: script development, filming, editing, page design, development or implementation. If the client or another supplier owned part of the work, include that boundary. A precise contribution is easier for a buyer to compare with the service they need.

Output and observation

Show the delivered material and explain what can be observed directly. A video may demonstrate a specific presentation and edit. A website example may show a completed enquiry route or service-page structure. If there is no reliable outcome measurement beyond delivery, say what was delivered and stop there. That is a valid project account.

A fictional example of the writing approach

Imagine a business commissioned a presenter-led explanation of one service for its website and social channels. In this fictional example, the client supplied the factual service information, while the production team developed the script, filmed the presenter and edited the agreed versions. The brief required a clear explanation of the service and a next step the viewer could understand. This is a teaching scenario, not a LunaSol client claim.

The case study could describe how the script was organised around the buyer’s first question, how the presenter delivered the explanation and which versions were handed over. It could show the actual approved film if this were a real publishable project. It would not claim that revenue doubled, that leads increased or that the customer became a market leader without records supporting those outcomes.

A useful closing statement would connect the delivery to the original brief: the business received the agreed explanation and formats for the stated uses. A separate results section could be added later if reliable measurement becomes available. The initial case remains useful because a prospective buyer can inspect the production and understand who did what.

Prepare screenshots and captions that preserve context

Choose images that demonstrate the relevant work rather than simply looking busy. For a website, show the page or interaction being discussed and identify whether the image is a current live view or a dated capture. For a video, give the viewer a usable playback destination. Remove private information that is not part of the publishable example.

A caption should answer what is shown and the provider’s role. It can also identify a meaningful feature or decision. Avoid adding claims that the image cannot support. A screenshot of a dashboard may show a recorded number, but the surrounding text still needs to explain the period, definition and scope before it becomes a meaningful performance claim.

Connect the case to the service it proves

Link the project from the relevant service page and provide a clear route back to that service. Use the case as evidence for the actual work shown. A production example can support production capability; it should not automatically be used as proof of SEO results. The relationship between claim, project and enquiry should be understandable to a new visitor.

For GEO and AEO, this gives the public site a more specific account of the company’s role and work. A readable explanation beside the asset is more informative than an unexplained media grid. Keep business names and service descriptions consistent, and distinguish an observed delivery from an inferred commercial effect. The same discipline helps a human buyer assess the evidence.

Make the case usable in a sales conversation

Give the sales team a stable link and a short explanation of when to share it. A project should be sent because it helps answer the prospect’s question, not simply because it is the newest item in the portfolio. Identify the service, format or delivery constraint that makes it relevant. When the prospect asks whether their project will achieve the same commercial outcome, distinguish the demonstrated work from any result that was never measured. This lets the team use real evidence confidently without overstating it. Review the page when the linked asset, service scope or publication permission changes so the example remains useful after the first announcement.

Questions about case studies without revenue data

Is a video alone useful evidence?

Yes, for the visible production work it actually demonstrates. A concise explanation of the brief, role and delivered versions makes it easier to assess. It does not automatically prove a sales result, but the absence of that result does not make the film meaningless.

Can we publish a case without naming the client?

Use an accurate level of description that is permitted for the material. Explain the work and role without implying a named endorsement. Check that screenshots, spoken names or visible documents do not reveal information that the text intentionally leaves private.

Should we add estimated results to make the case stronger?

Do not present estimates as recorded client outcomes. If an illustrative calculation genuinely helps explain a decision, label it separately and state its assumptions. The case itself should remain grounded in the real work and supportable observations.

Add results with enough context to assess them

When reliable performance data exists, state the period, metric definition, baseline and relevant limitations. Explain whether the result is directly recorded or inferred. If the business cannot separate the effect of a website change from pricing, sales or advertising changes, avoid presenting the website as the sole cause.

Link the case from the service it supports and offer a relevant next step. Buyers evaluating agencies can use our agency selection guide alongside the work itself. To improve how your projects are presented, bring the available assets and accurate delivery scope to a discussion through our website page.

WhatsApp us