{"slug":"architecture/sellable-features","title":"Sellable Features","section":"architecture","sectionLabel":"Architecture","status":"unclassified","type":"document","path":"architecture/sellable-features.mdx","bytes":12307,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"The 14 Sellable Features (Updated)\nThe final architecture adds four new sellable features beyond the original 12: the 8-Stage Pipeline (trust infrastructure), the Depth Matrix (personalization moat), the Three Data Flows (completeness story), and the Re-ingestion Loop (compounding intelligence). Together, 14 features now map across four commercial tiers.\n\nTier 1 — Hook Features (Win the First Meeting in 20 Minutes)\nFeature 1: Account 360 — The Living Account Brief\n\nFeature statement: A real-time, AI-assembled brief for every account — pulling structured data (CRM, product usage, support), unstructured context (emails, Slack, documents), and AI session history — all normalized through the 8-stage pipeline and rendered from the Spine\n\nPain: CSMs spend 45–90 minutes manually assembling account context before every QBR from 5–8 disconnected tools\n\nBusiness benefit: Every account brief is available in under 3 seconds, always current, sourced and linked to the original evidence\n\nROI/outcome: Recover 8–10 hours per CSM per week; reduce QBR prep from 3 hours to 15 minutes\n\nOne-line pitch: \"Your Account 360 isn't a dashboard. It's the Spine's assembled truth about that account — from every system, in real time.\"\n\nFeature 2: Proactive Signal Engine — AI That Surfaces Risk Before It Becomes Churn\n\nFeature statement: The Depth Matrix continuously evaluates incoming Spine data against tenant-defined signal rules, surfacing anomalies as structured alerts with full evidence chains — before anyone asks\n\nPain: Teams discover churn risk at the QBR — 30–60 days after the intervention window has closed\n\nBusiness benefit: Risk surfaces 6–8 weeks earlier, with the evidence chain assembled, not assembled manually\n\nROI/outcome: One protected $1M account pays for the platform for 3+ years; average CS team identifies 2–3 at-risk accounts per quarter that were previously invisible\n\nOne-line pitch: \"The Spine watched every signal. The Depth Matrix knew it was risk. The alert arrived 8 weeks before your QBR.\"\n\nFeature 3: HITL Approval Card — Governance Built Into the Architecture\n\nFeature statement: Every AI-proposed action surfaces in the Workspace as a structured approval card containing the proposed action, evidence chain, reasoning narrative, and source attribution — with approve/edit/reject controls and a mandatory audit log\n\nPain: \"We cannot let AI act on our accounts without oversight\" — the #1 enterprise AI adoption blocker\n\nBusiness benefit: Full AI leverage with zero rogue execution — the architecture enforces human review, not a setting or a workflow rule\n\nROI/outcome: Governance compliance built in; audit log satisfies legal and security review; teams adopt AI faster because trust is structural, not assumed\n\nOne-line pitch: \"AI cannot execute anything in IntegrateWise without your approval. Not as a policy. As the architecture.\"\n\nTier 2 — Value Features (Win the Contract)\nFeature 4: The 8-Stage Normalization Pipeline — Trust Infrastructure\n\nFeature statement: All data entering IntegrateWise — from connectors, uploads, webhooks, or AI sessions — passes through a mandatory 8-stage pipeline: Ingest → Parse → Extract → Normalize → Deduplicate → Link → Score → Write. Nothing reaches the Spine that hasn't been normalized.\n\nPain: \"Our data is messy and inconsistent across tools — we don't trust any single view because every tool shows something different\"\n\nBusiness benefit: The Spine is always clean, consistent, and trustworthy — because the pipeline enforces it, not a team of data engineers\n\nROI/outcome: Eliminate manual data reconciliation; give AI a reliable foundation to reason from; make every downstream report and signal trustworthy by design\n\nOne-line pitch: \"Every piece of data passes through 8 normalization stages before it becomes truth. That's why the Spine can be trusted.\"\n\nFeature 5: The Depth Matrix — Your Definition of Risk\n\nFeature statement: A tenant-configurable signal weighting schema that defines what the Spine treats as risk, opportunity, or escalation — tuned to each organization's specific churn playbook, expansion triggers, and escalation logic\n\nPain: Generic CS platforms surface the same signals for every customer — they don't know your business\n\nBusiness benefit: The Spine learns your definition of risk, not a vendor's default. Signal rules reflect your operational reality.\n\nROI/outcome: Dramatically reduces false-positive alerts; surfaces the signals that matter for your accounts specifically; creates switching cost — a configured Depth Matrix is irreplaceable\n\nOne-line pitch: \"The Depth Matrix is your operational logic, wired into the Spine. Nobody else has your definition of risk.\"\n\nFeature 6: Three Data Flows — Completeness of Context\n\nFeature statement: IntegrateWise handles three distinct data flows through one governed architecture: Flow A (structured operational data — CRM, finance, support), Flow B (unstructured context — documents, emails, transcripts), and Flow C (AI/MCP sessions — governed memory). All three feed the same Spine.\n\nPain: Most platforms handle structured data or documents or AI — not all three in one governed system\n\nBusiness benefit: Entity 360 is genuinely complete — not just CRM fields, but also the email thread, the support escalation, the document the customer shared, and the prior AI reasoning session\n\nROI/outcome: AI reasoning quality is higher because it has all three data types; context gaps that cause bad recommendations are eliminated\n\nOne-line pitch: \"Structured data, documents, and AI sessions all flow through the same governed path. That's why Entity 360 is actually complete.\"\n\nFeature 7: Ask the Spine — Contextual AI Q&A\n\nFeature statement: Natural language interface over the full Spine — answering business questions from normalized, entity-linked, cross-system truth rather than a search index\n\nPain: Finding answers requires searching Salesforce, then Slack, then Gmail, then a spreadsheet — 30–40 minutes of manual assembly\n\nBusiness benefit: Answers arrive in seconds, sourced to the exact Spine entities and evidence that produced them — not inferred from documents\n\nROI/outcome: 40-minute manual data hunts replaced by 30-second Spine queries; answers are auditable back to source\n\nOne-line pitch: \"Ask your business anything. The Spine answers from normalized truth — not a search index, not a document pile.\"\n\nFeature 8: 50-Connector Integration Hub\n\nFeature statement: 50 pre-built, maintenance-free connectors feeding all data through the 8-stage pipeline into the Spine — CRM, finance, support, messaging, documents, product telemetry, and custom APIs. Plus 30 webhooks for real-time event ingestion.\n\nPain: Integration maintenance consumes 15–20% of engineering bandwidth at mid-market companies; connectors break and create silent data gaps\n\nBusiness benefit: All connectors write through the canonical pipeline — data quality is enforced, not manual\n\nROI/outcome: Eliminate data engineering overhead; first Spine write within 14 days of onboarding\n\nOne-line pitch: \"50 connectors. 30 webhooks. One pipeline. One truth. Zero maintenance.\"\n\nFeature 9: 12 Adaptive Department Views\n\nFeature statement: 12 purpose-built Workspace views — CS, Sales, RevOps, Finance, Product, Marketing, HR, Executive, Support, Legal, Partnerships, Knowledge — each rendering from the same Spine projections, adapted to each role's operating reality\n\nPain: Every team has a different tool, a different view, a different version of the truth — cross-functional alignment requires weekly sync meetings\n\nBusiness benefit: Every team sees what they need from the same Spine — consistency without uniformity\n\nOne-line pitch: \"One Spine. Every team's view of the truth.\"\n\nTier 3 — Retention and Expansion Features\nFeature 10: QBR Intelligence Pack\n\nFeature statement: Auto-generated client review decks assembled from Spine data — product usage trends, support history, open actions, renewal risk score, intervention recommendations — surfaced through the Workspace for CSM review and approval before use\n\nPain: QBR prep consumes 3–4 hours per account per quarter; decks are inconsistent and miss context the CSM didn't know to include\n\nROI/outcome: Prep time from 3 hours to 20 minutes per account; decks include every relevant signal because the Spine assembled them, not a human\n\nOne-line pitch: \"Your QBR deck, assembled by the Spine. You review, approve, and present.\"\n\nFeature 11: Re-ingestion Loop — Compounding Intelligence\n\nFeature statement: Every approved action outcome returns through the canonical 8-stage pipeline → Spine write → Entity 360 update → cognitive loop refinement. The system stays current and improves with every decision.\n\nPain: Most AI tools give you a recommendation today and forget it tomorrow — there's no learning, no closure, no improvement\n\nBusiness benefit: The Spine stays current post-action; the cognitive loop refines based on approved/rejected decisions; the platform gets smarter every week\n\nROI/outcome: Intelligence quality improves measurably over 90 days; platform value increases over time rather than plateauing\n\nOne-line pitch: \"Every decision you approve feeds back into the Spine. The system learns from you.\"\n\nFeature 12: Workflow Builder — Governed Automation\n\nFeature statement: Visual builder for multi-step governed workflows that chain Spine signals, L2 cognitive reasoning, HITL approval gates, and re-ingestion — configurable per tenant\n\nPain: \"We automate blindly with Zapier or we don't automate at all — there's nothing in between\"\n\nOne-line pitch: \"Automation that detects, reasons, asks for approval, acts, and re-ingests. Nothing moves without a human saying yes.\"\n\nTier 4 — Moat Features (Create Lock-In)\nFeature 13: Spine Intelligence Graph — Organizational Memory\n\nFeature statement: The Spine continuously builds a relational knowledge graph of every entity, relationship, decision, and signal — including all Memory Accumulator-captured AI sessions — creating an irreplaceable institutional memory\n\nPain: When a CSM leaves, account context walks out the door; when a sales rep changes territory, relationship history is lost\n\nOne-line pitch: \"The Spine never forgets. Your organization stays intelligent even as teams change.\"\n\nFeature 14: Memory Accumulator — Persistent AI Intelligence\n\nFeature statement: Every AI conversation, reasoning chain, and session is captured, linked to the relevant Spine entities, and surfaced back into the Workspace when those entities are accessed — persistent across sessions, organizational rather than personal\n\nPain: Every AI conversation starts from zero — prior reasoning is lost, context has to be re-established, decisions are not connected to each other\n\nROI/outcome: AI reasoning quality compounds over time; onboarding new team members takes days not months because AI memory already knows the accounts\n\nOne-line pitch: \"AI memory that lives in the Spine, not in a browser tab. Every prior session is context for the next.\"\n\nBuyer Persona Map (Updated)\nPersona Primary Features Core Message\nPersona Primary Features Core Message\nFounder / CEO Spine Intelligence Graph, Three Data Flows, Re-ingestion Loop, 12 Department Views \"One truth layer for the whole business. Every team, every system, always current.\"\nVP Customer Success / CCO Account 360, Proactive Signals, Depth Matrix, QBR Pack, HITL \"Know what's happening with every account before it becomes a problem — with evidence.\"\nRevOps / Operations Head 8-Stage Pipeline, 50 Connectors, Workflow Builder, Depth Matrix \"Data quality is enforced by the architecture. Every input is normalized before it becomes truth.\"\nSales / AE Account 360, Ask the Spine, 12 Views, Memory Accumulator \"Walk into every call with the full account picture already assembled. No research required.\"\nCTO / Head of Engineering 8-Stage Pipeline, Three Data Flows, Flow C governance rule, Re-ingestion \"The canonical data path ensures no connector or AI session writes dirty truth. Architecture enforces quality.\"\nSMB Owner Ask the Spine, 50 Connectors, Spine Intelligence Graph \"One system that connects everything you use and answers any business question in real time.\"\n"}