Skip to content
MoreProofOperator dossier

John Kipe

GTM AI Systems Builder

I build the systems between an AI promise and a responsible handoff, then document enough evidence for someone else to inspect the decisions.

01

Current post

Senior GTM AI Solutions Lead at Docebo

Since July 2026, my mandate has centered on workflow agentification, rapid validation, AI enablement, and governance across GTM work. These are areas of responsibility, not finished outcome claims.

Agentify real workflows

Turn recurring GTM work into governed, testable systems with explicit operator checkpoints.

Prototype and validate

Make the riskiest assumptions visible early through working prototypes and clear evaluation criteria.

Teach and govern

Build shared AI fluency, adoption patterns, and accountability around how systems are used.

02

Operating identity

What stays true across the systems

The stack changes. The accountability model does not.

01

Context is a system input.

Requirements, incentives, operating constraints, and failure costs belong in the architecture before a model does.

See the Transition Readiness system

02

Judgment needs a named gate.

Automation should expose the moment a person must review, override, approve, or stop the workflow.

Inspect MotionProof

03

Proof belongs beside the claim.

A confident narrative is not evidence. Source, audit, method, and limits should be reachable from the claim they support.

Open the systems ledger

04

Handoff is part of the build.

A system is unfinished until another operator can understand its controls, limits, and safe next action.

Review the OpenClaw record