ServiceMaster Case Study

One small-business shot took roughly 20 rejected takes.

A ServiceMaster-style AI ad exposed the real control problem: one water-damage shot needed the woman's line delivery, the handyman's performance, and the water FX to work at the same time. The final spot had to make do with the best available material and hide continuity errors in editing and sound design.

The Proof

One approved shot, two ways it failed first.

Approved generated ServiceMaster shot: crew standing in the doorway
Crew in doorway

Approved, generated from a storyboard image with Nano Banana and Kling 3.0.

Approved shot
Rejected ServiceMaster water-damage source still with homeowner and handyman
Water-damage iteration

One of two source/iteration stills for the shot that would not land.

Rejected / iteration
Rejected generated take for ServiceMaster water-damage scene
Rejected take

One of roughly 20 attempts where continuous leaking, line delivery, or restrained handyman performance broke.

Rejected take
Roughly 20 rejected takes stand behind the one shot that made the final cut.
Approved Beats

Some shots worked.

Three approved shots came from storyboard images via Nano Banana and Kling 3.0: crew in the doorway, nervous homeowner, truck driving off.

Rejected Takes

One shot would not land.

The water-damage shot produced roughly 20 rejects. Continuous leaking, homeowner line delivery, and restrained handyman performance kept failing in different combinations.

Editorial Rescue

The edit hid the gaps.

When generation could not land the shot exactly, continuity was softened with editing and sound design. That is production work, not prompt magic.

Evidence

Atlas Observe would remember the shot, the rejects, and why they failed.

This is not about whether AI can make a polished-looking frame. It is about whether the production can preserve intent across attempts: the storyboard image, the provider, the required performance, the water FX, the brand promise, and why each take was rejected.

A shot can look close and still fail the production.
Approved Shots

Three generated MP4s are confirmed as approved ServiceMaster shots made from storyboard images using Nano Banana and Kling 3.0.

Rejected Takes

Eight rejected takes and two source/iteration stills are documented from the water-damage shot, out of roughly 20 rejected attempts overall.

Continuity Cost

The final edit had to make do with the best available generation and hide continuity errors through editing and sound design.

Atlas Observe Need

A Creative Director platform should track source storyboard, provider, take status, and what must remain true in the next version.

Problem / Solution

The problem

Create a believable ServiceMaster-style ad where the homeowner's emotional beat, the handyman's response, and the water-damage threat all support the same commercial story — with shots that cut together like an intentional ad, not a loose set of impressive AI clips.

Why it was hard

The hardest shot had three moving targets: the water needed to continue leaking out of the wall after the initial pipe burst, the homeowner needed to deliver “I'm calling ServiceMaster,” and the handyman needed to read as defeated and in agreement that the job was over his head without becoming overly performative.

That made the shot expensive in attention — the team wasn't just choosing the prettiest render, it was judging whether the shot could perform inside the edit.

Rejected ServiceMaster take where the water leak, homeowner line delivery, and restrained handyman performance did not all land together
One failed take.

Most takes solved one requirement while breaking another — a frame from the pile that came close but didn't clear the bar.

What failed

After roughly 20 rejected takes, the generation tools still couldn't make every requirement land exactly — the final piece had to make do with the best available take, with the remaining continuity gaps covered in the edit.

Why Atlas Observe is needed

Atlas Observe should remember why each take failed, not just that it did — the difference between learning from iteration and simply burning through attempts.

A Creative Director should be able to see: this take failed water continuity, this one failed the homeowner line, this one made the handyman too performative, and this one was closest but required edit coverage.

The solution Atlas Observe provides

Atlas Observe becomes the production-memory layer around the tools: preserve the approved beat, track every take, mark what became canon, and carry the decision history into the next prompt, provider, or edit.

The goal is not more generations. The goal is fewer lost decisions.
The Rest of the Shoot

Two more approved beats, and why the hard shot failed.

Approved generated ServiceMaster shot: nervous homeowner watches the ground
Nervous homeowner

Poster frame from the approved homeowner reaction beat.

Approved shot
Approved generated ServiceMaster shot: truck driving off camera
Truck drives off

Poster frame from the approved service response beat.

Approved shot
Rejected ServiceMaster take where not all requirements landed together
Why it failed

Continuous water leakage, homeowner line delivery, restrained handyman performance, edit coverage, and sound-design rescue.

Analysis