Sales Value Narrative Example: SaaS
Offering: Route Optimizer (Fieldlight add-on) Sold to: service companies with 50-300 technicians; direct sales plus resellers Alternative that wins most: "Our dispatchers manage fine in spreadsheets and a whiteboard."
Why this example exists: the first draft opens with features. The rebuild opens with the cost of staying put, and shows that for a SaaS add-on "why now" is often a renewal date or a busy season.
## Draft critique (first)
Opens with "Fieldlight is the leading field service platform with 11 years..." and a feature tour.
No status quo, no why-now, one value statement for everyone.
## Narrative: Route Optimizer
**Why change**
Every time a job runs long or a rush call comes in, a dispatcher rebuilds the day by hand. The
cost is hours of dispatcher time and the jobs that slip. Calculation to repeat with their numbers:
reschedules per day x minutes each x working days = dispatcher hours per month. `[NEEDS SOURCE]`
for any benchmark; the customer supplies their own.
**Why now**
Triggers a rep can spot: peak season starting in 8-10 weeks; adding technicians (the board gets
harder to hold in one head); a dispatcher leaving; a missed-SLA complaint. Ask: "When did you last
rebuild the whole day, and who was on the phone?"
**Why us**
Pillars from the message house: rush calls fit without wrecking the day; right tech first time; tomorrow's plan tonight. Proof: 14-account pilot, `[NEEDS SOURCE]` until results are pulled.
## Value by role
| Role | Cares about | Value | Proof |
|---|---|---|---|
| Dispatcher | Not dreading rush calls | Reschedule in seconds | Pilot reschedule time `[NEEDS SOURCE]` |
| Ops manager | Jobs per tech per day | Fewer repeat visits | First-visit fix rate `[NEEDS SOURCE]` |
| CFO | Payback | Hours saved vs add-on price | Repeatable calculation |
| IT / security | Data handling | Technician location data handled under the existing DPA | DPA addendum (Legal, in review) |
| Reseller | Margin, easy demo | Five-minute demo, add-on margin | Margin sheet |
## Objections
| Objection | Behind it | Answer | Proof |
|---|---|---|---|
| "Spreadsheets work fine" | They don't see the cost | "Fair. How many times last week did you rebuild the day? Let's price it with your numbers." | Calculation |
| "Too expensive" | Over budget / no belief in savings | Clarify which, then show their hours saved vs price | Calculation |
| "We'll wait until next budget" | No trigger | "Peak season starts in 9 weeks. What does one bad week cost you?" | Their numbers |
| "Is technician GPS data safe?" | Privacy fear | Walk through the DPA addendum | Legal-approved text |
## Do-not-say (dated Jun 1)
- "Smartest scheduler on the market" (no basis)
- "Reduces drive time by X%" (pilot not pulled; do not quote until it is)
## Cards needed
Status quo (spreadsheets) first; then the one competitor that appears in 4 of the last 10 deals.What to learn from this
- The first card is for "do nothing," because that is who wins most deals.
- A do-not-say entry protects a claim that isn't ready. The pilot number is a promise to keep, not a number to quote.
- The calculation hands the customer the math, so the champion can defend it to their CFO.