Built for HR work that has to hold up over time.

The founder's perspective

This was missing in everyday work.

What was the problem you wanted to solve?

I have seen the same questions come back again and again: What is actually the difference between two roles? Why are they on different pay levels? And can the decision be explained if someone asks? Often the answer is scattered across spreadsheets, managers' judgements and historical fixes.

What makes blueprnt different?

blueprnt brings role evaluation, level structure and documentation together in one framework. The model can reflect what each organisation actually values, without losing the structure needed to work consistently and transparently.

What should an HR manager be able to do more easily with blueprnt?

An HR manager should be able to explain how roles relate to each other, compare them on the same basis and build a foundation that holds when the organisation changes. When role evaluation, level structure and documentation are in one place, the pay mapping becomes more accurate, consistent and easier to follow up. Less time goes into untangling history, and more decisions can be understood and justified.

Why is a shared structure needed?

Many organisations have roles, titles and salaries, but no shared structure for how they connect. Assessments end up in spreadsheets, historical fixes and individual managers' interpretations.

What did you want to build instead?

blueprnt was built to create a clearer foundation: a way of working where roles are assessed consistently, the right jobs are compared, and the pay mapping leads to actions that can be followed up.