Product Velocity as Moat

Sources#

Summary#

John Glasgow's claim that in an AI-native era, shipping speed itself is both the differentiator and the trust signal that wins enterprise deals. Campfire is "now the largest of the newer ERP cohort… purely on product velocity." Customers don't just buy the current feature set — they buy the belief that you'll keep up with them: "your velocity is so high, we feel confident you'll be able to scale with us." Velocity converts a startup's biggest weakness (incompleteness) into the reason to sign.

Velocity as a trust signal in mission-critical sales#

The hard part of selling unproven software into mission-critical workflows is trust — a CFO told Glasgow "I'm literally getting fired if you shut down." What closed those deals at 4 employees wasn't feature parity; it was demonstrated build pace: "look how much we've built in a short amount of time — we're going to continue to ship." Customers (Replit, PostHog among them) reason forward from observed velocity: as we add subsidiaries, need new features, get more complex usage-based revenue, you'll stay ahead of us. The proof point Glasgow offers: "we've never had anybody outgrow Campfire."

Why velocity is newly a moat (and not just hustle)#

Velocity has always helped startups; what makes it a moat now is the AI-native cost structure. When Campfire runs its own foundation model and custom agent platform, and agentic coding makes shipping cheap (Harness Shrinkage as Models Improve, Verification as the New Bottleneck), sustained high velocity is structurally available to the AI-native entrant and structurally hard for the legacy incumbent (old stack, big org, regression risk). Velocity is the operational expression of the The AI-Native Safe-Choice Inversion: the incumbent can't match the pace, so "AI-native = ships fast" becomes a defensible position.

The three things customers cite (velocity among them)#

Glasgow names the three reasons customers consistently give for choosing Campfire — velocity is the connective tissue:

Public-company readiness (audit, controls, approval workflows) — solving the end state customers aspire to.
Product velocity — confidence you'll scale with them.
Best AI — "maybe because we're the only one with our own foundation model and custom agent platform."

Velocity is what makes (1) and (3) believable as a trajectory rather than a snapshot.

Caveat: velocity as moat vs. velocity as treadmill#

The honest tension: a moat made of velocity must be continuously defended — it's only a moat while you out-ship everyone, which is closer to a treadmill than a structural barrier. It pairs with, but doesn't replace, durable moats: Compounding Data Moat (financial data + multi-entity workflow lock-in) and counter-positioning (Seven Powers Applied to AI). Velocity wins the land; data/workflow lock-in defends the expand.

The cohort's own version of the claim, and the only number attached to it (ICONIQ, September 2026)#

ICONIQ's 2026 State of Scaling (ICONIQ Venture & Growth, September 2026, empirical) interviewed five of its fastest-growing AI-forward portfolio companies (Anthropic, Braintrust, ElevenLabs, Glean, Legora) about what they think defends them, and the answer is this page's thesis nearly verbatim: "Product velocity is the moat that compounds. AI-generated code and shorter build cycles push learnings back into the product fast enough that the gap widens with every release." The framing sits under a heading that locates the moat first — "Defensibility is moving from the model to the specific workflow the product solves" — so velocity is presented as the mechanism that keeps a workflow moat (Compounding Data Moat) ahead of copying, not as a moat standing alone.

"The gap widens with every release" is the treadmill question answered by assertion. It is exactly what the caveat below denies can be assumed: the claim that a velocity lead compounds rather than being matched requires a competitor's pace to be lower and staying lower, and five self-selected winners have no visibility into that. practitioner-opinion inside an empirical document, from companies whose investor is publishing the report.

The one quantity in the vicinity, and it is about scaling speed rather than shipping speed. The same report puts its Pacesetter cohort at $1M → $100M ARR in ~14 quarters against ~22 for other software companies (~2–4 years on average; an outlier subset at "just 1–3 years"). That is the closest thing to a measured velocity gap the corpus has, and it is measured in revenue, not releases — and it is modeled, not observed: ICONIQ assumes 24 months from founding to $1M where undisclosed, assumes exponential growth between two press-released endpoints, and draws the curve only over companies that reached $100M. Useful as an order of magnitude for how much faster the frontier compounds; useless as evidence that velocity is what did it.

Connections#

Founder-Led Sales Discipline — founder-led selling is part of converting velocity into durable trust
John Glasgow / Campfire — "we're the largest purely on product velocity"
The AI-Native Safe-Choice Inversion — velocity is what sustains the "best AI / AI-native" claim the inversion rewards
Narrow Wedge into a Legacy Market — velocity is how a narrow wedge expands coverage without losing the customer
Harness Shrinkage as Models Improve — the cost structure that makes sustained high velocity structurally available to AI-native entrants
Verification as the New Bottleneck — the constraint on velocity is now verification, not coding; out-shipping means out-verifying
Compounding Data Moat — the durable moat velocity must convert into; velocity lands, data/workflow defends
Seven Powers Applied to AI — counter-positioning + which moats survive; velocity alone is a treadmill, not a Power
AI Native Product Cadence — Anthropic's 6mo→1mo→1day cadence is the same velocity-as-advantage thesis inside a frontier lab
Compounding Loop Optimization — the internal engine behind sustained velocity: Dan Carey's Claude Design team shipped 62 improvements Friday→Monday by optimizing every loop step

Open Questions#

Velocity-as-moat is a treadmill: it evaporates the moment a competitor matches pace. What converts Campfire's velocity lead into a structural moat before the AI-native cohort's pace converges? (Checked against the cohort's own answer and still open (2026-09-22). 2026 State of Scaling: The Great Sorting asked five of the fastest-growing AI-forward companies in its portfolio the same question, and their answer is the conversion this bullet asks for: velocity keeps a workflow moat ahead of copying — 'defensibility is moving from the model to the specific workflow the product solves' — with AI-generated code pushing customer learnings back into the product 'fast enough that the gap widens with every release.' That is a structural claim (velocity feeding an accumulating asset, not velocity alone), and it is the right shape of answer. It is also unfalsifiable as offered: no competitor pace, no convergence measurement, no case where the gap failed to widen — five self-selected winners describing their own moat in an investor's report. The bullet's trigger is unchanged: it needs a losing case, a company that shipped fast and was caught anyway.)
"Never had anyone outgrow Campfire" — is that survivorship (they haven't hit true enterprise scale yet) or a real claim that velocity closes the breadth gap faster than customers grow into it?

Sources#

The ERP for the AI Revolution is here
2026 State of Scaling: The Great Sorting — ICONIQ Venture & Growth, 2026 State of Scaling: The Great Sorting (September 2026, empirical; 52-page PDF, docling-parsed). Cited here for the Pacesetter operator interviews on velocity and workflow defensibility (p.28 — practitioner-opinion from five of the publisher's own portfolio companies, inside an otherwise operating-data report) and the quarters-from-$1M-to-$100M exhibit (p.24-25), whose curve is modeled between press-released endpoints through an assumed exponential and drawn only over survivors. Selection and COI at ICONIQ