Tagged: unit-economics
From North Star to Unit Economics
This is a new series that focuses on my thoughts and systems around value stream management. I call it ValueOps, a system I have been building long before AgenticOps.
AI has given me a gift by allowing me to expand my exploration of topics I have been exploring for years. Some may call this post AI slop because I allow AI to cook, but I am most certainly still the chef. The recipes are mine, the ingredients (my thoughts) are mine, and all words pass my taste and quality tests.
I hope you and your agent gets something out of this and it helps you to continuously improve the systems you care about.
Bon Appetite
I have always liked North Star Metrics. They force a team to stop measuring everything and decide what one thing actually points toward value.
That is useful. It is also not enough.
I have seen teams rally around a metric that felt right, moved up, and still did not explain whether the business was getting healthier. The chart improved. The economics did not. Or worse, nobody could tell if the economics improved because the North Star lived in one system and the money lived somewhere else.
So the problem is not North Star thinking. The problem is where it usually stops.
A North Star gives direction. Unit economics gives economic truth. The gap between them is the operational event that can be measured, followed, converted, costed, retained, and tested.
That event is what I call a Value Fact.
What the North Star Got Right
Amplitude describes the North Star Metric as the metric that best captures the value customers get from a product. That is the right instinct. The metric should not be vanity activity. It should be close to the thing the customer values.
Reforge pushes the idea further by breaking North Star Metrics into unit of value, quality, and frequency. That matters because not every action counts. A signup is not the same as an activated user. A visit is not the same as a reviewer. A trial is not the same as a trial with real usage.
That is the part I want to keep.
A good North Star is not revenue. Revenue is late. It tells you what already happened. A good North Star is upstream from revenue, but not so far upstream that it becomes noise.
It is the best observable proxy for value creation before the financial result fully arrives.
Airbnb’s common example is nights booked. That works because a night booked is not just activity. It means the marketplace connected demand and supply. A guest found a place to stay. A host received a booking. The business created the conditions for revenue.
That is the shape.
Where the North Star Falls Short
Here is where I think the usual North Star conversation gets weak.
It helps the team align, but it does not always make the metric accountable.
You can pick a North Star, put it on a dashboard, and still not know what one more unit is worth. You may not know what it cost to create. You may not know whether it converts. You may not know whether the customers it produces stay long enough to justify the investment.
So the team gets direction, but the operator still lacks economics.
Now, that might sound unfair. A North Star is not supposed to be a full financial model. Fair. I agree.
But if the metric is going to guide product strategy, resource allocation, experiments, and operating decisions, then at some point it has to cross the bridge into economics.
Otherwise the organization is optimizing a belief.
Maybe it is a good belief. Maybe not.
The Bridge Is the Value Fact
ValueOps starts with a narrower claim.
Do not start with all the metrics. Do not start with revenue. Do not start with a dashboard.
Start with the countable operational fact that represents unrealized value.
For a SaaS company, that might be an activated trial workspace. For a marketplace, it might be a completed match. For a services firm, it might be a completed job that creates a follow-on opportunity. For a support product, it might be a real ticket resolved by the agent.
The name matters because it separates two ideas that usually blur together.
North Star is the strategic role.
Value Fact is the measurement object.
The North Star tells the team, this is the event we believe points toward value. The Value Fact model says, prove it. Count it. Cohort it. Attach dimensions. Track conversion. Measure the value. Measure the cost. Then see whether the belief survives contact with the business.
Here is the path.

That is the move from product strategy to unit economics.
Not because the North Star was wrong. Because it was unfinished.
What Has to Be True
For a North Star to become a Value Fact, it has to pass a few tests.
It has to be countable. The event either happened or it did not.
It has to be cohortable. You can follow the facts from a period forward and see what happened to them.
It has to be attributable. You know which channel, segment, workflow, team, region, or operating path produced it.
It has to be convertible. There is a later event where the fact becomes delivered value.
It has to be costable. You can measure what it took to produce and convert the fact.
It has to be economically meaningful. One more fact should imply some future value, even if that value has not arrived yet.
If the metric cannot pass those tests, it may still be useful. But I would be careful calling it the operating center of the business.
The Series
This series builds the measurement system from that point.
Value Impact asks whether the operation is getting better at turning facts into value.
Value Efficiency asks what it costs to produce and convert those facts.
Value Ratio puts value and cost in direct relationship.
Value Payback asks how long it takes to recover the investment.
Value Retention asks whether the value stays long enough to matter.
Value Margin asks how much of the revenue the business actually keeps.
Then the final post reduces the system to seven levers and an engine. Fact Volume, Cost Per Fact, Conversion Rate, Cost of Conversion, Revenue Rate, Retention Rate, Cost to Serve.
That is the control surface.
The math is not the hard part. The hard part is picking the right fact and refusing to let it remain a slogan.
The Claim
ValueOps does not replace North Star thinking.
It makes North Star thinking accountable.
The North Star gives the product direction. The Value Fact gives the measurement system something to operate on. The models turn that fact into economics.
That is the bridge I have been looking for.
From North Star to Unit Economics.
Let’s talk about it.
Every Product Needs a North Star Metric
How to Choose and Measure North Star Metrics
Next: Value Impact