Chapter 01
Why software spend grows faster than headcount, and where it hides
Software is bought by whoever needs it, on whatever card is nearest, and renewed by default. That is why nobody has the full list.
Ask a finance controller at a 150-person company how much the company spends on software and you will usually get one of two answers: the ledger total for "software subscriptions", or a shrug. The ledger number is almost always too low, because a large share of software is not booked to that ledger at all. It sits in card spends booked to "miscellaneous", in employee reimbursements, in forex charges, and in annual plans paid once and forgotten.
Software spend grows faster than headcount for a simple reason: buying a tool costs one person five minutes and a card. Nobody needs a purchase order to start a free trial, and the trial turns into a paid plan the day a team starts relying on it. Each new joiner adds a seat to several tools at once. Each new project adds a tool or two. Very little of this passes finance before the first charge.
The six places software spend hides
| Where | What it looks like | Why it is missed |
|---|---|---|
| Company cards | A USD charge with a merchant name like "FIGMA SAN FRANCISCO" and a separate forex markup line | Booked to the card holder's department or to a suspense head, rarely tagged as software |
| Founders' and team leads' cards | The same, on four or five different cards | Each card holder sees only their slice; nobody sees the total |
| Reimbursements | "Monthly subscription" claims in the expense tool, every month, by the same person | The claim is approved as an expense, not reviewed as a recurring purchase |
| Bank transfers | Annual invoices from Indian vendors paid by NEFT or RTGS | Paid once a year, so they are invisible for eleven months |
| Marketplace and cloud bills | Add-ons bought through a cloud provider's marketplace | They appear inside a larger infrastructure bill |
| Free tiers that turned paid | A small charge that grows each month as usage rises | Nobody decided to buy it; it just started charging |
Why it matters more in India
Indian companies pay a large share of their software bill to vendors outside India, in dollars, on cards. That adds three costs a US company does not see: the bank's foreign currency markup on each card charge, GST on the currency conversion, and the GST reverse-charge liability on imported services that someone has to work out and pay each month. A tool you did not know you had is also a reverse-charge entry nobody made. Chapters 8 and 9 cover these in detail.
What "under control" looks like
You do not need a procurement department. A company has its software spend under control when it can answer five questions on any given day:
- What tools do we pay for, from which card or account, and how much a year in rupees?
- Who owns each tool, meaning who decides whether it renews?
- How many seats do we pay for, and how many people actually signed in during the last 60 days?
- What renews in the next 90 days, and what is the notice period for each?
- For every foreign bill, has the reverse charge been worked out, and do we hold an invoice?
The rest of this playbook works through those questions in order. Chapter 2 builds the list. Chapters 3 to 7 put owners, seats, renewals, overlaps and leavers under control. Chapters 8 to 10 cover payments, GST and income tax. Chapters 11 and 12 give you a policy and a tracker you can adopt this week.
Throughout this playbook, figures for "Neelgiri Labs" are a worked example about a fictional 120-person company. They show the arithmetic, not an industry average.