docs: add blob storage and data warehouse as optional pitch products
RustFS (S3-compatible blob) and DuckDB (historical analytics) added as optional add-on tiers with elicitation pain questions and tier model. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
9f4406d863
commit
c6e4a227c8
1 changed files with 54 additions and 1 deletions
|
|
@ -116,6 +116,15 @@ Each question gets its own slide. Large type. One implication line. No answer ye
|
|||
| 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."*
|
||||
|
|
@ -176,7 +185,51 @@ Three sentences for the deck:
|
|||
|
||||
---
|
||||
|
||||
## 8. Success Criteria
|
||||
## 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
|
||||
|
|
|
|||
Loading…
Reference in a new issue