Every builder has a “why.” For some, it’s a technical challenge, for others, it’s market opportunity. For me, building CapabiliSense started with a much simpler emotion: frustration.
Over the last decade, I’ve watched talented people stall in their careers. Not because they lacked intelligence or drive, but because no one—including themselves—could clearly sense what they were truly capable of.
Today, I want to share why I left the traditional playbook behind to build something new.
The Problem: The Broken Signal of “Capability”
Let’s be honest. Most capability assessments today are a performance theater.
-
Resumes are historical documents, not predictive tools.
-
Annual reviews are backward-looking rituals that create anxiety, not growth.
-
Certifications prove you can pass a test, not that you can solve a real problem.
We are living in a skills-first economy, but we’re using 20th-century tools to measure 21st-century potential. The result? Brilliant people get overlooked, teams misfire, and leaders make decisions based on gut feelings rather than signal.
I call this the Capability Gap. It’s the space between what someone can do and what the organization thinks they can do.
The Insight: Sensing, Not Just Measuring
Most platforms measure outcomes. They ask, “Did you finish the task?”
CapabiliSense is different. It asks, “What are you ready to do next?”
The core insight behind CapabiliSense is that capability isn’t a static data point—it’s a dynamic signal. It changes with context, collaboration, and curiosity. You can’t capture it with a quarterly survey. You have to sense it in real-time.
That’s where the “Sense” in CapabiliSense comes from.
We are building a system that listens to work patterns, respects privacy, and intelligently maps hidden strengths before they become obvious.
The Three Pillars of CapabiliSense
When I started architecting this platform, I wrote down three non-negotiable principles. These form the DNA of everything we build:
1. Privacy-First Intelligence
We do not spy on keystrokes. We do not sell data. CapabiliSense uses differential privacy and edge computing to ensure that capability insights are aggregated and anonymized. Your data is yours.
2. Actionable Over Analytical
Too many tools give you a beautiful dashboard and zero next steps. CapabiliSense doesn’t just say, “Your team lacks Python skills.” It connects you to micro-learning, mentorship matches, or project-based challenges inside the workflow.
3. Growth-Oriented, Not Gatekeeping
This is personal for me. I’ve seen capability tools used to fire people or deny promotions. CapabiliSense is built for development, not discipline. The goal is to unlock potential, not to filter people out.
What I’ve Learned So Far (Building in Public)
Building CapabiliSense hasn’t been a straight line. Here’s the truth:
-
Data modeling is the hard part. Defining what a “capability signal” looks like across different industries is like nailing Jell-O to a wall. But we’re getting closer every week.
-
People are hungry for this. Every time I demo the prototype, I hear the same thing: “I’ve been waiting for something that does exactly this.” That validation keeps me going at 2 AM.
-
Simplicity is the ultimate feature. Our biggest challenge isn’t adding features—it’s deciding what to leave out. CapabiliSense must feel effortless, not overwhelming.
Why Medium? Why Now?
I’m writing this on Medium for two reasons.
First, I believe in building in public. The feedback loop from thoughtful readers like you makes the product better. When I share a design decision or a failed experiment, your comments often unlock the solution.
Second, this problem is too big to solve alone. Whether you’re a founder, an engineer, an HR leader, or just someone who feels stuck in their own career—I want you in this conversation.
The Road Ahead (And How You Can Help)
Over the next 90 days, I’ll be shipping:
-
The first live beta of the CapabiliSense Individual Growth Module.
-
An open-source library for “capability sensing” algorithms.
-
A series of case studies from early design partners.
Here’s how you can get involved:
-
Try the beta. [Link to waitlist]
-
Share your horror story. Reply to this post with the worst “capability assessment” failure you’ve witnessed.
-
Just follow along. Hit the follow button to watch me make mistakes, iterate, and (hopefully) build something that matters.
The Bottom Line
I’m building CapabiliSense because I believe the most successful organizations of the next decade won’t be the ones with the most talent. They’ll be the ones with the most clarity about the talent they already have.
We are drowning in resumes and starving for insight.
It’s time to stop guessing and start sensing.
Let’s build.
