Running, updated most weeksBuilt solo
A standing read on where the product investment goes, and what it returns.
The read layer for a product organisation. It wires into the tools a team already runs, reads the operating model end to end on a schedule, and traces strategy to the work and the work to outcome. This read runs against public record only, so the method is checkable before a single tool is connected.
Every figure is computed by code. What is inferred is labelled inferred, on the surface.
The same four questions, answered without asking the company for anything.
Vercel is the worked example because its record is public end to end. The company was not consulted. Every figure below is computed from that record, and the console is the same one you can open.
- 01Choices
What did they choose to build?
- 02Velocity
How fast does it actually move?
- 03Landed
Did any of it land?
- 04Stop list
What should stop?
Illustrative model of Vercel, built from public information.GET /api/v1/landed
Each row carries the outcome someone committed to, the metric it is read on, where it started and the bar it has to clear. The verdict is whatever the distance between those two says it is.
- Lift new-user activationWatch47% of 60%
The onboarding revamp is working: activation has climbed to 54% from 47% and is trending toward the 60% bar. The top growth lever, and it is moving in the right direction.
activation rate · bar authored - Keep spend predictable as agent usage scalesWatch62% of 90%
Cost per agent workload is the lever; surprise usage bills are the failure mode.
Predictable spend · bar authored
Both rows read watch, and neither reads landed. The bar is set and the number is moving toward it, which is not the same claim as arriving, and this surface will not make the stronger one on the weaker evidence.Illustrative
Illustrative model of Vercel, built from public information.GET /api/v1/read
The read arrives ordered. Each move carries the metric it moves, the owner it routes to, and a projected band rather than a single confident number.
- 01
Overhead is already low, so the next improvement is moving review into evals
Routes to Operationscoordination overheadOperating modelMove review into the eval gate and agent observability, not more process. The healthy band is near 8%.
Projected liftProjected+4.5 projected · band +3.5 to +5.5 · n=2 · last measured +4
Learned land rate75% · n=2
- 02
v0 to deploy attach is the drag on the revenue plan
Routes to GTMv0 to deploy attachGo-to-marketTreat this as a product and pipeline problem together. The v0-to-deploy path is where generated apps become deploys, and where Sales and Marketing create and convert pipeline. Ship the path, set the attach target with GTM, instrument the ramp, and trace it to the v0 initiatives. Product builds the surface; GTM runs the motion on it; both stay true to the same number.
Projected liftProjected+5 projected · band −4.8 to +14.8 · n=1 · last measured +5
The band crosses zero, so this move could measure as a regression.
Learned land rate67% · n=1
- 03
A chosen bet is under-staffed
Routes to OperationsEnterprise trust, agent-safe allocationAllocationThe owning team's call: move 5% of effort from Compute that scales to agents back to plan, restore Enterprise trust, agent-safe first this cycle, accept slower Compute that scales to agents progress as the cost, re-check next month. The drift just makes it hard to ignore.
Projected liftProjected+2 projected · band +0 to +4 · n=2 · last measured +3
Learned land rate50% · n=2
Illustrative model of Vercel, built from public information. The same deterministic engine the web read uses (deriveSignals over the operating model). No model invents a number. Numbers are derived, not asserted.
A working console, password gated. Opened on request.The conversational surface and the wiring
- Current
- 12% of shipped entries
- Healthy band
- 35–50%
- Norm
- 41% · this company's own 2023 baseline
- Modelled from
- entries_naming_outcome / total_entries
- Reads true if
- The classification pass was reviewed by a person this cycle and the changelog format has not changed. Both hold right now.
- Why did this move?
- What would move it most?
- Show me the inputs
Volume is not the problem. There are 3.1x more entries than two years ago. What changed is that entries naming a customer outcome fell from 41% to 12%, and the drop starts in the same quarter the release cadence doubled. The work is still shipping. The record of why it shipped stopped being written.
- entriesPublic changelog · 1,340 entries, 8 quarters
- outcome_classClassified against a written rubric, human-reviewed
- baselineSame changelog, first half of 2023
Every read is scoped to one subject and grounded in the model above. Point the same engine at a connected stack and the identical surface becomes a live read.Illustrative
- ChangelogPublic release notesFresh · 12m ago
What actually shipped, when, and whether the entry names a customer outcome or only a mechanism
- entries
- ship_date
- outcome_class
- Docs & pricingPublic product surfaceFresh · 1h ago
How many surfaces exist to learn, and which ones changed shape between releases
- surface_count
- pricing_change
- Job postingsPublic org signalFresh · 6h ago
Where headcount is actually being pointed, which is the plainest statement of priority a company publishes
- role_mix
- org_signal
- Investor commentaryPublic earnings recordStale · 3d ago
What leadership said the priorities were, in their own words, on the record
- stated_priority
- What they decided to buildentries grouped by surface + stated_priority
- Which bets show they landedoutcome_class over trailing 2 quarters
- Where effort and outcome splitrole_mix vs outcome_class by surface
- What the next call probably isranked by gap x reversibility
Nothing is inferred from a source that is not listed here. When one goes stale it is marked, and the reads that lean on it inherit the mark rather than being quietly served as current.Illustrative
Watch it run on a real company
Open, with no password and no sign-in. It lands on the orientation tour rather than a cold console, and the operating read above comes from the same public API you can call yourself.
No affiliation, no endorsement. The reads above are the console’s own output, unedited.
Wired into the tools a team already runs, read on a schedule, decided by a person.
The question on top, four lenses reading it, the connected sources underneath.
- ChoicesWhat did they choose to build?Lineare.g. Linear
- VelocityHow fast does it actually move?GitHube.g. GitHub
- LandedDid any of it land?ClickHousee.g. ClickHouse
- Stop listWhat should stop?Sentrye.g. Sentry
- Linear
- GitHub
- Vercel
Slack
Salesforce- Stripe
- Sentry
- Datadog
Honeycomb- ClickHouse
Connected sources · wired once, read every cycle
- 01Wires into the stack you already run
Linear, GitHub, Vercel, Sentry, Datadog, Stripe and the rest, connected once and read every cycle. No new place for the team to go, and nothing to keep up to date by hand.
- 02Scores against one model
Nine channels, read the same way every cycle, so this quarter is comparable to the last one rather than to whatever was interesting that week.
- 03Separates measured from inferred
No number without its source. Anything derived is labelled on the surface, and a read that comes back thin says so instead of rounding up.
- 04Leaves the call to a person
Agents read, draft and check on a schedule. Approval is one step with one name on it, and nothing closes until the metric that was named up front moves.
Nine channels, read the same way every cycle. Six stages, one human gate.
An F1 crew does not stare at one chart. It watches live channels and acts on the few that need a call. Every channel feeds one loop: agents read and draft on a schedule, a named person approves, and nothing closes until the metric moves.
The trace from company bet to product, keeping roadmap and revenue aligned.
Telemetry, reliability and customer requests, plus the competitive read.
Traced to the work, held to the landing bar, judged after launch.
Committed against planned, deploy frequency tracked past the ship date.
The sales and marketing partnership: motions, targets, ramps.
Team health and capacity, execution risk surfaced early.
The instrumentation layer, deterministic and eval-gated.
Allocation, planned against actual, so the right bets are staffed.
Each bet against target, forecast from trend, and whether it landed.
The full loop, and the gap it closes
Strategy, delivery and outcome live in three different tools, and the work that moves between goal and outcome is exactly what goes unmeasured. That gap is what the loop reads across.
At the end of a quarter, this is what the board gets.
Four answers, a script that reads in under a minute, the portfolio it rests on, and one decision carried in with a number attached.
One company is one company.
Reading a company from the outside shows what it shipped and said. What the team declined, what it cost, and what was decided in a room are the parts a connected stack reaches and an engagement gets at.
- What it is
A working console, built solo, wired to read a real stack and currently pointed at one company so the method can be checked before anyone hires me.
- What it is not
Not a product. No login, no trial, no waiting list, and nothing here is for sale.
- Who it is for
Anyone deciding whether the way I read a product organisation holds up. The console is the evidence; the engagement is the work.
- What it costs
Nothing, and there is no upgrade. The read on this page is the whole of it.
More companies, read the same way. Until then the sample is one, and the read says so.
The principles it runs onThroughline reads a company from the outside. Your own record goes deeper.
From public signal to your real stack is where the judgment starts, and where the engagement does too.