Campfire vs Light: which one fits your company?
Research-backed and vendor-neutral: real-world pricing anchors, twelve functional domains rated side by side, and the situations where each system is the right call.
The short answer
Choose Campfire if you are high-growth software and tech companies from post-seed through early enterprise ($5M–$250M revenue); choose Light if you are lean multi-entity, multi-country scale-ups; europe-first ($5M–$100M). Campfire rates higher for revenue recognition & billing (4/5 vs 2/5); Campfire rates higher for core financials & accounting (4/5 vs 3/5).
Which one fits your revenue, industry, and requirements?
Score both in 10 minutes →Positioning
What each system is, in one paragraph
Campfire
ai-native ERP for high-growth tech companies
Campfire is a venture-backed, AI-native general ledger and accounting ERP aimed at high-growth technology companies, from post-seed startups through mid-market and early enterprise. Founded in 2023 out of Y Combinator by John Glasgow (ex-Invoice2go) and Paul Nichols, it sells a modern GL with multi-entity consolidation, an end-to-end revenue automation module (ASC 606 rev rec plus subscription, usage, milestone, and transaction billing), close management, and a proprietary accounting AI stack: the Ember assistant and a foundation model the vendor calls LAM (Large Accounting Model). It raised roughly $103M through October 2025, including a $65M Series B co-led by Accel and Ribbit only 12 weeks after a $35M Accel-led Series A, making it the best-funded direct rival to Rillet in the AI-native GL category. Like Rillet, it is a finance system, not an operational ERP: no native inventory, manufacturing, or order fulfillment. The core diligence question is vendor youth. The product is about three years old, review volume is thin, and its 95%-accuracy AI claims are vendor benchmarks, not independently audited results. Long-run scale, auditor familiarity, and data portability deserve explicit scrutiny.
Full Campfire profile →Light
ai-native ERP for multi-entity multinationals
Light is a Copenhagen-based, AI-native finance platform (self-described 'all-in-one AI-native ERP') founded in 2022 by Jonathan Sanders and Filip Kozjak. It rebuilds the general ledger on a custom high-performance database and layers AI agents on top, unifying multi-entity accounting, AP, AR, expense management with virtual cards, tax handling, and real-time consolidated reporting, with a command interface that works from Slack and Teams. It raised a $30M Series A led by Balderton in September 2025 ($43M total), and its named customers are European hypergrowth companies (Lovable, Sana, Legora, KeyShot, Famly). Its distinctive bet is Europe-first: multi-entity, multi-currency, multi-jurisdiction complexity from day one, including e-invoicing support (Peppol and local mandates), which US-centric rivals mostly lack. The referee's caution is proportionality: Light is the smallest and earliest of the AI-native cohort profiled here, with roughly $43M raised versus $100M+ at Rillet, Campfire, and DualEntry, a reported $1.2M ARR within six months of commercial launch, a tiny public review base, and essentially no US customer evidence. For a US mid-market buyer it is a watch-list system, not yet a default shortlist entry.
Full Light profile →Snapshot
Campfire vs Light at a glance
| Campfire | Light | |
|---|---|---|
| Category | ai-native ERP for high-growth tech companies | ai-native ERP for multi-entity multinationals |
| Vendor | Campfire | Light (light.inc) |
| Ideal company size | high-growth software and tech companies from post-seed through early enterprise | lean multi-entity, multi-country scale-ups; europe-first |
| Typical revenue range | $5M–$250M | $5M–$100M |
| Relative cost tier | medium | medium |
Pricing
Which costs less — and what you'll actually pay
Campfire and Light sit in a similar cost tier: typical annual software spend is Undisclosed; peers land ~$20K-$40K/yr for Campfire versus Undisclosed (no public data) for Light, with realistic year-one totals of ~$30K-$55K all-in (peer-anchored est., low confidence) and Undisclosed (no public data) respectively. Both are negotiable — treat these as anchors, not quotes.
| Campfire | Light | |
|---|---|---|
| Licensing model | Quote-based annual SaaS subscription; no published price list, tiers, or per-seat rates as of mid-2026. Third-party reviewers describe pricing as scoped to company size, revenue streams, reporting requirements, and stack complexity, which matches the complexity-based quoting pattern of the AI-native GL category. Implementation terms are also unpublished. | Quote-based SaaS subscription; no published price list, tiers, or pricing page exists as of mid-2026 (light.inc/pricing returns nothing), and no third-party pricing benchmarks, Vendr data, or practitioner-reported deal figures were found. Pricing structure (per entity, per user, per module) is itself undocumented publicly. |
| Entry annual cost | Undisclosed; category anchor ~$20K/yr | Undisclosed (no public data) |
| Typical annual software | Undisclosed; peers land ~$20K-$40K/yr | Undisclosed (no public data) |
| Implementation | Undisclosed; signals point mid-4 to low-5 figures | Undisclosed (no public data) |
| Realistic year-one total | ~$30K-$55K all-in (peer-anchored est., low confidence) | Undisclosed (no public data) |
| At renewal | No public renewal data exists; the risks are structural to young vendors. Early-adopter discounts can reset at first renewal, complexity-scoped pricing can move when entities or connectors are added mid-term, and a vendor posting 10x growth gains pricing power each year. Before signing, get in writing: the renewal uplift cap, the cost of adding an entity or integration mid-contract, and what happens to any promotional pricing at term end. | No renewal history exists; the company only began charging commercially around 2025. The structural risks are the same as the rest of the cohort (early-adopter discounts resetting, complexity-based repricing) plus one specific to Light: with $43M raised against rivals holding $100M+, a future down-round, acquisition, or pivot is a live scenario, and renewal terms could shift with it. Multi-year rate locks and contractual exit terms matter more here than anywhere else in this category. |
Pricing data confidence — Campfire: quote-based; limited public data — treat as rough anchors. Light: quote-based; limited public data — treat as rough anchors. Figures are directional anchors from cited public sources, not quotes.
Negotiating with Campfire
- ▪Competitive quotes from Rillet, DualEntry, NetSuite, or Sage Intacct; the vendor knows every deal is contested and Numeric-style comparison content confirms head-to-head selling.
- ▪Multi-year commitment or annual prepay in exchange for a rate lock and a capped renewal uplift.
- ▪Reference, logo, and case-study participation; the vendor's marketing leans heavily on named customers.
- ▪Itemized implementation fee with a defined historical migration window; push for a waiver against a competing quote.
- ▪Defined add-on pricing for future entities and connectors written into the order form.
Negotiating with Light (light.inc)
- ▪First-US-logo status: reference, logo, and case-study participation in exchange for pricing and onboarding concessions.
- ▪Competitive quotes from Rillet, Campfire, and DualEntry; Light must beat better-funded rivals on price or terms.
- ▪Multi-year rate lock with a defined renewal uplift cap.
- ▪Contractual data-export formats, exit assistance, and source-data escrow, given the vendor's stage.
- ▪Committed implementation timeline and named deployment resources in the order form.
These are market anchors. Get a year-one cost estimate for your company size.
Run the Fit Assessment →Capabilities
Functional depth, domain by domain
Ratings are 1–5 relative to each system's own target market— they show where each product concentrates its depth. Full evidence and caveats live on each system's profile page.
| Campfire | Light | |
|---|---|---|
| Core financials & accounting | ●●●●●leads | ●●●●● |
| Multi-entity & consolidation | ●●●●● | ●●●●● |
| Revenue recognition & billing | ●●●●●leads | ●●●●● |
| Inventory & warehouse | ●●●●● | ●●●●● |
| Manufacturing & production | ●●●●● | ●●●●● |
| Order management & commerce | ●●●●● | ●●●●● |
| Projects & services | ●●●●●leads | ●●●●● |
| Reporting & analytics | ●●●●●leads | ●●●●● |
| Platform & customization | ●●●●● | ●●●●● |
| Integrations & ecosystem | ●●●●●leads | ●●●●● |
| Usability & adoption | ●●●●●leads | ●●●●● |
| Scalability & performance | ●●●●●leads | ●●●●● |
Verdicts
The head-to-head calls our research makes
Campfire has roughly 2.4x Light's funding, a US customer base including NYSE-listed users, and a revenue automation module Light lacks; Light counters with native expense management and cards, European e-invoicing compliance, and the Slack/Teams command interface. For US buyers Campfire is the safer AI-native pick; Light's edge appears only when European jurisdictional complexity dominates the requirements list.
Delivery
Implementation: what each takes to go live
| Campfire | Light | |
|---|---|---|
| Typical timeline | Days to roughly three months depending on footprint. Numeric describes Campfire go-lives as potentially taking days for simple migrations (faster than Rillet's 4-6 weeks); a customer review documents a three-month path with two months of implementation and one month of parallel running. Messy rev-rec contract data and long historical windows extend timelines, same as the rest of the category. | Vendor-claimed 'live in weeks, not months,' consistent with the AI-native cohort's 4-8 week pattern, via foundation setup (entities, records, vendors) then configuration. No independent implementation reports exist; multi-jurisdiction footprints (per-country tax, e-invoicing, banking) are the obvious timeline variable. |
| Who delivers it | Vendor-led. Campfire's own team runs migration and onboarding; there is no partner delivery channel. That concentrates delivery quality and delivery risk in one small, fast-growing company's bandwidth. | Vendor-led by an in-house deployment team the company is actively expanding post-Series A. No partner delivery channel exists. Delivery quality is therefore consistent but capacity-bound, and US deployments will initially be served by a young US office. |
| Watch for | Rev-rec data cleanup underestimated: automated ASC 606 depends on clean CRM and billing contract data; dirty Salesforce or Stripe data is the most common timeline slip in this category. | Buying the category, not the product: Light shares the AI-native pitch with Rillet, Campfire, and DualEntry but has a different functional center (multi-country operations and spend, not rev rec); mismatched triggers lead to mid-implementation surprises. |
Decision
When to choose each
Choose Campfire when…
- ▪A Series A-C software company on QuickBooks with spreadsheet ASC 606, a lean finance team, and pressure to close faster and report ARR reliably.
- ▪A tech company quoted a 6-9 month NetSuite project plus SuiteBilling/ARM modules that wants most of the finance outcome in weeks at lower cost, and accepts a young vendor.
- ▪A multi-entity software group (US parent, a few international subsidiaries) doing manual consolidation who values automated FX handling.
- ▪A company with mixed billing models (subscription plus usage or milestones) that wants billing and rev rec in the same system as the ledger.
Choose Light when…
- ▪A European or Europe-heavy multi-entity scale-up (3-15 entities across several countries) drowning in per-country accounting tools, VAT regimes, and e-invoicing mandates.
- ▪A US company with material European operations that needs Peppol e-invoicing and per-jurisdiction tax handling that US-centric AI-native rivals lack.
- ▪A lean finance team that wants spend management, cards, AP, AR, and the ledger in one system instead of a Ramp-plus-GL stack.
- ▪A company whose finance workflows live in Slack or Teams and values the command-interface operating model.
Reading this on the train? Email yourself the link.
One email: this comparison plus the pricing summary. Nothing else.
FAQ
Campfire vs Light: common questions
Which costs less, Campfire or Light?
Campfire and Light sit in a similar cost tier: typical annual software spend is Undisclosed; peers land ~$20K-$40K/yr for Campfire versus Undisclosed (no public data) for Light, with realistic year-one totals of ~$30K-$55K all-in (peer-anchored est., low confidence) and Undisclosed (no public data) respectively. Both are negotiable — treat these as anchors, not quotes.
Is Campfire or Light better for revenue recognition & billing?
Campfire rates higher for revenue recognition & billing in our assessment (4/5 vs 2/5). Revenue automation is Campfire's flagship module alongside the GL: ASC 606 revenue recognition with automated journal entries, deferred revenue tracking by customer, contract, and product, and billing support spanning subscription, usage-based, milestone, and transactional models, with Stripe payment sync.
Is Campfire or Light better for core financials & accounting?
Campfire rates higher for core financials & accounting in our assessment (4/5 vs 3/5). A modern, GAAP-oriented core: customizable general ledger, continuous account reconciliation, automated FX gain/loss booking on AR and AP, close management with checklists and flux analysis, and audit trails with SOC 1 and SOC 2 attestations.
How long do Campfire and Light take to implement?
Campfire: Days to roughly three months depending on footprint. Numeric describes Campfire go-lives as potentially taking days for simple migrations (faster than Rillet's 4-6 weeks); a customer review documents a three-month path with two months of implementation and one month of parallel running. Messy rev-rec contract data and long historical windows extend timelines, same as the rest of the category.. Light: Vendor-claimed 'live in weeks, not months,' consistent with the AI-native cohort's 4-8 week pattern, via foundation setup (entities, records, vendors) then configuration. No independent implementation reports exist; multi-jurisdiction footprints (per-country tax, e-invoicing, banking) are the obvious timeline variable.. Timelines depend on scope, data quality, and implementation team as much as the product.
When should we choose Campfire instead of Light?
Campfire is usually the better call when: A Series A-C software company on QuickBooks with spreadsheet ASC 606, a lean finance team, and pressure to close faster and report ARR reliably. Or when: A tech company quoted a 6-9 month NetSuite project plus SuiteBilling/ARM modules that wants most of the finance outcome in weeks at lower cost, and accepts a young vendor.
When should we choose Light instead of Campfire?
Light is usually the better call when: A European or Europe-heavy multi-entity scale-up (3-15 entities across several countries) drowning in per-country accounting tools, VAT regimes, and e-invoicing mandates. Or when: A US company with material European operations that needs Peppol e-invoicing and per-jurisdiction tax handling that US-centric AI-native rivals lack.
Stop guessing between Campfire and Light.
Our free assessment scores both — and every alternative — against your industry, scale, and requirements, with the reasoning shown.
Run the Fit Assessment →Keep comparing
Related comparisons
Methodology: both systems were researched independently across vendor documentation, published pricing, user-review platforms, and practitioner communities; every rating and cost anchor traces to the cited sources on the Campfire and Light profiles. This comparison is educational decision support, not legal, accounting, or implementation advice — verify current functionality and pricing in demos and quotes scripted around your own scenarios.