March 2026 · Data
By the Numbers
Activity heatmaps, weekly token volume, model distribution, and cost comparisons — the raw data behind 78 days of building with AI.
Activity Heatmap
Jan 28 – Mar 30 · Each cell = one day · Intensity = session volume
Weekly Token Volume
Millions of tokens by model · Jan–Mar 2026
Model Mix
Share of total tokens
The ROI
My inputs vs. equivalent senior developer cost
Multi-Model Footprint
Claude Code + Codex · Deliberate routing, not redundancy
The median Codex session is one message — a surgical escalation when Claude produces a wrong diagnosis or gets the same bug wrong twice. The 42 web searches and ~2,900 tool calls in those sessions are mostly codebase exploration: reading files, tracing call stacks, isolating root cause before any fix is proposed.
Codex token estimates are derived from local session logs (visible text only), not billed API totals. Actual billed tokens would be higher due to system prompts and context packing.
What Was Shipped
5 production systems · All deployed · All serving real data
Work with Nektar
This is what Nektar does for clients — embed in your domain, build the analytical layer, ship software that would have cost 100× more the traditional way.
Book a free data auditHow the data was collected
The charts on this page are pulled from a single corpus of work between February and June 2026. Every session ran through Claude Code or the Anthropic SDK with structured logging on, so the activity heatmap is literal session count per day, the token chart is the actual API usage ledger, and the model mix reflects which model handled each turn rather than a post-hoc estimate.
Two numbers tend to surprise people. First, the token-volume cumulative line crosses 100M about eight weeks in — heavy use of subagent fan-out, not a single agent running long. Second, the ROI bars compare equivalent contract-engineer hours at SLC rates, not list-price API cost; that's the comparison that matters when you're deciding whether to invest in an AI workflow versus hire.
For the narrative around what changed week to week — workflow shifts, failure modes, validated tactics — see the companion piece on 40 Days of Daily AI Engineering. For the workflow patterns that produced these numbers, the FYBY essay and smoke-testing notes cover the operating model.