# One-Line Pitch

Make one Claude workflow safe enough to sell and ship team-wide.

# Positioning

ThumbGate is the AI reliability system behind one workflow with business value. It is not another horizontal agent platform. The front-line offer is a **Workflow Hardening Sprint** that gives teams shared memory, guardrails, and proof-ready runs so one workflow can be deployed, audited, and improved over time.

- **Primary Goal:** Turn "vibe coding" into a controlled rollout for one sharp agent.
- **Secondary Goal:** Convert real operator feedback into prevention rules, Thompson Sampling signals, and ThumbGate-ready datasets such as KTO/DPO pairs.

# Buyer Promise

We make one workflow measurable enough to justify and safe enough to roll out.

- Harden one Claude-first workflow without adding orchestration tax.
- Turn operator complaints into reusable prevention rules instead of repeated incidents.
- Prove what happened through audit trails, context provenance, and verification evidence.

# Buyer, User, Champion

- **Buyer:** consultancy owner, platform lead, head of ops, or AI product lead.
- **User:** the operator running the workflow day to day.
- **Champion:** the engineer or platform owner wiring ThumbGate, the Reliability Gateway, and Pre-Action Checks into the workflow.

# High-Signal Features

- **Context Packs:** Dynamic semantic assembly of project knowledge for agent boot-up and bounded retrieval.
- **Pre-Action Checks:** Repeated failures trigger non-bypassable `CLAUDE.md` / `AGENTS.md` rules and shared prevention policies.
- **Proof-Ready Runs:** Machine-readable evidence, audit trails, and hosted workflow artifacts for rollout decisions.
- **Release Confidence:** Changesets, SemVer, version sync, and exact-merge verification keep package publishes legible to enterprise buyers.

# Best First Wedge

Start with one workflow, not a platform migration or generic "AI employee" pitch.

- Best first offer: **Workflow Hardening Sprint**.
- Best fit: code modernization, PR review hardening, and internal ops automation.
- Qualification: one workflow owner, one repeated failure pattern, one proof review.
- Technical engine stays the same: feedback capture, context engineering, Thompson Sampling, and DPO export.

# Commercial Motion

- Start with the sprint, not the subscription pitch.
- The first repeatable next dollar should come from a booked workflow hardening sprint or named pilot agreement, not from hoping low-intent self-serve traffic converts.
- Keep the local CLI free as the adoption wedge and proof surface.
- Expand into Team seats when the buyer needs synced memory, shared rules, approval boundaries, auditability, and usage analytics across operators.
- Keep Pro as the solo self-serve side lane, not the headline offer.
- Use [WORKFLOW_HARDENING_SPRINT.md](WORKFLOW_HARDENING_SPRINT.md), [FIRST_DOLLAR_PLAYBOOK.md](FIRST_DOLLAR_PLAYBOOK.md), and [VERIFICATION_EVIDENCE.md](VERIFICATION_EVIDENCE.md) in every sales conversation.

# Academic Validation

ThumbGate's architecture — external skill memory that rewrites itself from failure feedback without retraining the underlying model — is validated by the Memento-Skills framework (arXiv 2603.18743, March 2026). That peer-reviewed research demonstrated 26–116% relative accuracy improvements using the same Read → Execute → Reflect → Write loop that ThumbGate implements as capture → infer → enforce → block. This is not a feature comparison; it is independent confirmation that context engineering beats fine-tuning for agent governance.

# ICP (Ideal Customer Profile)

- AI-first product teams shipping copilots or agentic workflows with real business owners.
- Platform teams standardizing behavior across Claude, GPT, Codex, Gemini, and custom runners.
- Consultancies installing AI workflows for clients who need proof, policy, and auditability.
