A photograph of a freshly cleaned patio tells a visitor what the surface looked like when the crew finished. It doesn't explain what condition the patio was in before the visit, which stains were treated, or whether the customer asked for anything beyond the original estimate.

Those missing details are what can make a completed job worth writing about. A short project story gives a prospective customer a way to judge the kind of work you handle and how you approach it. You can create one from a single well-documented job. You don't need an elaborate portfolio or a dramatic transformation.

Choose a Job That Can Answer a Customer's Question

Start with a real, completed job that you can describe accurately. The best candidate is not necessarily your largest or most photogenic project. Look for one that illustrates a decision a future customer may face:

  • A house-cleaning visit where the scope changed after an initial walkthrough.
  • A lawn renovation where site access or weather affected the work sequence.
  • A drywall repair where the customer needed to understand the difference between patching and repainting.

Ask what someone considering that service would want to know. Was this the kind of problem you accept? What did the quote cover? What made the work straightforward or complicated? What was actually finished?

If you cannot answer those questions from job records or reliable recollection, select another project rather than filling the gaps with plausible-sounding details.

Collect the Facts Before Writing the Story

A few minutes spent reviewing a completed job can save you from writing a vague success story. Gather the original request, approved scope, relevant job notes, photographs you have the right to publish, and any documented changes. Record the finish date if it matters to the story, but avoid suggesting that one project's schedule is standard for every job.

For each potential claim, identify the evidence behind it. A signed work order can support what was agreed to. A completion photograph can show visible work at a particular moment. Neither proves that a repair will last for years or that every customer will get the same result.

The Federal Trade Commission's advertising guidance says advertising claims should be truthful and supported by evidence. It also considers what an advertisement may imply, not only its literal wording. For a project story, that is a useful reason to distinguish what you observed from an outcome you haven't measured.

Write the Project in the Order the Customer Would Understand

A service-business case study usually needs four pieces of information. They can fit into a few short paragraphs rather than four rigid sections.

The starting situation. Describe the customer's practical problem and any condition that affected the job. Use details that matter to the service, not a long personal backstory.

The agreed scope. Say what your business was hired to do. If the estimate excluded related work, mention that boundary when it helps explain the result.

The work performed. Include one or two meaningful decisions. “We cleaned the yard” says less than explaining that the crew collected storm debris from accessible planting beds while leaving tree removal to a separate specialist.

The observed result. State what was completed and what evidence supports it. Don't quietly turn a finished task into a claim of permanent improvement or guaranteed customer satisfaction.

An Invented Example: A Small Landscaping Job

The following example is fictional and demonstrates writing structure, not an actual customer's experience.

Clearing an Overgrown Side Yard Before a Fence Installation

A homeowner needed the side yard cleared so a fencing contractor could inspect the property line and plan an installation. The narrow access path limited the equipment that could be brought into the space.

The landscaping crew removed loose brush and cut back the agreed-upon vegetation along the access route. The estimate covered vegetation clearing and bagging. Hauling the bagged material off-site was quoted separately, and no tree removal was included.

At the end of the visit, the access route was clear of the brush identified in the work order. Completion photos documented the condition of that area when the crew left. The fencing contractor's later work was outside the landscaping company's scope.

This story gives a customer useful boundaries: the reason for the visit, the access constraint, what the crew did, and what it did not do. It makes no claim about increased property value, faster fencing installation, or a result beyond the documented work.

Make Photos Explain Something

Before-and-after images are more helpful when readers know what they are looking at. Pair each image with a short, factual caption that identifies the relevant area and work. For example:

Before: Brush along the narrow side-yard access route, prior to clearing.

After: The same route after the agreed vegetation clearing and bagging were completed.

Use comparable views when possible. Don't present images from different properties as one project, crop away a visible limitation to create a false impression, or imply that a photograph documents work it cannot show.

Check publication rights before posting. The U.S. Copyright Office explains that original photographs are protected by copyright; owning a copy of an image does not automatically mean you own its copyright. Confirm permission or the necessary rights if a customer, freelancer, or another contractor took the picture. Separately, ask for appropriate permission before revealing a customer's name, identifiable home, or private details. You can often tell a useful story without including the street address.

Treat Customer Comments as Customer Comments

A customer quote can add perspective, but it should not be used to manufacture a stronger result than the records show. Ask permission before featuring an identifiable comment, preserve its meaning, and distinguish a customer's opinion from a technical claim.

For example, “The crew explained the access problem before starting” describes a customer's experience. “The drainage problem is permanently solved” is a much broader assertion that a casual comment may not support.

The FTC's consumer reviews and testimonials guidance distinguishes promotional testimonials from ordinary reviews and addresses fake or false testimonials. You can publish a useful case study without a testimonial at all. Do not invent one to complete the page.

Place the Story Where It Helps Someone Decide

A job story can live on a dedicated project page, but it does not need to. A small handyman business might place a concise repair example beside the service description for drywall patching. A cleaning company could link to a detailed move-out project from the corresponding service page, if it has one.

Give the piece a descriptive heading that tells readers what the job involved. “Side-Yard Clearing for Fence Access” is more informative than “Another Happy Customer.” Add a straightforward next step, such as asking customers to send a photo of a similar problem for an assessment, only if that reflects your real process.

One documented project is a sample of your work, not proof that every future job will have the same scope, timeline, or result. Let the specifics do the explaining.

Before publishing, read the story alongside the original work order and photographs. Mark every sentence you could not substantiate, then remove it or rewrite it as a clearly limited observation. The finished piece should help a prospective customer recognize a similar need and understand what your business actually did about it.

Sources and Further Reading