Product Management Without Revenue Made Me Better

The short version

The highest-stakes product of my career, at Crisis Text Line, had no revenue model, and it made me a better product leader than any monetized product I ever shipped. Mission-driven product management removes the one metric most teams hide behind. When there is no revenue to grow, you cannot tell yourself the product is working because the number went up. Every decision gets judged on pure outcome, did this help a person in crisis, with nothing to launder a weak call through. That is a harder test than revenue, not an easier one, and revenue turns out to be a crutch that lets product managers avoid judging real value. AI agents now force the same outcome-first discipline, because once building is cheap, effort stops being a proxy for impact too. Here is what working without revenue taught me, and why it is suddenly the most relevant lesson I have.

For most of my career, revenue answered the question I was supposed to be answering myself. Did this product matter. The number went up, so yes. I told myself that for years, at Adobe, at Salesforce, across four startups. Then I ran product at Crisis Text Line, where the thing we shipped helped people text a counselor in the worst moment of their lives, and there was no number to hide behind. It was the most uncomfortable, clarifying product job I have had.

Revenue is a crutch, and I leaned on it for a decade

Here is the part nobody says out loud. Revenue lets you avoid judging value.

A feature ships, conversion ticks up two points, and you call it a win. You never have to ask whether the product got better for the human using it, because the revenue line already told you a story you wanted to hear. I did this constantly. I shipped things that nudged a metric and degraded the experience, and I let the metric absorb the blame. The dollar was doing my judging for me.

Take the dollar away and you are naked. At Crisis Text Line, there was no conversion to point at. The question on every roadmap was blunt. Does this help a person in crisis get to a calmer place faster. You cannot fake your way through that with a chart. Either the change improved the outcome for a real human or it did not, and you had to have an opinion about which, and defend it.

“

Revenue lets product managers avoid judging real value. The number goes up, so you never ask whether the product got better for the human using it.

”

That is a harder job, not an easier one. People assume mission work is softer because there is no commercial pressure. The opposite is true. Commercial pressure gives you an excuse. Mission work removes it.

Pure outcome is a brutal scoreboard

The first quarter at Crisis Text Line broke a habit I did not know I had. I kept reaching for proxies. Engagement. Session length. Messages sent. All the metrics I had spent twenty years optimizing.

None of them were the point. A longer session could mean a better conversation or a person in more distress. More messages could mean engagement or confusion. Every proxy I reached for, the team could puncture by asking the only question that mattered. Did the person end up safer.

That forced me to define outcome with a precision I had been allowed to skip. Not a number that correlates with value. The value itself. We had to build the measurement around the actual change we were trying to create in a human being, then judge every decision against it. It is exactly the discipline I now teach as the impact loop, and I learned it the hard way, in the one job where I had no choice.

When the scoreboard is pure outcome, the work changes. You stop shipping things because they are clever or because they move a vanity metric. You ship the thing that changes the outcome, and you can prove it, or you do not ship.

What I got wrong on monetized products

Going back to commercial product after Crisis Text Line, I saw my old habits with new contempt.

At a couple of my startups, I had run roadmaps where revenue impact was the tiebreaker on every call. It felt rigorous. It was not. It was a way to avoid the harder argument about whether we were creating real value, because real value is hard to measure and revenue is easy. I had been optimizing for the measurable proxy and calling it discipline.

The mission product taught me to flip it. Define the outcome first, even when it is hard to measure, then find or build the measurement. Do not let the easy metric define the goal just because it is easy. This is the difference between a team that is busy and a team that is moving something real, and it maps directly onto why survivorship bias quietly wrecks product judgment. You see the products that monetized, you do not see the value they destroyed on the way there.

AI agents force the same discipline now

Here is why a story about a product with no revenue model is suddenly the most relevant thing I can write.

For decades, product had two crutches. Revenue, which let you avoid judging value. And build effort, which let you avoid it too. If something was hard to build, it must matter. We dignified six-month projects with their own difficulty.

AI agents kill the second crutch the way Crisis Text Line killed the first. When an agent ships a working prototype in an afternoon, effort stops being a proxy for impact. You can no longer point at how hard something was as evidence it was worth doing. The cost collapsed, so the alibi collapsed with it.

What is left is the same naked question I faced at Crisis Text Line. Did this improve the outcome for the customer. Not did it ship, not was it impressive, not did the metric twitch. Did the real outcome move. In my current work at Falkster.AI, the entire loop is built on listening agents that pull the actual outcome a customer is trying to reach, then dispatch other agents to build toward it. There is nowhere to hide effort or revenue in that loop. There is only the outcome.

“

Mission work killed my revenue crutch. AI agents kill the effort crutch. Both leave you alone with the only real question: did the outcome move.

”

The product managers who will struggle in the next few years are the ones who built their whole judgment around proxies. Revenue went up. The project was big. The launch was loud. When building is nearly free and the customer outcome is the only honest scoreboard, those proxies stop working, and a lot of careers were built entirely on them.

What the crutch was hiding

The uncomfortable lesson is that the crutch was never holding me up. It was holding me back.

Every year I let revenue do my judging, I got worse at judging. The muscle atrophied because I never used it. Crisis Text Line forced me to use it again, and within a quarter I was a sharper product leader than I had been at companies paying me three times as much to ship monetized features.

The skill that came back was the only one that survives the AI shift. Defining the outcome you are trying to create, with no proxy to launder it through, and judging your work against that and nothing else. That is the job now. It was always the job. Revenue and effort just let most of us avoid it.

Pick one thing to try this week

Take one feature on your current roadmap and delete its revenue justification entirely. Pretend the product has no revenue model. Now defend the feature purely on the outcome it creates for the user. If you cannot, you just learned something the revenue line was hiding from you. Do that for three items on your roadmap and you will find at least one you were only building because a number told you to. That is the muscle a mission product builds, and it is the exact muscle the AI era is about to demand from everyone.

Sources: Silicon Valley Product Group, on outcome over output · Harvard Business Review, on mission and measurement · Lenny Rachitsky, on product metrics that matter