What’s Your Time to Magic?

The metric I keep coming back to when a big vision is at risk of becoming a slow build.

A colleague of mine has a question he asks before he’ll let anyone start on a new idea: what’s the total addressable market, and is it actually big enough to be worth going after?

It’s a good filter. I use a version of it myself - I’ve written before about thinking in four directions to pressure-test whether an idea has room to grow forwards, backwards, deeper, and up and out. In a world where the time to build is collapsing toward zero, the bar for what counts as “big enough” keeps rising. You don’t want to spend your one shot building a sliver of a future.

So let’s say you’ve done that work. You have a massive vision. The market is real. You’re convinced.

Now what?

This is the part I’ve been thinking about a lot lately. Coming up with a good vision isn’t trivial - but it’s only part of the equation for success. There are two other hard parts that don’t get talked about enough.

One is making sure someone else doesn’t just walk in and take your spot while you’re building behind closed doors.

The other is making sure you can actually build a product users love. Not all features are created equal, especially in the AI age. Two teams can ship the same feature on paper and get wildly different results, because the magic isn’t in whether the feature exists - it’s in the taste underneath. It’s the difference between hiring a wedding photographer and handing your phone to a twelve-year-old. Both are technically taking pictures.

De-risking is not the same as building everything

A trap I see with a big vision is the feeling that you have to build all of it to prove the vision is real. That you owe the world a complete picture before you’re allowed to ship anything.

You don’t.

What you actually need to do is de-risk. Get something - the smallest thing that carries the core of the idea - in front of users as fast as possible, and then watch what they do. Are they staying? Are they coming back? Are they telling other people? At a big company, are internal stakeholders getting excited? There’s no single right signal, but the strongest ones tend to be hard to argue with.

The point of getting something out is that it forces a different kind of evidence than the one most people lean on.

Competitor launches are not evidence that you can build the right product

Here’s a pattern I see a lot. Someone has a big vision. They point at a string of competitor launches in adjacent space and say: see, the market agrees with me, this is the right area to be building in.

That’s a good signal that the space is interesting. I track these things too.

But it tells you nothing about whether you are the one who can actually build the right product in that space. A strategy doc doesn’t tell me what the product experience you want to build actually is. It doesn’t show me you have taste. It doesn’t show me you know how to make something users want and love and use.

The only way to demonstrate that is to build it. And then ship it, to prove people like what you’ve made.

Time to magic

Which brings me to the metric I’ve been sitting with: time to magic.

Once a user enters your product, how long until they hit a moment that makes them go whoa? Not “this is interesting.” Not “I see what they’re going for.” Magic. The kind of win that makes them want to tell someone.

The shorter that distance, the better.

NotebookLM’s audio overviews are a clean example. Add a source. Click a button. A few minutes later you have a podcast that sounds like two real people who actually read the thing. About five clicks to magic.

What makes it magic isn’t that the feature exists. It’s the quality of what comes out the other end. The taste in the voices, the pacing, the way they riff. Anyone with API access could technically build “turn a document into a podcast.” Almost none of those versions would feel like magic.

We’ve been climbing the same hill on Pomelli. You can take a genuinely bad cell phone photo of your product, click once, and we’ll turn it into a real photo shoot - one that actually feels like it belongs to your brand, not a generic stock template. You could do a watered-down version of this by dropping the same photo into Nano Banana with the prompt “make this better.” You’d get something a little nicer. You wouldn’t get magic.

The magic is in everything we do for the user behind that one click. Picking the templates that work for their photo. Pulling in their business DNA. Doing the editorial work they didn’t know they needed. The single click is the surface. The taste underneath is the product.

Two questions, in order

So when I’m pressure-testing an idea now, I’m really asking two things, and the order matters.

First: is the vision actually big enough to be worth the build? Have you thought far enough into the future that what you’re making won’t be a sliver of someone else’s product in two to six months?

Then: what is the smallest, sharpest moment of magic you can put in front of a user, and how fast can you get them to it?

The first question keeps you from building something too small. The second keeps you from spending two years building something nobody gets to feel.

You need both. But the one I want to call more attention to is the second.

What’s your time to magic? And how much smaller can you make it?