Created from a single voice note with Agent Craft

Somebody asks me how I scope a new company idea and I always give…

Somebody asks me how I scope a new company idea and I always give them the same answer, which is that I don't. Not in the way they mean, anyway. They want to hear about customer interviews, validation surveys, spreadsheets full of TAM calculations. And I get it. That sounds like the responsible thing to do. But in my experience, potential customers will tell you something in an interview and then do something completely different with their wallet. Not because they're lying. Because they don't actually understand their own problem well enough to describe it accurately. That's your job. Not theirs. So the real answer is just get going. Pick a space that has some genuine interest to it, something you can see value in, and start building. Not a finished product. Something rough that you can show people inside of a few weeks. Because the feedback you get from showing someone a real thing, even an ugly half-built thing, is worth about twenty times what you get from asking them hypothetical questions about a thing that doesn't exist yet. Here's where most people go wrong with this. They treat early conversations as validation. They hear something positive and they think that means they're right. Then they get six months down the road and discover that the thing they built doesn't match what anyone actually wants to pay for. That's not a research failure. That's a failure to stay in motion and keep adjusting. The discipline isn't in the upfront scoping. It's in how fast you can read a signal and move. And that means showing what you're building early and often, not waiting until it's presentable, and paying attention to what people say and do. Not just what they say. What they do is the signal. What they say is noise, at least partially. Something to remember here is that most people giving you feedback don't understand the problem you're solving, even if they're the customer experiencing that problem. They can tell you something feels off, or that they'd never use a particular feature. They're much less useful at telling you what you should build instead. That's your call. So the process, if you want to call it that, looks like this: pick your space, build something real, show it to people as fast as possible, watch how they react, and be prepared to move quickly when the evidence tells you to. You'll find your way through building, not through asking. The founders I've watched spin their wheels for years are usually the ones who spent too long trying to de-risk the idea before they started. The ones who move are the ones who figure it out.