{"slug":"internal/strategy/gtm","title":"IntegrateWise — GTM Canonical","section":"internal","sectionLabel":"Internal","status":"unclassified","type":"document","path":"internal/strategy/gtm.md","bytes":9827,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"<!-- DOCUMENT CLASS: INTERNAL | SOURCE: 12_INTEGRATEWISE_GTM_CANONICAL.md -->\n<!-- STATUS: Aligned with Founder Canon (31 August 2026) -->\n\n# IntegrateWise — GTM Canonical\n\n**Status:** Canonical GTM Target  \n**Company:** IntegrateWise  \n**Product:** SpineWorkspace  \n**Primary wedge:** Account Success / Customer Success  \n**Initial market:** India SMB SaaS  \n**Foundation:** Business Context Spine (THE semantic foundation)\n\n## The Tier-0 Principle\n\n> **Business Context is the semantic foundation of SpineWorkspace.** GTM messaging must explain how the product establishes, maintains, and serves Business Context. Without Business Context, the product has no meaning.\n\n## 1. GTM thesis\n\nThe market problem is not simply too many applications.\n\nThe deeper problem is:\n\n> **Business Context and work are fragmented across tools, people and AI systems, forcing humans to reconstruct context and coordinate execution manually.**\n\nSpineWorkspace creates a shared Business Context and coordinates work between people and AI without requiring customers to replace the systems they already use.\n\n## 2. Initial ICP\n\nThe supplied GTM memory identifies:\n\n- India SaaS;\n- 20–200 employees;\n- 5–20 CSMs;\n- approximately USD 5k–50k ACV;\n- cross-tool memory / renewal-risk continuity as the wedge;\n- no need to replace existing systems.\n\nThe structured GTM memory records this as the initial ICP and identifies Account Success, Business Operations / RevOps and Business Intelligence as solution areas. fileciteturn22file8L728-L744\n\n## 3. Priority segments\n\n### Tier A — India SaaS\n\nPrimary.\n\nSignals:\n\n- 20–200 employees;\n- SaaS;\n- 5–20 person Customer Success team;\n- multiple operating systems;\n- HubSpot/Freshworks/Zoho/Freshdesk/Jira/Slack or similar;\n- weak cross-tool context continuity;\n- no mature enterprise CS/RevOps platform;\n- founder/CEO/CS leader is accessible.\n\nThe supplied GTM policy explicitly identifies India SaaS as the top priority with these characteristics. fileciteturn22file7L631-L643\n\n### Tier B — Digital Services / IT Services\n\nSignals:\n\n- delivery teams;\n- account managers;\n- project managers;\n- multiple customer-facing systems;\n- knowledge retention challenges;\n- employee turnover.\n\n### Tier C — Operations-Heavy SMB\n\nSignals:\n\n- multiple systems;\n- manual coordination;\n- approval chains;\n- cross-functional handoffs.\n\nThe existing first-20 targeting model allocates 12 to India SaaS, 5 to Digital Services and 3 to Operations-Heavy SMB. fileciteturn22file1L24-L32\n\n## 4. Primary buyer / users\n\n### Economic buyer\n\n- Founder / CEO;\n- COO;\n- Head of Customer Success;\n- Head of Operations;\n- RevOps leader, depending on wedge.\n\n### Primary users\n\n- CSM;\n- CS Manager;\n- Account Manager;\n- Operations Manager;\n- RevOps practitioner.\n\n### Secondary participants\n\n- Finance;\n- Support;\n- Sales;\n- Product;\n- IT.\n\n## 5. Initial wedge\n\n### Account Success\n\nDo not sell:\n\n> \"AI for Customer Success.\"\n\nSell:\n\n> **Connected account context and continuity for customer-facing work.**\n\nThe wedge:\n\n```text\nCRM\n+\nSupport\n+\nProduct Usage\n+\nBilling\n+\nEmail\n+\nMeetings\n+\nSlack\n        ↓\nSpine Fabric\n        ↓\nAccount Context\n        ↓\nCS Workbench\n        ↓\nCSM + Twin\n        ↓\nRenewal / Risk Work\n```\n\n## 6. Wedge problem\n\nA CSM should not have to:\n\n- search five systems;\n- reconstruct customer history;\n- ask colleagues for missing context;\n- manually summarize meetings;\n- remember previous decisions;\n- chase internal approvals;\n- manually update multiple systems after every action.\n\nThe product removes the coordination burden without removing human ownership.\n\n## 7. Wedge outcome\n\nTrack:\n\n- context assembly time;\n- tool switching reduction;\n- renewal-risk response time;\n- follow-up completion;\n- work completion cycle time;\n- governance coverage;\n- reconciliation accuracy;\n- Twin proposal acceptance.\n\nThe existing product metric set includes Context Assembly Time, Tool Switching Reduction, Action Governance Coverage, Reconciliation Accuracy, Twin Proposal Acceptance and Time to First Value as North-Star style operating metrics.\n\n## 8. Customer discovery structure\n\nUse the Continuity Map:\n\n```text\nDiscovery\n ↓\nQualification\n ↓\nProposal\n ↓\nPilot Design\n ↓\nDeployment\n ↓\nSuccess Review\n```\n\nThe supplied GTM policy explicitly defines this sequence and treats the Continuity Map as the canonical GTM workbench where one memory and persistent context span every stage. fileciteturn22file1L54-L62\n\n## 9. Discovery questions\n\n1. Where does account context live today?\n2. How many systems does a CSM use every day?\n3. What information must be reconstructed before a renewal conversation?\n4. Where do decisions from meetings and Slack end up?\n5. Which actions require coordination across teams?\n6. Which actions require approval?\n7. How do you know an action actually completed?\n8. How much time is lost switching systems?\n9. What happens when a CSM leaves?\n10. Which recurring work does not actually require human judgment?\n\n## 10. Demo narrative\n\nDo not start with platform architecture.\n\nStart with a real work item:\n\n> **Payment failure / renewal risk / customer escalation.**\n\nThen demonstrate:\n\n```text\n1. User sees Work\n2. Twin observes\n3. Spine assembles context\n4. Workbench shows current state\n5. Twin proposes options\n6. Human decides\n7. Twin allocates work\n8. Agent/workflow executes\n9. Slack/email communication occurs if needed\n10. Source system changes\n11. Outcome returns\n12. Reconciliation occurs\n13. Context updates\n14. Future work gets better context\n```\n\nThis demonstrates the entire value chain.\n\n## 11. Pilot\n\nThe pilot should prove one complete continuity loop rather than broad platform coverage.\n\nRecommended pattern:\n\n```text\nOne team\n+\nOne business domain\n+\nOne or two connected systems\n+\nOne high-value workflow\n+\nOne Twin\n+\nOne measurable outcome\n```\n\nExample:\n\n> Account renewal-risk continuity for a 5–20 CSM team.\n\n## 12. Customer Zero\n\nCustomer Zero should prove:\n\n- connector activation;\n- context ingestion;\n- projection;\n- Workbench;\n- Twin;\n- governance;\n- execution;\n- reconciliation;\n- memory/knowledge evolution.\n\nThe supplied memory records Customer Zero as an active workstream alongside the Workbench, first connector, Activation Hub and continuity infrastructure. fileciteturn22file8L746-L754\n\n## 13. GTM motion\n\n### Phase 1 — Founder-led\n\n```text\nTarget Account\n ↓\nResearch\n ↓\nContinuity Signal\n ↓\nPersonalized Outreach\n ↓\nDiscovery\n ↓\nContinuity Map\n ↓\nDemo\n ↓\nPilot\n ↓\nOutcome\n```\n\n### Channels\n\nThe existing GTM memory identifies:\n\n- Website;\n- LinkedIn;\n- Medium;\n- MailerLite.\n\nfileciteturn22file8L739-L744\n\n## 14. Content strategy\n\n### Pillar 1 — Business Context\n\nTopics:\n\n- why business context fragments;\n- organizational memory;\n- context assembly;\n- entity relationships;\n- continuity.\n\n### Pillar 2 — Human + AI Work\n\nTopics:\n\n- work allocation;\n- human judgment vs AI work;\n- AI operational boundaries;\n- Twin architecture;\n- human-in-the-loop.\n\n### Pillar 3 — Operational Continuity\n\nTopics:\n\n- cross-tool workflows;\n- communication continuity;\n- reconciliation;\n- handoffs;\n- knowledge persistence.\n\n### Pillar 4 — Governed Intelligence\n\nTopics:\n\n- approvals;\n- authority;\n- AI governance;\n- evidence;\n- auditability;\n- AI agents without direct canonical access.\n\n### Pillar 5 — Domain Outcomes\n\nTopics:\n\n- Account Success;\n- RevOps;\n- Business Operations;\n- Business Intelligence.\n\n## 15. Competitive positioning\n\nDo not attempt to compete as:\n\n```text\nCRM replacement\nWorkflow automation replacement\nChatbot replacement\nGeneric AI assistant\n```\n\nPosition between fragmented operational systems and human/AI work:\n\n```text\nExisting Business Systems\n        ↓\n     Spine Fabric\n        ↓\nBusiness Context\n        ↓\nHuman + AI Work\n        ↓\nGoverned Execution\n        ↓\nExisting Business Systems\n```\n\n## 16. Objection handling\n\n### \"We already have Salesforce/HubSpot.\"\n\nResponse:\n\n> SpineWorkspace is not replacing the CRM. It connects the context around the CRM so people and AI can work across the business systems already in place.\n\n### \"We already use ChatGPT/Claude.\"\n\nResponse:\n\n> Those models provide intelligence. SpineWorkspace provides the governed business context, work continuity, user-specific Twin and execution loop around that intelligence.\n\n### \"We already have automation.\"\n\nResponse:\n\n> Automation executes predefined paths. SpineWorkspace coordinates contextual work, allocates work between humans and AI, governs consequential actions and reconciles the resulting business state.\n\n### \"Will AI replace our CSMs?\"\n\nResponse:\n\n> The product is designed to remove work that does not require the CSM and increase the CSM's leverage. Human responsibility and consequential judgment remain governed.\n\n## 17. GTM success criteria\n\n### Customer-level\n\n- measurable reduction in context assembly;\n- measurable reduction in tool switching;\n- shorter work cycle;\n- increased completion;\n- improved consistency;\n- successful governed execution;\n- reconciliation evidence.\n\n### Company-level\n\n- qualified pipeline;\n- pilot conversion;\n- time to value;\n- activation rate;\n- paid conversion;\n- expansion into additional domains.\n\n## 18. Policy locks\n\nThe supplied GTM material marks these as locked:\n\n- ICP priority;\n- exclusion list;\n- Continuity Score;\n- campaign architecture;\n- Continuity Map requirement;\n- continuity severity classification;\n- GTM motion;\n- governance rules;\n- metrics.\n\nThe existing policy review point is after 10 customers or 90 days. fileciteturn22file1L36-L50\n\n## 19. GTM principle\n\n> **Sell the business problem and outcome first. Demonstrate the connected context and work loop. Explain the platform only after the buyer understands the value.**\n\n"}