Scaling Needs Specialized Implementation Labor
Rillet
Rillet is choosing trust and correctness over pure software speed. Its CPA led onboarding means the hard part of growth is not just shipping product or closing deals, it is hiring enough people who can open a messy legacy ledger, map it into a new chart of accounts, migrate history, and get the first close right without breaking audit readiness. That creates a people capacity constraint, but it also makes the product much harder for lightweight software rivals to copy.
-
In bookkeeping and accounting, edge cases pile up fast. Checks, ACH payments, revenue contracts, and accruals often need business context that does not live cleanly in the source systems, which is why software alone still leaves a lot of work for trained humans who can interpret the facts and make the entry correctly.
-
Comparable companies show what this labor model does to scaling. Pilot built a human in the loop bookkeeping business to roughly 60% gross margins, but scaling still depended on building playbooks, routing complex customers to top operators, and hiring specialized talent outside engineering. Rillet is applying that same logic higher up the stack, with CPAs and ex auditors instead of general bookkeepers.
-
The partner motion helps offset that bottleneck. Alliances with EY and KPMG, plus implementation partners like Armanino, Wiss, and RSM, let Rillet add delivery capacity and trust without staffing every implementation internally. In ERP, that looks less like a self serve SaaS rollout and more like a services assisted system replacement.
Over time, the winning finance platforms will keep moving routine work into software, but the best ones will still wrap that software in expert implementation for the messy first mile. If Rillet keeps encoding CPA judgment into repeatable migration playbooks and partner led delivery, it can widen distribution without giving up the accuracy that makes controllers comfortable replacing NetSuite and legacy close workflows.