What does this person cost
A firm at twenty people pays for forty tools and can name fifteen of them. The cost of an employee is not just their salary. It is the SaaS sprawl attached to their seat.
A founder at a partner services firm can name fifteen of the tools the firm pays for.
The actual number is closer to forty. Some of them are billed annually and never come up unless a renewal lands. Some are billed per seat and grew quietly as headcount grew. Some were trial signups that became real subscriptions because nobody cancelled the card. The aggregate, across forty tools and twenty people, is a line item on the P&L that the founder reads as “software” and does not break down further. The cost is real. The breakdown is not.
The harder question, the one the founder rarely asks because the data does not exist, is what does any one person cost the firm.
Salary is not the cost
A salary number is the largest part of the answer, and the easiest. Benefits are a percentage on top. That is the version most firms model when they think about cost-of-employment.
The version that is actually true is salary plus benefits plus tools. The tools attached to a person’s seat are part of what the firm spends to keep that person productive. A senior consultant might carry an editor license, a project tool seat, a CRM seat, a design tool seat, a research tool seat, a meeting recorder, and an analytics dashboard. Each one is a monthly number. The aggregate is real. Most firms do not roll it up.
The roll-up matters in three places at once.
It matters when finance models a margin. If a person’s true cost rate is fifteen percent higher than the salary-based rate, the project margin the firm is quoting is fifteen percent too generous. The deal looked profitable. It was less profitable than that.
It matters when a person leaves. The seats attached to that person should leave with them, on a known list, in a known sequence. A firm that cannot say which tools were on a departing person’s seat cannot close the loop on the offboarding. The renewals keep landing.
It matters when the firm is deciding whether to hire. The next hire is not just a salary number. It is a salary number plus a tool stack. The tool stack is knowable if the firm has rolled it up before.
SaaS sprawl as a per-person fact
SaaS sprawl is a firm-level conversation in most write-ups. It is more useful as a per-person conversation.
A firm-level cost is hard to act on. “We spend ninety-six thousand a year on software” is an annual board-meeting number. It tells nobody on the team what to do this week. A per-person cost is a different shape. A senior consultant carrying eleven tools is a fact a manager can act on. A junior carrying four is a fact too. The two facts together tell the firm where the sprawl is concentrated and which roles are absorbing the most software cost per head.
The pattern is usually the same. The longest-tenured employees carry the most tools, because every tool the firm ever trialed got assigned to them and never got cleaned up. The newer hires carry less, because their stacks were spun up more recently. The senior consultant the firm assumed was the most efficient unit of revenue is actually the most expensive unit of cost too, and the firm did not know because the cost was distributed across forty vendor invoices the founder never reconciled.
The roll-up that closes the loop
Three numbers, on one screen.
For each employee: the list of tools granted, the monthly cost of each, and the total. The total is the SaaS sprawl attached to that seat. The list is the audit trail. When the person leaves, the list is the offboarding checklist.
For each tool: the seats granted, the cost per seat, and the total monthly burn. The view answers “what are we paying this vendor and for whom” without a finance request.
For the firm: the total monthly tool cost, the average per employee, and a department roll-up. Sales pays this much in software per head. Delivery pays this much. Admin pays this much. The numbers make the next budget conversation possible.
The discipline is in the linkage. The tool grant lives on the person, not in a vendor portal. When the person’s status changes, the grants change with it. When a tool is added to a person’s seat, the cost flows into the per-employee total immediately, not at the next finance reconciliation.
Cost-of-employment becomes a number the firm can read. Salary plus benefits plus the tool stack. The number the deal team should be quoting margin against, not the version that pretends the tools are free.
What PartnerView ships
Every employee record in PartnerView carries a live list of granted tools with the monthly cost of each. The per-employee total is on the same screen as the rest of the employee record, not in a separate portal. The cost rolls into the firm’s cost-of-employment view.
A department roll-up at the admin level answers “what does this team cost per month in software” without a finance request. A tool-level view answers “who has this seat and what are we paying.” Onboarding templates grant the tools that fit the role. Offboarding templates revoke them in bulk, so a departure closes the loop instead of leaving a long tail of renewals.
The SaaS sprawl stops being a quarterly mystery. It is on the person, on the role, and on the firm, on one screen each. The cost of an employee is what the firm actually spends to keep that employee productive, and the firm can read it without a spreadsheet.