Align every role

with where you're going

Your company knows exactly what it pays each role. AlonSkills is where it decides what it requires in return, with a named author and a source behind every requirement.

We don't process personal data. Role level, never person level.

Organizations Already On delivers to

KSATNorsk SykepleierforbundQuality NorwayKGK AcademyDFØStatsforvalterenHK-dir

See where a role requirement comes from

Company context in, one requirement per role out, and every line traceable to what caused it.

AlonSkills Overview: strategic goals traced through the organization

Still from the demo. Open on a larger screen to watch it run.

Your strategy changed. Your roles didn't.

A board decision. A new system. A regulation. A certificate that expires. All of it lands on the role. None of it is written into it.

One competencyComplaint handling
4 roles · 4 definitions
Customer Advisor
“Settles the complaint on the call, and knows the exact line where the case stops being theirs.”
Case Officer
“Reassesses a contested decision on its own merits, and writes it up so it survives review.”
Practice Lead
“Rules on the case that sets the precedent, and every similar case after it follows that ruling.”
Unit Manager
“Reads the pattern across complaints, and changes the practice that keeps producing them.”

Same competency. A different job in every role.

A competency is not one fixed thing you copy down a list. AlonSkills defines what it means, in its own terms, wherever it appears.

Connect every role to where you're going.

One connected model, four levels deep. Each level holds the strategy in a different state and inherits what the level above decided. Change it where it changed, and every requirement hanging below it moves with it.

Company
At this level
“Your direction. Goals, values, the markets you sell into and the regulation that lands on you. Everything below inherits from here.”
Division
At this level
“Strategy, divided. The mandate each part of the organization answers for.”
Department
At this level
“Strategy, in operation. What this unit is measured on, what it depends on, and where it is heading next.”
Role
At this level
“Strategy, resolved. What the role must be able to do, at a defined level, each requirement pointing back at what caused it.”

From company context to defined roles, in three steps.

01

Set your context

Tell AlonSkills who you are: vision, strategic goals, technology, values. This becomes the single source everything else is built from.

02

Get roles built for you

Role profiles are drafted from your context, not a generic template. You review, adjust, and stay in control. The heavy lifting is done; the decisions stay yours.

03

See what stopped being true

Every requirement points at a source. When the source is revised, the requirement stops reading as verified, and says which source and when.

See where your strategy stops.

Some goals reach a role. Some stop inside a division. Some never leave the top. Partially reflected is shown as itself, not rounded up to done.

The five questions we always get.

Does AlonSkills process personal data?

No. We model what a role requires, never who holds it.

No individual assessment, no gender data, no personal identifiers, no salary. Your people stay in your HR system. The two sides share only the position code.

We already have an HR system. Where does this sit?

Next to it, not instead of it.

Your HR system holds people, positions and payroll. AlonSkills holds what each position requires. They meet on the position code, and requirements export to CSV and Excel.

What does it cost, and how is it bought?

An annual subscription, priced by the size of the organization.

Sales assisted and invoiced. Two organizations of the same shape pay the same. Ask, and you get a number in writing.

How long before we see something real?

The first role profiles land the same week your organization is loaded.

One unit of 50 roles is a pilot you can put in front of that unit's own managers and ask whether it describes this company. Weeks, not quarters.

How is this different from a competency framework project?

A project ends with a document. This ends with a living model.

Every requirement carries an author and a source, and the model tells you which lines stopped being true when the strategy or the regulation moved. You build it once and keep it current.

Built for EU pay transparency

When the directive asks why a role sits where it does, the answer is already there. No consultants, no months-long evaluation.

One scale, used everywhere

Every role assessed on the same dimensions, so requirements stay comparable and gradings stay defensible.

Talk to the people who build it.

Pick a time that suits you. We look at your role structure as it is today, show one of your units in AlonSkills, and tell you what a pilot takes.

We answer within one working day.

Bring one role.

We tell you what it requires, more precisely than you could describe it yourself, built from your own strategy, regulations and targets. Forty-five minutes, no preparation.