Christie Perez has spent 18 years in indirect tax. At Webflow, the website experience platform trusted by enterprise marketing teams and agencies, she runs the function largely on her own. Her discipline is monthly: pull every transaction from the billing system, tie it against the tax engine, and confirm that what Webflow collected matches what Webflow owes. When those two numbers agree, tax is a pass-through. When they don't, the difference comes out of Webflow's pocket.
That discipline is exactly where the previous setup broke down. When Chris joined last August, she inherited a stack that failed on both sides of the equation. The engine calculated tax on transactions that should never have been taxed, so customers were overcharged and the excess had to be remitted anyway. It missed subscription upgrades and downgrades entirely, so tax was collected on stale amounts. And when a transaction was recorded incorrectly, there was no way to correct it. The error just sat in the books, compounding month over month, with a support queue between Chris and the fix.
Louisiana made the gap physical. With localities the old system couldn't support, Chris built work papers by hand, chased down why the numbers wouldn't tie, and filed manually online. Every hour of that work existed to compensate for calculations she couldn't trust.
"There was a point where we paid out of pocket because we overpaid on tax."
Tax that comes out of your own pocket isn't a pass-through. It's an expense. Closing that gap is what Anrok is built for.
The switch
By November, Webflow was live on Anrok. Implementation ran without delays, and the fixes mapped directly to the failure point
Webflow bills through Stripe, and Anrok connects natively, so the transaction record Chris reconciles against is the same record the engine calculates from. Subscription changes flow through as they happen instead of getting lost between systems. In nine months, her monthly analysis hasn't surfaced a discrepancy between the two. Corrections that used to be impossible now happen directly in the platform, which matters less because errors are rare and more because an error caught in month one no longer compounds into month six. And the returns the old vendor couldn't file at all, Anrok files and remits, Louisiana localities included. The hand-built work papers are gone.
"Anrok shaved off a good two to three days a month."
Two to three days is the visible saving. The invisible one is what those days used to exist for: manual verification of numbers the old system got wrong.
What the analysis finds now
Chris still runs the same month-end reconciliation she always has. She didn't relax the discipline because the vendor changed. The difference is what the analysis finds.
"The analysis we've done each month since putting Anrok in place shows very little coming out of pocket."
The one exception proved the point. Early on, the team left certain reports unlocked on returns Anrok doesn't file. That created a credit issue on non-US filings and a small amount of avoidable out-of-pocket cost. What matters is how it resolved: the monthly analysis caught it, the team traced it to a process gap rather than a calculation error, they locked the reports, and the tax exposure went back toward zero. Accuracy is not a single feature. It's the transaction data, the calculation, and the reconciliation habit all agreeing with each other, and a system transparent enough that when they don't, you can see exactly why. When something looks off, a quick Slack to the Anrok team gets an answer immediately, not a ticket number.
Everywhere Webflow sells
Webflow sells globally, and new markets used to be their own projects, each one a fresh chance for tax to leak back into the expense line: a new vendor to evaluate, a new registration process, new returns to figure out how to file. Now expanding into a new country is a configuration exercise. Chris turns it on in the testing environment, engineering verifies the calculations, and it goes live in production. Same engine, same reconciliation, same monthly analysis covering the new market alongside the old ones, across 150+ countries. Webflow is now moving its non-US filings onto Anrok to push the out-of-pocket number down further.
Where this goes
Chris is one person running indirect tax for a global platform, and she's candid about how she scales. She uses AI daily, and is currently onboarding to the Anrok Atlas beta, and she already knows her first ask: reconcile the month, Stripe against Anrok, without building a spreadsheet. The monthly discipline stays. The spreadsheets go.
$0 out of pocket isn't a promise on a page. It's what the infrastructure makes possible when the transactions are right underneath. Built for what's next.
.png)
.png)
