Ecosystem Cleanup — Decision Board

Everything below was verified against actual code (routes, APIs, SQL) on 2026-07-06. Work through Section 3 once — pick a decision on each recommendation, add notes, hit Export decisions, and the cleanup is settled. Your choices auto-save in this browser. Canonical text version: SaaS/.md/APP_BOUNDARIES.md.

The strategy these decisions serve: Every app exists to make B.O.O. restaurants more successful first, then gets sold separately to agencies later. So the priority order is: (1) every app has a real, working B.O.O. integration, (2) no two apps do the same job — because when agencies buy them à la carte, overlapping products compete with each other on your own pricing page.

✅ Executed 2026-07-06: R1/R2/R6/R7-copy + the R10 swap are DONE in code. boo-v2 branch ecosystem-cleanup (pushed): all app descriptions fixed (Replyee=chat, Compliee=scanning, Assistee=remote support, Servvee delisted, Staff Recognition naming) + BOO now consumes the Rewardee engine (new src/lib/rewardee.ts; staff reviews + checkout earn/redeem with ledger, legacy fallback until SQL runs). Rewardee repo: Phase 1 (43 files) committed+pushed + supabase/004_boo_bridge.sql. Your 4 steps: ① run Rewardee SQL 001→004 at studio.boommedia.us ② merge ecosystem-cleanup → main ③ test one order + one staff rating ④ create the 3 Rewardee Stripe products. Details: SaaS/.md/CLEANUP_EXECUTION_HANDOFF.md.

1 · Who owns what

The one-job-per-app map. If a feature idea fits the right column, it belongs in the other app.

AppOwns (the job)Does NOT do — owned elsewhere
AddeeAd & social creative generation (AI copy + visuals), Google Ads pushScheduling → Posttee · Blogs → Bloggy
BloggyLong-form SEO content — blogs, URL/YouTube-to-blog, autoblog, repurposeSocial publishing → Posttee · Ad creative → Addee
RankeeLocal SEO measurement — rank grids, audits, backlinks, competitorsCitations/reviews → Localey · Writing → Bloggy
PostteeSocial scheduling & publishing (Meta, GBP, LinkedIn)Creating the creative → Addee
LocaleyPublic reputation — citations, listings, review requests & monitoringChat → Replyee · Rank tracking → Rankee · Staff ratings → Rewardee
DasheeClient portal & reporting hub — analytics, invoices, appointments, docs, messaging per verticalTracked QR → QRcodee · E-signing → Signnee · ADA → Compliee
AproveeApproval workflows — visual feedback pins, sign-off audit trailLegal e-signatures → Signnee
ServveeB.O.O.-internal promo/menu layer (sunset candidate)Everything standalone
DisplayeeScreens — menu boards, signage, KDS on Fire TVOrdering itself → B.O.O.
ReplyeeAI chatbot (RAG) + live chat — bots, agent inbox, human takeover, leadsReviews — never. → Localey
QRcodeeTracked, branded QR codes + scan analytics, templates, bulk
RewardeeCustomer loyalty (points, stamps, gift cards) + staff recognitionPublic/Google reviews → Localey
ComplieeAccessibility scanning / monitoring / fix guidance (never “makes compliant” — FTC)
SignneeLegal e-signatures (DocuSeal) — documents, templates, client foldersApproval/feedback flows → Aprovee
AssisteeRemote desktop support (self-hosted RustDesk)

🔁 The content pipeline rule: Bloggy writes → Addee designs → Posttee publishes → Rankee measures. Four apps, four stages, zero overlap. And the reviews rule: anything a customer reads publicly = Localey; rate-your-server staff recognition = Rewardee; Replyee owns zero review functionality.

2 · B.O.O. integration board — “first they all need to integrate with BOO and be useful”

Current state of each app's B.O.O. hook and the single next action that makes it genuinely useful to a restaurant. Check items off as they ship (saved in this browser). Ordered: deepest value for restaurants first.

3 · Cleanup recommendations — decide once

Each card = one verified issue + my recommendation. Pick Approve (do it as written), Modify (add a note with your version), Defer, or Reject. Then export.

Verified from code 2026-07-06 · Canonical doc: SaaS/.md/APP_BOUNDARIES.md · Six feature “creep zones” to re-check before building anything new: reviews · QR · approvals · content generation · scheduling · documents.