Specialized Tax Infrastructure for SaaS
Michelle Valentine, co-founder and CEO of Anrok, on the modularization of the SaaS finance stack
This is why a SaaS specific tax engine could wedge into a market that already had big incumbents. Legacy vendors like Avalara and Vertex were built to sit beside ERP, ecommerce, and point of sale systems across many industries, so software sellers often had to map subscription logic, product taxability, and local edge cases by hand. Anrok won by making recurring software billing the default case, not a custom setup project.
-
For a store, tax usually follows a simple flow, one item, one shipment, one return. For SaaS, invoices mutate over time through seat changes, usage charges, refunds, true ups, and multi year contracts, so tax has to recalculate inside billing in real time, not after the fact.
-
The incumbents earned their scale by serving the broad market. Avalara, founded in 2004, built thousands of integrations across ERP, ecommerce, marketplace, and point of sale systems. Vertex, founded in 1978, became the heavyweight for large companies running SAP or Oracle. That breadth also made them less opinionated for software specific workflows.
-
The competitive line is now between general tax layers and software native ones. Stripe Tax has expanded beyond pure Stripe payment flows, but the category still splits between embedded tax features for simpler merchants and dedicated tax systems for companies with multiple billing, payment, and ledger tools.
The market is heading toward more specialized tax infrastructure that plugs into the rest of the finance stack. As software pricing gets more usage based, more global, and more fragmented across channels, the winning products will be the ones that can watch nexus, calculate tax on changing invoices, and file automatically without forcing finance teams into ERP style implementation work.