H
Howardismvol. 03 · quiet corner of the web
Plate IIArchitectureHOWARDISM

Narrow Wedge into a Legacy Market

PublishedMay 23, 2026FiledConceptTopicArchitectureTagsStartupGo To MarketProduct StrategyReading4 minSourceAI-synthesised

Disrupt without being feature-complete: be the best for a narrow customer profile (tech cos outgrowing QuickBooks); Google-Sheets MVP; the wedge-flip lesson

Illustration for Narrow Wedge into a Legacy Market

Sources#

Summary#

John Glasgow's answer to the standard objection that you must be feature-complete to disrupt entrenched enterprise categories (ERP, CRM, HRIS). Campfire disproved it by being the best for a very narrow profile rather than broad: target tech companies that had outgrown QuickBooks but use only a fraction of NetSuite, solve a handful of features they actually need extremely well, and ignore the incumbent's vast unused surface. Within nine months this narrow focus was pulling customers off NetSuite — the supposedly mature, complex incumbent.

The "you don't need to be feature-complete" insight#

"Yes, the incumbents are incredibly deep and broad — but within our initial market of tech companies, they're actually not using a lot of NetSuite."

The leverage: incumbents are feature-complete for the whole market, but any specific segment uses a small subset. So the disruptor's job is to identify the high-value subset for a sharply-defined customer and beat the incumbent there. Campfire's chosen subset:

  • Approval workflows — "doesn't sound sexy, but a key reason folks need it for audit; QuickBooks doesn't have it."
  • Multi-entity accounting — subsidiaries; "in the AI-native world folks go multi-entity very quickly."

Define the customer narrowly, too#

The wedge is a customer profile as much as a feature set: not "anyone on QuickBooks" (that's the PLG/SMB/bookkeeper market, "a very different product to build") but the in-house accounting team at a tech company bringing accounting in-house. Glasgow chose pure sales over PLG precisely to serve this profile. "Own that one moment in time for tech companies." Narrowness compounds: a narrow feature set for a narrow customer at a narrow moment is what let four employees displace a NetSuite install at a $300M-revenue company.

Mockup-first MVP#

The wedge was validated with an almost-embarrassingly-thin first product: the first paying version was a Google Sheet iframed into a login, with Brex and Mercury feeds in a tab and a bunch of spreadsheet formulas — shipped <1 month into YC. "Very rudimentary," but real customers paid for it. The YC mantra ("how fast can you get paying customers? we don't want free") forces you to find the wedge empirically rather than build broad on spec. (Cf. Disposable Micro-Apps and Zero-Friction Scope Creep: ship the thinnest real thing, resist breadth.)

The wedge-flip lesson#

Campfire's wedge wasn't right on the first try. They applied to YC as a full general-ledger ERP, then briefly led with a revenue-recognition/SaaS-reporting add-on as the entry product — but "that cohort didn't convert well to the core product." So ~month 3 they flipped it: core ERP became the primary purchase, revenue an add-on. Lesson: the wedge is the entry point that converts to the core, not just the easiest thing to sell — test conversion, not just adoption.

Connections#

Open Questions#

  • A wedge works going in; does it constrain going out? Campfire now serves public companies — at what point does "narrow-but-best" require becoming the broad incumbent it displaced, re-incurring NetSuite's complexity?
  • The wedge-flip shows the first wedge can be wrong. What's the fastest signal that a wedge converts to the core vs. merely sells — Campfire took ~3 months; can it be read sooner?

Sources#

§ end
About this piece

Articles in this journal are synthesised by AI agents from a curated wiki and are refreshed automatically as new concepts arrive. Topics, framing, and editorial direction are curated by Howardism.

Cited by 7
  • The AI-Native Safe-Choice Inversion

    Buying the legacy incumbent used to be "safe"; post-AI, *being* the incumbent = not AI-native; boards give buyers air c…

  • AI-Native Startup Lifecycle

    Anthropic's May 2026 reframing of Idea/MVP/Launch/Scale assuming AI infrastructure: each stage's headcount/capital/skil…

  • Campfire

    AI-native ERP (YC S23) pulling customers off NetSuite; custom foundation model + agent platform; Series B (Accel/Ribbit…

  • John Glasgow

    CEO/founder of Campfire; 10yr corporate finance; founder-led-sales advocate; long-horizon "last job I'll ever have"

  • Problem-Solution Fit Discipline

    Idea-stage thesis: three defenses against premature building (time, resources, belief friction) all eroded; AI as devil…

  • Product Velocity as Moat

    Shipping speed as differentiator + trust signal ("you'll scale with us"); a treadmill that must convert into durable lo…

  • Vertical Slice Tracer Bullets

    Pragmatic-Programmer tracer-bullet pattern applied to agent task decomposition; vertical slices > horizontal layers; Ka…

Related articles
  • AI-Native Startup Lifecycle

    Anthropic's May 2026 reframing of Idea/MVP/Launch/Scale assuming AI infrastructure: each stage's headcount/capital/skil…

  • Campfire

    AI-native ERP (YC S23) pulling customers off NetSuite; custom foundation model + agent platform; Series B (Accel/Ribbit…

  • Founder-Led Sales Discipline

    Stay founder-led until PMF; don't offload sales to an AE *or* an agent; explicit tension with Founder As Agent Orchestr…

  • John Glasgow

    CEO/founder of Campfire; 10yr corporate finance; founder-led-sales advocate; long-horizon "last job I'll ever have"

  • Compounding Data Moat

    Anthropic's prescription for Scale-stage defensibility: time-locked behavioral fingerprint + domain-encoded edge cases…