UGC for Service Businesses

Most UGC advice is written for physical product brands this lesson is specifically for Claude Code builders selling services

Most UGC content advice is written for physical product brands. "Show someone unboxing it." "Film a before-and-after of the product in use." "Get customers to review it on camera."

These formats do not transfer directly to service businesses. You cannot unbox a booking system. The before-and-after of a website build looks different on screen than a skincare transformation.

This lesson is specifically about how Claude Code builders produce UGC content that works for the kind of services you actually sell.

What Proof Looks Like for a Service Business

Proof for a physical product is obvious: show it working and show someone reacting to using it. Proof for a service business is less visual but equally compelling. It just requires different framing.

Proof Format 1: The Before Screen vs After Screen

This is the closest service equivalent to a product before and after. Capture the old solution such as a manual spreadsheet, a PDF form, or a basic website with no booking, then capture the new solution which is your system live and functioning. Two clips in sequence, narrated.

This is the highest-credibility format for builders because it shows the actual work and not a description of it.

Proof Format 2: The Specific Metric

No-show rate dropped from 22% to 4%. Response time went from 48 hours to under 2 hours. 5 hours per week saved on admin. Bookings up 30% in the first month.

Pick one metric. Say the before number and the after number. Say the time frame. That is the proof.

What makes this authentic is that it is falsifiable. The viewer could theoretically verify it. Vague claims like "they love it" or "it's so much better now" do not have this quality. Specific numbers do.

Proof Format 3: The Client in Their Own Words

Even a written testimonial read aloud by an avatar carries more weight than your own claims about your service. "My client said [specific quote about a specific result]" paired with context is more persuasive than you describing your own work.

If you have a client willing to film a real testimonial this beats everything else in this list.

Proof Format 4: The Timeline

Walk through what happened in order. "Day 1 I received the brief. Day 3 the first version was live. Day 7 the client's first online booking came in." The timeline format converts abstract service delivery into a concrete sequence the viewer can imagine.

UGC Angles That Work for Claude Code Builders

The "I built this for a client" angle

You or an avatar describing a specific project you completed. Not a general description of your services but one specific client, one specific problem, one specific system, and one specific result.

Script opening example: "A local hair salon came to me with a 25% no-show rate and zero online booking. This is what we built and what changed in 30 days."

The "here's what I actually charge for this" angle

Transparency about price converts because it removes uncertainty. "Most people assume a booking system costs £3,000 to £5,000. I build them for £1,200 as a flat fee. Here's what's included."

This works as an organic post to attract the right prospects and as ad creative because it filters in the right leads and filters out price shoppers who could not afford you anyway.

The "common mistake" angle

Most audiences do a specific thing and it costs them a specific consequence, followed by here is what to do instead. This positions you as knowledgeable without being salesy and creates authority through the teaching moment.

Example: "Most local service businesses send appointment reminders by text, manually, the day before. Here's why that's costing them 3 to 5 no-shows per month and what to use instead."

The "day in the life after" angle

Show a client's day with your system running. Not the system itself but the experience of having it. "Used to: answer 15 booking calls per day. Now: phone is quiet by 9am and bookings are already in the calendar."

Adapting the Script Prompt for Service Businesses

When using the main script prompt from the writing lesson, add this section to the brief:

Context for this service business prompt:

• I build [specific thing] for [specific audience]
• I do not have a physical product to demonstrate
• Proof available: [list your specific metrics such as no-show reduction,

time saved, or revenue added]

• The before situation: [describe what the client was doing before you

fixed it]

• The after situation: [describe what is now different and how the client

experiences it]

Make the proof concrete. Use the exact numbers from the Context section.

Do not use general claims like "improved efficiency" — say the specific

number.

The Screen Recording as UGC

For builders a 30-second screen recording walkthrough is often the most compelling content you can produce. It requires no avatar and no creator. You record your screen, add an ElevenLabs voice-over, add captions in CapCut, and publish.

What to record for maximum credibility: the live booking system on a real client's site with permission, a before and after showing the old manual process versus the automated system, or a dashboard showing metrics like bookings, response times, and revenue with client permission.

Script prompt for a screen recording:

Using @UGC.md — write a 40-second voice-over script for a screen

recording that shows [describe what the recording shows].

The script should:

• Open with a hook that explains what the viewer is about to see and not

"in this video"

• Narrate what is happening on screen as it happens
• Include the specific before-and-after metric ([your metric])
• End with a single CTA

Write conversationally. The voice-over should sound like a colleague

walking another colleague through something that actually worked.

What to Produce When You Do Not Have Client Results Yet

Starting out without client results does not mean you cannot produce UGC content. It means you change the angle.

Option 1: Use your own experience as the client

You built something for yourself such as your own portfolio, your own booking system, or your own proposal automation. Walk through what you built and what it saves you. You are the proof.

Option 2: Use process-as-proof

Walk through how you build something including the Claude prompt, the code, and the system taking shape, without needing a result metric. "Here is exactly how I build a booking system in one afternoon." The transparency is the credibility.

Option 3: Use a hypothetical with a realistic number

"A typical local service business with 20 appointments per week and a 20% no-show rate loses around £400 per week to no-shows. Here's what a booking system with automated reminders actually does to that number." Frame it as the category result and not a specific client result.

Do not invent specific client results you do not have. Hypothetical category data honestly framed is more durable than a fabricated testimonial.