Mike Litman
"But Does It Make Any Money?"
A TALK BY MIKE LITMAN

"But Does It Make
Any Money?"

The question that kills more creative careers than bad work ever will.

The scene

You show a friend something you built. Something you're proud of. Their first response:

"Yeah but you're just missing a bit about how any of it's made money."

That sentence stays with you longer than it should. Not because it's wrong. Because it skips everything that matters about why you built it.

01
Observation 01

The question beneath the question

"Does it make money?" sounds practical. Responsible, even. But when someone asks it before asking what the thing does, who it's for, or why you made it, they're telling you their only framework for value is transactional. They can't see the work. They can only see the invoice.

Transactional lens Skips the work Skips the why
Two worldviews
The Builder

Ships things. Learns by doing. Treats every project as a live brief that builds skills, portfolio, and reputation. Knows that revenue is an outcome, not a starting condition. Comfortable with the gap between making something and monetising it.

The Auditor

Evaluates things. Waits for proof before engaging. Measures output in pounds and status. Often hasn't shipped anything recently but has strong opinions about what's missing from yours. Confuses being critical with being smart.

02
Observation 02

To be fair

The question isn't always bad. A mentor who asks "how does this become sustainable?" is helping you think further ahead. A collaborator who asks "who pays for this?" is stress-testing the idea. The difference is timing and intent. A good question opens doors. The same question, asked to shut something down, slams them.

Intent matters Timing matters Relationship matters
03
Observation 03

The real cost of that question

Every creative career has a fragile middle period. You've started something but it hasn't paid off yet. This is where momentum matters most. The people around you either add fuel or pour water. "But does it make money?" is a bucket of cold water disguised as helpful advice.

Momentum killer Disguised as pragmatism Optimised for inaction
Translation

When someone asks "but does it make money?" perhaps what they're really saying is: "I don't know how to value something I wouldn't have built myself."

04
Observation 04

Comfort is the real opponent

By your late thirties, most people have optimised for safety. Mortgage, routine, predictable career path. Someone still experimenting and building and launching things is an implicit challenge to that entire value system. It's not that they think you're wrong. It's that they need you to be.

Optimised for safety You're a mirror They need you to be wrong
05
Observation 05

It gets worse with age

In your twenties, people celebrate ambition. In your thirties and forties, ambition makes people uncomfortable. The social contract shifts. You're supposed to have settled. Picked a lane. Stopped experimenting. So when you haven't, when you're still building and trying and launching, it holds up a mirror that not everyone wants to look into.

20s: celebrated 30s–40s: uncomfortable The contract shifted You didn't
06
Observation 06

Who actually asks this?

People in salaried jobs ask it more than freelancers. People who stopped making things ask it more than people who are still making things. People who chose safety ask it more than people who chose curiosity. It's never the person in the middle of building something who hits you with "but does it make money?" They're too busy shipping.

It's a tell Not about you About them
The follow-up

"No one really does any of this just for the fun of it."

Actually, some people do. And those are the people who end up building the most interesting things. Because when you're doing it for the love of the craft, you take risks that a spreadsheet would never approve. You explore ideas that don't have a clear ROI. You build taste and instinct that can't be outsourced. The fun is the competitive advantage.

The alternative

What builders say to each other

"This is cool, tell me how you built it."

"I sent it to someone who might find it useful."

"What are you working on next?"

"Can I pick your brain about how you did X?"

Curiosity before criticism. Generosity before judgement. That's the difference between someone who wants you to win and someone who needs you not to.

The real answer

Not yet. And that's fine. Because the people who build things before the business model is obvious are the ones who end up defining the market.

07
Observation 07

Revenue is a trailing indicator

Reputation, skills, network, taste, portfolio, speed. These are all leading indicators that compound over time. Every project you ship, even the ones that don't make a penny, builds the infrastructure for the ones that will. The people who only see the revenue line are reading the scoreboard in the first quarter and calling the game.

Skills compound Portfolio compounds Revenue follows
08
Observation 08

You've seen this pattern before

YouTube launched with no revenue model. Twitter spent years figuring out how to make money. Amazon didn't turn a profit for nearly a decade. Craigslist is one of the most visited sites on earth and barely tries to monetise. The pattern is consistent: the people who build something genuinely useful first and worry about the business model second tend to outlast the ones who start with a spreadsheet.

Usefulness first Revenue second Every single time
The real balance sheet
What revenue measures

One thing. Whether someone paid you. That's it. It says nothing about the quality of the work, the size of the idea, or whether it changed how you think. Plenty of lucrative projects are forgettable. Plenty of unpaid ones are career-defining.

What building gives you

Agency. The ability to make something from nothing. Speed. Taste you can only develop through repetition. A body of work that speaks for itself. A network of people who found you through your output. These are assets that no employer grants and no redundancy can take away.

20+

Live projects. None of them were commissioned. All of them were built because the idea was interesting enough to pursue. Each one sharpened a skill, tested a hypothesis, or opened a conversation that wouldn't have happened otherwise.

Culture Terminal
The Relevance Index
Oishii London
Modern Retro
First Out
The Pattern
Pub Guide London
Little London
The Visible Shelf
Taste OS
Curio
Buggy Smart

Find the people who ask "what are you working on?" not "what's it worth?" They're the ones who'll push you forward.

Note to self

Stop asking permission to build. The gatekeepers are just auditors with job titles. The best things you'll ever make will start without approval, without a budget, and without anyone asking you to.

The honest question

What if it never makes money?

Then I'll have spent my time building things I believe in, getting better at a craft I love, surrounded by work I'm proud of. I'll have a portfolio that proves I can think and ship, not just talk. I'll have skills that transfer to anything I do next. There are worse outcomes. Most of them involve never trying.

THE PUSHBACK
Where this breaks down

The revenue question isn't always hostile. Sometimes it's a genuine attempt to help you focus. Building without a business model isn't freedom, it's a hobby. The people asking 'does it make money?' might be the ones keeping you honest.

Revenue isn't the enemy. Asking too early is.

CONNECT THE DOTS

This deck defends building before the business model is obvious. The Weekend Sprint proves it works: from nothing to Stripe payments in 48 hours. The revenue question gets answered by shipping, not by planning.

Final thought

Ship anyway.

The people who need your work to fail in order to feel comfortable about their own choices will always find a reason to dismiss it. Build for the people who get it. They're out there. And they're not asking about your P&L.

Acknowledgement

Thanks to the friend whose question inspired this entire presentation.

Mike Litman

If this resonated, you're probably a builder.

Say hello. I'd love to hear what you're working on.

mikelitman.me · hello@mikelitman.me

Continue from slide ?