Engagements
New / update engagement (priced by calc/billing on the engine)
Onboard: start engagement (assigns the soft store keys + seeds the monitoring roster)
Without the soft store keys (aeo_store_client_id/metro_id/engagement_id) a client's store events can't be reconciled (Loop 2) and reports won't join. Seeding the roster is what makes weekly monitoring actually run for this client×metro. Supply an email to also raise the audit invoice.
Send the MSA for signature (DocuSign; keyless → a stub until creds are set)
Raise an invoice (Stripe; keyless → a stub that reports what it would charge)
Monitoring roster (1 active / 1 total client×metro)
| Client | Name | Metro | City | Flags | Status | Pause / un-pause |
|---|---|---|---|---|---|---|
| stg-eng-1 | STG | stg-metro | Tampa | — | active |
SEO panel (1 active / 1) — drives the weekly seo_capture job (serp/local-grid/gsc/crawl)
Metros: one per line as name, lat, lng, radius_km?, grid_size? — lat/lng enable the local-grid pass (radius_km default 16, grid_size default 5; odd N includes the exact center). A metro with no lat/lng is kept name-only and used for the organic SERP pass. Business is a NAP JSON object.
stg-eng-1active · roofing tampa · Tampa
Engagements (1)
| Id | Name | Tier | Metros | Comp | Monthly $ | Migration $ | 1st invoice $ | State | |
|---|---|---|---|---|---|---|---|---|---|
| stg-eng-1 | STG Engagement | aeo | 1 | standard | 2500 | 0 | 1500 | draft | Edit |