**Format:** Slide deck sent ahead; one-pager conversation anchor at meeting
---
## 1. Pitch Philosophy — The Elicitation Method
Do not open with features. Open with questions the prospect cannot answer.
Every question surfaces a pain their clients are already feeling — silently, expensively. The prospect feels that pain on their clients' behalf. By the time the intelligence layer is revealed, the prospect is not evaluating a product. They are relieving a pressure they just felt.
**Structure:** 6 unanswered questions → dramatic reveal → feature answers → business case → flexible partnership close.
---
## 2. The 6 Elicitation Questions
Each question gets its own slide. Large type. One implication line. No answer yet.
---
### Q1 — The Fuel Leak
> *"Which of your clients' drivers is costing them the most money in fuel — right now, this month?"*
**Implication:** Every fleet has a 20% fuel variance between its best and worst driver. Without this answer, that money disappears quietly every month.
**Intelligence feature revealed:** Driver Behaviour Score — trip-by-trip fuel cost, speeding events, harsh braking, idle time per driver, ranked fleet-wide.
---
### Q2 — The Ticking Clock
> *"Which vehicle across your entire client base is overdue for a service today?"*
**Implication:** A $300 service missed becomes a $3,000 breakdown. And when it happens, your client blames the tracker company, not the maintenance manager.
**Intelligence feature revealed:** Service Interval Forecaster — odometer-based service alerts, service history log, upcoming service calendar per vehicle, configurable thresholds by vehicle type.
---
### Q3 — The Dead Hours
> *"Which of your clients had a vehicle parked for 3+ hours during working hours yesterday — and why?"*
**Implication:** Idle time is the silent tax on every fleet. Operations managers know it exists. They cannot prove it, attribute it, or act on it.
**Intelligence feature revealed:** Fleet Utilisation Dashboard — idle time per vehicle per day, utilisation rate, ghost shifts, vehicle productivity score, city-level cohort comparison.
---
### Q4 — The Dispute
> *"If a driver disputes an overtime claim tomorrow, can your client pull the proof in under 60 seconds?"*
**Implication:** Without a timestamped trip audit trail, every dispute becomes the driver's word against the manager's. HR decisions get made on gut, not data.
**Intelligence feature revealed:** Trip & Stop Audit Trail — full GPS replay, stop duration and address, driver timeline per day, exportable to PDF or CSV for HR/legal.
---
### Q5 — The SLA Gap
> *"Do your clients know if their field teams are actually reaching customers within their promised response window?"*
**Implication:** ISPs, telcos, and field service companies are contractually measured on SLA. Without dispatch intelligence, they are reporting to their own clients on guesswork.
**Intelligence feature revealed:** Dispatch & SLA Intelligence — first-response time, job completion rate, field team coverage maps, SLA breach alerts, trend by city and team.
---
### Q6 — The Unit Economics
> *"Do your clients know what it actually costs them to serve one customer — per trip, per kilometre, per job completed?"*
**Implication:** A school bus operator who drove 450 km this week cannot tell a school board whether that was efficient or catastrophic without knowing routes completed, cost per child per day, and km per route. The same gap exists in every vertical: logistics, courier, field service, NGO.
**Intelligence feature revealed:** Unit Economics Engine — cost per km, cost per job/route/delivery, output ratio (km driven vs customers/deliveries/routes served), configurable per client vertical.
---
## 3. Full Deck Structure
### ACT 1 — THE QUESTIONS (Slides 1–8)
| Slide | Content |
|---|---|
| 1 | Cover: *"6 Questions Your Clients Cannot Answer Today"* — Fireside Communications, date |
| 2 | Context setter: *"You give your clients a dot on a map. That solved visibility. This is about what comes next."* |
| 3 | Q1 — The Fuel Leak |
| 4 | Q2 — The Ticking Clock |
| 5 | Q3 — The Dead Hours |
| 6 | Q4 — The Dispute |
| 7 | Q5 — The SLA Gap |
| 8 | Q6 — The Unit Economics |
### ACT 2 — THE REVEAL (Slides 9–15)
| Slide | Content |
|---|---|
| 9 | Pivot: *"We built the answers."* — one line, full bleed |
| 10 | The Intelligence Layer — what it is, what it sits on, what it connects to |
| 11 | Answer to Q1 — Driver Behaviour Score |
| 12 | Answer to Q2 — Service Interval Forecaster |
> *"We already run this for an 80-vehicle telco field service fleet across Nairobi, Mombasa, and Kampala. The stack is live. The question is whether your clients should have it next."*
**CTA:** Book a 45-minute working session. We pull live data from one of your client's fleets and show you what we see.
---
## 4. Partnership Models (Slide 20 Content)
Present all four — let them name the one they want.
| Model | Description | Best for |
|---|---|---|
| **White-label** | Intelligence layer runs under their brand; they bill clients directly | Resellers wanting full client ownership |
| **Revenue share** | Fireside builds and operates; reseller earns % of intelligence tier revenue | Resellers with no technical capacity |
| **Technology licence** | Reseller buys the stack and runs it on their own infrastructure | Resellers with in-house tech team |
| **Joint GTM** | Both companies co-sell a combined tracking + intelligence product to new clients | Resellers wanting to expand upmarket |
> Fleet Intelligence is an analytics and alerting layer that sits on top of any GPS tracking feed. It transforms raw position data into operational decisions: driver scores, service forecasts, utilisation reports, SLA compliance, and unit economics — all in real time, configurable per client. It is white-label ready and does not require replacing your existing hardware or tracking platform.
**Pitch angle:** Your client generates video evidence every day. Without a storage layer, that evidence is gone in 72 hours. With RustFS, they have a retrievable, organised archive — per vehicle, per driver, per incident. Self-hosted, S3-compatible, no third-party cloud dependency.
---
### Add-on 2 — Data Warehouse (DuckDB)
**Pain question (Slide 24):**
> *"Can your clients run a 12-month fleet performance report without calling you, hiring an analyst, or waiting overnight?"*
**What it enables:**
- 12–24 months of position, trip, and event history queryable in seconds
- Cross-period reporting — this month vs same month last year
- Export-ready datasets for finance, insurance, and compliance
- Feeds directly from RustFS-stored CSV/Parquet files — the two add-ons compound each other
**Pitch angle:** TimescaleDB handles live operations. DuckDB handles history. Together they mean a client never loses a data point and can answer any question about any vehicle on any day going back two years — with no data team required.
---
### Tier Model (Slide 25)
| Tier | Includes | Target client |
|---|---|---|
| **Intelligence** | 6 core features + Grafana dashboards | Any fleet 5–200 vehicles |
