HR finance for people leaders: P&L, gross margin, and where payroll lives
Most HR pros can't read the company's P&L — and it's why they lose seat-at-the-table arguments. Here's the finance literacy you need to talk headcount, comp…
On this page▾
- Why HR has to read the P&L
- The P&L in plain English
- COGS vs OpEx — and why HR cares
- Where people costs hide on the P&L
- The 3 numbers to memorise
- Fully-loaded cost — what a hire actually costs
- How to frame a headcount ask the CFO will say yes to
- Smart questions to ask your CFO this quarter
- FAQs from HR pros learning this for the first time
- A P&L is just 5 lines: revenue minus COGS = gross profit, minus operating expenses = operating income, minus tax and interest = net income.
- Where people costs sit on the P&L changes the conversation: COGS hires affect gross margin, OpEx hires affect operating margin.
- Three numbers every HRBP should memorise: gross margin %, burn multiple, revenue per employee.
- Headcount asks land when framed in payback period and unit economics, not 'we're drowning'.
- If you can't connect a hire to a revenue line, a cost-saving, or a risk reduction, expect a 'no' — and the 'no' is correct.
If you have never read a profit-and-loss statement before, this article is for you. If you have, but always quietly wondered what 'gross margin' really means or why finance gets weird when you want to hire customer-support people, this article is also for you. You don't need a CPA. You need to read a P&L well enough that the CFO stops translating for you. That's a 90-minute investment with permanent compounding returns — every headcount conversation, every comp request, every benefits debate gets easier once you can speak the company's actual financial language.
Why HR has to read the P&L
Imagine you walk into a leadership meeting and ask for 4 new hires on the customer-success team. The CFO frowns and says, 'We can't add more COGS this quarter — the board is watching gross margin.' If those words sound like a foreign language, the decision gets made without you. You are reduced to the role of bringing job descriptions to a meeting that has already happened.
Now imagine the same scene with finance literacy. You walk in already knowing that customer-success salaries sit in 'cost of goods sold' (COGS), which is why they move gross margin. You've pre-built the case: 4 hires at $120k loaded cost = $480k of COGS, but they protect $4.2M of annually-recurring revenue from churn. Net effect on gross margin is +1.2 points over 12 months, not -3 points. The CFO leans back. You just changed the conversation.
That second version is what 'business partner' actually means. Not a slogan — a vocabulary.
The P&L in plain English
The profit and loss statement (often shortened to P&L, or sometimes 'income statement') is the document that answers one question: in this period, did the company make money or lose money, and how? It is read top to bottom. Each line subtracts costs from the line above it until you arrive at the final answer — net income.
- Revenue (also called 'top line' or 'sales'): all the money customers paid you in this period for your product or service.
- Minus Cost of Goods Sold (COGS): the direct cost of delivering that revenue. For a SaaS company this is hosting, payment processing, and the support/services people who keep customers alive.
- = Gross Profit. Gross margin % = gross profit ÷ revenue. This is the single most important health metric for most software businesses.
- Minus Operating Expenses (OpEx): the costs of running the company that aren't tied directly to delivery. Usually split into Research & Development (R&D), Sales & Marketing (S&M), and General & Administrative (G&A — finance, HR, legal, ops, the CEO).
- = Operating Income (sometimes 'EBITDA' with a couple of adjustments). This shows whether the core business is profitable before tax and financing decisions.
- Minus Interest and Taxes = Net Income (the 'bottom line'). What's actually left for shareholders.
Think of the P&L as a coffee filter. Revenue is the water you pour in at the top. Each layer (COGS, then OpEx, then tax) absorbs some of it. Net income is what drips through to the cup at the bottom. Every cost belongs in one layer — knowing which one is most of the literacy.
COGS vs OpEx — and why HR cares
Here is where many HR conversations go sideways. 'Cost of Goods Sold' sounds industrial, like it only applies to factories. In a software or services business it absolutely includes people. It is the cost of producing and delivering what the customer pays for.
Operating expense, by contrast, is the cost of running the company itself — building new products (R&D), acquiring customers (S&M), and keeping the lights on (G&A). The exact same job title can sit in COGS at one company and OpEx at another. There is no universal rule; finance teams make a policy choice and stick to it.
Why should HR care? Because investors and boards watch gross margin (the COGS layer) very differently from how they watch OpEx growth. A hire that lands in COGS lowers gross margin, which can move the stock price or the next valuation. A hire that lands in OpEx is judged by whether the operating income still trends the right way. Same hire, very different scrutiny.
Where people costs hide on the P&L
| Function | Usually lives in | Why HR should care |
|---|---|---|
| Customer success, support, professional services delivery | COGS | Hiring here drops gross margin — investors and boards notice immediately. Frame asks in terms of retained ARR, not headcount. |
| Engineering building the core product | R&D (OpEx) | Some of it may be 'capitalised' (treated as an asset instead of an expense). Ask finance which roles, since this affects the P&L impact of a hire. |
| Sales, marketing, growth | S&M (OpEx) | Tied directly to CAC (customer acquisition cost) and payback period. Comp plans live here — bad plans destroy unit economics. |
| HR, finance, legal, IT, exec | G&A (OpEx) | Watched as 'overhead'. As a % of revenue, G&A should shrink as the company scales. HR hires in G&A get the most scrutiny per dollar. |
| Engineering doing platform/internal tools | R&D or G&A — varies | If it serves the product, R&D. If it serves the company, G&A. Worth asking — affects how the role is justified. |
The 3 numbers to memorise
If you only learn three financial numbers for your company, learn these. They unlock most strategic conversations.
- 1Gross margin %Gross profit ÷ revenue. For a SaaS business, 70–80% is healthy, 60% is concerning, 85%+ is exceptional. For services or hardware businesses the bar is lower. Knowing the number tells you how much room you have for any COGS hire.
- 2Burn multipleNet cash burned in the period ÷ net new ARR (annually recurring revenue) added in the period. Under 1 is great, 1–2 is fine, over 2 is concerning, over 3 means hiring is about to slow. Coined by David Sacks; widely cited at startup boards.
- 3Revenue per employeeAnnualised revenue ÷ headcount. A blunt benchmark, but boards love it. Best-in-class SaaS hits $400k+. Knowing where you sit tells you how a board will react to your next 20 hires.
Fully-loaded cost — what a hire actually costs
When you propose a salary of $120,000, the actual cost to the company is meaningfully higher. The 'fully loaded' (sometimes 'all-in') cost typically adds 25–40% on top of base salary, depending on geography and benefits. A useful default is base × 1.3 for the US, base × 1.25 for the UK, base × 1.45 for some European geos where social charges are heavy.
| Component | Typical % of base | Notes |
|---|---|---|
| Base salary | 100% | The starting line |
| Employer payroll taxes (FICA, NI, social charges) | 7–25% | Varies dramatically by country |
| Health, dental, vision, life insurance | 5–15% | Higher in US, lower in single-payer markets |
| Retirement / pension contribution | 3–8% | Match rates vary |
| Equity (RSU / option) expense | 10–25% | For tech companies; non-cash but a real cost |
| Bonus / commission accrual | 5–25% | Depends on role |
| Tools, laptop, workspace, training | 2–5% | Recurring per FTE |
Presenting headcount asks at base salary only. The CFO mentally multiplies by 1.3+, so your $120k ask is really a $156k ask. Bring the loaded number yourself. It signals you know how the company actually keeps score.
How to frame a headcount ask the CFO will say yes to
Most headcount asks fail not because the role isn't needed — but because the ask is framed in the wrong language. 'My team is drowning' is an honest description of pain, but it's not a business case. The CFO has to choose between your pain and 15 other pains across the company. You win that choice by making the financial story clearest.
- 1What the hire enablesA revenue line, a cost saving, or a risk reduction. Pick one. Be specific.
- 2Fully loaded cost over 12 monthsSalary + benefits + tools + ramp loss. Don't make finance do the math.
- 3Payback periodHow long until the hire 'pays for themselves' in the metric above? Under 12 months is easy; under 18 months is fine; over 24 months needs a strategic justification.
- 4What happens if you don't hireThe honest cost of inaction — churn risk, slowed roadmap, attrition of your existing team. Quantify where you can.
'This Senior CS Manager costs $180k fully loaded for year one. They directly own renewal of our top 12 accounts, which represent $4.2M of ARR. At our current renewal rate that segment loses 18% — about $750k per year. Industry-best CS coverage takes that to 8%. Pay back: 6 months. Without the hire, we're modelling $400k+ in additional churn next year.' That ask gets approved.
Smart questions to ask your CFO this quarter
- Walk me through our P&L line by line — which roles sit in COGS vs OpEx?
- What gross margin range are we trying to hold? What's the boundary for board concern?
- What's our current burn multiple, and what's the target?
- What's our revenue per employee, and how does that compare to peers?
- Which functions are over- or under-invested as % of revenue compared to benchmarks?
- What headcount assumptions are baked into the current operating plan?
- What financial signal would cause a hiring freeze? At what number would it lift?
FAQs from HR pros learning this for the first time
Frequently asked questions
Do I need to be able to build a P&L from scratch?
No. You need to be able to read one, ask sharp questions about it, and frame people decisions in its language. Building one is the CFO's job.
What if my company doesn't share the P&L with HR?
Ask. If still no, ask for the metrics — gross margin %, burn, runway, RPE. If the company won't share even those, that itself is information about how HR is positioned.
Is this only relevant for VC-backed startups?
No. Public companies file P&Ls every quarter; everyone reads them. Family-owned businesses and non-profits have the same underlying structure, just different vocabulary.
I'm in HR at a non-profit — what changes?
Replace 'revenue' with 'program revenue + grants', 'gross margin' with 'program efficiency', and 'investors' with 'board + funders'. Same logic, different words.
How long does it take to actually get fluent?
Two weeks of deliberate effort. Read your last 4 quarterly P&Ls, sit with a friendly finance person for 60 minutes, then use the vocabulary in your next 3 meetings even if it feels awkward.
- Unit economics for HRBPs: CAC, LTV, payback — what they mean for your hiring plan
- Headcount Modeling: The Spreadsheet Every CFO Wants and Most HR Teams Don't Build
- HR strategy on a page: the one document that aligns your people function to the business
- The Balanced Scorecard for HR — Kaplan & Norton, applied to people
Read next
All playbooksIf your CEO talks about CAC payback and you nod politely, you're outside the room where headcount decisions happen.
A clean approach to bottoms-up headcount modeling that survives finance scrutiny — driver-based, scenario-aware, and reconciled to revenue and product plans.
If you can't summarise your HR strategy on one page, you don't have one. Here is the template — 6 boxes, a 90-minute workshop to fill them, and the…