Operations
Who should own a tool? A simple model for 100-person companies
Every software tool needs one named person who decides whether it renews. A short model for assigning owners in a growing company, with what the owner does and does not do.
- Published
- 7 Nov 2026
- Read time
- 6 min
- Topic
- Operations
General information, not tax advice. Confirm with your chartered accountant. GST and income-tax positions on cross-border software change with CBIC notifications, Finance Acts and court rulings.
In a 20-person company, the founder owns every tool, whether they know it or not. By 100 people that stops working. Tools are bought by teams, paid on several cards and used by people the founder has never sat with. When a renewal comes up, nobody is sure who should decide, so nobody does, and it renews.
The fix is one rule: every tool has exactly one named owner. Not a team, not a department, a person.
What the owner does
- Decides at each renewal: renew as is, reduce seats, switch billing cycle, or cancel.
- Approves new seats and removes unused ones.
- Knows what the tool is for and which other tools overlap with it.
- Hands the tool over to a named person before leaving the company or the team.
What the owner does not do
- Pay for it. Payment method is finance's job.
- Decide tax treatment. GST and invoice questions go to the accountant.
- Manage access policy. Security rules for sign-in and data belong to IT.
Separating these stops the owner from becoming a bottleneck. The owner decides whether the company needs the tool and how many seats; finance and IT handle the rest.
A simple model for picking owners
| Kind of tool | Owner | Example (fictional tools) |
|---|---|---|
| Used by one team | The head of that team | Design tool: design lead. CRM: sales head |
| Used by everyone | IT or workplace admin | Office suite, video meetings, chat |
| Used by a project | The project lead, with an end date | A client's preferred tracker |
| Finance and HR systems | The function head | Payroll: HR lead. Accounting: finance controller |
| Bought on a personal card | The person who bought it, until reassigned | A reimbursed writing tool |
Two edge cases come up often. For tools shared by two teams, give it to the team with more seats and write the other team's lead in a notes field. For project tools, record the project end date, because the tool should be reviewed when the project closes, not at renewal.
Worked example: assigning owners in a week
Neelgiri Labs, a fictional 120-person company, started with a software register of 64 tools and no owners. Priya, the finance controller, ran this in one week.
| Day | Step | Result |
|---|---|---|
| Monday | Card holder set as provisional owner for every tool | 64 tools with a name against them |
| Tuesday | Each provisional owner gets their list and confirms or names someone else | Most confirmed; some passed on |
| Wednesday | Company-wide tools moved to IT, finance tools to finance | Card holders no longer own tools they only paid for |
| Thursday | Tools nobody claims listed for the leadership meeting | A short list of tools to cancel or assign |
| Friday | Owners added to the renewal calendar | Every renewal now reaches a person |
Signs a tool has no real owner
- The owner on record has left the company or moved team.
- Nobody can say how many seats are paid, or who has them.
- The renewal date is only known because the card was charged.
- Two teams each think the other one is paying for it.
- Requests for new seats go to whoever has the admin password.
Any one of these is enough to reassign the tool. Review owners every quarter, and every time a team lead leaves, because ownership tends to leave with them.
Write it down once
Put the rule in your software purchase policy: every tool has one owner, the owner decides at renewal, and owners hand over before they leave. The SaaS purchase policy template includes an owner section you can adopt as written.
In Ayush Agro Foods, every tool in the register has an owner field. Tools without one are listed in Owners and Requests until someone takes them, and every renewal alert goes to the owner by name on Slack, Microsoft Teams, WhatsApp or email. Finance controllers can see the full picture on the finance teams page.
Next post
Card forex markup on SaaS bills: how to see it and what to do about it
Every USD software bill paid on an Indian card costs more than the dollar price times the exchange rate. How to measure the difference on your own statements, and options to reduce it.
Read nextOwners, offboarding and the forex line, handled.
Every tool with a named owner, every leaver's seats swept, and the INR debited shown next to the vendor price.
- Read-only access
- Data hosted in India
- Priced in rupees
- 14-day trial on your data