A. Scaling to 200 staff with ad-hoc salaries? You’re building a lawsuit.

Every exception you approve today becomes tomorrow’s compensation problem: salary compression, unexplained pay gaps, inflated hiring costs and difficult conversations with your board. Once your workforce crosses 100 people, compensation can no longer be managed as a series of individual negotiations. You need an architecture.

B. The Expensive Problem

For a founder-led company, paying people based on what they negotiated at the point of joining can appear efficient. At 30 employees, the inconsistencies may remain invisible.

At 150 or 200 employees, they become a P&L problem.

Two people performing substantially similar work may sit at materially different salaries because one joined during a talent shortage, another negotiated aggressively, and a third received a discretionary adjustment after threatening to resign.

Then the problems compound.

A new hire demands ₦2.5 million because the market has moved. Your existing high performer earns ₦1.7 million. You make the offer because the role is critical — and create salary compression overnight.

Now imagine repeating that decision across 50 roles.

The consequence is not simply “pay dissatisfaction.” It can affect attrition risk, hiring cost, budget predictability, management credibility and potential disputes over the rationale for pay differences.

Globally, compensation structures are increasingly treated as business infrastructure. WorldatWork’s research found that 73% of surveyed organisations adjust compensation ranges annually, demonstrating that salary structures are systems that require active management rather than one-time HR documents.

C. Why the Old Way Fails

Mistake 1: Negotiating every salary independently.

Negotiation is useful. But when every hire becomes a standalone compensation decision, your organisation gradually accumulates exceptions instead of a system.

The result is a salary history — not a salary architecture.

Mistake 2: Copying another company’s grading structure.

A multinational’s global grades do not automatically fit a Lagos fintech, a Nigerian manufacturing company or an African professional-services firm.

Your architecture must reflect your own job complexity, organisational scale, market positioning and business model.

Mistake 3: Benchmarking titles instead of jobs.

“Manager” tells you very little.

A Finance Manager controlling a ₦20 billion operation is not necessarily equivalent to an HR Manager leading a 15-person function.

Pay should be anchored to the value, scope, complexity and accountability of the job, not merely the title.

WorldatWork similarly distinguishes job architecture from compensation structure: architecture establishes how jobs relate internally, while compensation structures connect those jobs to external market value.

D. The Framework: Build Your Salary Architecture in Five Steps

Step 1: Audit the current payroll before designing anything.

Start with facts.

Create a single workforce dataset containing employee, department, role, location, grade, base salary, allowances, variable pay, tenure, performance rating and reporting line.

Then identify anomalies:

• People in similar roles with large salary gaps
• Employees paid below or above emerging market norms
• Salary compression between junior and senior roles
• Legacy allowances attached to individuals rather than jobs
• Titles that no longer reflect actual responsibility

Do not redesign the structure before understanding the cost of your current one.

Step 2: Build the job architecture.

Group roles into job families — Finance, Technology, Sales, Operations, HR, Marketing and so on.

Then establish levels based on measurable differences in:

• Scope
• Decision-making authority
• Complexity
• Technical expertise
• Leadership responsibility
• Business impact

For example:

Level 1 — Associate → Level 2 — Specialist → Level 3 — Senior Specialist → Level 4 — Manager → Level 5 — Senior Manager → Level 6 — Executive Leadership.

The labels can change. The principle cannot: each level must have a defensible definition.

A sound job architecture creates the foundation for consistent job evaluation, career progression and compensation decisions.

Step 3: Create salary bands, not salary points.

A salary band gives management, controlled flexibility.

For each grade, establish:

Minimum → Midpoint → Maximum

The midpoint represents the market reference point you are targeting. The range around it gives you room to differentiate based on capability, experience, performance and sustained contribution.

This is where your compensation philosophy becomes visible.

Are you targeting the 50th percentile of your market? The 60th? Are critical technology roles treated differently? Do different locations require geographic adjustments?

These are executive decisions — not spreadsheet accidents.

Step 4: Test internal equity before implementation.

Now place every employee inside the proposed architecture.

Calculate their compa-ratio: Current Salary ÷ Salary Range Midpoint × 100

Then examine the distribution.

Someone at 82% of midpoint may be developing toward full role proficiency. Someone at 118% may have deep expertise, sustained performance or scarce capability.

But if ten people in comparable jobs range from 75% to 140%, you have a management question.

This is where People Analytics becomes powerful: the data exposes patterns that individual manager conversations often conceal.

Step 5: Put governance around exceptions.

This is the step most companies skip.

Your salary architecture will fail if every senior manager can bypass it.

Define:

• Who can approve an offer outside the band
• What evidence is required
• When salary ranges are reviewed
• How promotions affect placement
• How market adjustments are approved
• How exceptional talent is treated
• What happens when an employee is already above maximum
• How new roles are evaluated

Your compensation system should allow flexibility without allowing arbitrariness.

That distinction matters.

E. What Good Looks Like

Consider a fintech scaling from 120 to 300 employees in Lagos.

Instead of approving each new salary independently, leadership establishes eight job families, six organisational levels and salary bands for each relevant family.

Recruitment now works from approved ranges.

Finance can model the payroll impact of headcount growth.

Managers can explain promotion and salary decisions against defined criteria.

The CHRO can identify compression through analytics before it becomes an attrition problem.

And the CEO can look at workforce cost as a system rather than a collection of individual salaries.

That is what scalable compensation looks like: structure without unnecessary rigidity.

F. The Executive Takeaway

Your salary structure is not an HR spreadsheet.

It is part of your operating architecture.

When properly designed, it gives your board greater visibility over people cost, gives Finance stronger payroll predictability, gives managers clearer decision rules and gives your leadership team a defensible basis for compensation decisions.

It also creates a stronger foundation for broader HR Transformation — because workforce data becomes structured enough to support planning, analytics and strategic decision-making.

The objective is not to make everybody’s salary identical.

It is to make differences in pay intentional, explainable and connected to the value of the work.

To help you achieve that, we built the Pay Structuring & Salary Band Toolkit — an Excel-based working tool containing salary-band calculations, compa-ratio analysis, job architecture fields and governance checks.

Comment TOOL and we’ll send it to you.