Incumbents Undermine Rillet's Migration Case
Rillet
The real threat is not that incumbents copy Rillet’s architecture, it is that they remove just enough pain inside the controller’s existing system that migration stops feeling urgent. For most finance teams, buying new close automation inside NetSuite or Intacct is easier than replacing the general ledger, retraining the team, rebuilding controls, and reconnecting every upstream system. That leaves Rillet needing to win on day to day speed that is obvious enough to justify a full swap, not just a cleaner technical design.
-
NetSuite and Intacct are already pushing into the exact pain point Rillet uses to open deals. NetSuite now highlights AI based close monitoring, reconciliation assignment help, and generative AI for bank matching, while Sage Intacct markets Close Automation with a Close Assistant, subledger reconciliation help, and AI generated variance explanations.
-
This is the same wedge other finance tools use against legacy systems. Teampay grew by sitting on top of ERP and policy workflows rather than replacing the ledger, and even large customers often layer new workflow software beside legacy finance systems first, then move more activity over time if the new tool proves itself.
-
Controllers usually tolerate ugly back end systems if month end work becomes manageable. Research across bookkeeping and finance tools shows the hard part is not just storing debits and credits, it is matching messy data from banks, billing, payroll, and contracts. If incumbents make that exception work faster, many customers will postpone ledger migration for years.
Going forward, the market is likely to split between workflow overlays that make old ERPs good enough, and full stack replacements that are dramatically better from first transaction to close. Rillet’s path is to make the second category feel unmistakably superior, so finance teams see migration as a leap in operating speed, not an optional clean up project.