.png)
.jpg)
Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Driving Revenue Growth Through Strategic Pricing in Tax Management Applications
Indirect tax software used to be bought as a defensive tool. A company added it after entering enough states, facing enough filing deadlines, or discovering that tax logic had become too complex for spreadsheets. That framing is now too narrow. Since the U.S. Supreme Court’s June 21, 2018 South Dakota v. Wayfair decision removed the physical-presence rule that had constrained many state collection obligations, tax complexity has moved closer to the transaction itself: checkout, billing, ERP, marketplace reporting, exemption handling, and return filing.8
For tax-management vendors, the commercial consequence is clear. Pricing no longer merely recovers the cost of a calculation engine. It determines whether customers see growth as a reason to expand the relationship or a reason to control usage, delay launches, and seek concessions at renewal. The category spans different needs, but this article focuses on B2B indirect-tax applications that calculate tax, monitor obligations, manage certificates, prepare returns, and support filing.
Monetizely’s position is that an annual subscription based primarily on the customer’s sales revenue passing through the tax engine should be the core meter for established indirect-tax applications. Packages should reflect the scope of compliance work, and separate modules should capture added workflow value. Transaction fees belong at the self-service edge of the market, not at the center of a growth strategy for multijurisdiction customers.
Indirect tax pricing has become a growth lever, not a back-office setting
A tax application earns its value by allowing the customer to transact, enter markets, close the books, and withstand scrutiny with less manual work. None of those benefits rises neatly with the number of API calls. A retailer may generate extra calls through retries, testing, address corrections, multiple carts, or a new ecommerce integration without creating a proportionate increase in tax value.
The buyer sees the opposite pattern. When annual sales rise from $80 million to $125 million, the tax team faces a larger exposure, finance needs more reliable reporting, and leadership needs confidence that growth will not produce unmanaged compliance risk. Revenue growth is visible to the CFO, budgetable before the year begins, and tied to the commercial event that makes tax management more valuable.
Monetizely’s 5-Step Pricing Framework puts that sequence in the right order. It begins with goals and segmentation, because a company trying to maximize adoption should not price like one trying to expand enterprise ARR. It then moves through packaging, pricing metric, price points, and operationalization. The order matters: a rate card cannot repair a package that mixes incompatible buyers, and a clever meter cannot survive if billing systems cannot explain the invoice. As discussed in Monetizing Agentic AI, the framework treats price as the final expression of a set of business choices, rather than as a number to be adjusted in isolation.
Tax software vendors often begin at Step 4. They benchmark a rival’s rate, add a discount band, and ask sales to defend it. Revenue growth starts earlier, with a decision about which customer expansion should produce more recurring revenue and which usage should remain free because it makes the product easier to adopt.
Six market leaders reveal a meter problem, not a price problem
The category’s leading vendors show that tax-management pricing is already moving across three distinct anchors: transactions, jurisdictions, and customer revenue. The differences are not cosmetic. Each meter asks the buyer to accept a different relationship between growth and spend.
Exhibit 1 - Public pricing structures among major indirect-tax vendors
Sources and public prices were checked September 4, 2026. See footnotes 8-13. (avalara.com)
The table points to a central fact: the industry does not suffer from a shortage of price points. It suffers from overreliance on meters that can diverge from the customer’s understanding of value.
Transaction pricing is attractive because it is easy to meter. Stripe can count a taxable transaction. TaxJar can count orders. Avalara can count calculation activity. Yet ease for the vendor does not settle the question for the buyer. A customer does not want to restrict retries, suppress testing, or postpone a new channel because the tax engine has become more expensive to use.
Vertex’s public filings are especially instructive. Its 2025 subscription revenue grew 12.8% to $639.7 million, with expansion from existing customers through cross-selling, expanded use, and price increases contributing to that growth.6 The broader lesson is not that every tax vendor should copy Vertex’s rate card. It is that installed-base growth becomes more durable when the price rises alongside a customer’s business, not alongside incidental system activity.
Sales volume is the strongest anchor for recurring tax value
A primary meter must pass four tests. It should track the value a customer receives, support predictable budgeting, encourage productive use of the product, and remain simple enough to administer. Annual sales revenue processed through the tax application performs better than transactions, seats, or jurisdictions on the complete set.
Exhibit 2 - How the main tax-software meters perform
Scoring reflects Monetizely’s assessment for established B2B indirect-tax applications.
The implication is decisive: annual sales bands should set the recurring subscription, while jurisdictions and product modules should shape the package around that subscription.
An annual sales band tells a buyer, “As your business expands, the protection and automation you receive become more valuable.” A transaction meter says something very different: “Every time your systems ask us for help, your cost may rise.” The first statement supports adoption. The second can create defensive behavior.
Jurisdiction count has a legitimate role, but it should usually govern package capacity rather than serve as the main meter. A business filing in California, New York, Texas, and the United Kingdom has more work to manage than a single-state seller. Yet a strict per-market fee can penalize sensible expansion even when total sales remain flat. A package can include a defined number of active markets and offer clear expansion steps without making every new registration feel like a new tax on growth.
Seats perform worst as the primary meter. Tax applications are often used by a small tax team while creating value for ecommerce, finance, operations, billing, and legal. Charging only for named users leaves the vendor underpriced precisely when the application becomes embedded in the customer’s operating model.
Packages must price distinct compliance jobs rather than feature piles
Pricing metric and packaging solve different problems. The metric answers what customers pay in proportion to. Packaging answers what they receive. Confusing the two creates the familiar tax-software problem of a broad top-tier plan that sales discounts heavily because it contains too much for one buyer and too little for another.
A growing domestic seller does not need the same offer as a global manufacturer, even if both have similar annual revenue. The first may need accurate calculation, nexus monitoring, and basic filing. The second may need exemption certificates, ERP integrations, tax data controls, global VAT support, e-invoicing, returns outsourcing, and audit-ready reporting.
The package design should therefore separate three customer jobs:
- Tax determination: calculate the right tax at the point of sale or purchase.
- Compliance execution: monitor obligations, prepare returns, file, remit, and manage notices.
- Control and scale: manage certificates, multi-entity structures, global jurisdictions, advanced integrations, and audit evidence.
A revenue band should determine the commercial level of commitment. The customer’s operational needs should determine which of these jobs enters the contract. That structure lets a vendor raise ACV through real expansion rather than forcing an early-stage customer to buy features it will not use.
Exhibit 3 - Common pricing failures mapped to the 5-Step Pricing Framework
The framework sequence places packaging before meter selection and operationalization after rate setting, because each decision constrains the next.
The practical result is a clearer commercial ladder. Customers buy more when they add compliance work, integration depth, or business scale. They do not pay more simply because the product has become part of their normal operating flow.
AI agents will improve the offer without displacing accountable review
AI is entering tax management, particularly in research, exception handling, return preparation, and compliance review. Thomson Reuters, for example, positions ONESOURCE Indirect Compliance powered by CoCounsel as combining tax content, expert insight, and agentic AI for indirect-tax workflows.7
That development does not change the primary pricing recommendation. It changes what vendors can package and how they should protect margin. Most tax agents will not independently own the final compliance decision. A tax professional, controller, or outside adviser will still review material judgments, approve filings, and answer for the outcome.
The Agentic Monetization Spectrum, or AMS, helps make that distinction. AMS assesses an agent on three dimensions: zero-human ability, meaning how much work the agent can complete without human involvement; operational domain, meaning whether it handles a narrow task, a full function, or several functions; and output/cost ratio, meaning how sharply customer value rises relative to the cost of delivering the output. Greater autonomy, a broader domain, and a steeper output-to-cost curve move pricing away from seats and toward output or outcomes.
Exhibit 4 - AMS score for an indirect-tax compliance agent
| AMS dimension | Score | Tax-management interpretation | Pricing implication |
|---|---|---|---|
| Zero-human ability | Medium | The agent can research rules, prepare work, flag exceptions, and draft returns, but accountable staff still review and approve material filings. | Do not rely on pure outcome pricing for the core subscription. |
| Operational domain | Medium | The agent can support an end-to-end compliance workflow inside tax, but it does not replace finance, legal, and operating teams. | Package AI-supported compliance as a higher workflow level or module. |
| Output/cost ratio | Inflecting | A well-designed agent can remove substantial repetitive work while inference and expert-review costs remain meaningful. | Use included capacity and cost controls, but retain the annual sales band as the primary meter. |
The AMS score reinforces Monetizely’s view. Tax agents should raise willingness to pay by improving the compliance offer, not push vendors into billing customers per prompt, token, or purported filing outcome. Customers are buying reliable tax operations. The AI component is valuable when it shortens review cycles and catches exceptions, but it remains part of a governed workflow.
A revenue-based subscription fails if the vendor cannot define revenue cleanly. “Annual sales” must mean the same thing in the contract, CRM, billing system, customer-success playbook, and renewal model.
The operating rules should be explicit:
Operationalization is not administrative cleanup. Monetizely’s guidance notes that implementing a pricing model often requires three to five times the effort needed to design it, because systems must connect entitlements, usage data, contracts, invoices, and customer communication.
Exhibit 5 - How different meters respond to the same customer growth path
| Customer condition | Year 1 | Year 2 | Year 3 | What each meter would do |
|---|---|---|---|---|
| Annual sales through the tax engine | $80M | $100M | $125M | A revenue-band model creates a planned step-up when the customer crosses a stated annual-sales threshold. |
| Tax-calculation traffic | 1.0M calls | 2.0M calls | 2.5M calls | A transaction model doubles the bill in Year 2 even though annual sales rise only 25%. |
| Active tax markets | 8 | 8 | 12 | A market allowance remains stable through Year 2 and expands when the customer enters new jurisdictions. |
| Tax-team users | 5 | 5 | 6 | A seat model barely changes despite sharply higher business exposure and system reliance. |
The revenue-band model produces the most constructive commercial conversation: the vendor earns more when the customer’s business reaches a larger scale, while the customer can predict the next commitment before signing.
Revenue growth requires five decisions beyond the price book
Choose the customer expansion event the company wants to monetize. For indirect tax, make annual sales through the application that event, rather than system calls or named users.
Build the product roadmap around attachable compliance work. Measure demand for filing, certificate management, global support, e-invoicing, and advanced integrations separately. Fund the modules that repeatedly increase ACV and retention.
Migrate the installed base deliberately. Keep existing transaction-priced contracts intact through their committed terms, offer revenue-band pricing on new deals, and use renewal discussions to move customers onto the new structure without retroactive surprises.
Treat price exceptions as strategic decisions. Require a single approval path for nonstandard discounts, free modules, expanded market allowances, and custom true-up terms. Otherwise, the field will quietly undo the rate card.
Measure expansion quality, not only expansion volume. Track whether upsell comes from annual-sales-band movement, module adoption, new markets, or discount reversal. Revenue that depends on disputed overages is not durable growth.
Footnotes
- Monetizing Agentic AI. Accessed September 4, 2026. https://www.amazon.com/Monetizing-Agentic-AI-Handbook-Transformation/dp/B0H7Z13VKJ/
- Avalara, “AvaTax: Sales Tax Calculation Software” and “Pricing Information.” Accessed September 4, 2026. https://www.avalara.com/us/en/products/calculations.html https://www.avalara.com/us/en/products/pricing.html
- TaxJar, “How Much Does TaxJar Cost?” Last updated June 12, 2026. https://support.taxjar.com/article/139-how-much-does-taxjar-cost
- Stripe, “Stripe Tax Pricing.” Accessed September 4, 2026. https://stripe.com/tax/pricing
- Anrok, “Pricing.” Accessed September 4, 2026. https://www.anrok.com/pricing
- Vertex, Inc., Form 10-K for the year ended December 31, 2025, filed February 24, 2026. https://www.sec.gov/Archives/edgar/data/1806837/000110465926019165/verx-20251231x10k.htm
- Thomson Reuters, “ONESOURCE Indirect Tax Determination” and “ONESOURCE Indirect Compliance powered by CoCounsel.” Accessed September 4, 2026. https://tax.thomsonreuters.com/en/products/onesource-determination https://europe.thomsonreuters.com/solutions/indirect-tax/compliance
- Supreme Court of the United States, South Dakota v. Wayfair, Inc., decided June 21, 2018. https://www.supremecourt.gov/opinions/17pdf/17-494_j4el.pdf