How-to video — Danni narration + Skynet Flow demo

Use this page as the shooting script, screen-demo checklist, and discovery questionnaire for Danni. The live walk-through should use Dani's Express Mart — demo site (pickup, inventory story, sales and payroll band). Drop a hosted video URL into the embed below when it exists.

What the video should prove (in plain language)

• One pattern, many storefronts: each business gets a guest-facing site (hours, story, menu or offerings, optional pickup path) without exposing the operator console on the public web.
• AI assistant per business: scoped to that location’s catalog, policies, and voice — same Skynet Flow backbone, different “soul” and facts (hours, allergens, fuel vs kitchen, etc.).
• Payroll and payments: margins and revenue buckets (fuel, food, retail) stay separated in the story you already show on the Dani's page; payroll follows real shifts and islands (kitchen vs floor). Spell out options: who runs approve step, direct deposit vs check, which provider stays for now vs what Skynet Flow replaces later.
• Path from demo to live: today’s sites are static illustrations; wiring is “Flip these switches” — catalog, inventory truth, payments — not a redesign every time.

Narration + demo beats (≈ 8–12 minutes)

1. Open (15 s): Danni on camera or voice-only — “This is how we run every location on one stack.”
2. Hub (30 s): Screen: Maine Skynet Flow hub — show that Lincoln-area businesses each have a link; mention the full count you are targeting (e.g. nine public sites now, eleven businesses when you include entities without their own site yet).
3. Guest experience (90 s): Dani's site — hero, hours, gallery; stress “hosted on our site, not only Facebook.”
4. Pickup demo (2 min): Build a basket; say aloud that live mode checks stock.quant and kitchen capacity — demo is static but the contract is real.
5. Orders → inventory (90 s): Scroll “How orders hit inventory”; narrate the flow from web order to back office.
6. Sales, register, payroll (2 min): “Sales, register & payroll” section — buckets, shifts, islands; tie to how Danni actually approves payroll today.
7. AI assistant (60 s): Explain per-business assistant: answers from approved facts, hands off to staff for exceptions; no single chatbot for all brands mixed together.
8. Popmenu and “for now” (45 s): Acknowledge current Popmenu (or other) usage — Skynet Flow can sit beside it first, then absorb ordering or menu when you choose to migrate.
9. Close (30 s): CTA — “Answer the discovery list so we can clone the pattern for every business and wire feedback sites.”

Information to ask Danni (discovery — expand to all businesses)

Capture answers in a shared doc or form. Goal: enough signal to duplicate the Dani's template for every legal entity, public site, and feedback channel without guessing.

A. Master roster (11 businesses + sites)

• Legal business name, DBA, EIN or “uses parent EIN,” and which locations roll up together.
• Which entities need their own public website vs share one site with tabs.
• Primary address, phone, hours source of truth (who updates when hours change).
• Brand colors, logo files, and one “hero” photo per site.
• Social URLs (Facebook, Instagram) and whether embeds are allowed on the new site.

B. “Feedback websites” and customer voice

• Where do customers complain or praise today (Google reviews, Facebook messages, email, phone).
• Whether you want a dedicated feedback or survey page per brand, or one regional page.
• Who reads feedback weekly and who is allowed to respond publicly.
• Any industries with extra rules (alcohol signage, lottery, tobacco) that affect public copy.

C. Current IT — Popmenu and stack

• Popmenu (or other) login owner, contract end date, and which locations use it.
• What Popmenu does today only: online ordering, menu hosting, loyalty, email — check all that apply.
• POS in store (vendor, version), fuel controller if any, and whether sales export to accounting.
• Payroll provider, timeclock method, and who approves each pay run.
• Email domain and who administers DNS (needed later for SPF/DKIM and branded mail).

D. Our strategy “for now” vs replace-in-time

• Phase 1 — beside current tools: static or semi-live sites + AI from approved facts; no forced cutover from Popmenu on day one.
• Phase 2 — ordering truth: connect catalog and inventory so the web path matches what the store can fulfill.
• Phase 3 — payments and payroll in Skynet Flow: only when Danni picks providers and signers; document interim manual steps explicitly.
• Which workflows must never break during migration (e.g. lottery settlement, fuel).

E. What changes in Danni’s day-to-day processes

• Who enters new SKUs or menu items today — same person after go-live?
• How exceptions work (86’d item, price override): who gets pinged, SMS vs in-app.
• Training: one “store lead” per location certified on the operator console.
• Reporting: which weekly numbers does Danni need in one dashboard (margin by bucket, labor %).

F. Payments and payroll options (decision log)

• Card present vs card not present; who eats processing fees for online pickup.
• Tips: pooled vs by employee; charge tips to card settlement rules.
• Direct deposit cutoff times; new hire onboarding checklist (I-9, W-4).
• Multi-store payroll: single FEIN run vs separate runs per entity.

Technical references stay in sqv-forge/README.md per this repo README; keep the video and this page operator-facing.