AI-era work intelligence,
for the person doing the work.

See what your work actually is, classified, with your trajectory month over month.

read-only GitHub access · no training on your data · private by default
problem

Activity metrics were always a proxy. In the AI era, they break.

Productivity looks fine until you ask what kind of work got done, and who is being automated out of a job they still appear busy in.
the visible
Commits, tickets, PRs. These count output, not nature. A commit that wires GPT into a form field looks identical to one that designs a new architecture.
the invisible
Reviews, mentoring, unblocking, design docs, cross-team wiring. The work that makes teams function goes uncredited because nothing counts it.
the consequence
The people whose work is most automatable look productive right up until the moment they do not. Nobody sees the cliff. Not the company, not the employee.
See how workdna classifies this
how it works

Three quiet steps. The classifier rules stay with the manager.

The role page on workdna shows a Software Engineer IC2 profile defined by the manager: a job description snapshot and a numbered list of KPIs that drive how the classifier grades each commit.
01Manager defines what your job actually is. The classifier rules stay in their hands.See it live →
See a sample report
audiences

Built for the person doing the work, and for the team around them.

Two views of the same data. Different incentives. Zero leakage from the personal to the team side.

Trajectory

Your work mix over weeks and months. See whether you're drifting toward maintenance or deepening in new capability, before anyone else notices.

Automation risk

A rolling score grounded in template density, novelty, and cross-module coupling. Specific patterns flagged, not vibes, so you can act on them.

Skill shifts

Career moves rooted in what you already do well, not a generic map. If you review a lot of infra PRs, that's signal, and we tell you where to point it.

Built employee-first, with no leaderboards, classified semantically, and crediting the invisible work.

workdna · principles · v1
Read the four refusals
roadmap

Starts with engineering. Ends nowhere near it.

Software commits are the densest, most structured signal of knowledge work, which makes engineering the right place to prove the method. The same classification layer maps cleanly onto product, design, analytics, ops, chat, meetings, and hiring loops.

now · live
GitHub
engineering
GitHub
on the roadmap
LinearJira
product
Linear · Jira
Figma
design
Figma
Jupyter
analytics
Jupyter
Google CalendarGoogle Docs
ops
Google Calendar · Google Docs
Slack
chat
Slack
ZoomGoogle Meet
meetings
Zoom · Google Meet
Bring this to your team
Contact

Tell me what you're trying to figure out, and I will write back.

Replies come from me, not a queue. If you want to bring workdna to your team, share what your team looks like and what you would want to see first.

replied to within 2 business days
no marketing list, no auto-responder

See the shape of your work. Before someone else does.

read-only · private by default · no training on your data
five threads · one signature
for humansfor machines