Every new hire raises your software bill
TL;DR
Per-seat pricing ties your software bill to your headcount, so growth makes it bigger by design.
Median SaaS spend is now $9,455 per employee per year, and 79 percent of IT leaders saw a price rise at renewal.
A 20-seat team in India can pay roughly 12 to 15 lakh a year in software licences.
At $60 a seat, building your own tool starts to beat renting at around 55 to 75 users.
The question is not rent or build. It is whether you want a bill that grows with every hire, or a cost you own.
You hire a good person. You celebrate. Then the software bill goes up.
Nobody warned you, because nobody thinks of a hire as a software purchase. But that is what per-seat pricing does. Every tool you rent charges you per person. Add a person, add a fee. Add ten people, add ten fees, on every tool, every month, forever. Your team grows, your bill grows with it, and the growth you worked for quietly funds your vendors.
This is not a complaint about one tool. It is the shape of the whole market. Most business software is sold by the seat. The price looks small, twenty or sixty dollars a month, until you multiply it by your team, by twelve months, by every tool that uses the same model. Then it stops looking small.
How does per-seat pricing actually work against you?
It charges you for growth, and it charges you again at renewal.
The model is simple. A vendor sets a price per user per month. Your bill is that price times your headcount. When you hire, the bill rises automatically. When someone leaves, you keep paying until you remember to remove their seat, and most teams do not. Unused seats are so common that Zylo's 2026 SaaS Management Index puts median spend at $9,455 per employee per year, with about 36 percent of licences unused (source). You are paying for people who no longer work there, on tools your current team barely opens. It is the same waste as paying for software your team never uses, only this time the bill grows by itself.
Then renewal comes. Zylo's same index found that 79 percent of IT leaders saw a price increase at renewal in the past twelve months. The per-seat price itself goes up, usually 8 to 18 percent a year depending on the category. Renewal dates are dates nobody watches, so the rise lands as a surprise, not a decision. The 2026 pricing report from SMB Newsroom puts CRM mid-tier pricing at $65 per user per month, up 8 percent year on year, and project management up 12 percent (source). So your bill grows twice: more seats, and a higher price per seat.
Do the maths on a small team. Twenty people, one core tool at $60 a seat, is $1,200 a month, $14,400 a year, for one tool. Add a CRM, a project tool, a chat tool, a support tool, each with the same model, and the total stops being a line item. It becomes a salary. Zynteq's India pricing guide puts it in rupees: a 20-seat team typically pays roughly 12 to 15 lakh a year in SaaS licences (source). That is a full-time hire, spent on rent.
This is why your one monthly fee hides your value matters on both sides of the table. When the fee is one flat number, nobody can see what it buys. When the fee is per seat, everybody can see it grow, and nobody can stop it growing.
When does renting stop making sense?
When the seat count crosses the line where owning costs less than renting.
There is a real crossover point, and it is lower than most founders think. Akoode's five-year cost model, published November 2026, works it out plainly: with a $60-a-seat subscription and prices rising 10 percent a year, building your own tool starts to beat renting at roughly 55 to 75 users (source). One seat costs $720 in year one and about $4,396 over five years at that price path. At 60 seats, that is over $260,000 across five years for one tool.
Below that line, renting usually wins. You get a working tool on day one, someone else keeps it running, and you pay a small monthly fee. Above that line, the maths flips. You are paying build-level money for rent-level control, and the bill keeps rising with every hire.
| Team size | One tool at $60 a seat | Five tools at $60 a seat |
| 10 people | $7,200 a year | $36,000 a year |
| 20 people | $14,400 a year | $72,000 a year |
| 50 people | $36,000 a year | $180,000 a year |
| 100 people | $72,000 a year | $360,000 a year |
The table leaves out price rises, which make the real numbers worse. At 10 percent a year, the 20-person row is about $88,000 over five years for five tools, not $72,000. And it leaves out the seats you pay for and never use, which Zylo puts at roughly a third of all licences.
The point is not that every team should build. The point is that the decision has a number on it, and most founders have never run it. They signed up when they were five people, the price was trivial, and then the team grew around a bill that grew with it. Nobody re-ran the maths at twenty, or fifty, because nobody owns the maths. It is the same gap as the spreadsheet that runs your business: the cost lives in a place nobody reviews.
What is the fixed-fee alternative?
You pay once for the build, and the bill stops growing with your headcount.
The market has split into two honest shapes, and the split is now visible in print. On one side, per-seat SaaS: a monthly tax on every person you employ. On the other, fixed-fee build with full ownership: you pay for the system once, you own all of it, and there are no per-seat fees, ever. That last line is quoted from SkillMammoth's survey of twelve AI automation agencies, where seven of twelve print a price and the ownership shape is stated plainly (source).
The ownership shape has its own costs, and they should be named. You pay for the build. You pay for hosting and care. A custom ops CRM in India runs roughly 40,000 to 85,000 rupees one-time plus 3,000 to 7,000 a month in running costs, per Zynteq's guide. That is real money. But it is fixed money. Hire five more people and the bill does not move. Hire fifty more and it still does not move. The tool is yours, the data is yours, and nobody can raise your price at renewal, because there is no renewal.
This is the shape BaseEngine is built on: no per-seat fees, a fixed build, and a buy-out so the system is yours. It is not the right shape for every business. A five-person team with a simple need should rent. But a twenty-person team paying 12 to 15 lakh a year in licences should at least run the comparison, because the alternative is not a cheaper subscription. It is a cost that stops growing.
The other thing ownership buys is fit. A rented tool is built for everyone, so it fits no one exactly. Your team bends its work around the tool, keeps the real process on WhatsApp and Excel, and pays for seats on a system your team never opened. A tool built for your process fits the way your team actually works, which is why it gets used, which is the only thing that makes any software worth paying for.
How do you decide which shape fits your business?
Run three numbers, and be honest about all three.
First, count your real software bill per employee. Not the headline price of one tool. Every tool, every seat, every month, including the seats of people who left. If that number is above 50,000 rupees a year per person, you are already in the range where ownership deserves a look.
Second, count your growth. If you plan to double headcount in the next two years, your per-seat bill doubles with it, plus the renewal rises. A fixed build looks expensive today and cheap in year two. If headcount is flat, renting stays reasonable for longer.
Third, count the fit gap. How much of your real work still lives outside the rented tools, in chats, sheets and memory? If the answer is most of it, you are paying per-seat rent for a system your team routes around. That is the worst of both worlds: a growing bill for a tool that does not hold the work.
If all three numbers point the same way, the decision is not really a decision. It is arithmetic. And if they point to renting, that is a fine answer too, as long as it is an answer you chose this year, not a subscription you signed when you were five people and never revisited.
A hire should cost you a salary, a laptop and a welcome lunch. It should not quietly raise the price of every tool you own. The moment it does, your software is taxing your growth. Run the numbers, and decide on purpose which side of that tax you want to be on.
Frequently Asked Questions
What is per-seat SaaS pricing?
Per-seat pricing charges a monthly fee for every user on the account. Your bill is the price per seat multiplied by your headcount, so it rises every time you hire and falls only when you remember to remove seats. Most CRM, project management and support tools use this model.
How much does the average company spend on SaaS per employee?
Zylo's 2026 SaaS Management Index puts median spend at $9,455 per employee per year, with about 36 percent of licences unused. A 20-seat team in India typically pays roughly 12 to 15 lakh a year in software licences, according to Zynteq's India pricing guide.
When does building custom software beat renting SaaS?
At around $60 a seat with prices rising 10 percent a year, building starts to beat renting at roughly 55 to 75 users over five years, per Akoode's November 2026 cost model. Below that line renting usually wins. Above it, you are paying build-level money for rent-level control.
Do SaaS prices go up every year?
Usually, yes. Zylo's 2026 index found 79 percent of IT leaders saw a price increase at renewal in the past twelve months. Category price rises run 8 to 18 percent a year, so a per-seat bill grows twice: more seats and a higher price per seat.
What does fixed-fee ownership mean for software?
You pay once for the build and own the system, with no per-seat fees and no renewal price rise. You still pay hosting and care costs, but those are fixed and do not move when you hire. A custom ops CRM in India runs roughly 40,000 to 85,000 rupees one-time plus 3,000 to 7,000 a month in running costs.