Unclassified

01 — Company and Founding Narrative

Status: Canonical narrative; historical details require source evidence

Why IntegrateWise exists

Modern organisations have many specialised tools but no durable continuity
across them. People become the integration layer: reconstructing customer,
project, decision, and execution context before useful work can begin.

The founding problem is the “Human API” experience—manually bridging an
enterprise account across Sales, Customer Success, Support, Product, Finance,
communications, and delivery systems. IntegrateWise exists so people no longer
have to carry operational continuity in their heads.

Mission

Give every person a role-specific Workbench where they and their Twin can work
over connected organisational truth, with durable context and governed action.

Vision

An organisation should be able to connect its working systems once, preserve
operational truth in its own Spine, and let every authorised user receive the
minimum relevant context and capabilities for the work at hand.

Company doctrine

  • Spine owns truth. Memory can inform truth but is not truth.
  • AI is non-authoritative. Confidence never creates authority.
  • Governance is a hard gate. No approval token means no execution.
  • The user stays in control. Twin prepares and proposes; it does not act
    autonomously.
  • One surface. The Workbench is composed by role and context rather than
    split into architectural layers.
  • Broad underneath, narrow at the surface. Complexity remains in the
    platform, not in the user's interaction model.

Company operating questions

Every initiative should answer:

  1. Does it reduce context reconstruction?
  2. Does it strengthen ownership, provenance, or portability of operational
    truth?
  3. Does it make useful work easier without weakening authority boundaries?
  4. Can its end-to-end path be traced from user or platform need to verified
    outcome?
  5. Is it demonstrably used by Customer Zero or a design partner?

Historical handling

Earlier category labels, product names, and layer-based UI descriptions remain
valuable as evolution evidence. They must be marked Historical or Superseded and
must not override the frozen product definition.