CHAPTERS
Campfire’s mission: an AI-native ERP for high-growth finance teams
John Glasgow explains what Campfire is building: an AI-native ERP that automates accounting and financial reporting work so finance teams can focus on higher-leverage, strategic tasks. The conversation sets the scope around taxes, investor reporting, and operational finance workflows.
What an ERP is—and why the market is enormous but tough to enter
Andrew asks for a definition of ERP, and John frames it as the system of record for accounting and financial reporting. They discuss why the market is broad (every company needs one) yet challenging because it’s mission-critical and dominated by incumbents like NetSuite.
Founder-market fit: learning the pain from inside legacy finance systems
John connects his 10+ years in corporate finance to the conviction that ERP was ready for disruption. He also gained perspective through partnerships with legacy ERP vendors and heard repeated customer pain, reinforcing the opportunity.
“Why now?”: catalysts for a new ERP generation
They unpack the investor question John heard early: why attempt ERP disruption now. John’s initial thesis was that the rest of the finance stack modernized (payroll, spend, AP) while the general ledger lagged, creating sharp contrast and demand for a modern core.
YC speed-run prototype: shipping the first product in Google Sheets
John describes building the earliest version of Campfire in Google Sheets, embedded in a web login, with bank feeds and spreadsheet logic. The goal was to get paying customers quickly and iterate, aligning with YC’s ‘ship fast’ ethos.
Winning without being feature-complete: narrow segment, critical features
Andrew challenges the common belief that enterprise incumbents require feature parity to displace. John explains Campfire’s strategy: target tech companies outgrowing QuickBooks and build only the few NetSuite-driving capabilities they truly need (approvals, multi-entity, audit readiness).
Pulling customers off NetSuite: pain points, trust, and “venture investment” buying behavior
They discuss the surprising early outcome: Campfire moved customers from NetSuite within months. The win came from modern APIs/UX, doing a few things much better, and convincing CFOs to take a calculated risk—sometimes explicitly framed as a bet on the team’s ability to execute.
Early demand generation: events, community, and daily LinkedIn content
John outlines how Campfire found early customers—heavy presence at events, building advocates, and consistent LinkedIn publishing. Product demos converted prospects who expected to buy later but discovered Campfire already met their needs.
Velocity as a product: shipping speed builds confidence and retention
Andrew and John emphasize that fast product development reduced perceived risk for buyers. Customers believed Campfire would keep up with their growth (new subsidiaries, more complex revenue) and John claims no customer has outgrown the platform due to continuous shipping.
Go-to-market refinement: from rev-rec wedge to “core ERP first”
They revisit an early strategy debate: start with a revenue recognition/product wedge versus selling the full ERP. Campfire learned that rev-rec buyers didn’t convert well to the core ledger, so they flipped the packaging—core ERP first, revenue as an add-on.
Choosing sales-led over PLG: targeting in-house accounting moments
John explains why Campfire avoided the SMB/bookkeeping path: it implied a different product and go-to-market motion (PLG). Instead, they focused on companies bringing accounting in-house, which aligned with sales-led distribution and deeper workflow requirements.
Seed to Series A: founder-led sales, being close to customers, and micro-pivots
John describes reaching classic Series A metrics (around $1M ARR) primarily through founder-led sales. He argues founders should stay close to sales and customers until PMF, using constant micro-adjustments to features and messaging rather than major pivots.
The long grind to traction: referenceable customers and the Q4 ’24 inflection
Despite early paid users, John says real traction took over a year, with meaningful inflection around Q4 2024. Larger customers required more build-out; once they became referenceable, growth accelerated and ARR began doubling quarter over quarter.
Scaling after the Series A: new expectations, hiring, and operating differently
John shares the shift in mindset after raising a much larger round: moving from scrappy survival to scaling a real organization. He notes the overnight change in how investors expected him to hire, operate, and plan.
Competition and differentiation: product velocity, public-company readiness, and proprietary AI
Asked about new entrants, John frames Campfire’s edge as velocity, readiness for public-company audit/control rigor, and AI quality. He claims Campfire has strong references even in public markets and stands out by building its own foundation model and agent platform.
Long-term ambition and founder lessons: building a durable public company
John explains he chose ERP intentionally as a category large enough to build an enduring public company. He closes with advice to earlier-stage founders: enjoy the early days, expect stress to increase with scale, and keep conviction through the wilderness period.
Get more out of YouTube videos.
High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.
Add to Chrome