| Browser Extensions (Manifest V3 & Complex DOM Injection) |
Working Production Implementation |
support-coach-extension (Chrome Web Store item kfmbekgngkgbcejoinohlalmbmkegnbi, v1.0.25 live public, v1.0.26 submitted; TypeScript, Vite + CRXJS, Shadow DOM, 90 extension unit tests). |
Platform-adapter DOM architecture across Zendesk (contentEditable), Intercom (contentEditable), and Zoho SalesIQ (<textarea> with synthetic input/change event dispatch); elementsFromPoint z-order visibility gates and >=25% geometric overlap checks to eliminate modal false positives; edit-box focus guards; passive self-diagnostics (coaching_ui_fault); minimal 5-host manifest permissions. |
Chrome/Chromium browser only (does not run inside native Windows/macOS desktop help-desk apps such as the SalesIQ desktop client); Chrome blocks content scripts and password-manager autofill inside chrome-extension:// popups. |
Teams need an in-page AI copilot or compliance checker overlaid inside Zendesk, Intercom, Zoho, or a web CRM without breaking host-page editors, stealing cursor focus, or requesting invasive <all_urls> permissions. |
| Support Operations Tooling & Real-Time Pre-Send Coaching |
Working Production Implementation |
support-coach-extension packages/rules (84 tests) + packages/ai (45 tests) + apps/backend (287 tests), dogfooded daily by a 13-agent support team since March 2026. |
3-layer cost/latency architecture: Layer 1 local rules engine (0ms, offline-capable, 12 rule families with co-occurrence gating that cut good-reply false positives from 90% to 8% across a 63-reply corpus); Layer 2 paused-typing AI check; Layer 3 pre-send 8-dimension AI check with deterministic sanitizeRewrite preserving every factual instruction and mid-draft closing. Pre-send rewrites accepted 2,108 / 2,338 times (90.2%) Oct 5–25, 2026. |
Intentionally draft-only (does not scrape customer messages, trading full conversation context for strict privacy/security compliance); no external customer CSAT or resolution-time uplift has been measured yet. |
Support agents send blame-heavy, dismissive, or dead-end replies in live chat when rushed, and managers only discover the escalation days later during post-hoc QA. |
| Multi-Tenant SaaS Development & Billing Lifecycle |
Working Production Implementation |
supportcoach-ai (www.supportcoach.io — Next.js App Router, TypeScript, Supabase Auth & PostgreSQL RLS, Paddle v2 billing) + support-coach-extension admin (admin.supportcoach.io). |
End-to-end multi-tenant SaaS with organization-scoped queries, Paddle checkout + HMAC-verified webhook lifecycle (subscription.activated, subscription.updated, subscription.canceled), server-side billed seat quantity enforcement + daily Paddle seat true-up cron, and per-seat monthly AI spend ceilings (aiCostControls.ts). |
38 backend files in supportcoach-ai use the Supabase service-role key and rely on application-level .eq('organization_id', orgId) filters (audit Task 46a verified 198 queries on Nov 11 and flagged 2 anon-key topic pages to switch to server session auth); plan-tier feature gating is not yet hard-enforced. |
Founders need a production-ready Next.js + Supabase + AI SaaS MVP with working subscription billing, seat management, and per-tenant LLM cost caps so a trial user cannot burn unbounded OpenAI spend. |
| Data Analysis, Transcript QA & Topic Reporting |
Production + Staged Branch Expansion |
supportcoach-ai worker (/api/process-jobs, pdfjs-dist, Recharts, pdf-lib) in production; Product Confusion Topics & Coaching Notifications (Tasks 37–45) built and verified locally on main backlog. |
PDF transcript ingestion with SHA-256 duplicate detection, idempotent job claiming, sender misattribution repair, domain-specific QA guardrails (exempting remote screen-share gaps >=5 min and scoring abandoned chats neutrally at 7/10), AI follow-through tracking across subsequent chats with manager override precedence, and AI-proposed / human-approved Product Confusion Topics clustering with Postgres RPC aggregation. |
Tasks 37–45 (Product Confusion Topics, Zoho SalesIQ auto-sync, and Resend/Slack coaching PDF notifications) are built on local main (36 commits ahead of origin) awaiting Vercel Pro deployment and SQL function execution. |
Product and CX leaders have thousands of raw support transcripts but cannot quantify which product modules confuse customers or whether agents actually apply 1:1 coaching feedback. |
| AI Integrations, Multi-Agent Governance & Human-in-the-Loop Ops |
Working Personal Platform (Internal Dogfooding) |
life-os (https://life-os-beta-self.vercel.app — Next.js 16, React 19, Supabase Realtime, db/001..004.sql, 10+ role files in roles/*.md, evals/life-chief.md). |
Role-as-code prompt management, multi-provider connection routing (Anthropic, OpenAI, Google Gemini, xAI Grok) with weekly quota pace tracking, two-tap mobile Approval Cards with pre-committed hidden decision predictions and diff journaling (journal/README.md), security-definer cross-agent task board (/hand/[token]), and Python data-wall enforcement (bridge/sync.py). |
Single-owner personal deployment (Workspace 1 RLS locked to owner email); subscription usage meters require a browser-bound reader task because providers do not expose subscription usage APIs. |
Executives and operations teams want multi-agent automation across Claude, OpenAI, and Gemini without risking unauthorized emails, spend, or data leakage across accounts. |
| Workflow Automation & Auditable Outbound Pipelines |
Working Internal Implementation + Staged API Mode |
support-coach-acquisition (GitHub Issue #1 round-trip verified ACQ-TEST-001) + support-coach-extension outbound engine (outbound.ts, outboundReviewer.ts, outboundInstantly.ts, 25 Instantly unit tests). |
4-track prospect state machine (research -> contactability -> owner approval -> evidenced outcome), AI prospect company-fit reviewer (filtering out >200 employee / non-ICP orgs), deterministic claim checker (marketingCopy.test.ts), Instantly API v2 campaign sync + Titan webmail manual send-later mode, and bounce-rate circuit breakers (>5% auto-pause). |
Commercial cold-email conversion is not yet proven (EXP-002 static sources yielded 0 human replies from 38+ touches; EXP-003 stage-gated Instantly test launches after domain warmup around Nov 30, 2026); Railway Hobby blocks direct outbound SMTP ports. |
B2B teams want automated lead qualification, personalizado first-line research, and outbound sequencing with hard human approval gates and automatic bounce/claim safety checks. |
| APIs, Webhooks & Privacy-First Third-Party Integrations |
Working Production + Staged Connectors |
Paddle v2 webhooks, custom zero-SDK PostHog batch forwarder (analytics.ts), Next.js Edge Middleware first-touch attribution, Zoho SalesIQ REST API v2 client (salesiq.ts), Resend REST API, Cloudflare Turnstile verifier. |
Server-side-only telemetry forwarding (zero third-party scripts in extension or marketing pages to uphold strict /privacy and /security commitments), timing-safe webhook verification, Zoho multi-DC OAuth refresh and HTTP-200 body-level error/throttle handling (error 1023), and hedged OpenAI calls with nested timeouts. |
Public Reply Checker endpoint (POST /api/public/reply-check) is deployed in production with kill switch PUBLIC_CHECK_ENABLED=false pending Turnstile secret configuration on Railway. |
Companies need reliable third-party API and webhook integrations (help desks, billing, analytics, LLMs) that respect strict enterprise privacy policies and never block the primary user path. |
| Knowledge Systems & Evaluated Prompt Engineering |
Working Internal Implementation |
life-os handoff protocol (handoff/README.md), evaluation suites (evals/life-chief.md), support-coach-acquisition LEARNINGS.md, and support-coach-extension experiment register (docs/EXPERIMENTS.md). |
Structured append-only knowledge handoffs treating external content strictly as data (prompt-injection defense), pre-registered experiment hypotheses with decision gates, and golden-corpus regression testing before any prompt or sanitizer change ships. |
karpathy-wiki and cf-support-dashboard KB curation repositories on disk were outside sandbox read permissions and are excluded from this showcase's primary evidence. |
Teams building with LLMs suffer from prompt drift, regressions when fixing isolated bugs, and unverified marketing/product claims because they lack structured evals and state handoffs. |