Launch Control / buyer path cockpit

One page to prove the whole machine works.

Configurator front door, Snap Suite app layer, restaurant WhatsApp attack flow, campaign motion, browser preview leads and production capture status. This is the cockpit we use before switching on live API persistence.

0Total preview leads
0Homepage leads
0Snap leads
0Configurator leads
0Restaurant orders
0Partner fallback leads
0Client demo leads
0Campaign touches
OffCapture endpoint

Production capture status

Reads `_site/attoh-lead-config.js`. Keep endpoint, asset endpoint and public token empty until Craig approves the live route. Readiness means: endpoint configured, CORS accepts the public site, token validation passes, JSON fallback or persistence is confirmed, and this smoke test accepts a harmless payload.

Smoke test idle. Configure endpoint/token only after approval, then run a harmless test payload.

Recommended launch sequence

Use this when we move from local preview to live capture.

1. Static pathConfigurator + Snap pages load shared config
2. API pathFastAPI `/api/lead-capture` receives JSON
3. PersistenceJSON fallback first, Supabase table when configured
4. Sales layerFollow-up includes recommended Snap app tools

White-label product shelf

The immediate products to sell through partner trust while ATTOH powers fulfilment, tooling and lead capture.

72-hour white-label campaign board

Run these first. Each route has a partner-branded product shelf, a controlled offer and copy you can paste into manual outreach today.

Recent homepage leads

Recent configurator leads

Recent Snap leads

Recent partner fallback leads

Recent client demo leads

Sector app-layer matrix

What the configurator should recommend after a buyer picks a sector.

One-click buyer-path tests

Use these to quickly prove the front door, Snap tools and lead dashboard in the browser.