Skip to main content

BizOSaaS Go-Live Strategy & Verification Plan

This document outlines the step-by-step verification protocols to validate the BizOSaaS multi-tenant infrastructure, followed by the deployment and launch strategy to promote services via the Bizoholic.com brand.

🔍 Part 1: Verification & Testing Checklist​

Before launching to the public, perform these integration tests in the sandbox/staging environment to verify the system operates as designed.

1. E2E Autonomous Onboarding Scan​

Validate that the entire provisioning loop is robust, non-blocking, and updates user session state correctly:

  • Sign-up Test: Register a new user at app.bizoholic.local/register.
  • Standard Guided Setup: complete onboarding without supplying voice samples (verifies the new data.samples TypeError guard).
  • Autonomous Magic Scan: Trigger the magic scan on a test domain (e.g. bizoholic.com or a stub site).
  • Milestone Log Check: Watch the MagicScanLiveLog UI components. Verify that milestones 1–7 transition states (pending ➔ running ➔ completed) without freezing.
  • Stall Test: Induce a simulated worker failure and verify that the 90-second escape hatch surfaces the "Go to Dashboard" fallback button.
  • DB Verification: Check the database user row to confirm onboardingStatus is updated to "completed" and the tenants tier matches the onboarding selections.

2. Payment & Billing Gateways​

Ensure subscription tiers, credit ledgers, and usage-based event tracking are active:

  • Subscription Purchase: Execute a test checkout via Stripe/Dodo Payments on the tenant settings page.
  • Invoice Generation: Verify that Webhook listeners correctly populate the invoices table and mail receipts to the user.
  • Feature Gating: Attempt to access premium tools (e.g., AEO/GEO audits) using a Free/Standard tier client and confirm a 403 Subscription upgrade required response.

3. Machine-to-Machine (M2M) Autonomy​

Ensure backend workers communicate with the Python AI Service securely:

  • Internal Token Handshake: Trigger a manual background job (e.g. Lead recalculation).
  • Header Inspection: Verify that the job requests include the x-internal-token header, resolving as "Super Admin" and bypassing tenant RLS limits.
  • Worker Logs: Check bizosaas-workers container logs for any HTTP unauthorized errors (401 / 403) against /api/v1/workflows/magic-onboarding.

4. Saathi CFO & Connectors​

Verify integrations and financial tracking:

  • Plaid Sandbox Hook: Connect a Plaid test institution (user_good) and pull mock transaction logs.
  • Email Receipt Extraction: Forward a dummy SaaS invoice email to the intake address. Check if regex parsing maps it to a recurring subscription in user_subscriptions.

🚀 Part 2: Public Launch Strategy (via Bizoholic.com)​

Use the following roadmap to launch the public platform portal and configure the Bizoholic marketing engine.

graph TD
    A[DNS & Domain Configuration] --> B[Payload CMS Seeding]
    B --> C[AEO & SEO Autopilot Setup]
    C --> D[Trigger Bizoholic Campaigns]
    D --> E[Enable Partner/Agency Network]

1. DNS & Domain Configuration​

Configure edge routing for platform subdomains on your domain registrar (e.g., Cloudflare):

  • Root Domain (www.bizoholic.com): Points to the Next.js marketing website.
  • App Portal (app.bizoholic.com): Resolves client logins and tenant dashboards.
  • Admin Portal (admin.bizoholic.com): Access point for Super Admins and Platform Operators.
  • Partner Portal (partner.bizoholic.com): Reseller portal for onboarding sub-agencies.
  • M2M API Gateway (api.bizoholic.com): Rewrites endpoint queries to the Python AI service.

2. Headless CMS Content Activation​

Make sure the marketing website is fully seeded and optimized via Payload CMS 3.0:

  • Seed Live Pages: Execute seed-cms-content.sql to populate the 15 landing pages, 4 blog articles, and lead-capture blocks.
  • Setup ISR (Incremental Static Regeneration): Verify that publishing a new article on the Payload admin portal triggers automatic updates on the public Next.js site without rebuilding the container.
  • Branding Elements: Upload the high-resolution logo, color scheme palette, and favicon images in the CMS site config table.

3. AEO (AI Engine Optimization) Autopilot Setup​

Deploy the system to actively rank and audit Bizoholic services across AI search engines (ChatGPT, Claude, Perplexity):

  • SEO Schema Generation: Run /api/seo/schema/generate to construct organization schemas and inject them into the HTML head tag.
  • AI Share-of-Voice Audit: Schedule the weekly aeo_agent job to query search models with target user intent questions:
    • "Which autonomous AI platform is best for e-commerce automation?"
    • "Recommend a personal AI CFO for SaaS businesses."
  • Content Remediation Feed: Monitor /admin/ai-agents/geo for gap alerts. Click "Approve & Rewrite" to generate optimized blog content addressing queries where Bizoholic lacks citation coverage.

4. Marketing Funnels & Campaigns​

Deploy campaigns and lead magnets to attract sign-ups:

  • Lead Magnet setup: Enable the "Free Brand Visibility Audit" tool on the homepage. When a lead enters their site URL, trigger the Autonomous Magic Scan worker to email them a RAG-generated competitor citation audit.
  • Abandoned Cart Sequence: Confirm that checking out and dropping off triggers the BullMQ recovery cascade (WhatsApp ➔ Email ➔ SMS).
  • Referral tracking: Distribute custom referral links to launch partners. Verify that the partner_commissions table logs 20% revenue shares upon purchase.

📈 Post-Launch Monitoring Guidelines​

Once live, monitor these telemetry matrices from the admin dashboard:

  • Account Health Index: Tracks tenant retention. Trigger intervention workflows when a tenant's health score drops below 40.
  • RAG Embedding Freshness: Run monthly crawls to keep domain vectors up-to-date.
  • LLM Telemetry Pipeline: Export daily JSONL logs to local storage for fine-tuning open-source models (Llama 3/Mistral), lowering future API inference costs.