What running TrimCI actually looks like

Fieldnote Labs builds a logistics SaaS: fourteen engineers, twelve active repositories, a heavyweight integration suite and nightly e2e pipelines. CI is owned by Marta, a staff engineer, because she broke it last. A release just slipped two days — a nightly pipeline had been silently red since the previous Thursday, and "re-run until green" is muscle memory nobody logs. She knows CI is bad; she cannot say which pipeline to fix first or what the waste costs.

She creates a TrimCI organization (14-day Business-equivalent trial, no credit card), installs the GitHub App — Actions and Metadata read-only, never repository contents — and ticks all twelve repos for the 60-day backfill. In org settings she sets a $75 fully-loaded hourly rate and two SLO targets; on the billing card she excludes one drive-by external contributor.

The estimated-loss card reads ≈$10,200 for the 30-day window — modelled as 40 engineer-minutes per failure at her rate plus a 15% rework tax, an estimate, not payroll. The report turns that into a fix list: the cost Pareto shows two pipelines carrying 71% of cumulative failure cost, the flaky-pipelines section flags the integration suite at a 44% flip ratio, retry tax counts 18% of runs retried (≈1,900 wasted minutes), and error fingerprints cluster the failed-log tails into named problems. MTTR puts the nightly's median recovery at 52 hours — and the "silent red nightlies" callout names it explicitly.

Marta quarantines the flaky tests, the team fixes the test-container issue the fingerprints pointed at, and nightly ownership joins the on-call rotation — TrimCI never touched the pipeline; it ranked the fire. Six weeks later the movers section documents the worst repo's failure rate falling from 22% to 9% over decisive runs, and estimated loss drops by about $4,100 a month.

The monthly bill: 11 active contributors × $9 on Team = $99/month. Members who only read dashboards cost nothing.

Ferrite Labs is a seed-stage devtools startup: eight engineers, nine private repositories, all-in on GitHub Actions. The CTO still merges code daily, owns the infra bill and the investor update — and nobody owns CI. The Actions invoice grew ~40% across two quarters with zero attribution, and tools demanding code access were a non-starter for private repos.

The afternoon the invoice landed he connected TrimCI: the GitHub App's read-only, zero-code-access permissions made it a two-minute security decision even on private repos. He set an hourly rate, a compute rate per runner-minute, and a failure-rate SLO target.

The 30-day baseline was uncomfortable: an 11.6% failure rate over decisive runs, ≈$4,970 of modelled failure loss against $488 of attributed compute spend, and — the real find — the trigger breakdown's "silent red nightlies" callout showing the e2e pipeline red nine straight days. On day 8 of the trial, automatic spike detection fired: the 24-hour failure rate had jumped from 6% to 31% after a runner-image change, and the AI batch (self-hosted model — logs never leave TrimCI's servers) named the affected repos.

The team rolled back the runner image the same day; the catch was TrimCI's, the fix was theirs. By trial end the failure rate sat under the SLO target, and the report's executive summary became the delivery-health slide in the investor update. Post-trial the org continued on Free — the two highest-cost repos stayed active, nothing was deleted, and the longer window reopens over the already-collected history the moment they upgrade.

The monthly bill: 6 of the eight engineers actually trigger pipelines, so Team costs 6 × $9 = $54/month. Bots are excluded automatically.

Marta leads seed investments at a small EU fund. Her portfolio company — three employees, none technical — outsources all development to a 12-person software agency contracted for five FTE. She has a $250k milestone tranche to release, and her only progress signal is the agency's own status slide. The agency refuses repo access, reasonably: their IP, other clients' code. She could not read code anyway.

TrimCI dissolves the stand-off because it never reads source code: the agency connects the GitHub App (Actions and Metadata read-only — a runtime allowlist blocks anything else in code) and invites Marta as a member. Her own login, read-only, free on every plan — dashboard-only members are never billed.

Her weekly pulse is the Total Runs card: ~500 runs in the 30-day window, a daily sparkline with no dead weeks — pipeline runs are hard-to-fake exhaust of real development. The failure calendar shows weekday clustering consistent with steady work. Before each steering call she generates the PDF report herself; on the call, the agency walks her through the billable-contributors view: four distinct humans triggered pipelines in the last 30 days against five contracted FTE — a factual conversation starter, not a verdict. (The fifth is a designer who rarely touches CI. Runs prove activity, not hours — this is delivery observability, not time tracking.)

The tranche was released on evidence plus slides, not slides alone. Six weeks and two steering calls later, the failure rate is under the agreed target and MTTR fell from 5.1 to 3.2 hours — and Marta arrives at steering calls with informed questions instead of hopeful ones.

The monthly bill — paid by the agency, not the investor: 4 active contributors × $9 on Team = $36/month. Marta's seat: $0.