What's shipped, what's active, and what's queued for the payments + loyalty app. One config-driven codebase — every merchant is a config, never a custom build.
The keystone. Cloudflare D1 as the queryable system-of-record: customers, loyalty, transactions, consent log, and an append-only event log feeding the reporting dashboard (bad reviews saved, new/returning customers, messages sent, sent to Google, surveys — 30d/90d/all). Live on flavir-api; tracked Google redirect + consent endpoint wired.
The link in the temp-points SMS. Branded, count-up/stamp graphic, expiry countdown, happy-hour, birthday, two-tier consent. Live at helplocal-signup.pages.dev. Worker wiring pending.
Customer "my rewards" home: shared loyalty graphic (balance/progress), expiry + happy-hour chips, and a merchant-controlled specials/deals/events feed. Live at helplocal-hub.pages.dev.
flavir-api deployed with Stripe secrets + Connect webhook; app + onboarding point at the live API. Test mode until live keys flip on (the go-live switch).
Rep tool: create a Stripe Standard account + hosted setup link, configure the app, set the free trial, launch. Verified against the sandbox end-to-end.
Fee computed server-side (client can't lower it); $0 during trial, auto-activates after. Reviews/surveys/customers counted from day one; merchant scoreboard page renders the results.
Counter + sit-down flows: rewards ask, lookup, join incentive, review, tenders, tip, receipt. Live at helplocal-app.pages.dev.
Onboard + direct charge + application fee routed to the platform. Verified end-to-end in the sandbox.
Per-merchant config + billing on the record; two-tier (merchant vs master) enforced server-side; app pulls its config by slug. Tested via wrangler dev.
The tablet check-in screen: phone-number entry → points or stamp mode, counter / table / online service, plus demoable scenarios (new, returning, reward, IG-follow, happy-hour, survey). Fully config-driven — one build, every merchant. Live at helplocal-kiosk.pages.dev.
The compliant review-acquisition flow, played out on the customer's phone: 1–5★ survey → one-time next-visit coupon (+ optional text-club opt-in) → review routing (happy → Google, unhappy → private make-it-right, public always offered) → done. Ask-once suppression built in. Lives in the kiosk survey scenario.
Audit + extend the worker routes for the full flow. Includes the review-link SMS sender + a tracked redirect (to capture Google click-through) and wiring the signup/hub pages to the backend.
Points/stamp ledger + earn/redeem, inactivity expiration, happy-hour multipliers, and the config-driven stacking earn engine (base + code + streak + happy-hour). Server-authoritative like the fee. Builds on #26; hosts the #36 streak state.
Prototype shipped (helplocal-kiosk ?scenario=streak): 🔥 streak badge + stacked-earn breakdown on the check-in confirmation, and the full streak SMS comms series in the preview (ignite → at-risk → milestone), each transactional + neutral link (come-back lives on the hub). Params: streak / streakgoal / streakperiod (day|week|month). Still to do: the layerable config array (cadence/count × day/week/month, %-off reward, per-layer per-visit/milestone) + server-authoritative state in D1, computed like the fee — lands with #28.
The streak-led product as its own toggle position + options (top of the demo toggle). NEW customer: phone entry → step 2 consent screen (phone prefilled/greyed + "check for offers & perks" marketing boxes, unchecked = PEWC) → step 3 "reply YES to the text to confirm." Streak credited on step 1 — never gated behind consent; returning customers skip the consent step. Two previewable SMS variants: no opt-in = transactional status + neutral link to a streak-benefits page (details live on the page, not the text); opted-in = more descriptive in-text. Plus the confirmation "Reply YES" text. New streak-benefits webpage = the neutral-link destination.
The strategy-session tool: toggle streaks (layerable) + happy-hour + expiration + base earn + bonuses live in front of the merchant and preview the customer experience. Output = the merchant's config record. The consultative sell — not a dumb points app. (Merchant self-serve version = #19, later.)
Visual guide + discovery questions + design framework for designing a merchant's program: visit-frequency → streak period, threshold just above the median (incremental, not cannibalizing), reward choice, happy-hour to slow periods, expiration for urgency. Economics guardrails baked in. Usable in a real meeting before the designer UI exists.
The missing "learn" asset. Mom-Test-style questions (Rob Fitzpatrick) to learn a merchant's real pain BEFORE pitching — non-leading, past-behavior-focused. Run alongside the demo so every conversation teaches, not just sells. The demos are the "show"; this is the "learn."
Name the single belief that kills this if it's false (e.g. "merchants pay $100/mo for streak differentiation" or "streaks actually change visit frequency"), then design the cheapest test of just that. Aims the effort at the kill-shot instead of building broadly.
15–20 real in-lane shops (signal-filter per vertical-gtm-matrix: anonymous-transaction, <~50 reviews, newer) + how to actually get in the door this week. A demo with no distribution is a painting in a closet.
A structured first-yes: free or discounted pilot in exchange for feedback + being a reference. The cheap way to land merchant #1. (Demo narrative / walkthrough script is covered by #39.)
Time-based messaging the worker can't do yet: points-expiry reminders + automated re-engagement. Respects consent, STOP, quiet hours.
Pair a device to a merchant at first-run; per-device token required to charge + write settings.
Download customers / transactions as CSV, opens in Excel. Small, DB-agnostic worker endpoint.
Off-machine backup + version control. 10+ commits live only on this machine. Needs a gh login.
WebView + Stripe Terminal SDK; discover the M2 reader (BLE/USB) and fire a charge. Verify with the simulated reader. Spec first.
M2 ($59) + roaming mount ($5), paired to a host phone (M2 reads the card, so no NFC needed). Run a real live charge.
Internal-testing track or direct install — no public store needed for direct-sold merchants.
Merchant dashboard to edit their own settings. Build when manual changes become a burden.
Auto-post a daily code to the merchant's Instagram story; customers enter it (any time that day) for a stacked bonus — turning loyalty into a daily owned-channel impression. Gated: Meta app review (instagram_content_publish) + merchant IG Business connect; static story only (no interactive stickers). Confirm merchant demand before building.
On-device Clover app — the no-second-device / scale play. Deprioritized: don't let it block launch.
Move to ~/dev for faster git. Optional — only if local git feels slow. Keep Time Machine on the rest.
Swift + WKWebView + Terminal iOS SDK for the App Store. Only if an iPhone-based merchant needs it.
Single charge + ACH-sweep of fees (no Stripe app fee), optional residual. The Stripe-freeze hedge.