Team Development Platform
Komforan Competency Platform
Unlock your team's full potential
Where it came from
The Komforan Competency Platform did not start as a product idea. It started as a problem its founder had already spent years solving by hand.
Henning Kjær has decades of experience leading technical teams, and built the Tech Academy at a major Danish company — a programme that supported the growth of more than 400 developers and technical staff. Running something at that scale teaches you exactly where competency development falls apart: not in the intent, but in the administration. Spreadsheets go stale, skills matrices are rebuilt from scratch every year, and the conversation about what someone wants to learn happens once and is never referred to again.
The platform is the tool that was missing.
Onboarding that seeds the matrix
When someone creates an account they state three things: the skills they have, the strengths they are best at, and what they want to learn.
Those three lists are not a welcome-survey that gets discarded. They seed everything downstream. When the user later joins a competency matrix, it is pre-populated automatically — strengths land at expert level, skills at proficient, and learning goals appear as growth targets. All three lists stay editable from profile settings, so the picture stays current instead of ossifying at the moment of signup.
This is the design decision the whole product hangs off. The reason skills matrices die is that filling one in is tedious and the payoff is invisible. Seeding the matrix from something the user has already told you removes most of that first cost.
Teams first, organisations only if you need them
The team is the primary unit. You create one, invite people by email — an invitee without an account can sign up straight from the invitation — and build a matrix together. The creator is the owner; owners and admins invite people, change roles, and create matrices and sessions, while members view and participate.
Organisations are an optional layer above that, for people running several teams. They let skills roll up across teams and departments to nest into a company hierarchy. Optional is the important word: a single team does not need one and is never made to create one.
That restraint is deliberate. Most tools in this category assume an enterprise org chart on day one, which makes them unusable for the eight-person team that would benefit most.
The competency framework
Each competency supports multiple proficiency levels, descriptive indicators for each level, and associated learning resources. Competencies group into skill areas, and skill areas form the structured development matrix a team works from.
The descriptive indicators are what stop this becoming a numbers exercise. "Level 3 in testing" means nothing on its own and invites people to rate themselves by confidence rather than evidence. A written indicator for what level 3 actually looks like turns the same rating into a conversation two people can have without arguing about what the number meant.
Market of Skills
The differentiator is Market of Skills: an interactive, facilitated session format where a team shares knowledge, gives feedback, and identifies growth opportunities together. Facilitators create a session, invite participants, and guide them through structured activities.
This is what separates the platform from a generic HR skills tracker. A tracker records the state of a team's skills for somebody else to read. A facilitated session is the event where the team actually looks at that data together and decides what to do about it — which is the part that produces change, and the part software usually leaves out.
Tracking what changed
Progress is visible through dashboards and reporting, visual competency matrices, and trends over time, with exportable reports for stakeholders who need the summary rather than the tool.
The platform is live at komforan.io. It is the clearest example on this site of what we mean by building from domain expertise rather than from a feature list — the product exists because the person who designed it had already run the process manually, at scale, and knew which parts genuinely mattered.
Highlights
- Visual Team Competency Matrix
- Interactive Market of Skills sessions
- Secure, scalable AWS backend
We built this the same way we build every client project. See how the one-day web development process works, or what a fixed-price website build costs.