diff --git a/CLAUDE.md b/CLAUDE.md index bae46ed..7cbd487 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -1,5 +1,29 @@ # CLAUDE.md — Fireside Communications · Tracksolid Fleet Intelligence +## 0. Commands + +**Package manager:** `uv` (not pip/poetry) + +```bash +uv sync # Install / sync dependencies +pytest tests/ # Run test suite +ruff check . # Lint +mypy . # Type check +``` + +**Run a query via Docker (DATABASE_URL is internal-only):** +```bash +DB=$(docker ps --filter name=timescale_db --format "{{.Names}}" | head -1) +docker exec $DB psql -U postgres -d tracksolid_db -c "SELECT COUNT(*) FROM tracksolid.devices;" +``` + +**Run a migration file:** +```bash +docker exec -i $DB psql -U postgres -d tracksolid_db < 07_your_migration.sql +``` + +--- + ## 1. What This Project Is Fleet telematics ingestion and analytics stack for a **telco first-line support client** operating in Nairobi, Mombasa, and Kampala. The client dispatches field technicians to install, repair, and maintain home and business broadband, handle LOS signal faults, service migrations, and maintain outside plant infrastructure. The fleet is ~80 vehicles across three cities, all tracked via Tracksolid Pro (Jimi IoT API). @@ -33,7 +57,7 @@ See `docs/CONNECTIONS.md` for the full shape. Summary: - **DB name:** `tracksolid_db` · **DB user:** `postgres` (internal) · `tracksolid_owner` (app) · `grafana_ro` (read-only) - **DB schema:** `tracksolid_2` (current live data, legacy stack) · `tracksolid` (new stack target, currently empty) · `infrastructure` · `dwh_gold` (aggregates) - **⚠ Schema split:** new ingestion code targets `tracksolid`; all live rows are in `tracksolid_2` until the new stack is deployed and `sync_driver_audit.py` has run. -- **DB direct access:** `DATABASE_URL` in `.env` points to `31.97.44.246:5888` — queries can be run locally via psql without SSH. Note: value has a leading space, strip it. +- **DB access:** `DATABASE_URL` points to `timescale_db:5432` (internal Docker network — not reachable locally). Use `docker exec` pattern above. See `docs/CONNECTIONS.md` for full reference. - **Container naming:** Coolify appends a random suffix. Always resolve with: ```bash docker ps --filter name= --format "{{.Names}}" | head -1 @@ -58,6 +82,7 @@ docker-compose.yaml # Services: timescale_db, ingest_movement, ingest_ev grafana/ # Grafana provisioning (baked into image) n8n-workflows/ # n8n workflow exports docs/ # Reference docs (connections, API, KPIs, project context) +docs/superpowers/ # Pitch specs and implementation plans (not deployed code) 02_tracksolid_full_schema_rev.sql # Full schema bootstrap 03..06_*.sql # Incremental migrations (06 adds assigned_city, dispatch_log, ops.*) 01_BusinessAnalytics.md # SQL analytics library — read before writing queries diff --git a/docs/superpowers/plans/2026-04-18-fleet-intelligence-pitch-copy.md b/docs/superpowers/plans/2026-04-18-fleet-intelligence-pitch-copy.md new file mode 100644 index 0000000..9931a11 --- /dev/null +++ b/docs/superpowers/plans/2026-04-18-fleet-intelligence-pitch-copy.md @@ -0,0 +1,29 @@ +# Fleet Intelligence Pitch Copy — Implementation Plan + +> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking. + +**Goal:** Write complete slide-by-slide copy for a 25-slide pitch deck and a two-sided one-pager for the fleet intelligence partner pitch. + +**Architecture:** Two output documents — pitch deck copy (all 25 slides, full text) and one-pager (front/back). Both saved to `~/Downloads/59_fleet_intelligence/`. + +**Tech Stack:** Markdown documents, no code. + +--- + +### Task 1: Write slide deck copy + +**Files:** +- Create: `~/Downloads/59_fleet_intelligence/fleet-intelligence-pitch-deck.md` + +- [ ] Write all 25 slides with complete copy +- [ ] Commit to repo copy in `docs/superpowers/specs/` + +--- + +### Task 2: Write one-pager copy + +**Files:** +- Create: `~/Downloads/59_fleet_intelligence/fleet-intelligence-one-pager.md` + +- [ ] Write front (6 questions) and back (feature summaries, models, contact) +- [ ] Commit to repo copy in `docs/superpowers/specs/` diff --git a/docs/superpowers/specs/2026-04-18-fleet-intelligence-one-pager.md b/docs/superpowers/specs/2026-04-18-fleet-intelligence-one-pager.md new file mode 100644 index 0000000..1609f52 --- /dev/null +++ b/docs/superpowers/specs/2026-04-18-fleet-intelligence-one-pager.md @@ -0,0 +1,126 @@ +# Fleet Intelligence — One-Pager +**Fireside Communications · April 2026** + +> Layout: Print double-sided A4 or A5. Front = the 6 questions. Back = product + models + contact. +> Font guidance: Questions in 24–28pt. Implication lines in 11pt. Body copy in 10pt. Generous white space — resist the urge to fill it. + +--- + +## FRONT — THE 6 QUESTIONS + +--- + +**6 Questions Your Clients Cannot Answer Today** + +--- + +**1. The Fuel Leak** +Which of your clients' drivers is costing them the most money in fuel — right now, this month? + +*Every fleet has a 20% fuel variance. Without this answer, that money disappears quietly.* + +--- + +**2. The Ticking Clock** +Which vehicle across your entire client base is overdue for a service today? + +*A $300 service missed becomes a $3,000 breakdown — and your client blames the tracker company.* + +--- + +**3. The Dead Hours** +Which of your clients had a vehicle parked for 3+ hours during working hours yesterday — and why? + +*Idle time is the silent tax on every fleet. Managers know it exists. They cannot prove it.* + +--- + +**4. The Dispute** +If a driver disputes an overtime claim tomorrow, can your client pull the proof in under 60 seconds? + +*Without a timestamped trip audit trail, every dispute is the driver's word against the manager's.* + +--- + +**5. The SLA Gap** +Do your clients know if their field teams are actually reaching customers within their promised response window? + +*ISPs and field service companies are measured on SLA. Without dispatch intelligence, they report on guesswork.* + +--- + +**6. The Unit Economics** +Do your clients know what it actually costs them to serve one customer — per trip, per kilometre, per job? + +*A school bus operator who drove 450 km this week cannot tell a school board if that was efficient — without knowing routes completed and cost per child.* + +--- + +**We built the answers. Ask us.** + +--- + +## BACK — THE INTELLIGENCE LAYER + +--- + +**What Is Fleet Intelligence?** + +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 — in real time, configurable per client, white-label ready. + +--- + +**The 6 Features** + +**Driver Behaviour Score** +Ranks every driver by trip fuel cost, speeding events, harsh braking, and idle time. Fleet managers see a weekly league table. Typical fuel saving: 15–20% within 90 days. + +**Service Interval Forecaster** +Tracks odometer against configurable service thresholds. Alerts fire 500 km before the interval is due. Service history logged per vehicle, two-week forward calendar included. + +**Fleet Utilisation Dashboard** +Shows idle time, utilisation rate, and unaccounted stops per vehicle per day. Surfaces the bottom five vehicles by utilisation every week. + +**Trip & Stop Audit Trail** +Full GPS replay, stop duration, stop address, driver timeline — per day, per vehicle. Any trip retrievable in under 10 seconds. Exportable to PDF or CSV. + +**Dispatch & SLA Intelligence** +Measures first-response time, job completion rate, and SLA compliance per field team per city. Breach alerts fire in real time. Weekly trend reports automated. + +**Unit Economics Engine** +Calculates cost per km, cost per job, and output ratio (km driven vs customers/deliveries/routes served). Configurable per vertical: logistics, school transport, ISP field service, courier, NGO. + +--- + +**Optional Add-Ons** + +**Blob Storage (RustFS)** — S3-compatible self-hosted storage for dashcam video, trip exports, driver documents, and incident evidence. Evidence that exists is evidence that wins. + +**Data Warehouse (DuckDB)** — 12–24 months of fleet history queryable in seconds. Cross-period reporting, export-ready datasets for finance and compliance. The two add-ons compound each other. + +--- + +**Partnership Models** + +| Model | How it works | +|---|---| +| White-label | Runs under your brand. You price and bill clients. | +| Revenue share | We operate it. You earn a % of intelligence revenue. | +| Technology licence | You buy the stack and run it yourself. | +| Joint GTM | We co-sell combined tracking + intelligence together. | + +We are flexible. The right structure is whatever accelerates both businesses. + +--- + +**The stack is already live — 80-vehicle telco field service fleet, Nairobi · Mombasa · Kampala.** + +**Book a 45-minute working session. We pull live data. No slides. No demos.** + +--- + +David Kiania · Fireside Communications +david@firesidecomms.com · [phone] + +--- +*© 2026 Fireside Communications. Confidential.* diff --git a/docs/superpowers/specs/2026-04-18-fleet-intelligence-pitch-deck.md b/docs/superpowers/specs/2026-04-18-fleet-intelligence-pitch-deck.md new file mode 100644 index 0000000..2072a98 --- /dev/null +++ b/docs/superpowers/specs/2026-04-18-fleet-intelligence-pitch-deck.md @@ -0,0 +1,470 @@ +# Fleet Intelligence — Pitch Deck Copy +**Fireside Communications · April 2026** + +> Presenter notes are in *italics* beneath each slide. Slide copy is in regular text. + +--- + +## ACT 1 — THE QUESTIONS + +--- + +### SLIDE 1 — COVER + +**Headline:** +6 Questions Your Clients Cannot Answer Today + +**Subline:** +Fleet Intelligence · Fireside Communications + +**Footer:** +April 2026 · David Kiania · david@firesidecomms.com + +--- +*Presenter note: Send this deck 24–48 hours before the meeting. No covering explanation needed — the title does the work. At the meeting, open with: "I sent you something. Did any of those questions land?"* + +--- + +### SLIDE 2 — CONTEXT SETTER + +**Headline:** +You gave your clients visibility. + +**Body:** +A dot on a map. Speed. Ignition status. + +That solved the first problem. Your clients know where their vehicles are. + +But their operations managers are now asking harder questions — and the current platform has no answers. + +**Footer:** +This is what comes next. + +--- +*Presenter note: Pause here. Let it breathe. Do not rush to the questions.* + +--- + +### SLIDE 3 — Q1 · THE FUEL LEAK + +**Question (large type):** +"Which of your clients' drivers is costing them the most money in fuel — right now, this month?" + +**Implication line:** +Every fleet has a 20% fuel variance between its best and worst driver. +Without this answer, that money disappears quietly every month. + +--- +*Presenter note: Watch their face. If they shift slightly, they already have a client this applies to. Don't fill the silence.* + +--- + +### SLIDE 4 — Q2 · THE TICKING CLOCK + +**Question (large type):** +"Which vehicle across your entire client base is overdue for a service today?" + +**Implication line:** +A $300 service missed becomes a $3,000 breakdown. +And when it happens, your client blames the tracker company — not the maintenance manager. + +--- +*Presenter note: This one lands hard with resellers. The breakdown is their support problem too.* + +--- + +### SLIDE 5 — Q3 · THE DEAD HOURS + +**Question (large type):** +"Which of your clients had a vehicle parked for 3+ hours during working hours yesterday — and why?" + +**Implication line:** +Idle time is the silent tax on every fleet. +Operations managers know it exists. They cannot prove it, attribute it, or act on it. + +--- +*Presenter note: "Silent tax" is the phrase to land. It's money leaving without anyone signing off on it.* + +--- + +### SLIDE 6 — Q4 · THE DISPUTE + +**Question (large type):** +"If a driver disputes an overtime claim tomorrow, can your client pull the proof in under 60 seconds?" + +**Implication line:** +Without a timestamped trip audit trail, every dispute is the driver's word against the manager's. +HR decisions get made on gut, not data. + +--- +*Presenter note: School transport clients and ISP field teams feel this acutely. If you know their client mix, call out the relevant vertical here.* + +--- + +### SLIDE 7 — Q5 · THE SLA GAP + +**Question (large type):** +"Do your clients know if their field teams are actually reaching customers within their promised response window?" + +**Implication line:** +ISPs, telcos, and field service companies are contractually measured on SLA. +Without dispatch intelligence, they are reporting to their own clients on guesswork. + +--- +*Presenter note: If the reseller has telco or ISP clients, this is their highest-value question. Reorder slides to put this one second or third for those meetings.* + +--- + +### SLIDE 8 — Q6 · THE UNIT ECONOMICS + +**Question (large type):** +"Do your clients know what it actually costs them to serve one customer — per trip, per kilometre, per job completed?" + +**Implication line:** +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 kilometres per route. + +The same gap exists in every vertical: logistics, courier, field service, NGO. + +--- +*Presenter note: The school bus example is concrete and memorable. Use it even if they have no school clients — the principle lands universally.* + +--- + +## ACT 2 — THE REVEAL + +--- + +### SLIDE 9 — PIVOT + +*(Full bleed slide. Single line. No logo. No footer.)* + +**Copy:** +We built the answers. + +--- +*Presenter note: At the meeting — say nothing. Click to this slide and let them read it. Wait three seconds. Then move.* + +--- + +### SLIDE 10 — THE INTELLIGENCE LAYER + +**Headline:** +Fleet Intelligence — What It Is + +**Body:** +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. + +**Three pillars (visual block):** + +| Ingest | Analyse | Act | +|---|---|---| +| Live GPS + events every 60 seconds | Trips, stops, driver behaviour, cost | Dashboards, alerts, scheduled reports | + +--- + +### SLIDE 11 — ANSWER TO Q1 · DRIVER BEHAVIOUR SCORE + +**Heading:** The Fuel Leak — Answered + +**Feature name:** Driver Behaviour Score + +**What it does:** +Ranks every driver by trip-by-trip fuel cost, speeding events, harsh braking, and idle time. + +Fleet managers see a weekly league table. The bottom 10% get a coaching flag. + +The saving is typically 15–20% on fuel spend within 90 days of deployment. + +**One-line summary:** +*"You finally know which driver is costing your client money — by name, by trip, by day."* + +--- + +### SLIDE 12 — ANSWER TO Q2 · SERVICE INTERVAL FORECASTER + +**Heading:** The Ticking Clock — Answered + +**Feature name:** Service Interval Forecaster + +**What it does:** +Tracks odometer readings against configurable service thresholds per vehicle type. + +Alerts fire 500 km before the interval is due. Service history is logged per vehicle. Operations managers see a two-week forward calendar of upcoming services. + +No vehicle goes over interval without a deliberate decision. + +**One-line summary:** +*"Your clients stop reacting to breakdowns and start preventing them."* + +--- + +### SLIDE 13 — ANSWER TO Q3 · FLEET UTILISATION DASHBOARD + +**Heading:** The Dead Hours — Answered + +**Feature name:** Fleet Utilisation Dashboard + +**What it does:** +Shows idle time, utilisation rate, and unaccounted stops per vehicle per day. + +Benchmarks each vehicle against the fleet average. Surfaces the bottom five by utilisation every week. + +Operations managers can identify ghost shifts, reassign underutilised vehicles, and justify fleet reduction decisions with data. + +**One-line summary:** +*"Your clients stop paying for vehicles that are not working."* + +--- + +### SLIDE 14 — ANSWER TO Q4 · TRIP & STOP AUDIT TRAIL + +**Heading:** The Dispute — Answered + +**Feature name:** Trip & Stop Audit Trail + +**What it does:** +Full GPS replay, stop duration, stop address, and driver timeline — per day, per vehicle. + +Any trip from any date is retrievable in under 10 seconds. + +Exportable to PDF or CSV for HR, legal, or finance. + +**One-line summary:** +*"Every dispute resolves in 60 seconds. The data is the witness."* + +--- + +### SLIDE 15 — ANSWER TO Q5 · DISPATCH & SLA INTELLIGENCE + +**Heading:** The SLA Gap — Answered + +**Feature name:** Dispatch & SLA Intelligence + +**What it does:** +Measures first-response time, job completion rate, and SLA compliance per field team per city. + +Breach alerts fire in real time. Weekly trend reports run automatically. + +Operations managers can prove performance to their own clients — or identify the teams that are dragging the numbers down. + +**One-line summary:** +*"Your clients stop guessing and start guaranteeing."* + +--- + +### SLIDE 16 — ANSWER TO Q6 · UNIT ECONOMICS ENGINE + +**Heading:** The Unit Economics — Answered + +**Feature name:** Unit Economics Engine + +**What it does:** +Calculates cost per km, cost per job, and output ratio — kilometres driven against customers served, deliveries made, or routes completed. + +Configurable per client vertical: +- Logistics & courier → cost per delivery +- School transport → cost per child per day +- ISP / telco → cost per site visit +- NGO → cost per beneficiary + +**One-line summary:** +*"Your clients finally know if the fleet is paying for itself — and which vehicles are not."* + +--- + +## ACT 3 — THE BUSINESS CASE + +--- + +### SLIDE 17 — CLIENT VERTICALS + +**Headline:** +One intelligence layer. Every vertical you serve. + +| Vertical | Key features | Primary KPI unlocked | +|---|---|---| +| Logistics & courier | Unit Economics + Utilisation | Cost per delivery | +| ISP / telco field service | SLA Intelligence + Audit Trail | First-response time, SLA compliance | +| School transport | Unit Economics + Service Forecaster | Cost per child per day, route completion rate | +| Construction & utilities | Utilisation + Service Forecaster | Vehicle uptime, maintenance cost per asset | +| NGO / aid delivery | Unit Economics + Audit Trail | Cost per beneficiary, donor reporting pack | + +**Footer:** +The same platform. Configured per client. No custom development required. + +--- + +### SLIDE 18 — REVENUE EXPANSION + +**Headline:** +What the intelligence layer adds to your monthly recurring revenue + +**Body:** +Today you earn **[X]** per device per month. + +The intelligence tier adds **[Y]** per device. + +Across a 200-device client, that is **[Z]** in additional MRR — from software running on data you are already collecting. + +> *Fill X, Y, Z with the reseller's actual ARPU and your proposed intelligence tier price before sending.* + +**Key line:** +No new hardware. No new SIMs. The data is already there. You are leaving revenue on the table every month it is not productised. + +--- +*Presenter note: Come to the meeting with a number filled in. "If your average client pays $8 per device and we add $4 — across your 500 active devices that's $2,000 in additional MRR from one conversation." Make it concrete.* + +--- + +### SLIDE 19 — HOW IT WORKS WITH YOUR STACK + +**Headline:** +No rip-and-replace. No migration. No risk. + +**Three points:** + +**Compatible** +Works with any Tracksolid / Jimi IoT API feed. If you are reselling Jimi hardware, the integration is already built. + +**White-label** +Runs under your brand, your domain, your client relationship. Your clients see your product. You see the intelligence. + +**Flexible hosting** +Deployed on your infrastructure or ours. Self-hosted means your client data never leaves your environment. + +--- + +### SLIDE 20 — PARTNERSHIP MODELS + +**Headline:** +We are flexible. Tell us what works for you. + +| Model | How it works | Best for | +|---|---|---| +| **White-label** | Intelligence layer runs under your brand. You price and bill clients directly. | Resellers wanting full client ownership | +| **Revenue share** | We build and operate. You earn a percentage of intelligence tier revenue. | Resellers without in-house technical capacity | +| **Technology licence** | You buy the stack outright and run it on your own infrastructure. | Resellers with an in-house tech team | +| **Joint GTM** | We co-sell a combined tracking + intelligence product to new clients together. | Resellers looking to move upmarket | + +**Footer:** +These are starting points. The right structure is whatever accelerates both businesses. + +--- + +### SLIDE 21 — CLOSE + +**Headline:** +The stack is live. + +**Body:** +We already run Fleet Intelligence for an 80-vehicle telco field service fleet across Nairobi, Mombasa, and Kampala. + +Driver behaviour. Service forecasting. Utilisation tracking. SLA compliance. Unit economics. Running today. + +The question is whether your clients should have it next. + +**Call to action:** +Book a 45-minute working session. + +We pull live data from one of your client's fleets and show you exactly what we see. +No slides. No demos. Live data. + +**Contact:** +David Kiania · Fireside Communications +david@firesidecomms.com · [phone] + +--- +*Presenter note: End here in the meeting. Do not go to the add-on slides unless they ask "what else?" or the conversation naturally opens to storage / history. The add-ons are a second conversation or a follow-up email.* + +--- + +## ACT 4 — OPTIONAL ADD-ONS + +--- + +### SLIDE 22 — ADD-ON INTRO + +**Headline:** +Two optional add-ons for clients who need more than intelligence. + +**Subheadline:** +Storage. History. Compounding value. + +**Body:** +The intelligence layer answers operational questions in real time. + +Some clients need more: a place to keep the evidence, and the ability to look back years — not hours. + +These two add-ons are optional, independently useful, and more powerful together. + +--- + +### SLIDE 23 — BLOB STORAGE · RUSTFS + +**Pain question:** +"Where does your client's dashcam footage go after a road incident — and can they retrieve it in court?" + +**Feature:** Blob Storage (RustFS) + +**What it stores:** +- Dashcam video from camera-capable devices (JC400P and equivalents) +- Trip report exports — PDF and CSV +- Driver documents — licences, PSV badges, insurance certificates +- Vehicle photos — incident evidence, pre/post condition reports +- Raw webhook event payloads for long-term compliance audit + +**Pitch angle:** +Your client generates video evidence every day. Without a storage layer, that evidence is gone in 72 hours — before any insurance claim, HR process, or court date can use it. + +With blob storage, they have a retrievable, organised archive per vehicle, per driver, per incident — held for as long as they need it. + +**Technical note (for technical conversations):** +S3-compatible. Self-hosted. No third-party cloud dependency. Runs alongside the intelligence stack on existing infrastructure. + +--- + +### SLIDE 24 — DATA WAREHOUSE · DUCKDB + +**Pain question:** +"Can your clients run a 12-month fleet performance report without calling you, hiring an analyst, or waiting overnight?" + +**Feature:** Data Warehouse (DuckDB) + +**What it enables:** +- 12–24 months of position, trip, and event history — queryable in seconds +- Cross-period reporting: this month vs the same month last year +- Export-ready datasets for finance teams, insurance renewals, and compliance audits +- Feeds directly from blob storage files — the two add-ons compound each other + +**Pitch angle:** +The live database handles operations. The warehouse handles history. + +Together, your clients never lose a data point and can answer any question about any vehicle on any day going back two years — with no data team, no waiting, no calling you. + +That is a different category of value from what they have today. + +--- + +### SLIDE 25 — TIER MODEL + +**Headline:** +Choose your stack. + +| Tier | Includes | Best for | +|---|---|---| +| **Intelligence** | 6 core features + Grafana dashboards | Any fleet, 5–200 vehicles | +| **Intelligence + Storage** | + RustFS blob storage (video, documents, exports) | Camera-device fleets, compliance-heavy clients | +| **Intelligence + Warehouse** | + DuckDB historical analytics (12–24 months) | Finance reporting, insurance, multi-branch | +| **Full Stack** | All three layers | Enterprise, telco, school networks | + +**Footer:** +Start with Intelligence. Add storage and history when your clients need them. No migration required. + +--- + +*END OF DECK* diff --git a/docs/superpowers/specs/2026-04-18-fleet-intelligence-pitch-design.md b/docs/superpowers/specs/2026-04-18-fleet-intelligence-pitch-design.md new file mode 100644 index 0000000..8165f0c --- /dev/null +++ b/docs/superpowers/specs/2026-04-18-fleet-intelligence-pitch-design.md @@ -0,0 +1,239 @@ +# Fleet Intelligence — Partner Pitch Design +**Date:** 2026-04-18 +**Author:** David Kiania / Fireside Communications +**Target:** Regional GPS tracking reseller (East Africa, mixed SME/enterprise client base) +**Relationship:** Existing — structured meeting already booked +**Outcome:** Exploratory partnership (white-label / revenue share / licence / joint GTM) +**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 | +| 13 | Answer to Q3 — Fleet Utilisation Dashboard | +| 14 | Answer to Q4 — Trip & Stop Audit Trail | +| 15 | Answer to Q5 — Dispatch & SLA Intelligence | +| 16 | Answer to Q6 — Unit Economics Engine | + +### ACT 3 — THE BUSINESS CASE (Slides 17–21) + +| Slide | Content | +|---|---| +| 17 | Client verticals — how each feature maps to logistics, school transport, ISP/telco, courier, NGO | +| 18 | Revenue expansion — *"You earn $X per device per month today. Here is what the intelligence layer adds."* (fill ARPU before sending) | +| 19 | How it works with your stack — white-label ready, Tracksolid/Jimi API compatible, no rip-and-replace | +| 20 | Partnership models — 4 options, flexible | +| 21 | Close | + +### ACT 4 — OPTIONAL ADD-ONS (Slides 22–25) + +| Slide | Content | +|---|---| +| 22 | Intro: *"Two optional add-ons for clients who need more than intelligence — they need storage and history."* | +| 23 | Blob Storage (RustFS) — pain question, what it stores, pitch angle | +| 24 | Data Warehouse (DuckDB) — pain question, what it enables, pitch angle | +| 25 | Tier model — Intelligence / +Storage / +Warehouse / Full Stack | + +### CLOSE — Slide 21 + +> *"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 | + +--- + +## 5. Intelligence Layer — Technical Summary (Slide 10 Content) + +Three sentences for the deck: + +> 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. + +**Stack (internal reference, not for deck):** +- Ingestion: Python → TimescaleDB/PostGIS (60s position poll, 30m high-res trail, webhook push) +- Analytics: SQL aggregates → `dwh_gold` layer → Grafana dashboards +- Deployment: Docker Compose on Coolify; self-hosted, client-isolated +- API source: Tracksolid Pro / Jimi IoT Open Platform (compatible with any Jimi-based reseller stack) + +--- + +## 6. One-Pager Layout (Meeting Leave-Behind) + +**Front — The 6 Questions** +- Headline: *"6 Questions Your Clients Cannot Answer Today"* +- Q1–Q6 listed cleanly, large type, no answers +- Footer: *"We built the answers. Ask us."* + +**Back — The Intelligence Layer** +- Section 1: What it is (3 sentences from Slide 10) +- Section 2: The 6 features in 2 sentences each +- Section 3: Partnership models (4 options, one line each) +- Footer: David Kiania · Fireside Communications · contact details + +--- + +## 7. Preparation Checklist Before the Meeting + +- [ ] Fill in reseller's actual device ARPU on Slide 18 before sending the deck +- [ ] Confirm their primary client verticals (logistics-heavy? school transport? ISP?) and reorder Q slides to lead with their most relevant pain +- [ ] Prepare one live Grafana dashboard screenshot per feature for the meeting (not the deck) +- [ ] Have a 45-minute working session slot ready to offer at close +- [ ] Know the answer to: *"Which of your clients would you pilot this with first?"* — be ready to suggest one + +--- + +## 8. Optional Add-On Products + +### Add-on 1 — Blob Storage (RustFS) + +**Pain question (Slide 23):** +> *"Where does your client's dashcam footage go after a road incident — and can they retrieve it in court?"* + +**What it stores:** +- Dashcam video from camera-capable devices (JC400P) +- Trip report exports (CSV/PDF) +- Driver documents — licences, PSV badges, insurance certificates +- Vehicle photos — condition reports, incident evidence +- Webhook event payloads for long-term audit + +**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 | +| **Intelligence + Storage** | + RustFS blob (video, docs, exports) | Camera-device fleets, compliance-heavy clients | +| **Intelligence + Warehouse** | + DuckDB historical analytics | Finance, insurance, multi-branch reporting | +| **Full Stack** | All three layers | Enterprise, telco, school networks | + +--- + +## 9. Success Criteria + +The pitch succeeds if the prospect: +1. Books the 45-minute working session, OR +2. Names a preferred partnership model, OR +3. Names a client they want to pilot with + +Any one of these three is a win. The deck and one-pager are designed to generate at least one of them.