Fractional practice · Darren Card

I design how work gets done
when agents do the production.

Building software got cheap. The work moved to judgment: what is worth building, and whether what shipped actually landed.

Agents read, draft, and check. A person still makes every call.
On one team, “we got better” is a story.
Across a dozen, read the same way, it is something you can see.

Throughline is the working prototype: the whole method running on one company's public record, free to read. Nothing on this site is for sale. The paid work is the practice.

The whitepaper

Leave an address and the whitepaper opens straight away. The whole model in one place: the approach, the build, the did-it-land read, and the maturity ladder. You get a note when there is something to use, not a cadence.

did the onboarding revamp land?asked in plain words
ThroughlineImpactExample, from public sources
The read
Did what shipped actually land?
Agent-led deploys
Moved the metric it was aimed at.
landed
Onboarding revamp
Climbing, not yet at the bar.
watch
Self-serve upgrade
Shipped. Nothing moved.
stalled
The move · drafted for approval
Shipping is holding. Landing is where the gap is. Pull the next cycle onto the stalled bet before adding new surface.
Measured·A person approves
You ask in your own words. The answer comes back as blocks you can act on, built for the question, not a paragraph to interpret. Read from what is public. Put a dozen of these side by side and the pattern shows.
◆ The whole case, in six

Building software got cheap.

For forty years the expensive part was producing the work. That constraint moved, in software and well outside it, and almost every process a company runs was designed around the old one.

What that looks like

In a product org, Cursor writes the code and Claude Code opens the pull request. In a consultancy, a model drafts the estimate a senior specialist used to spend a day on.

1 / 6
◆ Three ways in

Pick the one that matches why you came.

All three are real. None of them needs a form first.

01 · Hire the work

The practice

I design the operating model and install the measurement underneath it. Two domains: software product orgs, and companies that run on expertise rather than code. Fixed scope, fixed price, named deliverables.

For a CTO, CPO, or COO with an AI mandate and a pilot that stalled.

Start with three days, USD $9,500
02 · See it running

Throughline

The working prototype. My whole thesis on agentic product strategy and operations, running against one company’s public record instead of asserted in an essay.

For anyone who wants to check the method before they trust the person.

Open the prototype
03 · Hire the person

Full-time

The same work owned end to end on one team, at CPTO, CPO, or VP Product altitude. Employee #1 through post-Series B.

For a founder or hiring team filling the seat rather than renting the work.

What I have built
The operating system

A team of humans and agents needs an operating system, not an org chart.

In 2015 you could run a product from a laptop, the way you read a car’s diagnostics. Agents move at racing speed, and you cannot steer that blind. So you build a pit wall: one screen showing the strategy, the design, the build, and how it sells.

The job did not change. One person still makes the call. What multiplied around them is the machine: the screens, the data, and the agents that read it.

FigureThe same job, on two different surfaces
2015 · one screen2026 · a wall of interfaces, one person reading it,and making the necessary calls
A personone owner each
The agentsnever a decision
Business fitDesign qualityTechnical fitFinal approval
Read the contextDraft the optionsCheck the rulesPropose the next move
The system, running

Throughline is the system above. Vercel is the illustrative example.

It is built and running against Vercel’s public record, as an illustrative example of a multi-product company. Fixed code does the math, so no number is guessed. Where it writes back to a tracker, a person approves the draft first.

The case study · one company, read end to end
One screen, read by one person.

The company on display is Vercel, read from the outside. It is built entirely from public information, labelled illustrative throughout, and never Vercel-confirmed. A real company you know, instead of a made-up one.

Open Throughline
Read from
  • Vercel engineering posts
  • Trust Center subprocessor list
  • Public Ship talks
What it shows
  • The did-it-land read
  • The pit wall
  • Human owns the call
  • Every answer traces to its source
Field notes
org design · 3 min

Agents broke the product org chart

Production got cheap. The chart we built around it stopped showing who's building the value.

The org chart is a theory of where value comes from. We drew the current one when building was the expensive part. Engineers built. PMs decided what to build. Designers shaped it. The boxes reflected who held which scarce skill. Making the thing was the hard part, so the people who could make it sat at the centre.

Agents took the hard part away. One person with good tools can now build in a few days what a small team used to spend a quarter on. I have done it, and I have watched others do it. When building gets cheap, a chart organised around who can build stops describing much.

What's scarce now is judgment, in two specific forms. Deciding what's worth building. Knowing whether what shipped landed. Both were always in the job. Neither was the constraint, so neither showed up as the thing you hired and promoted for. Now they're the work, and they don't map to the boxes.

The chart also can't show that part of the team is no longer human. Agents do the read, the draft, and the check. They gather the background, write the first version, and check it over. That is a large share of the daily work, and none of it fits in a box with a headcount attached. What stays human is the call. One decision, one owner. An agent can draft the call and check the call. It never makes the call.

That gives you a better unit of organisation than the function: the decision. Which segment to serve. What the pricing tier is. Whether to keep the launch or pull it. Each one carries exactly one name. That person should be able to say what they knew when they decided, and how much of it was measured versus still a bet. Run that list for a quarter and you'll learn more about your org than the chart ever told you.

It also settles a question people keep getting wrong. The tidy story is that PMs win and engineers lose, or the reverse. Neither. The people who carry over are the ones with taste, meaning they can tell a good idea from a passable one, and taste is spread across every function. An engineer who always had a view on what was worth building is worth more now. A PM who ran process and routed decisions is exposed. So is a designer who shipped pixels without a point of view. The line runs through the functions, not between them.

So the chart misleads three times. It says the valuable people are the ones who can produce, when production is cheap. It sorts by function, when the thing that predicts value cuts across functions. And it counts only humans, when a real share of the output now comes from agents no box accounts for. Two people with the same title, one indispensable and one overhead, look identical on it.

A reorg won't fix that, because the boxes were never the problem. What helps is smaller and less satisfying. Write down the decisions your org makes. Put one owner on each. Note whether the evidence behind it was measured or still a bet. Then, a quarter later, go back and see which ones landed. The people you need are already in your org. The chart is not pointing at them.