11 SaaS products · Ecosystem role definitions · What's done · What's next · Critical gaps
Current state of all 11 SaaS products and their integration with Boom Online Ordering (BOO)
BOOM_ECOSYSTEM_MASTER_CONTEXT.md. The master doc only lists 10 products; the SaaS portfolio has 11. These need to be added.
Build status, deployment status, ecosystem role, and integration checklist for each product
Creative output engine — generates ads from BOO menu items, publishes to social via Ayrshare, handles print-on-demand via Printful.
ad_ · CoolifyDemand generation — drives organic search traffic to BOO ordering pages via SEO-optimized blog content with UTM-tagged ordering CTAs.
bl_ · CoolifySEO infrastructure layer — auto-generates schema markup for every BOO ordering page, tracks Google Maps rank position, feeds keyword opportunities to Bloggy.
rk_ · CoolifyReporting & white-label layer — powers BOO Enterprise "white-label portal" feature. Should eventually pull from all 11 products into unified client view.
The Moat: BOO price change → Displayee TV updates instantly via Supabase Realtime. No other platform offers this. Menu sync is the primary reason clients add Displayee.
di_ · CoolifyDistribution engine — for restaurants without BOO ordering. Shares the same multi-channel publish API with BOO Promotion Center (build once, use both). Hard Sep 15 launch deadline.
sv_ · Target Sep 15, 2026AI customer support layer — embeds on BOO ordering pages to answer customer questions, handle order FAQs, and let human agents take over live via the Live Inbox dashboard.
ry_ · Vercel (NOT Coolify)Physical-to-digital bridge — printed QR codes on table cards, menus, and flyers bring dine-in customers into the BOO digital ordering experience.
qr_ · CoolifyQuality gate — ensures AI-generated content (Addee ads, Bloggy posts) gets client approval before publishing. Prevents unauthorized content from going live under restaurant's brand.
ap_ · CoolifyCatering conversion tool — walk-in guests see live catering packages (from BOO menu) and sign contracts on iPad on the spot. Eliminates the "I'll email you a contract" delay that loses deals.
sn_ · CoolifyTrust & compliance layer — Compliee widget auto-installs on EVERY BOO client ordering page. Free widget + monitoring = compliance signal that differentiates BOO from competitors. ⚠️ Never market as "ADA compliant" (FTC fine risk).
cp_ · Coolify (Playwright needs Docker) · NOT VercelWhich products talk to which, and what's the current status of each connection
| From → To | Data / Event | Status | Priority |
|---|---|---|---|
| BOO Core → SaaS Tools | |||
| BOO → Displayee | Menu items, prices (Realtime) | ✅ Live (beta, Guarapos) | — |
| BOO → QRcodee | Ordering URL pre-loaded | ⚡ Partial | High |
| BOO → Bloggy | Restaurant name/menu → content context | ⚡ Partial | Med |
| BOO → Rankee | Menu data → schema markup | ⚡ Partial (manual) | High |
| BOO → Compliee | Client site URL → auto-scan | ○ Not Built | 🔴 Urgent |
| BOO → Replyee | Widget embed on ordering page | ○ Not Built | High (Oct) |
| BOO → Addee | Menu items → ad generation trigger | ○ Not Built | Med |
| BOO → Signnee | Catering menu items + pricing | ○ Not Built | Q4 2026 |
| BOO → Dashee | Orders, revenue, customer data | ○ Not Built | High |
| BOO → Servvee | Shared distribution API | ○ Not Built (Aug 3) | 🔴 Sep 15 |
| SaaS Tools → SaaS Tools | |||
| Rankee → Bloggy | Keyword opportunities → topic suggestions | ○ Not Built | Med |
| Addee → Aprovee | Generated creative → approval queue | ○ Not Built | Med |
| Addee → Displayee | Approved promo creative → TV slot | ○ Not Built | Low |
| Aprovee → Addee | Approval signal → publish to social | ○ Not Built | Med |
| Compliee → Signnee | Widget embed on iPad pages | ○ Not Built | Q4 2026 |
| Bloggy → Aprovee | Post draft → client review (optional) | ○ Planned | Low |
| SaaS Tools → BOO (Return Loop) | |||
| Bloggy → BOO orders | utm_source=blog → orders.source_utm | ○ Migration 031 pending | High |
| QRcodee → BOO orders | utm_source=qr → orders.source_utm | ○ Migration 031 pending | High |
| Compliee → BOO portal | Accessibility score → restaurant dashboard | ○ Not Built | Med |
| Replyee → SureContact | Visitor email → restaurant contact list | ○ Not Built | Med |
| All Products → Dashee (Reporting) | |||
| BOO → Dashee | Orders, revenue, customers | ○ Not Connected | High |
| Rankee → Dashee | SEO rank score widget | ○ Not Connected | Med |
| Bloggy → Dashee | Post count, traffic performance | ○ Not Connected | Med |
| Compliee → Dashee | Accessibility score widget | ○ Not Connected | Med |
| Addee → Dashee | Ad performance, social metrics | ○ Not Connected | Low |
| Third-Party APIs | |||
| BOO → SureContact | Order confirmations (transactional) | ✅ Live (241 Guarapos contacts) | — |
| BOO → Stripe | Payment processing | ✅ Live (card, Apple Pay, Google Pay) | — |
| BOO → Claude API | AI upsells, menu generation | ✅ Live | — |
| → Google My Business API | Promo posting to Maps/Search | ○ Building Aug 3–9 | 🔴 Sep 15 |
| → Meta Graph API | Instagram promo posting | ○ Building Aug 17–23 | 🔴 Sep 15 |
| → LinkedIn Share API | LinkedIn promo posting | ○ Building Aug 17–23 | 🔴 Sep 15 |
| Resource | Value | Status |
|---|---|---|
| Supabase (self-hosted) | db.boommedia.us | ✅ Live, all 9 apps migrated |
| Coolify (deploy platform) | 159.65.235.140:8000 | ✅ Live |
| DocuSeal (e-signature) | sign.boommedia.us | ✅ Live (for Signnee) |
| Stripe account | Shared across all products | ✅ Live |
| Resend (email) | From addresses per product | ✅ Live |
| Google OAuth credentials | My Business API | ❌ Not obtained |
| Meta Business OAuth | Instagram Graph API | ❌ Not obtained |
| LinkedIn Developer OAuth | Share API | ❌ Not obtained |
| SureContact promo templates | 3 templates (Limited/Seasonal/Weekly) | ❌ Not created |
| Compliee GitHub repo | github.com/boommedia/compliee | ❌ Code not pushed |
| Compliee Stripe products | STARTER/PRO/AGENCY price IDs | ❌ Not created |
Ordered by urgency — these block the Sep 15, 2026 launch or are urgent pre-requisites
Compliee MVP is code-complete (Jun 9, 2026) but has NEVER been deployed. The Git repo has not been initialized or pushed. No DB migration run. No DNS configured. Every BOO client ordering page is supposed to have the Compliee widget — but there's nothing to point them to.
git init && git add . && git commit && git push → github.com/boommedia/complieesupabase/migrations/001_compliee.sql on db.boommedia.usReplyee Phase 1 live chat is code-complete (Jun 10, 2026) but the Vercel deployment hasn't been done, and the live_chat SQL migration hasn't run. The type-check was kicked off in background but result not confirmed.
migrations/002_live_chat.sql on db.boommedia.usThe entire Servvee + BOO Promotion Center launch on Sep 15 depends on Google/Meta/LinkedIn OAuth credentials being obtained and SureContact promo templates being created. Without these, the distribution API build (Aug 3) cannot start.
The BOOM_ECOSYSTEM_MASTER_CONTEXT.md describes Replyee as "Unified review inbox for Google, Yelp, Instagram, Facebook reviews." Replyee.online is actually an AI chatbot platform with live human takeover. This must be corrected before any team briefing, pitch deck, or client-facing material references the ecosystem doc.
BOOM_ECOSYSTEM_MASTER_CONTEXT.md to: "AI chatbot + live support (RAG, SalesIQ-style)"BOOM_MASTER_ECOSYSTEM.html Tab 2 Replyee product cardBoth Dashee (white-label dashboards) and Aprovee (approval workflows) are live products in the SaaS portfolio but are NOT listed anywhere in BOOM_ECOSYSTEM_MASTER_CONTEXT.md. The doc says "10 SaaS products" when there are 11.
BOOM_ECOSYSTEM_MASTER_CONTEXT.md as "White-label portal / reporting dashboard"BOOM_MASTER_ECOSYSTEM.html header: "10 SaaS products" → "11 SaaS products"BOOM_ECOSYSTEM_MASTER_CONTEXT.md section 3 says Compliee uses prefix co_. The actual Compliee code (001_compliee.sql) uses prefix cp_. Must be corrected before the migration runs to avoid confusion.
BOOM_ECOSYSTEM_MASTER_CONTEXT.md section 3: Compliee prefix from co_ → cp_SAAS_PORTFOLIO.md table prefix section (currently blank for Compliee — should be cp_)These migrations must be run on db.boommedia.us before the Aug 3 development kickoff:
publish_status JSONB, promo_analytics tabletier_allocations JSONB, google_oauth JSONB, meta_oauth JSONB, linkedin_oauth JSONBorders.source_promo_id, source_channel, source_utmcp_sites, cp_scans, cp_violations, cp_statements, cp_subscriptionsconversations.mode, conversations.assigned_to, messages role='agent'Jun 13 – Dec 2026 · Ecosystem integration milestones
Conflicts between the master ecosystem doc, the SaaS portfolio, and actual code — must be resolved
"Replyee — Unified inbox for Google, Yelp, Instagram, Facebook reviews; sentiment analysis; auto-reply. Links customer orders → reviews they left (order → reviewer match)."
AI chatbot platform with RAG (pgvector + OpenAI embeddings + Claude Haiku). Widget embeds on any site. Phase 1 adds SalesIQ-style live chat with human agent takeover via Live Inbox dashboard.
Not mentioned anywhere. Doc says "10 SaaS products." White-label portal is listed as an Enterprise feature but the underlying tool (Dashee) is not named.
Dashee is built and live at dashee.boommedia.us. It IS the white-label portal. It should power the BOO Enterprise "White-label portal" feature AND give all clients a reporting dashboard.
Not mentioned anywhere. No approval workflow concept is described in the master ecosystem document.
Aprovee is built and live at aprovee.boommedia.us. It serves as the quality gate for AI-generated content before it goes to clients. Critical for the content pipeline: Addee → Aprovee → publish.
Section 3: co_ prefix for Compliee
cp_ prefix (cp_sites, cp_scans, cp_violations, cp_statements, cp_subscriptions)
co_ → cp_.
Optional add-on: "Replyee ~$75/mo — review management" with note: "Links customer orders → reviews they left"
SaaS portfolio says ~$49–$99/mo (TBD). Product is AI chatbot, not review management. There's no order → reviewer match feature built or planned in current Replyee codebase.
Status: "📋 Planned" for Compliee
Compliee MVP was completed Jun 9, 2026. Code exists at SaaS/Compliee/. Status should be "🔨 Built — pending deploy."
ECOSYSTEM_ROLE.md was created in each SaaS product's .md/ folder