Unclassified

11 — Positioning

Status: HISTORICAL REFERENCE · Superseded for current positioning
Owner: Product Marketing
Last verified: 2026-07-21

Current authority: 00 Current GTM Canon
supersedes this document's category, audience, and narrative choices as of
2026-07-22. Do not use this page to author new external positioning until it
is migrated.


Purpose

One positioning statement, defended with evidence, that every other commercial artifact derives from. If a sentence on the website, in a deck, or in a sales call can't be traced back to this document, it doesn't ship.

Target audience: Founders, marketing, sales, anyone representing IntegrateWise externally.

Objectives: (1) Lock the positioning statement. (2) Define the competitive alternatives we position against. (3) Give per-audience variants that stay coherent.


1. The Positioning Statement (canonical)

For teams whose work is scattered across dozens of disconnected tools — and whose AI experiments quietly failed — IntegrateWise is the workspace for human and AI collaborative work. Every person works alongside a governed Twin on a shared workbench, over operational truth the organization owns. Unlike copilots bolted onto single apps, automation tools that move data without understanding it, or assistants that forget everything, IntegrateWise gives humans and AI one place to do the work together — with memory that persists, actions that require approval, and truth that never belongs to the AI.

Compressed (25 words): IntegrateWise is the workspace where humans and their Twins do the work together — one shared workbench, governed actions, and truth the organization owns.


2. Positioning Inputs (April Dunford model)

Competitive alternatives (what customers do today, in order of frequency):

  1. The Human API — the person shuttles context between 5–200 tools by hand. The real competitor is the status quo.
  2. Per-app copilots — Microsoft 365 Copilot, Gemini, Einstein/Agentforce: AI trapped inside one vendor's silo, multiplying fragmentation instead of ending it.
  3. General assistants — ChatGPT, Claude in a browser tab: no shared state with the org's work, session amnesia, ungoverned memory.
  4. Automation/iPaaS — Zapier, Workato, n8n: move data, don't understand it, no memory of why it matters.
  5. Internal builds — dashboards a departed engineer once maintained.
  6. Category point tools — Gainsight for CS, CDPs for marketing: one department, one moment in time.

Unique attributes (what only we have):

  1. Shared-state collaboration — human and Twin work on the same workbench object, not chat-and-paste. No competitor has a collaboration model; they have a chat sidebar.
  2. The Adaptive Spine — canonical operational truth independent of any single SaaS app, with source attribution and confidence on every field.
  3. TruthLayer — approval-gated organizational memory. Every other AI auto-writes its memory; ours cannot.
  4. Projection, not portals — one truth projected into role-composed workbenches; change flows back governed.
  5. Governance as architecture — proposal → approval → execution → audit is the physics of the system, not a setting.

Value (what the attributes enable — see 16 Value Proposition):

  1. The 2–4 hours/day of context reconstruction disappears — work starts where it left off.
  2. AI becomes trustworthy enough for consequential work, because evidence and approval are structural.
  3. Institutional memory compounds and survives turnover — continuity as an asset.

Who cares most (33 ICP): B2B SaaS companies, 50–1,000 employees, whose customer-facing teams (CS first) drown in tool sprawl and have already been burned by an AI rollout.

Category (05 Category Definition): Workspace for Human and AI Collaborative Work.


3. The Three-Layer Position

LayerClaimProof
ProblemWork is fragmented across tools; AI made it worse by adding amnesiac chat tabs. The person is the integration layer.130+ SaaS apps per business (Productiv); 2–4 hrs/day context gathering; ~80% quiet AI demotion
ProductOne workspace: human + Twin on shared workbenches, over the Spine, with governed actions.Live: 70+ connectors, Entity360 < 200ms, TruthLayer, governed proposal lifecycle
Proof of trustAI never owns truth. Nothing executes without approval. Everything is auditable.Governance architecture; "Truth you own. AI you rent. Approval in between."

4. Positioning by Audience

Practitioner (CSM/AM/ops):

"Your morning is eight tabs and a prayer. IntegrateWise opens on what changed, what needs you, and what your Twin already prepared. You decide; it finishes."

Executive buyer (VP CS / COO):

"Your team's context lives in tools and leaves with people. IntegrateWise makes it organizational: one workspace where every person works with a governed Twin over truth you own. Time returns in week one; continuity compounds forever."

Technical evaluator (IT/Security):

"The Adaptive Spine holds canonical state with tenant isolation and provenance on every field. The Twin reads scoped projections and proposes; execution requires human approval and produces an audit trail. AI never writes truth directly. Your tools stay; your data stays yours."

Investor:

"Every vendor is bolting a copilot onto its silo. Nobody owns the layer where humans and AI actually work together over shared, governed state. That layer — not the model — is where the switching costs live."


5. What This Positioning Forbids

  • Leading with integrations or connector counts (that reads iPaaS — a forbidden category).
  • Leading with the model or "AI-powered" (the AI is rented; the truth is the asset).
  • Demoing chat before demoing the workbench (chat-first reads assistant).
  • Any sentence where the Twin is the hero. The human is the hero; the Twin is the ally.

6. Positioning Tests

Run quarterly (73 Marketing Metrics):

  • Ten cold prospects hear the one-liner; ≥7 can say back what we do without using "chatbot," "integration tool," or "dashboard."
  • Win/loss notes show the shared-workbench + governed-truth distinction was understood in ≥80% of evaluations.
  • Zero pipeline deals where we were evaluated primarily against Zapier/Workato (if that happens, positioning leaked into iPaaS).

KPIs: message pull-through rate in sales calls; category words used by prospects unprompted; analyst restatement accuracy (66 Analyst Relations).


Related: 18 Terminology · 12 Messaging · 17 Differentiation · 08 Competitive Landscape · 53 Website Copy