{"slug":"business/LAUNCH_PHASE_ADDENDUM","title":"Positioning Framework — Launch Phase Addendum","section":"business","sectionLabel":"Business","status":"unclassified","type":"document","path":"business/LAUNCH_PHASE_ADDENDUM.mdx","bytes":23392,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n> Addresses 6 gaps identified in strategic review.\n> Read alongside POSITIONING_FRAMEWORK.md and PRODUCT_CATALOG_20.md.\n> This addendum overrides any conflicting guidance in the main framework.\n\n---\n\n## Canonical Internal Doctrine Guardrail\n\n- User Workbench = the projection-native customer/product shell.\n- Twin Workbench = full AI ecosystem surface (skills, knowledge, agents, prompts, conversational library).\n- Governance is embedded at every layer — not a separate workbench.\n- The Twin is a native Cloudflare surface (iw-agent-runtime), not a separate shell.\n- When this doc uses public-facing language like \"Workbench\", interpret that internally as the User Workbench unless stated otherwise.\n- Twin runtime surfaces use the canonical Forest + Paper system language.\n- Midnight Executive is investor-deck / fundraising language only.\n\n---\n\n## GAP 1: CTA — \"Start Free\" vs \"Book a Demo\"\n\n### The Problem\n\nThe positioning framework says \"Start Free\" throughout. But self-serve onboarding is not live at launch. Shipping a \"Start Free\" button that leads to a broken or manual flow kills trust on first click.\n\n### The Fix — Phase-Based CTAs\n\n| Phase              | Timeline         | Primary CTA        | Secondary CTA       | Why                                                                          |\n| ------------------ | ---------------- | ------------------ | ------------------- | ---------------------------------------------------------------------------- |\n| M1-3 (Founder-led) | Launch → Month 3 | \"Book a Demo\"      | \"Join Early Access\" | No self-serve. All onboarding is founder-led.                                |\n| M3-6 (Guided)      | Month 3-6        | \"Start Free Trial\" | \"Book a Demo\"       | Self-serve onboarding built. Free tier = 1 connector, 24h sync, 10 entities. |\n| M6+ (Product-led)  | Month 6+         | \"Start Free\"       | \"Talk to Sales\"     | Full PLG. Free tier is truly self-serve. Growth/Command are self-upgrade.    |\n\n### What to change on the website at launch\n\n- Hero CTA: **\"Book a Demo\"** (not \"Start Free\")\n- Secondary CTA: **\"Join Early Access\"** (waitlist form, collects email + company + role)\n- Pricing page: Show all 3 tiers but Growth and Command are **\"Talk to Sales\"** gated\n- Starter tier: **\"Join Early Access\"** (not \"Start Free\")\n- Remove all \"No credit card\" and \"Connect your first tool in 2 minutes\" copy until self-serve is live\n\n### When to switch\n\nSwitch to \"Start Free\" only when ALL of these are true:\n\n1. Self-serve signup flow works end-to-end (email → onboarding → workspace)\n2. At least 1 connector OAuth flow works without manual intervention\n3. Creamy load completes within 2 minutes of connecting a tool\n4. The workspace renders with real data (not empty state)\n\n---\n\n## GAP 2: Connector Count — 70+ vs Actual Production-Ready\n\n### The Problem\n\nThe registry defines 70+ connector specs (65 in the unified registry plus India/Dubai connectors and accelerators). Production-ready (OAuth tested, field mapping verified, sync modes working) may be a subset.\n\n### The Fix\n\n- On the website: State the **tested and verified** count only\n- If all 70+ are production-tested: say \"70+ connectors\"\n- If a subset is tested: say \"25+ connectors\" (or whatever the real number is) and list the rest as \"coming soon\" on the connectors page\n- The connectors page should show: Live (green badge), Coming Soon (gray badge)\n\n### Verification needed before launch\n\nRun this check for each connector:\n\n1. OAuth flow completes without error\n2. Creamy load (30 days) returns data\n3. Field mapping produces valid Spine entities\n4. Delta sync works on second run\n\nAny connector that passes all 4 = \"Live.\" Others = \"Coming Soon.\"\n\n---\n\n## GAP 3: Entity 360 Demo — Interactive vs Static\n\n### The Problem\n\nThe homepage spec calls for an interactive Entity 360 demo. The platform has a live API (GET /api/entity360/:id). But embedding a live API call in a static marketing site adds engineering complexity and failure risk.\n\n### The Fix — Three Options (pick based on timeline)\n\n**Option A: Static JSON (fastest, ship today)**\n\n- Export a JSON snapshot from the Entity 360 API for a demo entity \"Acme Corporation\"\n- Build a React component that renders the 6 layers from static JSON\n- No API calls, no failure risk, looks identical to the real product\n- Update the JSON monthly or when the product changes\n\n**Option B: Live API with demo tenant (best experience, needs 2-3 days)**\n\n- Seed a demo tenant with Acme Corporation data across all 6 layers\n- Build a React component that calls GET /api/entity360/demo-acme\n- Progressive rendering: Truth loads first, Context and Signals animate in\n- Requires the Gateway to be publicly accessible with CORS for the marketing domain\n- Fallback to static JSON if API is unreachable\n\n**Option C: Recorded video/GIF (simplest, least impressive)**\n\n- Record a 30-second screen capture of Entity 360 in the real product\n- Embed as autoplay video or animated GIF\n- No engineering, but less engaging than interactive\n\n### Recommendation\n\nShip with Option A (static JSON) for launch. Upgrade to Option B when the Gateway is stable and publicly accessible. Option C is the fallback if neither A nor B is ready.\n\n---\n\n## GAP 4: TruthLayer / Memory Accumulator Demo Readiness\n\n### The Problem\n\nTruthLayer is the central sales pitch for Command tier. But Memory Accumulator was on the defer list. If the triage → approve → write → Twin reads path does not work, Command tier is vaporware.\n\n### The 4-Step Verification (run this week)\n\n**Step 1: D1 Buffer → Triage Bot**\n\n- Send an AI output to the Flow C endpoint\n- Verify it appears in D1 buffer\n- Verify the triage bot processes it (entity extraction, confidence scoring)\n- Pass/Fail: Does a triage result appear?\n\n**Step 2: Triage Inbox → Human Approval**\n\n- Triage inbox → review queue\n- Verify the triage result from Step 1 appears as a pending item\n- Click Approve\n- Pass/Fail: Does the approval action succeed?\n\n**Step 3: Approved Memory → Entity 360**\n\n- After approval in Step 2, check Entity 360 Memory layer for the entity\n- Call GET /api/entity360/:id and check the Memory layer\n- Pass/Fail: Does the approved memory appear in Entity 360?\n\n**Step 4: Twin Reads Verified Memory**\n\n- Trigger a Twin evaluation for the entity from Step 3\n- Check if the Twin insight references the verified memory as evidence\n- Pass/Fail: Does the Twin use verified memory in its reasoning?\n\n### What to do based on results\n\n| Steps passing                | Action                                                                                                                    |\n| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------- |\n| All 4 pass                   | TruthLayer is demo-ready. Sell all 3 tiers from Day 1.                                                                    |\n| Steps 1-3 pass, Step 4 fails | Demo TruthLayer as standalone. Twin integration is \"coming in 2 weeks.\" Sell Starter + Growth. Command is \"early access.\" |\n| Steps 1-2 pass, Step 3 fails | Fix the write path (approval → consolidated_memories → Entity 360 read). This is a data wiring issue, not architecture.   |\n| Step 1 fails                 | Focus engineering here. The D1 → Triage Bot path is the foundation.                                                       |\n\n### Timeline\n\n- Week 1-2: Ship Storefront (static site)\n- Week 2-4: Build/verify TruthLayer demo loop\n- Week 4+: First sales demo using live TruthLayer flow\n\n---\n\n## GAP 5: Personal Space — Self-Serve vs Waitlist\n\n### The Problem\n\nPersonal Space at Rs999/$49 assumes self-serve at scale. But M1-6 is founder-led B2B sales. Running a consumer self-serve product and a B2B sales motion simultaneously as a solo founder is not feasible.\n\n### The Fix\n\n- M1-6: Personal Space is a **waitlist** on the website. \"Coming soon. Join the waitlist.\"\n- The Personal Space surface page exists (shows LifeOps, WealthPilot, etc.) but the CTA is \"Join Waitlist\" not \"Start Free\"\n- M6+: Open Personal Space self-serve when B2B revenue sustains the business\n- The positioning framework correctly includes Personal Space — it shows breadth and vision. But do not ship it as a live product until M6.\n\n### Website implementation\n\n- /personal page: Full content (5 products, 3 tiers, TruthLayer) but CTA = \"Join the Waitlist\"\n- Pricing page: Personal Space column shows prices but marked \"Coming Soon\"\n- Homepage three doors: Personal Space door exists but leads to waitlist page\n\n---\n\n## GAP 6: PLG vs Founder-Led — Launch Phase Distinction\n\n### The Problem\n\nMultiple sections assume product-led growth is operational (free tier, self-serve, auto-upgrade). But M1-3 is founder-led sales.\n\n### The Fix — Phase Map\n\n| Phase | Motion      | Website CTA        | Pricing                                    | Onboarding          |\n| ----- | ----------- | ------------------ | ------------------------------------------ | ------------------- |\n| M1-3  | Founder-led | \"Book a Demo\"      | Contact-gated                              | Manual, founder-led |\n| M3-6  | Guided PLG  | \"Start Free Trial\" | Self-serve Starter, contact Growth/Command | Semi-automated      |\n| M6+   | Full PLG    | \"Start Free\"       | Fully self-serve all tiers                 | Fully automated     |\n\n### What this means for the website at launch\n\n- No \"Start Free\" buttons\n- No \"Connect your first tool in 2 minutes\" copy\n- No \"No credit card\" messaging\n- Pricing page shows tiers but is contact-gated for Growth and Command\n- Starter is \"Early Access\" (invite-only)\n- All CTAs route to: demo booking (Calendly) or waitlist form (email capture)\n\n---\n\n## STRUCTURAL IMPROVEMENTS\n\n### Split Product Definitions\n\nThe positioning framework Part 3 (20 product definitions, 4,000+ words) is too long for a positioning doc. It belongs in a separate file.\n\n**POSITIONING_FRAMEWORK.md** should contain: Parts 1, 2, 4, 5, 6, 7, 8, 9, 10\n(positioning, TruthLayer, competitive, pricing, website, sales, summary, never/always)\n\n**PRODUCT_CATALOG_20.md** already contains the full product definitions.\nThis is the reference for engineering, docs, and detailed sales prep.\n\n### Add Sync Entitlements to Pricing\n\nThe pricing section should include sync capabilities as a tangible justification for tier differences:\n\n| Capability        | Starter | Growth   | Command         |\n| ----------------- | ------- | -------- | --------------- |\n| Sync interval     | 4h      | 1h       | 15min           |\n| Records per sync  | 5,000   | 25,000   | 100,000         |\n| Records per month | 50,000  | 500,000  | Unlimited       |\n| Historical data   | 90 days | 365 days | Unlimited       |\n| Max connectors    | 3       | 5-10     | 10+ / Unlimited |\n| Delta sync        | Yes     | Yes      | Yes             |\n| Full refresh      | Yes     | Yes      | Yes             |\n| Two-way sync      | No      | Yes      | Yes             |\n| Webhooks          | No      | Yes      | Yes             |\n\n### Add Edge Deployment to Competitive Section\n\nAdd this row to the competitive comparison table:\n\n| Edge deployment | 300+ Cloudflare PoPs, 0ms cold starts | Cloud only | Cloud only | Cloud only |\n\nThis matters for enterprise buyers in regulated industries (healthcare, financial services) where data processing latency and data residency are concerns.\n\n### Add Progressive Hydration as Sales Feature\n\nThe B0→B7 bucket system is a \"time to value\" story:\n\n- B0→B2 (minutes): Connect a tool, see 30 days of data normalized\n- B2→B5 (hours): Twin triggers start firing, insights appear\n- B5→B7 (days): Full cognitive mode with verified memory\n\nSales line: \"See value in minutes, not months. Connect one tool and watch your data normalize in real time.\"\n\n### Add Productized Services Reference\n\nIn addition to subscription tiers, IntegrateWise offers 5 productized services for implementation and activation:\n\n1. Spine Foundation Sprint\n2. Connector Activation Pack\n3. Twin Calibration Workshop\n4. TruthLayer Configuration\n5. AI Memory Activation\n\nThese are sold through sales conversations, not self-serve. Pricing and details in a separate SERVICES.md. Reference them in the pricing section as: \"Need help getting started? Our implementation services accelerate time-to-value.\"\n\n---\n\n## EXECUTION SEQUENCE (Next 72 Hours)\n\n### Today\n\n- Run the 4-step TruthLayer verification\n- Audit connector count (how many pass the 4-point production test)\n- Decide: Entity 360 demo = Option A (static JSON) or Option B (live API)\n\n### Tomorrow\n\n- Build Storefront using POSITIONING_FRAMEWORK.md + WEBSITE_FIGMA_BUILD_SPEC.md\n- Apply all CTA fixes from Gap 1 (Book a Demo, not Start Free)\n- Apply connector count from Gap 2 audit\n- Apply Entity 360 demo decision from Gap 3\n\n### Day 3\n\n- Ship the site to Cloudflare Pages\n- Start Phase 2: LinkedIn assets, sales deck, demo script\n- Book first 3 pilot conversations within 7 days of site going live\n\n---\n\n_This addendum is the bridge between strategy and execution. The positioning framework is the what. This addendum is the when and the how. Both are required to ship correctly._\n\n---\n\n## DAY 1 WEBSITE SHIP CHECKLIST\n\nUse this as the QA punch list before pushing to Cloudflare Pages. Every item must be verified.\n\n### Hero Section\n\n- [ ] Primary CTA: \"Book a Demo\" (NOT \"Start Free\")\n- [ ] Secondary CTA: \"Join Early Access\" (email capture form)\n- [ ] No \"No credit card\" copy anywhere on the page\n- [ ] No \"Connect your first tool in 2 minutes\" copy anywhere\n- [ ] Headline: \"Every AI remembers. Only IntegrateWise remembers the truth.\"\n- [ ] Sub-headline references $67B hallucination problem\n\n### Entity 360 Demo Section\n\n- [ ] Static JSON component (Option A) rendering Acme Corporation with 6 layers\n- [ ] Truth, Context, Signals, Memory, Goals, Relationships all visible\n- [ ] Twin Insight card with evidence chain and confidence score\n- [ ] No live API calls — all data from static JSON file\n\n### Three Doors Section\n\n- [ ] Account Success door → links to /account-success (full page)\n- [ ] Business Ops door → links to /business-ops (full page)\n- [ ] Personal Space door → links to /personal (waitlist page, NOT live product)\n\n### Surface Pages\n\n- [ ] /account-success: 3 tier sections (No Twin → Basic Twin → Full Twin + TruthLayer), CTA = \"Book a Demo\"\n- [ ] /business-ops: 3 tier sections, CTA = \"Book a Demo\"\n- [ ] /personal: Full content (5 products, 3 tiers) but CTA = \"Join the Waitlist\"\n\n### Pricing Page\n\n- [ ] 3 tiers shown: Starter / Growth / Command\n- [ ] Geo-pricing toggle: India (INR) / UAE (USD) / Enterprise (USD)\n- [ ] Starter tier: \"Join Early Access\" button (not \"Start Free\")\n- [ ] Growth tier: \"Talk to Sales\" button\n- [ ] Command tier: \"Talk to Sales\" button\n- [ ] Sync entitlements visible (sync interval, connectors, records, history)\n- [ ] TruthLayer access row: Read-only / Limited write / Full TruthLayer\n- [ ] FAQ section with 8+ questions\n\n### Connector Count\n\n- [ ] Number on homepage matches actual production-tested count from 4-point audit\n- [ ] Connectors page (if built): Live connectors = green badge, Coming Soon = gray badge\n\n### TruthLayer Section\n\n- [ ] Visual flow diagram: AI proposes → Triage Bot → Human Approves → Spine Truth\n- [ ] No live demo of TruthLayer (visual/diagram only until 4-step verification passes)\n- [ ] Competitive comparison table showing \"Auto\" vs \"Triage → Approval → Truth\"\n\n### Footer\n\n- [ ] 4-column layout: Brand, Platform, Company, Resources\n- [ ] Social links: Twitter/X, LinkedIn, GitHub\n- [ ] Legal links: Privacy, Terms, Cookies\n- [ ] Copyright: 2026 IntegrateWise\n\n### Technical\n\n- [ ] All pages render on mobile (< 640px)\n- [ ] Open Graph meta tags on every page\n- [ ] Page title and description set for SEO\n- [ ] No console errors in browser dev tools\n- [ ] Loads under 3 seconds on 4G connection\n\n### What Must NOT Be On The Site At Launch\n\n- [ ] No \"Start Free\" buttons\n- [ ] No \"No credit card\" messaging\n- [ ] No \"Connect your first tool in 2 minutes\"\n- [ ] No live product signup flow\n- [ ] No Personal Space as a live product (waitlist only)\n- [ ] No interactive Entity 360 with live API calls (static JSON only)\n\n---\n\n## FIRST 3 PILOT TARGET PROFILES\n\nBook these within 7 days of site going live. These are the highest-probability first conversations based on your network, expertise, and product readiness.\n\n### Pilot 1: Mid-Market SaaS CS Team\n\n| Attribute           | Target                                                                                     |\n| ------------------- | ------------------------------------------------------------------------------------------ |\n| Company             | B2B SaaS, 50-200 employees, $5M-$30M ARR                                                   |\n| Buyer               | VP Customer Success or Head of CS Ops                                                      |\n| Team size           | 3-10 CSMs managing 30-80 accounts each                                                     |\n| Pain                | CSMs check 5-8 tools daily, no unified account view, reactive churn detection              |\n| Stack               | Salesforce or HubSpot + Zendesk or Intercom + Stripe + Slack                               |\n| Entry product       | SuccessPilot (Basic Twin) — health scoring, risk flags, next-best-action                   |\n| Upgrade path        | SuccessPilot → ChurnShield → SuccessCommand                                                |\n| Why first           | They feel the pain daily. Fastest path to champion-led adoption. You speak their language. |\n| Demo focus          | Connect their CRM, show Entity 360 for one of their accounts, show a Twin trigger firing   |\n| Qualifying question | \"How much time does your team spend gathering data before a QBR?\"                          |\n\n### Pilot 2: Founder / Operator You Know Personally\n\n| Attribute           | Target                                                                                                                                  |\n| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |\n| Company             | 10-50 person company, any industry                                                                                                      |\n| Buyer               | Founder, CEO, or COO (direct purchase, no procurement)                                                                                  |\n| Pain                | Checks 8-12 tabs every morning, no single view of the business                                                                          |\n| Stack               | Stripe + HubSpot/Pipedrive + Slack + Google Sheets + 3-5 other tools                                                                    |\n| Entry product       | OpsCore (Full Twin) — unified business Entity 360, weekly briefs                                                                        |\n| Upgrade path        | Already at top tier. Expand to team seats.                                                                                              |\n| Why second          | You are the proof point. Show them YOUR dashboard running YOUR business on IntegrateWise. Founder-to-founder credibility is unbeatable. |\n| Demo focus          | Show your own OpsCore dashboard. \"This is how I run IntegrateWise. Same platform, your business.\"                                       |\n| Qualifying question | \"How many tabs do you have open right now?\"                                                                                             |\n\n### Pilot 3: MuleSoft / Salesforce Network Contact\n\n| Attribute           | Target                                                                                                                                                                                 |\n| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Company             | MuleSoft partner or Salesforce ecosystem company                                                                                                                                       |\n| Buyer               | Solution Architect, Technical CSM, or Partner Manager                                                                                                                                  |\n| Pain                | Managing complex integration accounts across Salesforce + Anypoint + Zendesk + multiple client systems                                                                                 |\n| Stack               | Salesforce + MuleSoft Anypoint + Zendesk + Amplitude + Slack                                                                                                                           |\n| Entry product       | ArchitectIQ (No Twin) → SuccessPilot (Basic Twin)                                                                                                                                      |\n| Upgrade path        | ArchitectIQ → SuccessPilot → ChurnShield                                                                                                                                               |\n| Why third           | Your credibility is highest here. You built the Spine to save an $8M red account. This is your origin story. MuleSoft accounts are complex enough to showcase Entity 360's full power. |\n| Demo focus          | Show ArchitectIQ integration landscape mapping, then Entity 360 with all 6 layers for a complex account                                                                                |\n| Qualifying question | \"How do you track the technical health of your customer's integration landscape?\"                                                                                                      |\n\n### Outreach Sequence (Same for All 3)\n\n**Day 1 (LinkedIn DM or email):**\n\"[Name], I built something that solves a problem I think you deal with daily. [One sentence about their specific pain]. Would a 15-minute walkthrough be worth your time this week?\"\n\n**Day 3 (Follow-up if no response):**\n\"Quick follow-up — I can show you [specific thing relevant to their role] in under 15 minutes. [Calendar link]\"\n\n**Day 7 (Final follow-up):**\n\"Last note — we're opening early access to [X] people this month. If the timing isn't right now, happy to keep you in the loop. [Waitlist link]\"\n\n### Success Criteria for Pilots\n\nA pilot is successful if:\n\n1. They connect at least 1 tool during the demo or within 48 hours\n2. They see their own data in Entity 360 (not demo data)\n3. They say \"this would save me [X] hours per week\" or equivalent\n4. They agree to a 30-day trial or paid Starter subscription\n5. They provide a testimonial quote or agree to be a reference\n\nIf 2 out of 3 pilots meet criteria 1-3, the product-market fit signal is strong enough to proceed to Phase 2 outreach at scale.\n\n---\n\n_This addendum + the positioning framework + the product catalog + the platform features doc = the complete GTM system. Freeze these documents. Build to them. Ship._\n"}