tokenthread
private beta
// ai impact engine · for engineering orgs

every ai token, mapped to the work it shipped.

tokenthread is the only product that ties llm consumption to the prs, tickets, and commits your teams ship. every team on one board. cross-team work split. shadow ai surfaced. no manual tagging. by monday of week two.

request beta → see the activity board ↓
// six questions your tools can't answer

your ai stack can tell you what it spent.
not what it shipped.

  1. 01 what did this week's tokens actually ship?
  2. 02 which teams are getting the most agent leverage?
  3. 03 which projects are ai-leveraged — and which are stuck?
  4. 04 which teams ship more code with agent help than without?
  5. 05 when agents fail, what work gets wasted?
  6. 06 which prs would never have shipped without ai?
// the answer

tokenthread answers all six. by monday of week two.

× no manual tagging · × no proxies · × no sql
see the engineering dashboard ↓
// the activity board · spend → pr acme inc · this week

every token, attributed. or counted as missing.

team activity · this week
live · 60s
// org spend · this window
284.4M
235.2M on 25 PRs·49.2M unattributed (17.3%)·13% from agents
spend → pull requests
each cell is one PR, sized by tokens. hover for detail.
mergedreview / opendraft / closedunattributed
rank · teampull request map (cell = tokens)
01growth▲
68.5M
5 engineers · 5 PRs
unattributed15.8M
02infra
58.5M
8 engineers · 8 PRs
unattributed8.9M
03frontend
52.9M
6 engineers · 3 PRs
unattributed7.3M
04platform
48.6M
7 engineers · 5 PRs
unattributed8.8M
05data eng
35.0M
4 engineers · 2 PRs
unattributed5.8M
06appsec
20.8M
3 engineers · 2 PRs
unattributed2.6M
// 284.4Mtotal ·235.2Macross 25 PRs ·13%from agents ·49.2Munattributed (17.3%)hover a tile for PR detail
// monday in slack
top teams + agent share per team, weekly digest in-channel. /tt-expert for ad-hoc lookups.
// cross-team work, split
a PR touching two teams is split across them. never double-counted.
// unattributed, visible
tokens that didn't ship show as hatched tiles. nothing hidden.
// new teams, eased in
teams onboarding to ai or running sensitive work: full capture, no public rank. opt-in.
// from token to outcome, in 2 hops

capture, then correlate. that's the whole pipeline.

01

capture

metric collector · agent-agnostic

a metric collector per engineer captures metrics from the tools you already use — claude code, codex, aider, cursor. no ide plugin, no proxy, no workflow change.

02

correlate

git anchors · session match

every session is bound to the pr or ticket it produced. cross-team work is split across teams. unattributed tokens stay visible as hatched lanes.

// drill: from org, to team, to the sub-team that shipped helio · this week

the org map shows it.

// focus
// pivot
// window
top-level teamsteamssub-teamspull requestsengineering177Mdata + ml37.7Msecurityops + sredesign + researchunattributedgrowth53.3Mplatform44.7Mfrontend43.4Minfra35.8Mdata eng28.0Mappsecsreml platformdesign syspipelines28.0Macquisition27.9Mmonetization25.4Mapp23.3Mstoragedesign-systemsdkauthcomputereliabilityinfra-secmodelsapiproduct-secproductPR-1880 · feat: tokens v3 p…PR-980 · feat: 4 staging + …PR-2210 · feat: ab harness …PR-2270 · feat: shared expe…PR-991 · feat: custom sql l…PR-3901 · feat: typed sdk c…PR-1820 · feat: settings re…PR-1844 · fix: 11 axe viola…PR-2244 · feat: stripe link…PR-220 · feat: supply-chain…PR-3812 · refactor: collaps…PR-540 · feat: online store…PR-3940 · fix: webhook repl…PR-4821 · feat: dual-write …PR-228 · refactor: least-pr…PR-2284 · perf: lazy-load p…PR-3829 · feat: redis-backe…PR-2289 · perf: preconnect …PR-680 · feat: keda trigger…PR-4901 · test: stabilize 1…PR-410 · feat: chart palett…PR-3915 · docs: sdk migrati…PR-4839 · fix: replay verif…PR-4855 · chore: drop legac…PR-688 · docs: cold-start r…PR-4960 · docs: reliability…PR-4912 · test: retry harne…
token flow — width = tokensunattributed — tokens with no PR
// swipe to see all lanes →
tokens this wk
412.6M
outcomes
47 PRs · 23 tickets
tokens / PR
2.02M
shadow ai
2.3%

every lane is tokens flowing through four columns: top-level team → team → sub-team → the pr they shipped. wide lanes are high-leverage flows. hatched lanes are tokens with no linked pr. the activity board ranks teams.

// monday morning, in-channel

the team board,
in your engineering channel.

by 9am monday, the weekly impact digest lands in a shared engineering channel: top teams, what they shipped, agent share per team — every rank one click from the merged pr. no private leaderboards, no pulled-aside conversations. engineers can /tt-expert any topic without leaving the thread.

$ /tt-expert checkout v2
#engineering·142 members
tokenthreadAPPmonday 9:00 am
weekly impact snapshot. your org spent 412.6M tokens. here's what each team shipped.
top 3 teams this week
01
growth▲ +9▲
·shipped checkout v2 ab harness · 3 variants
·cut /pricing LCP 300ms · merged
·21% of tokens came from agents this week
77.9M
02
platform▼ -2
·refactored auth middleware · redis sessions
·opened sdk v2 codegen pipeline · in review
·9-bug P2 rollup · 1 of 9 merged
76.4M
03
frontend▼ -1
·published tokens v3 to npm · merged
·fixed 11 axe violations · merged
·settings rebuild on tokens v3 · in review
61.3M
try /tt-expert checkout v2 to see who's already shipped this
// what week two looks like

every team's ai impact, in slack by monday.

// request access
work emailstep 1 of 3
// stays here. no list-buying, no enrichment.
// in the box
+ private dashboard at your-org.tokenthread.ai
+ weekly impact digest in slack, ready for monday
+ every llm session correlated to a pr or ticket
+ learning mode for new teams — full capture, no rank
+ shadow ai surfaced — unapproved tool spend, day one
// ready to see your own?

book the pilot.

30-day private beta, gated to one engineering team at a time. drop your details and we'll be in touch.

jump to the form ↑
// not yet?

track our build.

monthly progress notes — what shipped, what's next, what we learned. one click to unsubscribe.

// monthly progress notes.