00 — Current GTM Canon
Status: CURRENT CANON · Commercial OS
Owner: Founder + Product Marketing
Last aligned: 2026-07-22
Authority: Explicit founder correction and approved visual direction supplied on
2026-07-22. Product and runtime behavior remain governed by the
Architecture Lock.
Purpose and precedence
This is the active commercial framing for IntegrateWise. It replaces the
conflicting 2026-07-21 framing that described IntegrateWise primarily as a
"Workspace for Human and AI Collaborative Work" sold through a Customer
Success / HubSpot wedge.
Customer Success, HubSpot, and any other supported connected system remain
valid proof paths. They are not the category, the homepage story, the only
buyer, or the sole launch requirement.
Until historical documents are migrated, this document wins for category,
positioning, audiences, website architecture, offers, GTM motion, and launch
narrative. It does not change the frozen product contract: the Spine is the
source of truth, governance is a hard gate, and the Twin never acts without
approval.
1. Category, brand, and promise
| Layer | Current canon |
|---|---|
| Category | The Operational Capability Platform for the AI Era. |
| Brand doctrine | Operational Continuity. Governed Intelligence. |
| One-liner | IntegrateWise connects people, AI surfaces, and operational systems through one governed capability fabric, so work can continue with context, control, and accountability. |
| Product promise | One platform gives every role the capabilities and context it needs to move work forward across the connected ecosystem. |
| Trust promise | Human intent is resolved through policy and approval before consequential execution; the resulting context and outcomes remain governed. |
The market story is bigger than an AI assistant, an integration product, or a
departmental workspace. It is the governed layer that connects AI, people,
applications, data, and operational work without asking an organization to
replace the systems it already relies on.
Campaign headlines and limits
- Primary platform headline: “The Operational Capability Platform for the
AI Era.” - Brand line: “Operational Continuity. Governed Intelligence.”
- Customer aspiration: “Your AI already knows language. Now let it know
your business.” - Campaign line under validation: “Your Last Auth to Complete Your
Ecosystem.” Use it only where the live product scope can substantiate the
authentication and connected-capability experience. It never claims that one
credential grants universal access to every system.
2. The product story customers should see
AI surfaces + people + applications/data
↓
Universal Capability Fabric
↓
Adaptive Spine + governance + continuity
↓
Twelve role-specific operational Workbenches
↓
Approved, auditable outcomes in connected systems
This is a market map, not an alternate runtime diagram. The frozen runtime and
approval sequence remain authoritative in the Architecture Lock.
| Proof surface | What it makes tangible |
|---|---|
| Platform | The governed fabric connecting AI surfaces, people, systems, data, and policy. |
| Workbenches | One platform composed for twelve operational roles, not a one-size-fits-all dashboard. |
| Capabilities | Work the platform can resolve, prepare, govern, and execute through approved connected systems. |
| Ecosystem | Connectors, sync, data, developer tools, custom and legacy systems, and the MCP path. |
| Developers | APIs, SDKs, webhooks, and capability extension points for builders. |
| Governance and Continuity | Why consequential action remains under human control and why context survives across time, people, and tools. |
Experience-led proof
The category must be proven through a legible operating experience, not only a
brand diagram. The supplied product references establish this activation story:
- Set the workspace context. Capture organization, role, goals, and
access configuration so the Workbench can be composed for real work. - Connect and scope systems. Use Integration Manager to establish a
supported connection, disclose the selected data scope, and test it before
activation. - Make the data path visible. Show connected data moving through the
governed pipeline into the Adaptive Spine, with health, quality, and status
explained at the appropriate technical depth. - Open the role-appropriate Workbench. Show a single operational surface
with current context, material work, and available capabilities for that
role—not a generic dashboard or chat-first product. - Make human control obvious. Show the four controls—Store in Spine, Ask
Your Twin, Assign Your Twin, and Approve Twin’s Action—and show a receipt
after an approved action.
This sequence turns the category into a credible activation story: connected
systems produce governed context; governed context makes the Workbench useful;
the user remains in control of consequential work.
Visual and language reconciliation
The visual references are an experience and information-architecture source,
not a blanket claim set. Use the following reconciliation when turning them
into launch pages, product tours, or UI work:
| Preserve as proof | Reconcile before publication |
|---|---|
| Integration Manager, Activation Hub, Configuration Manager, connection health, pipeline visibility, Workbench composition, governance, and auditability. | IntegrateWise is the product name; do not revive “IW-Continuity-Bridge” as an external product name. |
| Connected-system graph and connector marketplace as a way to make the ecosystem tangible. | Customer Success examples are one Workbench proof path, never the product’s sole audience or category. |
| The activation progression from workspace context through connection, governed data, and a ready Workbench. | The Twin is silent by default and a capability of the Workbench—not a persistent sidebar/panel destination. Hermes remains a governed execution concern, not a customer-facing AI-surface label. |
| The Four Buttons and an approval-visible Workbench. | “One click,” “total continuity,” “zero downtime,” “automated handoffs,” connector counts, logos, certifications, and provider coverage require current evidence. Never imply autonomous consequential execution. |
| Configuration, connection, pipeline, and governance status as operational proof. | Internal terms such as “creamy load” and engineering-layer labels do not belong in customer-facing copy. |
3. Audience and buying motion
The category is broad; the first motions must still be narrow enough to prove.
Select proof paths by operational pain, connected-system readiness, and a
credible champion—not by declaring one department to be the product.
| Audience | Job to be done | First proof to show |
|---|---|---|
| Executive sponsor — COO, CIO, digital/AI leader, founder | Turn fragmented AI, teams, and systems into a governed operating capability. | Platform architecture, a cross-system outcome, and the control boundary. |
| Operational leader — Sales, Marketing, Account Success, Customer Success, Product, Engineering, Operations, Support, Finance, HR, Governance | Give a role the right context and approved capabilities at the moment of work. | The relevant Workbench, a material workflow, and a measurable before/after. |
| IT, security, and governance | Enable AI and ecosystem access without surrendering policy, approval, tenancy, or auditability. | Identity boundary, approval flow, audit receipt, and scope documentation. |
| Developer, architect, and ecosystem partner | Extend the connected ecosystem with APIs, SDKs, MCP, webhooks, or custom capabilities. | Developer quickstart, public contracts, capability discovery, and a supported integration path. |
The initial motion is category-led, activation-assisted, proof-gated:
- Create demand for the platform category and its operational-continuity
outcome. - Qualify a concrete cross-system operational problem with an executive,
operator, and technical/control champion. - Activate a bounded ecosystem and one or more role-appropriate Workbenches.
- Demonstrate an evidence → proposal → approval → execution → receipt loop.
- Convert the verified outcome into expansion across more capabilities,
Workbenches, and connected systems.
4. Offer architecture and calls to action
| Intent | Primary call to action | Guardrail |
|---|---|---|
| Learn the category | Watch the platform overview | Show the fabric, continuity, and governance—not a chat-only demo. |
| Evaluate for a role | Explore Workbenches | Start from the role's work, then show the shared platform underneath. |
| Evaluate the ecosystem | Explore connectors and capabilities | Publish only currently supported systems and capabilities. |
| Build or integrate | Read developer documentation / explore SDK | Keep service internals, credentials, and tenant access private. |
| Start activation | Start free or request guided ecosystem activation | Offer self-serve only where the journey is genuinely supported; otherwise set clear guided expectations. |
| Buy with confidence | Talk to an expert / review security and governance | Do not claim certifications, customer logos, or control coverage without current evidence. |
The public navigation follows the approved direction: Platform · Workbenches
· Capabilities · Ecosystem · Developers · Resources · Pricing, with sign-in
and activation paths. A Customer Success page can be one solution page among
the Workbenches; it must not stand in for the whole product.
5. Message architecture
| Level | Message |
|---|---|
| Category | The Operational Capability Platform for the AI Era. |
| Promise | One governed fabric turns intent into accountable progress across the ecosystem. |
| Mechanism | Capability Fabric + Adaptive Spine + Workbenches + Governance. |
| Outcome | Operational continuity: context, evidence, approvals, and outcomes travel with the work. |
| Human control | The Twin prepares and proposes; people approve consequential action. |
Every asset should use a simple three-part narrative:
- Fragmented ecosystem: AI, people, and applications do not share enough
operational context. - Governed capability fabric: IntegrateWise connects the work through
discoverable, policy-bound capabilities. - Continuous outcome: the right role works with current context; actions
are approved, auditable, and become part of the organization’s continuity.
Do not lead with a connector count, a logo wall, a security certification, a
named AI provider, or a claim of autonomous execution. Those are evidence only
when current and verified; none is the category.
6. Launch and GTM phases
| Phase | Objective | Exit evidence |
|---|---|---|
| Foundation | Make the platform story, public contracts, activation path, and trust boundary internally consistent. | Current website information architecture, product tour, developer path, claims register, and technical release gates all pass. |
| Prove | Validate the fabric in real operational work across more than one applicable pattern. | Permissioned evidence of first governed outcomes, adoption quality, and a clear activation-to-value path. |
| Launch | Announce the category with product proof, not aspirational imagery alone. | Production-ready platform, verified screenshots/demo, current security posture, public pages for all proof surfaces, and approved proof material. |
| Repeat | Turn the activation into a reusable commercial and delivery playbook. | A repeatable discovery → activation → first-outcome → expansion motion across more than one buyer/use-case pattern. |
| Expand | Scale ecosystem and market reach after the core motion is repeatable. | Retention, expansion, support capacity, partner readiness, and channel economics support broader investment. |
7. Channel plan and 90-day scorecard
| Channel | Purpose now | Evidence of progress |
|---|---|---|
| Platform website and product tour | State the category and let buyers navigate to their role, ecosystem, or technical concern. | Qualified Platform, Workbench, capability, and developer journeys. |
| Founder and operator content | Teach operational continuity and governed intelligence through real problems and proof. | Qualified conversations and message pull-through, not reach alone. |
| Guided ecosystem activation | Turn high-intent evaluation into a bounded, governed first outcome. | Time to first governed outcome and expansion-ready capability adoption. |
| Developer and MCP ecosystem | Let builders discover, evaluate, and extend supported public contracts. | Documentation activation, SDK use, integration completions, and partner-quality inquiries. |
| Design-partner proof | Establish credible operating outcomes across selected Workbenches. | Permissioned, attributable before/after evidence; no invented logos or performance numbers. |
Track qualified platform evaluations by audience; time to first approved
governed outcome; active Workbenches and connected capabilities per activated
organization; approval-to-receipt completion; ecosystem depth; developer
contract adoption; and proof/claims freshness.
Days 0–30: build the six navigation surfaces, platform overview, product
tour, Workbench catalog, ecosystem/developer path, governance explanation, and
claims audit. Replace generic logo, certification, provider, connector-count,
and "one auth" claims with verified evidence or clear roadmap language.
Days 31–60: run guided ecosystem activations around selected operational
problems. Capture baseline, approval path, receipt, adoption signal, outcome,
and permission for every proof candidate.
Days 61–90: publish only verified proof, standardize the discovery and
activation playbook, and decide whether the public launch gate in
51 Launch Strategy is met. Do not set a launch date
merely because assets exist.
Migration record
The following 2026-07-21 documents contain superseded category or wedge
language. They remain useful historical context until migrated, but this
document takes precedence for the stated scope:
The live operating documents are updated to implement this canon: 50 GTM
Strategy, 51 Launch Strategy,
and the operational Go-Live and GTM Plan.