Ramp AI Flywheel Replaces Microtasks

Diving deeper into

Geoff Charles, VP of Product at Ramp, on Ramp's AI flywheel

Interview
What is more likely to happen in the near term is the elimination of low-cost services that high-cost services use, like mechanical turk based services.
Analyzed 4 sources

The first margins AI takes are the hidden labor margins inside service businesses, not the expert layer customers actually pay to trust. In finance workflows, that means receipt reading, contract parsing, expense coding, and other micro tasks can shift from offshore ops queues and Mechanical Turk style workforces into software. Ramp benefits because it sits at the source of these documents and transactions, so cheaper interpretation directly expands what it can automate inside spend management and procurement.

  • Ramp’s concrete example is document understanding. Before LLMs, vendors like Scale, Veryfi, and Ocrolus used OCR plus large human labeling operations to turn messy receipts and invoices into structured fields. Ramp argues LLMs can now reach similar accuracy for many tasks at a fraction of the cost.
  • This is the same squeeze seen in bookkeeping. Pilot built a strong business as human middleware between source systems and QuickBooks, with about $43M ARR and 60% gross margins in 2023, but that model is vulnerable as AI gets better at the repetitive reconciliation and classification work underneath the service.
  • The important distinction is that low skill annotation gets automated first, while high skill review persists. Scale’s 2023 surge to $760M ARR came from RLHF and labeling demand, yet the business also faces the risk that models get closer to human parity on labeling tasks. That is why the value pool shifts upward, from raw labor supply to workflow owners with proprietary data and distribution.

The next step is a finance stack where software handles most first pass judgment and humans only step in on edge cases, approvals, and strategy. That favors platforms like Ramp that already capture the transaction, the receipt, the invoice, and the contract in one workflow, because as the low end service layer disappears, more of the economics consolidate into the system that owns the data and triggers the action.