Marketing

Turn ServiceM8 jobs into website case studies

Case study automation picks up completed ServiceM8 jobs that the customer agreed to feature and gathers the notes and photos from each one. It drafts a short case study as a WordPress draft and a LinkedIn post, both of which the owner edits and publishes.

An example of how the studio would build it. No live services are connected.

From a completed job to a case study on your website.

  1. Step 01

    Job completed

    ServiceM8 reports a completed job that has been marked as agreed for a case study.

  2. Step 02

    Material gathered

    Collect the job description, notes and photos, and flag photos for the owner to check for house numbers, faces or number plates.

  3. Step 03

    Drafts written

    Use Claude to draft a short case study covering the problem, the work and the finish, plus a LinkedIn post.

  4. Step 04

    Owner edits

    Save the case study as a WordPress draft and send the LinkedIn text to the owner to edit and approve.

  5. Step 05

    Work published

    The owner publishes the page and shares the post, with the customer’s location kept as general as they agreed.

The result

Your best work is shown off while it’s fresh, instead of sitting in a camera roll.

Only jobs with the customer’s recorded permission are used, and drafts never name them or their address unless they agreed. Nothing is published automatically.

Before we connect it.

Where this is useful

Useful for builders, kitchen fitters, landscapers, electricians and other trades whose best work rarely makes it onto their website. A sensible first version drafts the case study only, then adds the LinkedIn post and other channels once the format feels right.

What we need to connect

  1. 01ServiceM8 access to jobs, notes and attachments, with a job field or badge that records the customer’s permission to feature it.
  2. 02A WordPress site where drafts can be created through the REST API, and the LinkedIn profile or page you post from.
  3. 03An agreed case study structure, your tone and rules on what may be shown, such as the town but not the street.

What needs careful handling

Customers may agree to their job being shown but not their name, so the permission field records exactly what they agreed to. Job notes are written for the team, with prices, codes and shorthand, so drafts leave out prices and anything internal unless the owner adds them back. Photos taken on site can show the customer’s home, family or car, so the owner checks every photo before it is used.

Questions people ask.

Who writes the case study?

Claude drafts it from your job notes and photos, in a structure and tone you agree. The owner then edits it, adds anything only they would know and decides whether to publish. The draft is a starting point, so you can rewrite as much as you like.

How do we ask customers for permission?

Usually at the end of the job, as part of your sign-off or follow-up, with a simple yes or no for photos, name and location. The answer is stored on the job in ServiceM8, so only agreed jobs are picked up.

All automation examples