Pay transparency is here. For a small shop, that's an advantage

Hi everyone. I spent years as the product owner of an internal HR system at an IT services company, sitting next to the HR managers and accountants who actually used it. Now I'm building Helia HR, and pay transparency is the topic founders keep raising with a sigh. So here's the more useful way to look at it.

The deadline passed. The panic is aimed the wrong way.

The EU Pay Transparency Directive (Directive (EU) 2023/970) had a national transposition deadline of 7 June 2026. The headline requirements are simple to state: candidates get pay ranges before they're hired, employees can ask what peers in equivalent roles earn, and companies above certain headcounts report their gender pay gap.

Big companies dread it, and fairly — they have a decade of ad-hoc raises, "don't discuss your salary" culture, and pay gaps nobody wants surfaced. But most of the commentary is written for those companies. If you're 20, 30, 50 people, you're reading someone else's problem and borrowing their anxiety.

Here's the contrarian bit: for a small, honest shop, transparency is a hiring weapon — and it's nearly free to pick up.

Why the small honest shop wins

1. You have almost nothing to hide yet. At 30 people you haven't accumulated ten years of inconsistent deals. Cleaning up two or three anomalies is a Tuesday. For a 2,000-person company it's a project with a steering committee.
2. Ranges kill your worst time-sink: the salary mismatch. The single most expensive interview is the one where you both spend four rounds falling in love and discover at the offer that you're €1,500/month apart. Publishing the range up front deletes that meeting from existence. In a market where searches already run two months, that speed is a real edge.
3. Transparency reads as confidence — and candidates can tell. When a small company posts a real range, engineers read it as "these people have their act together." When a big company hides it, they read it as "there's a game here." You get to look like the grown-up in the room for the price of one honest sentence in the job post.
4. It forces a rate card, which you needed anyway. You can't post ranges you haven't defined. The work of writing down "mid engineer: €X–€Y" is the same work that makes your bill rates, your margins, and your promotions defensible. The directive is just the deadline that makes you finally do it.

What "getting ready" actually means at your size

Not a consultant and a 40-page policy. Four things:

1. Write down a band per role and level. A mid backend engineer, a senior QA, a delivery manager — each gets a min and a max. Keep it on one page. It doesn't have to be perfect; it has to exist and be applied.
2. Sort your current people into those bands and look for outliers. Two people doing the same job two grades apart in pay is the thing the directive is designed to expose. Better you find it in a quiet spreadsheet than in a formal employee request.
3. Put the range in the job post. One line. Watch your unqualified-applicant volume drop and your offer-accept rate climb.
4. Decide who can answer the "what do peers earn?" question, and how. You don't need to publish individual salaries — you need to be able to answer the equivalent-role question calmly, with a band you can point to.

When you genuinely don't need to panic

If you already pay consistently for the same work, you are 80% done — the rest is writing it down and putting a number in your job ads. The directive doesn't force you to pay more or to publish everyone's salary on the homepage. It forces you to be consistent and able to explain yourself. Small teams that hire on gut but pay on principle are closer to compliant than they think.

The one real trap is stalling. "We'll formalise pay later" is how you arrive at 80 people with the exact mess the big companies are now paying consultants to untangle. Do the one-page version this quarter, while it's cheap.

Transparency isn't the tax on being small. Opacity is the luxury only the big and slow can still afford — and they're about to lose it too.

We keep the compliance detail in a separate, evergreen guide: [the EU Pay Transparency Directive, explained for small IT companies](/guides/eu-pay-transparency).