Today we're announcing the most significant version of SkillsDB in the company's 18 year history. Not a release. Not a redesign. A rebuild — every line of the product, every part of the data model, every workflow — engineered around a single argument we'll defend on any whiteboard: skills are invisible in most organizations, and when they're invisible, every workforce decision built on top of them gets made on assumption.
This is the platform we wished existed when the company started in 2008. It's the platform our enterprise customers have been asking for in different shapes for the last five years. It's the one now finally live.
Here's what we built, why we built it, and what changes for you starting today.
The Argument We Built Around
Most organizations don't know what their people can actually do.
That sounds like an exaggeration until you sit in a workforce planning meeting and watch what happens. The HRIS produces a list of job titles. The LMS produces a list of completions. Someone pulls a spreadsheet that hasn't been updated in 14 months. A senior manager says "we have plenty of Python engineers" and a junior manager flinches because she knows three of them have moved off the language entirely.
Every workforce initiative — recruiting, training, succession, internal mobility, resource planning, AI transformation — sits on top of what people can do. When that layer is invisible, the initiatives compromise each other. Recruiting can't tell what's already inside the building. Training fires generic content at gaps it can't measure. Succession runs on relationships, not capability. Resource planning leans on resumes that are years out of date.
This isn't a training problem. It's not even really an HR problem. It's a visibility problem. And the products in the market — LMS with a skills tab, HRIS with a skills field, content platforms that infer skills from what people watched — were never built to solve it. They were built to do other things and now have a skills label glued on.
We rebuilt SkillsDB from scratch because the skills intelligence category needs infrastructure that didn't exist. Not an opinion in a deck. Infrastructure in production.
What "Skills Intelligence" Actually Means in the New Platform
Three properties define the new system. Each one is a deliberate decision the legacy product couldn't make.
A real skills database underneath everything. Not a table. A typed, queryable, versioned data layer where skills, competencies, role benchmarks, and proficiency assessments live as first-class entities with relationships. Definitions don't drift across teams because there's one place they're defined. History doesn't get lost because everything is versioned. Identity is resolved across systems because the platform was built knowing it would have to integrate, not assuming it'd be alone.
Assessment-first, not inference-first. Proficiency is measured, not guessed from course completion or scraped from LinkedIn. Manager assessment plus self-assessment plus benchmark data, run on a configurable scale, all stored as evidence — not opinions. When a CHRO walks into a board meeting and says "we have these capabilities and these gaps," she can show the receipts.
APIs and extensibility from day one. Everything you can do in the UI, you can do via API. Other systems can read from the skills layer, write to it, subscribe to changes. That's how a skills platform survives — by becoming the source of truth other systems consume, not by trying to be the only place anyone logs in.
If you've followed the argument we made last week, this is the resolution. We weren't trying to convince you "platforms" is a meaningful word. We were laying down what the word should mean, and then showing you the work.
What Changed in the Product
The full rebuild touches every surface. Three changes are worth calling out because they change what's possible for the buyer:
- The skills database itself. Org-wide, real-time, queryable. Search by skill, role, certification, proficiency band, or any combination. Live skills matrix that updates as assessments come in. No more spreadsheet export-and-stare.
- Assessments and scorecards. Manager + self-assessment side-by-side, against role benchmarks, rendered as radar charts. Historical view across cycles so growth is visible, not anecdotal. Direct hand-off into learning plans that target the actual gap.
- Career pathways and internal mobility. Skills-based progression maps with the gap analysis baked in. Employees see what's needed to move; managers see who's ready, ready-soon, or still developing. The career conversation becomes specific instead of vague.
This is the surface. Underneath, there's a redesigned permissioning model, a new audit log that's actually immutable, multi-language support, and an API surface our enterprise customers have been waiting on for a year.
For the full feature pass, the new use cases pages walks through how the platform handles talent development, workforce planning, succession planning, and career pathways — each one rebuilt against the new data model.
What This Means if You're Already a SkillsDB Customer
You already have access. The new platform is live across your workspace. No data migration to run, no flip-the-switch project to schedule, no waiting list — the upgrade happened. Your skills frameworks, assessments, scorecards, career paths, and certifications are intact and now operate on the new system.
Three things to do this week:
- Sign in and explore the redesigned product and skills matrix views — they're built for daily use, not quarterly review.
- Forward this post to one peer in another department who's been frustrated with HR tech. The platform's value compounds when more teams build on it.
- If you want to schedule a walkthrough of the new capabilities, reply to this — we want every customer to see the new system in context, not just discover it.
A separate email is coming Wednesday with the specific feature highlights for your team.
What This Means if You're Already Evaluating
The buyer landscape just shifted. The vendors who pitched "skills features" on top of an HRIS or LMS still have those features. They just have to compete now against a product whose entire architecture is built around the problem they treat as a side dish.
The right next step depends on where you are:
- If you're early — read some of our blog content to get caught up.
- If you're evaluating — book a walkthrough. We'll show the platform against your specific workforce questions, not a generic demo.
- If you've already evaluated us and stalled — the rebuild closed the gap you flagged. Get back on a call. We'll catch you up in a single session.
Where the Bar Sits Now
Eighteen years with the same dedication tells you what holds and what doesn't. Trends come and go. Skills "platforms" appear every cycle. The ones that survive get built on a foundation, not a feature. The ones that don't, end up as a skills tab in a product that's mostly about something else.
We built the new foundation. It's now live. It's already running your assessments, your skills frameworks, your career pathways, and the workforce questions your team will ask this quarter.
The next time someone in your category uses the word "platform," ask them to draw the data model on a whiteboard. The answer tells you everything.