CHAPTERS
- 0:05 – 0:39
Campfire’s mission: an AI-native ERP for finance teams
Andrew introduces John Glasgow and Campfire, framing the company as an AI-native ERP aimed at automating manual accounting and reporting work. John explains the value proposition: letting finance teams spend less time on repetitive tasks and more on strategic work.
- •Campfire positions itself as an AI-native ERP for high-growth companies
- •Focus on finance/accounting automation: reporting, taxes, investor reporting
- •AI enables shifting work from manual operations to strategic finance
- 0:39 – 1:54
ERP 101 and why the market is enormous (and hard)
John defines ERP as the system of record for accounting and financial reporting, emphasizing that every company needs one. They discuss the reality that it’s a mission-critical, established category, which makes disruption difficult but the opportunity broad.
- •ERP = enterprise resource planning: core accounting + financial reporting backbone
- •Universal need: taxes, audits, investor reporting create a wide market
- •Disruption challenge: mission-critical software and entrenched incumbents
- 1:54 – 2:54
Founder–market fit: a decade inside legacy finance stacks
John explains how his corporate finance background and later partnerships work with legacy ERPs exposed recurring pain across customers. This direct exposure built conviction that the problem was widespread, not just personal frustration.
- •10+ years in corporate finance living in legacy systems
- •Post-acquisition role partnering with large ERP vendors and their customers
- •Customer feedback validated the pain and motivated the leap to build Campfire
- 2:54 – 3:24
The ‘why now’ question and finding a wedge into an incumbent market
They unpack investor skepticism about timing and the need for a catalyst in a mature category. John describes how he had to think deliberately about entry strategy and how to win trust despite incumbents like NetSuite.
- •Investors pressed hard on “Why now?” for established ERP markets
- •Need for a credible catalyst + a practical go-to-market wedge
- •Trust barrier is high because ERP is core infrastructure
- 3:24 – 5:09
Shipping fast in YC: the first paid product was a Google Sheet
John recounts how YC’s pressure to ship forced extreme pragmatism: the earliest version was essentially Google Sheets embedded in a web login with financial feeds. The key was getting paying customers quickly and iterating from real usage.
- •YC constraint: ship in ~3 months, get paying customers quickly
- •Prototype: Google Sheet iframed into a browser with Brex/Mercury feeds
- •Paid customers arrived within the first month; rapid iteration followed
- 5:09 – 6:52
You don’t need NetSuite’s entire feature set—focus on what tech companies actually use
They challenge the assumption that enterprise software must be feature-complete to compete. John explains Campfire’s segmentation: tech companies outgrowing QuickBooks only need a subset of “grown-up” capabilities, which Campfire prioritized.
- •Incumbents are broad/deep, but many customers use only a small portion
- •Target segment: tech companies graduating from QuickBooks
- •Priority features: approval workflows (audit), multi-entity accounting, scaling needs
- 6:52 – 8:51
Pulling customers off NetSuite: winning on APIs, UX, and trust
Andrew probes how Campfire convinced companies to switch from NetSuite even under contract. John explains that dissatisfaction with legacy APIs and UI created openings, but early customers also ‘bet on the team’ given the risk of ERP migration.
- •Customers unhappy with legacy APIs and outdated interfaces
- •Mission-critical switch requires credibility beyond price or novelty
- •Early CFOs viewed adoption as a “venture bet” on Campfire’s survival and roadmap
- 8:51 – 10:47
Demand generation: events, daily LinkedIn, demos, and customer advocacy
John outlines how Campfire found and converted early customers through a mix of in-person community building and consistent content marketing. Group demos and visible shipping velocity helped prospects realize Campfire already met their core requirements.
- •Go to many events; build community presence
- •Daily LinkedIn posting helped drive awareness; business became heavily inbound
- •Group demos converted skeptics once they saw feature readiness
- •Word-of-mouth and references amplified growth
- 10:47 – 12:39
Go-to-market and product packaging: rev-rec wedge vs ‘sell the core ERP’
They revisit an early strategic debate: start with revenue recognition/SaaS reporting as a wedge, or push the full core ledger/ERP. Campfire learned the rev-rec buyer cohort didn’t reliably convert to the core ERP, prompting a packaging flip.
- •Initial thought: sell rev-rec/revenue accounting as a wedge alongside ERP
- •Discovery: rev-rec-first customers didn’t convert well to full ERP migration
- •Decision: make the core product the entry point; rev-rec became an add-on
- •Strategic lesson: optimize for the path to the main product, not the easiest first sale
- 12:39 – 13:16
Choosing the customer and sales motion: in-house accounting teams, sales-led (not PLG)
John explains why Campfire avoided building an SMB/bookkeeping-oriented product and instead focused on in-house finance teams at scaling tech companies. This choice pushed them toward a sales-led motion and a specific ‘moment in time’ trigger: bringing accounting in-house.
- •SMB QuickBooks market implies a different product (more PLG)
- •Campfire chose sales-led, targeting in-house accounting teams
- •Key trigger: companies bringing accounting in-house as they scale
- •Focus on owning a specific transition point for tech companies
- 13:16 – 15:19
Seed to Series A: founder-led sales, customer proximity, and micro-pivots
John describes the operating principles that helped them reach Series A: in-person building, speed, and intense founder-led sales. He argues founders should stay close to customers, using sales insights to drive engineering priorities while iterating via “micro-pivots.”
- •YC advice remembered: build in the Bay, build in person, get to Series A
- •Founder-led sales through the first ~$1M ARR; John ran demos and sales
- •Founder proximity: in customer Slack channels, joining sales calls
- •No major pivot, but continuous micro-adjustments on features and positioning
- 15:19 – 16:20
When it started working: referenceable migrations and the Q4 ’24 inflection
They discuss the long ramp typical of ERP: even with early paying customers, meaningful traction took over a year. NetSuite-to-Campfire migrations became transformative references, enabling rapid ARR acceleration beginning in late 2024.
- •Long build cycle: traction meaningfully appeared after ~1+ year
- •Key turning point: successful NetSuite-to-Campfire migrations (summer ’24)
- •Referenceability unlocked broader adoption (fall ’24)
- •Q4 ’24 onward: ARR more than doubled quarter-over-quarter
- 16:20 – 16:44
Scaling mindset shift after the Series A: from scrappy to structured
John reflects on the psychological and operational change after raising a much larger Series A. Investors pushed them to rethink hiring and scaling, forcing an overnight transition from survival mode to building a repeatable growth machine.
- •Funding step-change: from ~$3.5M to ~$35M raised
- •Investors demanded a new operating model and hiring approach
- •Founder transition: scrappy execution to scalable organization design
- 16:44 – 18:06
Competition and differentiation: product velocity, public-company readiness, and AI moat
John addresses the growing cohort of modern ERP startups and explains why Campfire wins: faster shipping, credibility with public-company-grade requirements, and AI capabilities. He claims Campfire’s AI stands out, citing their foundation model and custom agent platform.
- •Modern ERP field is getting crowded; Campfire claims leadership by size
- •Differentiators: product velocity, audit/controls rigor, public-company references
- •AI differentiation: “best AI,” including their own foundation model + agent platform
- •Strategy: solve for the end-state rigor (IPO/public readiness) to win earlier-stage customers
- 18:06 – 27:38
Long-term ambitions and founder lessons: go public, enjoy the journey, and persist through the plateau
John shares his intent to build a durable public company and frames Campfire as a decades-long mission. He closes with lessons: stress grows with scale, early days are uniquely memorable, and perseverance through a mid-journey stall was essential to reaching the inflection.
- •Ambition: build a massive, durable company and ultimately go public
- •Personal commitment: Campfire as the last job for the next decades
- •Advice: enjoy the early days—responsibility and stress increase over time
- •Hardest phase: ~spring ’24 plateau; conviction to keep grinding without a major pivot
- •Why now (revisited): finance stack modernized everywhere except the general ledger; AI flipped ‘safe’ away from incumbents
