Kaprin
All insightsSaaS Tax Diagnostics

When to Replace a SaaS Vendor: A Seat Tax Diagnostic

By Kaprin Engineering 6 min read

This is a checklist for CFOs and CTOs who suspect they're overpaying for a SaaS product but don't want to replace it on instinct. If a renewal is coming and the invoice grows every time you hire, run the diagnostic below before you sign.

Our earlier post on the SaaS seat tax and build versus buy makes the general case. This one is the working tool: four questions, a keep-or-replace rule and arithmetic you can redo with your own numbers. We practice forward deployed engineering (FDE), where senior engineers embed in your team and build inside your cloud, so we've seen both outcomes. Sometimes the right answer is to renew.

What is the SaaS seat tax diagnostic?

It's four questions about one vendor: how much of the product you use, how its pricing behaves as you grow, who controls your data and your agents' access to it, and how the spend shows up in your accounts. The answers feed a simple rule for keeping or replacing the vendor.

Run it per product, since one vendor can supply a commodity module you should keep and a workflow module you should replace. Work from usage logs and invoices. Allow a few hours of someone's time. If the data is hard to find, that's a finding in itself.

Question 1: What share of the features do you actually use?

List every module, feature and integration you pay for, then mark the ones used in the last 90 days by more than a handful of people. If the workflow that matters to your business touches a small share of the product, you are renting a large platform to run a narrow application.

Describe the workflow itself and skip the category. "We use the CRM" means little. "We use contact records, one pipeline, two reports and a webhook" is a diagnosis. Count the work-arounds too: spreadsheets and manual re-entry that exist because the product's data model doesn't match your process. Those hours belong in the cost.

Question 2: Does the pricing penalize headcount growth?

Per-seat pricing ties cost to the number of people with logins, whatever value they get. If you plan to hire, or to give more contractors and partners access, the invoice rises in step. Teams under that pressure ration seats or share logins.

Check the contract for four things: seat definition (named or concurrent), minimums, tier thresholds that trigger a higher per-seat rate, and the notice period before renewal. Then model your hiring plan against it. Here is illustrative arithmetic, with an assumed price and no real vendor in mind:

Illustrative scenario (assumed numbers)UsersAssumed price per user per monthAnnual cost
Today150$100$180,000
After hiring 30 more180$100$216,000
Added cost of growth30$100$36,000 per year, every year

150 users at an assumed $100 per user per month comes to $180,000 a year (150 x $100 x 12). Thirty more users add $36,000 a year. The prices are made up for the example, so swap in your own contract figures and any increases the contract actually specifies.

Question 3: Who controls your data and your agents' API access?

If your data sits behind the vendor's schema and API limits, any AI agent you build against it inherits those limits. Check the rate limits, the cost of higher tiers, what you can bulk-export, and whether the vendor restricts automated or agent access in its terms.

This question matters more than it did a few years ago. An agent that reads and writes records at machine speed will hit a request cap that a human team never noticed. Four things to ask the vendor:

  • What are the documented API rate limits, and what do they cost to raise?
  • Can you export all of your data in a usable format, on demand, without a services fee?
  • Do the terms permit automated agents to act on your account?
  • If the vendor changes pricing or terms, how long would it take you to leave?

Owned software in your own cloud account removes these limits, since the data sits in your database and the only constraints are the ones you set. That's the logic behind our SaaS replacement work: you own 100% of the code, database and IP.

Question 4: What does the spend look like on your balance sheet?

Subscription fees are generally an operating expense with no residual asset. Internal-use software can sometimes be capitalized when specific accounting criteria are met, which changes how the spend appears. This depends on your accounting framework and jurisdiction, so involve your finance team before assuming a treatment.

Look past the accounting label and ask what you hold after three years of paying. With a subscription you hold nothing, and if you stop paying the capability goes away. With owned software you hold the code and the database, and you can change either. Our CFO guide to renting versus capitalizing software covers the accounting questions in more depth.

When should you keep a SaaS vendor and when should you replace it?

Keep a vendor when the product is a commodity, regulated, security-critical or deeply embedded in your integrations. Replace it when your workflow uses a small share of the features, per-seat pricing punishes your growth, or API limits block your agents. When both sets apply, split the product and replace only the workflow layer.

SignalKeep the vendorReplace with owned software
Product typeCommodity with strong alternatives (email, chat)Your own workflow, rules or data model sit at the center
RegulationThe vendor maintains compliance you would otherwise carryYour compliance needs are specific and you must evidence them yourself
Security roleIdentity management and payment railsInternal tools with contained data and clear access rules
IntegrationsDozens of integrations your teams depend onFew integrations, and you control the ones that matter
Feature useYou use most of what you pay forYou use a small share of the product
Pricing shapeFlat or usage-based and predictablePer-seat, and your headcount is growing
Agents and APILimits comfortably cover your agentsRate limits or terms block the automation you plan

Replacing isn't free. Owned software has an upfront build, hosting and a maintenance burden, and it needs an owner. If you can't name who will maintain it, don't replace the vendor. A good engagement includes handoff by design, so your team can run the result.

How do you run the diagnostic in one afternoon?

Gather the invoices and usage data, answer the four questions, and score each product against the keep and replace signals. The goal is a shortlist of one or two products worth a closer cost comparison. It won't give you a final decision.

  1. Pull the last 12 months of invoices and the current contract for one product.
  2. Export 90 days of usage by feature and by user.
  3. List the five workflows your business cannot run without, and map each to features used.
  4. Mark each row of the table above as keep or replace for this product.
  5. Model three years of cost at your planned headcount, using your real prices, then compare with a build estimate and ongoing hosting and maintenance.
  6. Check the data export and API terms in writing.

If more rows say replace than keep, the product is a candidate. For an example of owned software running a core business workflow, read how Solidex built its lead distribution engine. If you'd like a second opinion on a specific renewal, you can talk to us and we'll tell you plainly if the answer is to keep the vendor.

Questions readers ask

What is the SaaS seat tax?

It is the recurring cost of per-user SaaS pricing, which rises each time you add people whether or not they use more of the product. Fast-growing teams that use a narrow slice of a broad platform feel it most.

When should a company keep its SaaS vendor?

Keep the vendor when the software is a commodity with strong alternatives, when the vendor maintains regulatory or compliance obligations for you, when it is security-critical, or when your workflow depends on many integrations. Building in those cases usually adds risk and no advantage.

How do I know whether my team uses enough of a SaaS product to justify the price?

Start by listing every module and feature you pay for, then check usage logs for the last 90 days. If the workflow that matters to your business touches only a few of them, you are paying for a whole platform to run a narrow application.

Does owned software always cost less than SaaS?

Only sometimes. Owned software has an upfront build cost plus hosting and maintenance, and it wins when the license fees you avoid and the workflow gains add up to more than those costs over a realistic horizon. That is why the diagnostic has keep rules as well as replace rules, and why you should run your own numbers.

Can custom software be treated as a capital asset?

Sometimes. Under many accounting frameworks, internal-use software development costs can be capitalized when specific criteria are met, whereas subscription fees are generally operating expenses. Treatment depends on your jurisdiction and standards, so confirm it with your finance team and auditors before relying on it.

Bring us the broken prototype, the SaaS bill, or the manual process

Tell us what is stuck. We reply within 24 hours with a scoped plan, a fixed timeline and the one number we will move.

More insights

FDE = forward deployed engineering. Strict NDA protection. Senior architect review.