A system of intelligence and action, not a system of record

Most HR platforms are built to store what already happened. skillfora is built to help you decide what happens next.

I spent years as a talent strategist inside hyper-growth companies, and the same scene kept repeating itself. A leader has to make a high-context judgement call. Who is ready for more scope. Who should lead this project. Who is quietly at risk of leaving.

Those calls are worth a lot of money and a lot of careers. And they get made on gut feel, through many loops of human audit, outdated expectations and a spreadsheet with expectations somebody last updated two quarters ago.

I've watched brilliant leaders fly completely blind. The leaders were never the problem. The systems around them were simply never built to answer the question.

Your HRIS is a System of Record. That is exactly what it was designed to be.

Legacy HR platforms hold contracts, payroll, headcount, holiday balances, org charts and compliance artefacts. Most of them hold that data well. Record-keeping is a real job and somebody has to do it properly.

But a record only tells you what your organisation has already agreed about a person. It tells you almost nothing about what that person can actually do today.

That gap has a concrete price:

preventable turnover, because people leave when hired with the wrong expectations or when nobody can see what they're capable of
redundant external hiring, because you paid a recruiter for a skill already sitting two desks away
stalled projects, because the right internal person was never surfaced
blocked progression, because no one could show anybody a credible path

None of that shows up on an HRIS dashboard. It shows up in your attrition numbers twelve months later.

What we mean by a system of intelligence

skillfora reads the signals in everyday work and builds a picture of what each person can genuinely do.

It doesn't start with a survey. It doesn't start with a self-assessment. It doesn't start with an annual skills audit that goes stale the second you hit save. Currency of data matters as much as accuracy, and manual approaches lose on both counts.

The platform suggests the skills it finds based on observations, and a manager approves or rejects them in one click. Validated in the flow of work, verified by a human.

That gives you three things the record never could: skillfora helps organisations understand their current capabilities, predict future needs, and connect the right people to the right opportunities.

And a system of action

fora, the agent at the centre of the product, answers plain-language questions about your teams and turns the answers into work. It:

drafts skill profiles
builds job level frameworks
writes job ads from the gaps that actually exist
surfaces internal candidates before you brief an agency
benchmarks your team's capability against the wider market
flags skill gaps before they become operational risks

Every recommendation shows the evidence behind it. Evidence over instinct, every time.

The same three questions, answered differently

"Who could take this project on?"

A System of Record gives you job titles and a performance review from March.
A system of intelligence gives you the people who have demonstrably done this work, plus the people who are one step away and would grow into it.

"Do we need to hire for this?"

A System of Record gives you a headcount plan.
A system of intelligence tells you whether the capability is already in the building, and what it would cost you to develop rather than buy.

"Why do our best people keep leaving?"

A System of Record gives you an exit interview, written after the decision was made.
A system of intelligence shows you who was ready months ago, while you can still do something about it.

Customisation isn't a feature. It's the premise.

This is where most skills tooling falls over. It arrives with a generic skill library, asks you to map your organisation onto somebody else's taxonomy, and quietly flattens the thing that makes your company distinctive.

Two scale-ups can have identical headcount, identical funding stage and identical job titles on the org chart, and completely different capability underneath. The titles are the least interesting thing about either of them.

So skillfora is built to be shaped around how your organisation actually works. You configure:

the taxonomy, rather than inheriting a library assembled for somebody else's company
the skill definitions, written in the language your teams already use in their own documents
the proficiency levels, so "advanced" means the same thing to engineering and to finance
the levelling framework, so scope and expectation are described the way you actually promote people
the approval flows, so the right person validates a skill before it counts for anything

That last one matters more than it sounds. Who gets to confirm that somebody is good at something is a governance question, not a settings question, and every organisation answers it differently.

The model also gets sharper the more it learns about how you work, which makes configuration a compounding advantage rather than an administrative tax you pay once at implementation.

The people in the profiles get a say

A skills profile that is only ever written about someone, never with them, will be resented. Fairly.

So skillfora gives people their own side of it. Employees can update their skill profile, add relevant certifications, and build a growth plan against the capabilities their organisation actually needs next.

The evidence read from real work gives you the honest baseline. What people add themselves gives them agency over how they're seen. Both run through the same validation, so nothing becomes fact just because it was typed in.

This is the half of the category that gets ignored. Skills data is usually sold as a planning tool for the top of the house, when the people with the most to gain from capability being visible are the ones whose capability is currently invisible.

Stand-alone, or connected to what you already run

Nobody wants another rip-and-replace programme.

skillfora works as a stand-alone platform. You don't have to change your HRIS, migrate years of data, or wait out a twelve-month implementation before anything useful happens.

It also connects to the tools your teams already live in: Slack, Teams, GitHub, Confluence, Linear and any HRIS. Your System of Record stays your System of Record. skillfora sits alongside it as the layer where decisions actually get made.

Transparency, not surveillance

skillfora is built with trust in mind:

Permission-aware and zero-trust: it mirrors the permissions that already exist in your tools, so it never surfaces anything a person couldn't already see
Sovereign and GDPR-first
Deterministic and designed to be bias-free
We don't sell data and we don't train public models on it

The purpose of all this isn't to watch people more closely. It's to make capability visible, so the person who is ready for more scope actually gets asked. Top performers rarely leave because of the work. They leave because nobody could see what they were capable of.

Where we are

We're early, and there is a lot still to do, but we're moving fast.

skillfora is pre-launch. The waitlist is open, and we're selecting 10 Design Partners from high-growth scale-ups: roadmap influence, direct collaboration with the founding team, and a 50% lifetime discount.

Join the waitlist at skillfora.io, or book a demo with the founder and tell us where your current system leaves you guessing.