Key Takeaways
- These are three different products, not three versions of 'better NetSuite' — Campfire is the deepest-AI bet — a proprietary Large Accounting Model trained exclusively on accounting data (95%+ accuracy on reconciliations). Rillet is the SaaS-precision bet — native ARR/MRR/NRR from the general ledger, purpose-built integration stack. DualEntry is the speed-and-breadth bet — 24-hour go-live claim, strongest multi-entity documentation. They do not compete head-to-head for the same buyer.
- Altis diligence data puts DualEntry behind Campfire and Rillet on SaaS automation — The Altis report (free at altis.vc/reports/dualentry) finds DualEntry trailing on SaaS-specific modules. Some evaluators report automation depth below what was marketed. The close-time reduction (15-20 days to 8-10 days) is documented, but the AI architecture claim is less differentiated than Campfire's LAM.
- The permanent moat is the trained model, not the migration tooling — All three platforms benefit from the same dynamic: AI-assisted migration has cut the labor cost of moving from NetSuite by roughly half, opening a switching window. The durable advantage for whichever platform wins comes from the AI model trained on customer-specific transaction history over 24+ months — not from the migration convenience itself.
- ICP-fit is the decision criterion, not a ranking — SaaS companies with standard billing stacks: Rillet. Companies where close-cycle automation depth matters most: Campfire. Multi-entity mid-market companies wanting fastest modern ERP path: DualEntry. The platforms are not alternatives; they are targeting different primary buyers.
Three bets on the same window — different execution theses
Three tier-one VC syndicates made concurrent bets on AI-native ERP in 2025: Lightspeed and Khosla into DualEntry ($100M+ Series A), Accel and Ribbit into Campfire ($100M total), a16z and ICONIQ into Rillet ($108.5M across two rounds, ~$500M valuation). The shared thesis is that AI-assisted migration has compressed the switching cost protecting NetSuite's $4 billion mid-market franchise. The disagreement is on which buyer profile moves first and which AI architecture sustains the advantage after the migration window closes.
DualEntry is betting on deployment speed across a broad mid-market. Campfire is betting on close-cycle automation depth for SaaS. Rillet is betting that native SaaS metrics calculated directly from the general ledger become the standard. The migration window is the same; the product thesis — and the customer who validates it — is not.
AI architecture: the substantive difference
Most "AI ERP" claims in the market are query-layer enhancements on top of legacy databases — natural language interfaces that translate questions into SQL. Architecture-native AI means the model is in the data layer: journal entries are categorized, reconciled, and anomalies flagged before a human reviews them. The AI is acting on data as it flows in, not responding to queries about it.
Campfire's LAM is the most credible architecture-native claim. The Large Accounting Model is trained exclusively on accounting data — the first domain-specific model in the category — and achieves over 95% accuracy on reconciliations and variance analysis. LAM acts on records directly, and every action carries audit-ready attribution. Customers report five-times faster close cycles; 144 days reclaimed annually is the stated figure.
Rillet's Aura AI operates at the GL level: journal entries are automated natively, flux analysis and accruals are generated without manual triggers. The 200+ native integrations to the SaaS finance stack mean the model's data inputs (Stripe events, payroll runs, spend data) arrive clean and structured rather than requiring import and transformation. The platform's specific differentiation — native SaaS metrics from the GL — is an architectural decision, not a feature layer.
The Altis diligence data (altis.vc/reports/dualentry) finds DualEntry's automation depth trailing Campfire and Rillet on SaaS-specific workflows — bank matching, OCR, and transaction categorization are present, but the SaaS-native coverage gap is documented. The 13,000+ integrations and 24-hour go-live claim are the real differentiators; the AI architecture is not the reason to choose DualEntry.
Feature comparison
DualEntry vs Campfire vs Rillet
| Feature | DualEntry | Campfire | Rillet |
|---|---|---|---|
| AI architecture | |||
| AI model type | Generalist AI with accounting-specific tuning; 13,000+ integration points for automated data flows | LAM (Large Accounting Model) — proprietary model trained exclusively on accounting data, 95%+ accuracy on reconciliations | Aura AI — conversational access to financial data + automated workflows for flux analysis and accruals |
| Model in data layer (architecture-native) | AI automation on key workflows; some features are query-layer rather than data-layer native | LAM acts on records directly as they flow in — the strongest architecture-native claim in the category | Aura AI operates at the GL level; journal entries automated natively, not via query |
| Anomaly detection & auto-categorization | AI flags misclassifications, duplicate entries, outliers; pattern-based matching rules | Built into LAM — variance analysis and anomaly detection are first-class model outputs | Real-time anomaly flagging; Aura generates accruals and flags variances automatically |
| Close automation | |||
| Documented close-time reduction | Close times reported falling from 15-20 days to 8-10 days (Altis diligence data) | 5× faster close cycles; 144 days reclaimed annually per customer (vendor-stated, documented in customer cases) | Real-time close capability; customers report moving from 15+ day close to under 10 days |
| Reconciliation automation | AI-assisted bank matching, intercompany reconciliation, custom matching rule suggestions | LAM handles reconciliations at 95%+ accuracy; audit-ready attribution for every LAM action | Automated reconciliations with native SaaS billing sources (Stripe, Brex, Ramp) as primary inputs |
| Flux analysis | Available; depth of automation relative to Campfire and Rillet is lower per Altis evaluation | Built into LAM — variance analysis is a core model output, not a report | Aura AI generates flux commentary automatically; included in close management workflow |
| Revenue recognition (ASC 606) | Full RevRec module — one of DualEntry's documented strengths | Revenue automation is a core Campfire product; real-time recognition as billing events arrive | Automated revenue schedules across pricing models; generated and booked without manual journal entries |
| SaaS fit | |||
| Native SaaS metrics (ARR / MRR / NRR) | Available; requires configuration — not first-class GL outputs | Supported; Campfire's primary differentiation is close automation, not SaaS metric calculation | ARR, MRR, NRR calculated directly from the general ledger — no configuration, no BI layer required |
| Native SaaS stack integrations | Stripe, Salesforce, and 13,000+ total integrations — breadth is a DualEntry differentiator | Stripe, HubSpot, Rippling, and billing/payroll stack; growing ecosystem | 200+ native endpoints: Stripe, Ramp, Brex, Rippling, Salesforce, HubSpot — purpose-built for SaaS stack |
| SaaS-specific customer base | Serves SaaS and non-SaaS; Altis notes SaaS module depth lags behind Campfire and Rillet | PostHog, Replit, Decagon, Klarity, CloudZero — SaaS-dominant reference customer set | Windsurf, Bitwarden, Decagon — tightly SaaS-focused ICP; 200+ customers, 200+ ARR doubled post-Series B |
| Multi-entity & scale | |||
| Multi-entity consolidation | Documented strength — multi-entity consolidation is a stated DualEntry differentiator | Supported; less documented than DualEntry at multi-subsidiary complexity | Supported; primary design is for single-entity SaaS companies; complex multi-entity is less documented |
| Multi-currency | Full multi-currency support; intercompany eliminations documented | Multi-currency supported; global customers on six continents per vendor | Multi-currency supported; native for globally distributed SaaS customer base |
| Upper market readiness | Claims NYSE-listed customers; enterprise feature maturity still developing vs. NetSuite | 10× YoY revenue growth; aimed at IPO readiness; enterprise audit trail capabilities | ~$500M valuation; 200+ customers; enterprise feature maturity an open question |
| Implementation & cost | |||
| Implementation time | 24-hour go-live claim (greenfield, clean data); faster than any legacy ERP by design | Days to weeks for standard implementations; significantly faster than legacy ERP | Days to weeks for SaaS companies with standard billing stacks |
| Pricing model | Free preview tier available; SaaS subscription pricing — exact rates not publicly listed | SaaS subscription; no implementation consulting requirement for standard use cases | SaaS subscription; pricing not publicly listed; Sequoia/a16z-backed, no implementation fee model |
| Funding / runway | $100M+ (Lightspeed, Khosla, GV, Contrary, Vesey) — Oct 2025 Series A launch from stealth | $100M total ($35M Series A + $65M Series B, Accel + Ribbit) — 10× YoY revenue | $108.5M total ($25M Sequoia + $70M a16z + ICONIQ) — ~$500M valuation, Aug 2025 |
ICP fit: the actual decision criteria
Campfire is the strongest fit when close-cycle automation depth is the primary criterion — finance teams whose biggest constraint is reconciliation, categorization, and flux analysis, and who need the best-documented AI architecture on those specific tasks. Best fit: $10–100M SaaS companies with complex billing stacks where the majority of close-cycle time is rote work. PostHog and Replit are the right reference customer profile.
Rillet is purpose-built for SaaS companies that want native ARR/MRR/NRR as first-class GL outputs rather than configured dashboards. The 200 native integrations to the SaaS finance stack (Stripe, Ramp, Brex, Rippling, Salesforce, HubSpot) mean the platform was designed around the existing stack, not adapted to it. Best fit: $5–200M ARR SaaS companies with a standard billing and payroll infrastructure. Windsurf and Bitwarden are the reference customer profile.
DualEntry is the strongest fit for multi-entity consolidation requirements or greenfield mid-market evaluations where deployment speed and integration breadth outweigh SaaS-native automation depth. The 24-hour go-live claim and 13,000+ integration breadth are genuinely differentiated at that use case, even where the AI architecture lags Campfire and Rillet on SaaS-specific workflows. Best fit: $10–500M mid-market companies — multi-entity structures, non-SaaS verticals, or companies wanting the fastest path to a modern ERP without a SaaS-optimization requirement.
None of these platforms replace NetSuite for a $300M+ multi-entity enterprise with 15 years of configuration baked in. The relevant buyer is the company currently evaluating NetSuite, or currently on it for under three years, with a finance team still running a 15-day manual close.
The secondary moat: what matters after the migration window
The same AI-migration tooling that makes it easy to switch from NetSuite also makes it easier to switch away from any of these platforms after year two. The permanent lock-in is not migration convenience — it is the AI model trained on customer-specific transaction history over time. Campfire's LAM, after processing 24 months of a company's data, has learned that company's specific vendor payment patterns, revenue recognition edge cases, and intercompany quirks. That trained institutional memory is the moat that outlasts the migration window.
Campfire has the clearest path to that moat today: the LAM claim is explicit, documented, and customer-verified. Rillet's 200+ native integrations create a different kind of lock-in — the platform becomes the authoritative data layer for the entire SaaS finance stack, making re-migration structurally expensive even before model personalization compounds. DualEntry has not published an equivalent trained-model differentiation claim; its moat rests on integration breadth and multi-entity depth rather than proprietary model advantage.
Which AI-native ERP is best for a SaaS company in 2026?
Rillet is the most purpose-built for SaaS: native ARR, MRR, and NRR calculated directly from the general ledger (no configuration required), 200+ native integrations to the standard SaaS finance stack (Stripe, Ramp, Brex, Rippling, Salesforce, HubSpot), and a reference customer set (Windsurf, Bitwarden, Decagon) that maps exactly to the SaaS CFO's peer group. Campfire is the close second, with better-documented AI automation depth. DualEntry trails on SaaS-specific modules per the Altis diligence data.
Is DualEntry's 24-hour deployment claim real?
Real for greenfield implementations with clean data and a standard billing stack. For companies migrating from a multi-year NetSuite instance with custom modules and complex revenue recognition, '24 hours' is shorthand for 'dramatically faster than NetSuite's 6-18 month implementation' rather than a wall-clock guarantee. The Altis diligence report is more measured: close times falling from 15-20 days to 8-10 days, which is documented automation value independent of the go-live claim.
What is Campfire's LAM and how does it differ from DualEntry's AI?
LAM (Large Accounting Model) is a proprietary model Campfire built from the ground up, trained exclusively on accounting data. It achieves over 95% accuracy on reconciliations and variance analysis — the first domain-specific model in the ERP category. The architectural distinction: LAM acts on accounting records directly as they flow into the system, rather than responding to user queries. DualEntry's AI is more broadly tuned across general-purpose and accounting-specific use cases, with lower documented accuracy on the specific reconciliation tasks LAM targets.
Should we move from NetSuite to any of these platforms in 2026?
Evaluate against your rote-work fraction first. If more than 60% of your finance team's close cycle is manual categorization, matching, and reconciliation, the AI-native platforms are removing a material operational cost. If your close is already judgment-heavy, you are buying a cleaner interface rather than compressing rote work. Run a three-day parallel pilot against your last real month-end close — that separates what a vendor claims from what the automation delivers against your specific workload. NetSuite is not broken; it is manual in specific ways these platforms have targeted precisely.
Will NetSuite's AI features close the gap with these platforms?
NetSuite is shipping AI features under NetSuite Next: natural language reporting, AI-assisted data entry, automated reconciliation suggestions. The architectural gap is harder to close — NetSuite's data layer is a legacy relational database, and AI features sit on top of it rather than inside it. Moving AI from the query layer to the data layer is a migration for a platform running 40,000+ companies. Whether that gap closes before the entrants reach enterprise feature maturity is the open timing question — and the bet $313M of VC capital is taking on the wrong side of.
Ready to Find the Right AI Tools?
Browse our data-driven rankings to find the best AI tools for your team.