Mike David — Marketing Pilot Timeline

Phase 1

Weeks 1–3

Data Foundation & Validation

POS data ingestion, 5 validation scripts, 44K customer profiles, 9 segments built. POS-agnostic from day one.

Already started

Customer Intelligence Layer

Behavioral patterns, tier classification, churn alerts, engagement decline detection. Three verified revenue levers: profile gap, 53.6% dormancy, $790K unused points.

RFP 4.1 — Core deliverable

Phase 2

Weeks 4–6

A/B Offer Testing & SMS Automation

Design and execute controlled offer tests. Track redemption, ROI. Build SMS micro-survey system for demand signals.

RFP 4.1 + 6.3

In-Store Optimization & Competitive Signals

Product/promo/timing insights from intelligence layer. Gas Buddy API + local price monitoring. Early warning system.

RFP 4.5 + 4.6

Founder Command Dashboard (Retail)

One screen, 30 seconds. 5 KPIs: returning %, at-risk customers, partnerships, offer ROI, revenue protected.

RFP 4.7

Phase 3

Weeks 7–8

"What Would Mike Do" Playbook

Codified founder decision logic from transcript evidence. When X happens, do Y.

RFP 4.2

Partnership Outreach Engine

Scripts, value props, tracking system built. Your team executes. Mechanics, dealers, fleet, contractors, realtors, tourism.

RFP 4.4 — We build, you execute

POS Migration Checklist & Replication Playbook

What's portable, what localizes, what breaks at scale. Documentation after system is proven.

RFP 4.3 + 4.8

Decision Gate

Open Questions Before Kickoff

Scope & Strategy

Voice agent: optional or required? RFP says "optional" but success metrics say "non-negotiable." This changes Phase 1 timeline and pricing.
Execution ownership. We build tools and strategy. Who on Mike's team runs campaigns, makes calls, sends messages?
Revenue assumptions. Three levers identified from verified data — dollar impact depends on execution assumptions we validate together.
Relationship intelligence is separate. Mike mentioned wanting this, but it's not in the RFP. The $5K/mo covers marketing pilot scope only — not transcription intelligence, SOP generation, or dashboards for Tiffany/Leah.

POS & Data — Questions from Zain

POS scope: Is this about migrating/changing the POS in the future, or just wiring up to Supabase? If it's just the connection, that's an easy lift. If it involves Delphi upgrades, that's a different project.
POS data sync: Andre's sync still appears to be manual or delayed. Are the inflated sales numbers resolved? What's the actual refresh cadence — end of day? Real-time?
In-store optimization depth: How much historical data do they actually have? What depth of analysis are they expecting?

Deployment & Maintenance — Questions from Zain

Their environment or ours? Are we deploying in Mike's infrastructure, or are we hosting and they access through us? This changes credentialing, costs, and handoff complexity.
Credentials: Their API keys and accounts vs. ours? Needs to be sorted before any deployment.
Data retention: Do they want full indefinite retention of outputs and artifacts? Or can we consolidate/delete after a certain period?
Who maintains internally? After the pilot, who on their side keeps these systems running — Andre? Tiffany? This determines how we build for handoff.
Tiffany as operator: Would she run the marketing systems month-to-month after they're built? Needs to be confirmed before Phase 1 is actionable.
Long-term support plan: If we build these systems, we need to explain how we support him ongoing — or have a clean handoff process documented.