Message House Example: SaaS
Offering: Route Optimizer, an add-on in Fieldlight (field service SaaS) Target: dispatchers and ops managers at 50-300 technician service companies Positioning: "For dispatch teams at mid-size service companies who lose hours each day to manual rescheduling, Route Optimizer rebuilds the day in seconds when the plan breaks..."
Why this example exists: the team's first draft is three features. The rebuild shows the cover test, the trace, and why the foundation matters for a new module.
## Draft critique (first)
Pillars as submitted: "AI routing engine," "Real-time GPS," "Drag-and-drop calendar."
Cover the name and any competitor could claim all three. They are features. No pillar traces to
a customer pain.
## Message House: Route Optimizer
**ROOF**
> When the day falls apart, your schedule fixes itself before the phone stops ringing.
| Pillar | Outcome | Traces to | Cover test |
|---|---|---|---|
| 1 | Fit the emergency job in without wrecking the day | Pain: "a rush call blows up my afternoon" (7 of 9 dispatcher interviews) [FROM YOU] | Passes |
| 2 | Send the right tech the first time | Pain: repeat visits because of wrong skills or parts [FROM YOU] | Passes |
| 3 | Know tomorrow's plan tonight | Gain: dispatchers want to leave on time [AI-SUGGESTED, VALIDATE THIS] | Needs interview evidence |
**Proof**
| Pillar | Proof | Type | Source |
|---|---|---|---|
| 1 | Median reschedule time, before vs after, across pilot accounts | Measured pilot | `[NEEDS SOURCE]`: 14 pilot accounts ran; results not yet pulled |
| 2 | First-visit fix rate change | Measured pilot | `[NEEDS SOURCE]` |
| 3 | Calculation: dispatcher hours saved = reschedules per day x minutes each x days, with *your* numbers | Repeatable calculation | Built from template |
**Foundation:** 11 years in field service software; [N] customers `[NEEDS SOURCE]`; SOC 2 Type II
report dated [date] `[NEEDS SOURCE]`; 24-hour support.
**Superlatives found:** "smartest scheduler on the market." Basis: none. Removed.
## Variants
| Role | Lead pillar | Wording |
|---|---|---|
| Dispatcher | 1 | "A rush call won't blow up your afternoon." |
| Ops manager | 2 | "Fewer repeat visits, more jobs per tech per day." |
| CFO | 3, with calculation | "Hours back each week, from numbers you can check." |
| Reseller | All three, short | "An add-on your customers ask for and you can demo in five minutes." |
## Words
Use: "fix the day," "rush call," "first-visit fix" (customers' words, interviews). Avoid: "AI-powered,"
"optimization engine," "seamless."
## Test plan
Five dispatchers from the interview pool. Read roof and pillars aloud. Ask what they heard,
believe, doubt. Result that changes the house: if fewer than 3 repeat pillar 1 unprompted, re-cut.What to learn from this
- The cover test killed all three original pillars in about ten seconds.
- Two pillars rest on pilot data nobody has pulled. Flagged
[NEEDS SOURCE]rather than filled, so they stay out of external material until the numbers exist. - The foundation carries the new module. A first-year add-on borrows the company's track record.