Motion deep-dive
The BUILD motion: the AI-Native bet
When the company is rebuilding how users interact with the product, as a declared objective (like mobile-first), and engineers build with us inside real coding and release cycles. Rip and replace of the interface paradigm. Sheet timing: strategic, Q4 test to the C-suite.
What defines this motion
- The buyer's mental model: a strategic platform decision, not a purchase. "Who owns the interface between our users and our product for the next decade?"
- Pain: urgency. The initiative is declared and nothing is shipping (sheet). The 80%-of-internal-AI-projects-never-reach-production stat is the wound; press it gently.
- Buyer maturity: more evolved; wants education and architecture, not benefits copy. Messaging is code-forward and concept-heavy: the three layers, the flywheel, FE-not-IP.
- Decision profile: C-suite, multi-stakeholder, business case + technical validation. Slower, bigger, stickier.
Sales mechanics: top-down
- Sell the vision, then de-risk it: classic enterprise motion is vision → big contract → org rollout; reps need deep stakeholder-pain fluency and a real business case (Dock, Chasm Group).
- Our twist: prove speed early. "1–2 business days per product" converts the vision sale into an evidence sale. Scope a flagship workflow into production fast; the rollout sells itself internally.
- The committee: CTO signs, AI Engineer and Developer evaluate, CPO co-owns the bet, CFO asks about tokens. Each needs their own artifact (see persona pages).
Buyer behavior facts that shape build messaging
Technical buyers verify, not believe: the effective outreach artifacts are benchmarks, architecture deep-dives, and video walkthroughs of the actual interface, not decks (
daily.dev,
Uplift).
Peer relevance beats product relevance: "a named outcome at a recognizable company in their sector is worth ten thought-leadership articles" (
Somebody Digital). This is why logo clearance matters most in the build motion.
The dark funnel is where the decision forms: engineering leaders discover tools in private Slack groups, invite-only roundtables, and conference hallways (KubeCon, re:Invent, QCon). Podcast + open technical content = our presence there.
The competitive frame (negative space)
The build buyer's head contains LangChain/LangGraph, Anthropic Managed Agents, Braintrust, Arize, CrewAI, OpenAI AgentKit. The entire category says "reliable," "production-ready," "agents that work," "ship at scale": "reliable" is now the most overused word in the category; using it unironically makes us wallpaper. Required move: concede, then differentiate. Orchestration frameworks are excellent at Layer 1; Managed Agents overlaps at the brain. None of them is the product-embedded interface layer with user context, in-product execution, and the intent flywheel. We are Layer 2. Their Layer 1 stays; we front it via A2A.
Message architecture for this motion
| Layer | Build-motion version |
|---|
| Promise | You built the brain. We're the operator. AI-Native shipped in days, not quarters. |
| Pillars | Agentic Interface, FE not IP (your moat stays yours) · Build with us: A2A, MCP, SDK, deployment, testing · Control: AI Score = latency, cost, quality per action |
| Proof | Optibus: 4 products live, 1–2 business days each, A2A to their loops, 20–35% token cost cut (anonymize externally until cleared) |
| Classification line | "This is a build, with your engineers, in your codebase (Developer plugin). We are the layer, you own the product." Never let it be mistaken for a widget purchase. |
| CTA ladder | docs → engineering session on their hardest workflow → scoped production pilot → exec briefing |
Features to emphasize in build conversations
- Developer plugin + SDK (in-codebase; show the snippet in minute one).
- A2A + MCP: the no-lock-in argument and the partner posture toward their existing stack.
- Per-response metrics (model, tokens, cache, price) and Optimizer/routing: the CFO-grade cost story.
- Trust Lab (early access): golden sets, tool-use evals, import-from-production regression. "A prompt change is a code change."
Build-motion vocabulary
Say- "You built the brain; we're the operator"
- "Layer 2" · "FE, not IP" · "hours not quarters"
- Protocols, endpoints, eval types, real numbers
Never- "Reliable," "production-ready," "agents that work," "ship at scale," "agentic transformation"
- "End-to-end agent platform," "build the layer," "democratize AI"
- Activation-curve language in the exec room; any metric we don't have