Purpose: One app per job. This is the canonical "does / does NOT do" list for the 14 live SaaS apps (Servvee CUT 2026-07-11 — see below), verified against actual code (routes, APIs, SQL schemas) on 2026-07-06 — not marketing copy. When a sales page, tier card, or doc describes an app differently, fix the page to match this file.
Trigger: a BOO tier card described Replyee as "AI reviews & live chat" — Replyee does NOT do reviews. Reviews belong to Localey.
2026-07-11 decisions (Eric): (1) Servvee is CUT — remove/retire it; fold its promo/menu logic into Boom Online Ordering. (2) Replyee copy fixed everywhere: "AI chatbot & live chat," never "reviews." (3) Dashee = standalone client-dashboard software for any vertical; it is NOT a Boom Online Ordering feature and must not be marketed as part of BOO.
The one-line ownership map
| App | Owns (the job) | Does NOT do (owned elsewhere) |
|---|---|---|
| Addee | Ad & social creative generation (AI copy + visuals), Google Ads push | Scheduling/publishing calendar (Posttee) · long-form blogs (Bloggy) |
| Bloggy | Long-form SEO content — blogs, URL/YouTube-to-blog, autoblog, repurpose, WP publish | Social publishing (Posttee) · ad creative (Addee) · keyword rank tracking (Rankee) |
| Rankee | Local SEO measurement — rank grids, SEO audits, backlinks, competitors, recommendations · website translation add-on (multilingual SEO: translated /es/-style subpaths, hreflang — ruling #10) | Citations/listings/reviews (Localey) · writing the content (Bloggy) — see ⚠️ AI Studio below |
| Posttee | Social scheduling & publishing (Meta, GBP, LinkedIn) | Creating the creative (Addee) · writing posts' source content (Bloggy) |
| Localey | Public reputation — citations, listings, review generation/monitoring, review-request campaigns | Chat (Replyee) · rank tracking (Rankee) · internal staff ratings (Rewardee) |
| Dashee | Client portal + reporting hub per vertical (analytics, invoices, appointments, docs, messaging — e.g. bail-bonds portal). Standalone client-dashboard software — NOT a BOO feature | Tracked/branded QR (QRcodee) · e-signing (Signnee) · ADA scans (Compliee) · anything BOO-owned — see ⚠️ below |
| Aprovee | Approval workflows — visual feedback pins, sign-off audit trail on any deliverable | Legal e-signatures (Signnee) |
CUT 2026-07-11. Was named "service ticketing" but code was only a BOO promo/menu layer (promos table). Retired — logic folded into Boom Online Ordering | — | |
| Displayee | Screens — digital menu boards, signage, KDS on Fire TV | Ordering itself (B.O.O.) |
| Replyee | AI chatbot (RAG) + live chat — bots, agent inbox, human takeover, visitors, leads, canned replies | Reviews — NOT Replyee, never was. Reviews = Localey |
| QRcodee | Tracked, branded QR codes + scan analytics, folders, templates, bulk | Being a plain QR utility inside other apps (allowed — see Dashee note) |
| Rewardee | Customer loyalty (points, stamps, gift cards) + staff recognition (rate-your-server → staff reward pool) | Public/Google reviews (Localey) — staff ratings are internal-only |
| Compliee | Website accessibility scanning/monitoring/fix-guidance (never "makes compliant" — FTC) | Bail-bond "compliance" in Dashee (naming collision only) |
| Signnee | Legal e-signatures (DocuSeal) — documents, templates, client folders | Approval/feedback workflows (Aprovee) · doc storage in portals (Dashee) |
| Assistee | Remote desktop support (self-hosted RustDesk) — devices, technicians, sessions | Ticketing (dead with Servvee) |
Content pipeline rule (3 apps, 3 stages, no overlap): Bloggy writes → Addee designs → Posttee publishes. Rankee measures and briefs the other three.
Reviews rule (the question that triggered this doc): Localey owns anything a customer might read publicly (Google/Yelp/directories, review requests). Rewardee's /rate flow is staff recognition — a guest rates their server, the server earns reward-pool points; it never publishes anywhere. Replyee owns zero review functionality.
⚠️ Verified overlaps & the ruling on each
Found by inspecting routes/APIs in every repo (2026-07-06):
- Replyee mislabeled as "AI reviews & live chat" on a BOO tier card (Growth+ add-on, $75).
Ruling: copy error. Change to "AI chatbot & live chat." No code overlap exists. - Rewardee
/rate+003_staff_reviews.sqlvs Localey reviews.
Verified: Rewardee's flow = scan table QR → pick server → star rating → server earns points (tips display-only). Internal recognition, not public reviews.
Ruling: keep both, but market Rewardee's as "Staff Recognition" — never the word "reviews" on pricing pages. Any "ask the customer for a Google review" feature belongs in Localey only. - Rankee AI Content Studio vs Bloggy/Addee.
Verified:/ai-studiogenerates content from completed SEO audits. Third content generator = the biggest creep risk.
Ruling: Rankee's studio should output SEO briefs/recommendations (what to write, target keywords) and hand off to Bloggy for the writing. Don't grow it into a blog writer. - Dashee
/api/qrvs QRcodee.
Verified: Dashee generates plain untracked QR data-URLs via theqrcodelib.
Ruling: allowed as an embedded utility. Never add branding, analytics, or dynamic destinations to it — the moment tracking matters, it calls QRcodee. - Addee
/approve/[token]+ Bloggy/approve/[token]vs Aprovee.
Verified: both apps have one-click client-approval pages for generated content.
Ruling: in-app single-asset approvals may stay (low friction). Multi-step review, visual pin feedback, and anything cross-app = Aprovee. Optional later consolidation: back these token pages with Aprovee's API. - Rankee vs Localey (both "local SEO").
Ruling: Rankee = measure (where do you rank, what's broken, who's beating you). Localey = manage presence (get listed, get reviews). State this split on both sales pages. - Bloggy
/calendarvs Posttee.
Ruling: Bloggy's calendar schedules blog publishing only. Social distribution of repurposed content hands off to Posttee. - Dashee scope — code shows a full vertical client-portal (court dates, check-ins, invoices, jobs, documents, messages), well beyond "analytics dashboard."
Ruling: embrace it — Dashee = portal/reporting hub. But docs stored there get signed in Signnee, and its/dashboard/compliance(bail-bond check-ins) must never be marketed with the word Compliee uses (ADA/accessibility). - Servvee — code no longer matches its "service ticketing" description (it manages promos/menus).
Ruling (2026-07-11): CUT. Retire the app; fold the promo/menu logic into Boom Online Ordering. Remove from all suite showcase / pricing / portal pages. Archive theServvee/repo + ClickUp folder. - Website translation (ruling 2026-07-14, Eric approved).
Rankee owns website translation as a multilingual-SEO add-on: translated subpath pages (/es/*,/pt/*),hreflangtags, indexed translated content. Rationale: the buyer's motive is search reach — Rankee's job. Build sketch:@boom/translateNext.js middleware, translate-once via Claude API, cache strings in shared Supabase, $19–29/mo first language, ~$10/language after.
Fence (so the creep zones stay closed): Bloggy = multilingual authoring of its own content only (may hand off to Rankee's engine); Replyee = answering chat in the visitor's language, never translating the site; Compliee/Localey = no translation features at all.
Clean, no overlap found: Displayee, Signnee, Assistee, Compliee, QRcodee (as products), Replyee (in code), Posttee, Approvee.
Verified from code by route/API/SQL inspection 2026-07-06. Re-verify when adding features that involve: reviews, QR, approvals, content generation, scheduling, or documents — those are the six creep zones.