Three years ago, I sat in a quarterly review for a high-performing team. The numbers were green. Revenue was up. Churn was down.
But when the VP asked, “Who here is ready to step into a leadership role next year?”—silence.
Not because the team lacked ambition. Because no one actually knew what skills existed in the room.
We had resumes, we had performance reviews. We had gut feelings. But we had zero real-time visibility into who could code in Rust, who had crisis negotiation training, or who secretly led a cross-functional project to success.
That frustration followed me home. And eventually, it turned into an obsession.
That obsession is now CapabiliSense.
The Problem: The Hidden Skill Tax
Most organizations operate with what I call the Skill Gap Tax—the silent drag on productivity caused by invisible competencies.
Here’s what that looks like in real life:
-
A senior engineer spends three weeks rebuilding a module that a junior data scientist already mastered.
-
A sales director hires an external consultant for $15k, unaware that an internal manager closed a similar deal six months ago.
-
A project fails because no one documented the person who understood the legacy system—they left six months prior.
We aren’t suffering from a lack of talent.
We’re suffering from a lack of sensing.
The Core Insight: Skills Aren’t Static—So Why Are Our Maps?
Traditional HR tools treat skills like trophies on a shelf. You earn them. You list them. They collect dust.
But in 2026, skills evolve weekly.
-
A marketer learns prompt engineering over a weekend.
-
An ops lead picks up low-code automation between sprints.
-
A finance analyst masters SQL from YouTube tutorials.
CapabiliSense isn’t another credential database.
It’s a living skill radar that detects, updates, and visualizes what people can actually do—right now.
“We don’t need more certificates. We need more signal.”
Why I’m Building This Myself (Not Just Buying an ATS)
You might be thinking: “Doesn’t LinkedIn already do this? Or Workday?”
Here’s the truth: existing platforms are designed for compliance, not capability.
-
They rely on self-reported data (inflated or outdated).
-
They don’t integrate with real work (Slack, GitHub, Jira, Gmail).
-
They treat skill discovery as a yearly exercise, not a daily habit.
I started building CapabiliSense because I believe three things deeply:
1. Small teams win with hidden strengths.
The most innovative solutions don’t come from new hires—they come from recombining skills already inside your four walls.
2. People want to be seen for what they can actually do.
Nothing kills motivation faster than being pigeonholed by an old job title. Skill transparency is a retention strategy.
3. AI should reveal human potential, not replace it.
CapabiliSense uses lightweight AI to infer skills from work artifacts—with privacy first. No creepiness. No surveillance. Just useful signals.
How CapabiliSense Is Different (The Honest Tech)
We’re not building a massive HR suite. We’re building a skill inference engine that lives where you already work.
Here’s the current stack:
-
Slack & Teams integration – Detects expertise from questions answered and documents shared.
-
Project tool connectors (Jira, Asana, Linear) – Maps skill application, not just self-declaration.
-
Privacy layer – Users approve insights before they’re visible to managers. No secret scoring.
-
Live skill graph – Visualizes clusters of expertise across teams, locations, and time zones.
We are deliberately starting with teams of 20–200 people. Why? Because that’s where skill visibility breaks first—too big for tribal knowledge, too small for bloated enterprise tools.
What I’ve Learned So Far (The Unfiltered Journey)
Building CapabiliSense hasn’t been a straight line.
1. What worked:
-
Early users love the “skill radar” dashboard. Seeing hidden experts on day one creates instant value.
-
Privacy-first design earned trust faster than expected.
2. What failed:
-
My first attempt at auto-tagging skills from emails was overconfident and noisy. We scrapped three months of work.
-
I assumed managers would want total transparency. Many prefer ambiguity. We had to build permission controls.
3. What I’m optimizing now:
-
Reducing latency between a skill being used and appearing in the graph (target: <4 hours).
-
Building a “skill request” feature – so teams can ask for hidden capabilities without guessing.
The Roadmap: Where CapabiliSense Goes From Here
| Quarter | Focus |
|---|---|
| Q3 2026 | Live skill graph + Slack bot (beta) |
| Q4 2026 | Jira/GitHub connectors + manager insights |
| Q1 2027 | Skill gaps detection + anonymized team benchmarks |
| Q2 2027 | Internal marketplace (request/project → skill match) |
We’re not trying to replace your HRIS. We’re the radar layer that sits on top of it.
Who Is This For? (And Who Is It Not For?)
This is for you if:
-
You manage a team and feel like you’re guessing who knows what.
-
You’re an IC who’s tired of being invisible for skills your title doesn’t show.
-
You lead a startup or scale-up and need to grow without wasting talent.
This is NOT for you if:
-
You believe skills never change (good luck).
-
You prefer command-and-control over capability visibility.
-
You’re looking for another certification tracker.
Try It (Or Just Tell Me I’m Wrong)
I’m not building CapabiliSense in a vacuum. I’m building it with the people who feel the skill gap tax every single day.
Here’s how you can help:
-
Join the early waitlist – Get access when our private beta opens next month.
-
Reply with your #1 skill visibility headache – I read every response.
-
Share this post if you’ve ever watched talent hide in plain sight.
👉 [Join the CapabiliSense waitlist →]
Conclusion: The Shift from Resumes to Radars
I didn’t start building CapabiliSense because I love writing code at 2 AM. I started it because I’ve watched too many talented people sit silent in meetings while their skills went unused. I’ve watched too many managers beg for budget to hire “someone who knows X” when that person was already two desks away.
The old way of managing talent—relying on static resumes, annual reviews, and gut feelings—is broken. It creates friction, frustration, and expensive turnover.
CapabiliSense is my attempt to fix that. Not with bloated HR software. Not with invasive employee monitoring. But with a simple, privacy-first radar that answers one question: What can my team actually do right now?
This isn’t about replacing people with AI. It’s about connecting people to opportunities that already exist inside their own organization. It’s about giving every employee a visible, living map of their own growing capabilities—so they’re never stuck in a role that underestimates them.
I’m building this in the open. The beta is imperfect. The roadmap is ambitious. But the mission is clear:
Stop flying blind. Start seeing skill.
If that resonates with you, join the waitlist. Break the tool. Tell me what I got wrong. Or just share this with one manager who keeps hiring for skills they already have.
Frequently Asked Questions (FAQs)
1. What exactly is CapabiliSense? Is it an HR tool?
CapabiliSense is a skill visibility engine, not a full HR system. Think of it as a radar layer that sits on top of your existing tools (Slack, Jira, GitHub, etc.). It detects and visualizes what your team members can actually do in real time—without relying on self-reported resumes or annual reviews. It doesn’t replace your HRIS, payroll, or recruiting software.
2. How is this different from LinkedIn or Workday skills sections?
| Platform | Problem |
|---|---|
| Self-reported, rarely updated, focused on job hunting not internal mobility | |
| Workday/SAP | Rigid, compliance-focused, requires manual entry |
| CapabiliSense | Automatically inferred from real work, updates weekly, privacy-first, designed for internal team discovery |
CapabiliSense shows applied skills—what people actually do—not what they claim to know.
3. Isn’t this creepy? Are you monitoring employees?
No. This is our most important question—and the one we designed around first.
CapabiliSense does NOT:
-
Record keystrokes, screenshots, or messages
-
Score or rank employees secretly
-
Share any insight without user approval
What we DO:
-
Analyze anonymized work patterns (e.g., “User A answered 12 questions about Python in Slack”)
-
Require explicit user consent before any skill is added to their profile
-
Allow users to hide, edit, or delete any inferred skill at any time
You are never surprised by what CapabiliSense shows about you.
4. What tools does CapabiliSense integrate with?
Current & planned integrations:
| Category | Tools |
|---|---|
| Communication | Slack, Microsoft Teams, Email (optional) |
| Project management | Jira, Asana, Linear, Trello |
| Development | GitHub, GitLab, Bitbucket |
| Documentation | Notion, Confluence, Google Drive |
| Calendar | Google Calendar, Outlook (for meeting expertise signals) |
We add new integrations every month. If yours is missing, request it on our roadmap page.
5. How accurate is the skill detection?
Current accuracy (internal testing): ~82% for technical skills, ~71% for soft skills.
We are transparent about confidence scores. Every inferred skill includes a confidence percentage (e.g., “Python: 94% confident based on 47 commits and 23 Slack answers”). Low-confidence skills require manual confirmation before appearing.
We don’t guess. If there isn’t enough signal, nothing is shown.
6. Who owns the data? Can my employer fire me based on this?
You own your skill profile. Your employer owns the aggregated team insights (e.g., “The engineering team has 12 people with Python skills”).
We have a strict No Adverse Action policy in our terms of service: CapabiliSense data cannot be used for layoffs, performance reviews, or disciplinary decisions. Managers see skill availability, not skill quality.
That said—always check your local labor laws. We built the tool ethically, but we can’t control how every company uses it. If you’re concerned, talk to your HR team before enabling.
7. What size team is CapabiliSense best for?
Sweet spot: 20–200 people
-
Under 20: You probably already know everyone’s skills by word of mouth.
-
20–200: Tribal knowledge breaks down. Managers start guessing. This is where we add the most value.
-
Over 200: It still works, but you may need custom enterprise features (contact us).
We are not building for 10,000-person enterprises yet. We want to get the experience right for fast-growing teams first.
8. How much does it cost?
Pilot phase (current): Free for the first 3 months for beta testers.
Launch pricing (Q1 2027):
-
Team plan (20–50 users): $8 per user/month
-
Growth plan (51–200 users): $6 per user/month
-
Enterprise (200+): Custom pricing
No per-seat minimum. Cancel anytime. No hidden fees for integrations.
9. Can I try CapabiliSense without my manager knowing?
Yes. During onboarding, you can choose “Individual Discovery Mode” —this lets you see your own inferred skills without sharing anything with your team or manager. If you find value, you can opt into team sharing later. Your data stays private until you explicitly grant permission.
10. How do I get started?
1st Step: Join the waitlist below (30 seconds)
2nd Step: We’ll email you when your spot in the beta opens (estimated 2–4 weeks)
3rd Step: Connect Slack or GitHub (or skip and upload a skills log manually)
4th Step: Review your first skill radar in under 10 minutes
No credit card required for beta.
11. What if my company already uses something like Eightfold, Gloat, or Degreed?
Good question. Those are talent marketplaces—they focus on internal job matching and career paths.
CapabiliSense is a skill radar—we focus on lightweight, real-time visibility without the complexity or cost of a full marketplace.
We can actually export data to those platforms. Many customers use us as the “skill sensor” layer and feed insights into their existing marketplace.
12. I have a question you didn’t answer. Where can I ask?
Reach me directly:
-
Email: [your-email]
-
Twitter/X: [@yourhandle]
-
Slack community (link in waitlist confirmation)
I personally answer every question within 48 hours. No bots. No support tickets.
