Owning the bookkeeping customer workflow

The real bottleneck was not the ledger, it was the customer workflow wrapped around the ledger. For firms like Pilot and inDinero, the hard part was collecting missing receipts, asking founders how to classify messy transactions, tracking special rules for each customer, and turning that back and forth into a repeatable monthly close. QuickBooks already handled the accounting engine, so the bigger product gap was the operating layer that kept humans and customers aligned.

• Pilot was tightly coupled to QuickBooks, and customers could still log in to see their books there. That meant Pilot did not need to rebuild double entry accounting, reporting logic, and years of accounting rules. It could focus software effort on making bookkeepers faster and making the monthly process easier for customers.
  2 sacra 3 sacra 4 sacra
• The CRM layer in this context looked less like Salesforce and more like case management for bookkeeping. Pilot stored the handful of facts that made each customer unusual, routed questions through a shared support workflow, and tried to make it possible for any trained operator to pick up an account without losing context.
  2 sacra
• Bench was the counterexample. It used its own proprietary software stack instead of QuickBooks, but it sold that software only as part of a managed service, not as a stand alone accounting product. That shows how much easier it was to build workflow software for an in house team than to replace the broader accounting system of record for the market.
  1 sacra 5 sacra

Going forward, the winners in tech enabled bookkeeping are likely to keep the ledger underneath and compete on the layer above it, where data gets collected, exceptions get resolved, and new services get cross sold. As automation improves, the advantage shifts to whoever owns that customer workflow, because that is the piece that can expand from bookkeeping into tax, CFO work, and a broader finance operating system.