Status summary & roadmap to live testing · Updated v0.3 · May 2026
Prototype v0.3
Concept → Validation phase
Commercial model — confirmed
Brand pays ProofPoint directly · Agency is the licensed operator
Brand
Pays the subscription. Account holder. Owns all data. Controls which agencies can operate on their behalf.
Dashboard, analytics, exports, billing, agency management
Manager
Pays nothing. Licensed by the brand. Runs campaigns on the brand's behalf.
Control centre, campaigns, supervisors, reports
Supervisor
Pays nothing. On-ground data entry — collects paper sheets, inputs batch data via tablet.
Mobile batch entry app only
What's been built
✓ Complete
App blueprint
Name, value prop, user roles, feature set, monetisation model, tech stack.
✓ Complete
UX flow
All screens, navigation, button actions, empty/error states, user journeys — all three roles.
✓ Complete
Screen design plan
Colour system, typography, layout spec, and sample copy for every key screen.
✓ Complete · v0.3
Interactive prototype
Three roles: Brand portal (5 screens), Manager dashboard (5 screens), Supervisor mobile app (4 tabs). Live counter sync. Paper tally batch entry model.
✓ Complete · v0.3
Training manual
Branded PDF — 10 sections covering all roles, commercial model, paper tally workflow, data security commitments, sales data strategy.
✓ Complete
Sales data strategy
6-method layered approach — supervisor confirmed (MVP default), QR codes, CSV upload, POS API, retailer partnership, receipt OCR.
✓ Confirmed
Paper tally model
Reps use paper in the field. One supervisor per location collects sheets hourly and inputs aggregate batch data via tablet. No per-rep device required.
✓ Confirmed
Data security framework
Brand owns data. RLS at DB layer prevents cross-brand access. ProofPoint is data processor only. DPA 2020 / POPIA / GDPR-aligned.
Roadmap to live testing
Phase 1Validate the conceptNow — Week 2
Send the prototype + manual to 2–3 brand clients or agencies. The brand portal is now live — send to both the agency contact and their client brand. Ask if either would pay $199–$599/month for this.
Validate the commercial model. Confirm with your pilot agency that the brand-pays model works for their client relationships. Some agencies may prefer to absorb the cost and mark it up — test both conversations.
Identify a pilot brand + agency pair willing to run a real campaign on the MVP. Ideally a brand already in conversation with the agency about an upcoming activation.
Register proofpoint.app + proofpoint.io before someone else does. Low cost, high importance.
Phase 2Design system + legal foundationsWeeks 2–4
Hire a part-time UI/UX designer (contractor, 4–6 weeks). Deliver a Figma component library from the screen design plan. This is what the developer builds from — not the HTML prototype.
Draft the Terms of Service + Data Processing Agreement. The data ownership and RLS commitments in the prototype need to exist in writing before any paying client signs up. Engage a commercial lawyer now.
Paper tally sheet design. Design a branded, printable paper tally sheet template for field use — age range, gender, outcome columns, hourly collection slots. This is a physical product the supervisor uses every day.
Phase 3Hire and set up the buildWeeks 3–6
Hire a full-stack developer — React Native + Next.js + Node.js. Give them the blueprint, UX flow, Figma system, and build roadmap as the spec. Most important hire.
Stand up infrastructure — GitHub repo, Supabase project (free tier), Vercel, Expo EAS. Most are free to start. Configure row-level security policies from day one — not as an afterthought.
Database schema — brands, agencies, campaigns, supervisors, batches, interactions tables. Brand-scoped data isolation at the schema level. JWT role claims in Supabase Auth replacing the prototype's email lookup.
Stripe integration — brand subscription billing. Three tiers: Starter ($199), Campaign Pro ($599), Enterprise (custom). Brand is the billing entity, not the agency.
Phase 4Build the MVP core loopWeeks 5–14
Supervisor mobile app — Expo + React Native. Batch entry screen with tally counters, shift home, GPS check-in/out, offline queue via WatermelonDB, batch history.
Manager web dashboard — Next.js. Real-time Control Centre via Supabase subscriptions, campaign management, supervisor oversight, hourly batch chart.
Brand portal — read-only analytics view, live KPI dashboard, demographic charts, location comparison, campaign archive, self-service exports, billing screen with Stripe.
PDF report builder — server-side Puppeteer render. Section toggles, branded template, download + email-to-brand delivery.
Sales data layer — supervisor-confirmed batch counting first. CSV upload fallback. QR/promo code generation. POS API after pilot feedback.
Phase 5Live pilot with a real campaignWeeks 14–18
One brand. One agency. One store. Supervisors use paper sheets in the field, input hourly batches via tablet. Manager watches Control Centre live. Brand watches their dashboard simultaneously.
You attend in person. Watch a supervisor transcribe paper sheets and input a batch. Watch the brand dashboard update. Find every friction point before a paying client does.
Definition of done: 100+ interactions logged via batch entry, manager and brand dashboards updating live, PDF report in under 5 minutes, brand able to self-serve exports — zero WhatsApp messages or spreadsheets involved.
Key milestones
✅
Concept + prototype complete
Blueprint, UX flow, three-role prototype, training manual, commercial model confirmed. Ready to show to real brands and agencies today.
Today
🎯
Commercial validation
A brand decision-maker sees the prototype and says "yes, we'd pay for this." Gate before any development spend.
Week 2
📄
TOS + DPA drafted
Legal documentation for data ownership, processing commitments, and the brand-pays commercial relationship.
Week 3
🎨
Figma design system
Designer delivers component library. Developer can start building against real design specs.
Week 4
🔧
Developer hired + infrastructure live
Build starts. GitHub, Supabase, Vercel, Expo, Stripe configured. DB schema + RLS policies locked in.
Week 5–6
📱
Internal MVP testable
Supervisor app, manager dashboard, and brand portal working end-to-end with real data flow.
Week 10
🚀
Live pilot campaign
Real supervisors, real paper sheets, real store. Brand watches their dashboard live. The product proves itself in the field.
Week 16
💳
First paying brand client
Brand signs up and pays ProofPoint directly. Stripe active. Product is in market.
Week 18–20
The one thing that matters most right now
Do not spend money on development until a real brand decision-maker — not just an agency contact — has seen the prototype and confirmed they would pay for it directly. The commercial model only works if the brand sees the value. That conversation is the only gate left between concept and build.