Central Valley
Central Valley
Tim × Claude

A field report

Two operators.
One shop.

What happens when a building-supply IT lead pairs an AI collaborator for six months of real shipping work — across an ERP rewrite, a ground-up ERP of its own, a helpdesk bot, an autonomous shadow-org, business operating systems, and a lot of late nights. the receipts, in order.

See the receipts Watch the feed
Last commit shipped — · loading…

By the numbers

Receipts — not promises.

Pulled from our self‑hosted Gitea. Toggle the comparison to see what one operator typically ships without an AI partner.

Commits authored
0
Feb 7 — Aug 17, 2026 (192 days)
commit history doesn't lie
17× baseline
Lines of code
0
hand‑written, generated code excluded
production — not ChatGPT toy code
3.9× baseline
Live projects
0
active repositories
measure twice, ship once
3.7× baseline
Code volume
0
total source size on disk
heritage hardware, modern stack
5.1× baseline

Baseline = typical mid-market IT lead, solo, held at the same daily rate across this six-month window. Adjust your priors.

Cadence

How the work shipped.

Commits per month, February through August 2026. Seven months of shipping — and the pace still climbing — what happens when an AI partner joins a shop that already knows what it wants.

Peak month
—
Last 90 days
—
First commit
—

Daily output

198 days. 149 green ones.

One square per day, Feb 1 through Aug 17. Darker red is heavier shipping. Click any day to see what went out the door.

MonWed FriSun
Less More

The stack

What we build with.

A working IT lead's polyglot reality — TypeScript for the ERP, PowerShell for the helpdesk floor, Python for the agents, PHP for the legacy stack we still keep alive.

    12
    Languages

    The portfolio

    Seven builds, one shop.

    Hover any card to see what's inside. Every one of these went into production for Central Valley or one of its dealers.

    Filter

    The reel

    1,600 commits, in order, accelerating.

    Every Web-App commit from Feb 7 to today (Aug 17) — starting at the pace you'd read each one, ending at the pace they actually shipped. That's the whole point.

    Scroll into view to play — 1,600 ships, in order.
    Commit
    001
    of 1600
    Date
    —
    day 1
    SHA
    —
    Web-App
    Velocity
    0×
    commits per second
    tap replay to run again
    Live commit feed — Tim × Claude, last 60 ships

    The proof is in the changelog.

      The math

      What you'd hire to do this.

      Read the commits. Categorize the work. Add up what a normal company would have to staff. Then look at how it actually got built.

      In a normal company

      The team you'd post to LinkedIn.

      Click any role to see real commits from that work stream.

      • 1.0

        Senior Backend Engineer

        TypeScript / Node / SQL Server — ERP integration lead

        $220K
        • Stockout-risk perf: rewrite to mirror overstock's query shape 60s → 5s
        • API accuracy sweep — line-level cost for exec reporting
        • Hotfix: PerRuleConversion coverage + ProductPrice sellPrice source
      • 1.0

        Frontend Engineer

        React PWA / Vue — UI & UX across Web-App and BOS

        $190K
        • Documents: truck icon linking to Journey Map on orders with a journey
        • Two-column layout for Agendas — Upcoming and Past side by side
        • Web+addin: apply Central Valley design system (fonts, tokens, layout)
      • 1.0

        Data / SQL Engineer

        BI & pricing models — BisTrack data lineage

        $180K
        • Inventory UOM normalization via ol.StockPerConversion
        • UOM conversion: by-PerType-match frame selection
        • Phase 3 Paperclip watchers: GL anomalies, AR aging delta, count variances
      • 0.75

        DevOps / SRE

        CI/CD — release safety — production firefighting

        $210K
        • CI guard: catch v851-class migration apostrophe bugs before deploy
        • Hotfix: escape apostrophe in v851 changelog — API was crash-looping
        • Update CI/CD for new branch strategy (dev/production/master)
      • 1.0

        IT Systems Engineer

        PowerShell / AD / M365 / hybrid identity

        $140K
        • winagent: add hourly self-update scheduled task
        • lifecycle: route Paylocity updates to hybrid AD + BisTrack
        • phishing-sweep: skip unlicensed users and guests in tenant listing
      • 1.0

        AI / ML Engineer

        Multi-agent systems — local GPU inference

        $240K
        • All 16 agents on local GX10 inference — zero cloud tokens
        • GX10 tensor parallel cluster live, NemoClaw sandboxing operational
        • Add Gauge competitive pricing agent + scraper toolkit
      • 0.75

        Product / PM + QA

        Prioritization — testing — the work that doesn't show up in git

        $170K
        • Phase 1 / 2 / 3 Paperclip watcher rollout (receipts, price, GL)
        • Quarterly planning, Talent Assessment rename, module access control
        • Day 2 daily intelligence brief — 7 agents, 8 pages, branded PDF
      Total headcount 0 FTE
      Quarterly comp ~$0K
      Year 1 (loaded) ~$0M

      In reality

      The actual setup.

      One IT director with a day job and a Claude subscription.

      200
      Users supported
      company-wide, every layer
      35
      Servers managed
      on-prem & cloud, every patch cycle
      1
      Direct report
      reports analyst — not IT, not engineering
      0
      Engineers on staff
      all IT & code runs through Tim
      40+
      Day-job hours
      tickets, on-call, planning
      spare
      When this was built
      nights, weekends, before dawn
      Engineering team hired none
      Recruiters engaged none
      Onboarding ramp none
      Tools licensed Claude Team — $200/mo
      Annualized tooling cost ~$0/yr

      the rest is just leverage.

      What it would have cost
      ~$1.6M / yr
      ÷
      What it actually cost
      ~$2,400 / yr
      =
      Multiplier
      ~667×

      What it means

      Three reasons it matters.

      Beyond commit counts — the real outcome of a senior operator paired with a thinking partner that doesn't sleep.

      01

      Velocity without staff

      1,600 commits to a single ERP integration in six months — the kind of throughput a startup pays a four-engineer squad for. Central Valley got it from one operator and an AI partner.

      02

      Real production work

      Not demos. Not slideware. The Web-App ships behind a v2026.08.1738 tag with CI guards and migration-apostrophe checks — because real software breaks in real ways.

      03

      Across the whole stack

      ERP TypeScript, helpdesk PowerShell, Paperclip Python agents, an LBM ERP built from scratch, century-bos planning systems, decompiled C# business rules, a kiosk fleet and an SMTP signature relay. One operator, every layer.

      The pitch

      Buy the engineer, get the bench.

      Hiring me means hiring a team. I bring deep institutional context — years inside Central Valley, the BisTrack data model, the helpdesk floor, the reseller network — and Claude brings tireless code generation, pattern recognition, and 24-hour pairing.

      Together we ship at the velocity of a small startup, with the domain knowledge of a tenured department head, for the cost of one person.

      that's the trade.
      Tim D Domain · Direction · Decisions
      ×
      Claude Code · Cadence · Coverage