You have an idea, $50,000, and six months to prove it works.

The coffee tastes different when you're unemployed by choice.

You're sitting in your apartment on a Monday morning. The Monday after you quit your job at Corvane. Five years in product management, a solid reputation, and now... this. A laptop, a notebook full of ideas, and $50,000 from Kim Anderson, an angel investor who'd heard you describe this product over more dinners than either of you could count, and finally decided to write a check. Her money is for the company. You'll live on your savings.

"Six months," Kim had said. "Show me something real."

Your phone buzzes. Text from Alex, your best friend since college.

"You actually did it? You're insane. Also proud. Mostly insane. Lunch?"

You stare at the blank document on your screen. You've been thinking about this product for two years. Inside companies the size of Corvane, someone is at their desk at 11 p.m., copying customer data between two systems by hand, because the connector broke six months ago and nobody owns it. You lived it. You know why nobody fixes it. You think you can.

But knowing the problem and building a company are very different things.

Raul Santos, a senior engineer you worked with at Corvane, texted yesterday: "Heard you jumped. If you need a builder, I'm listening." You called him back last night, and the deal is set. He works for you by the month, paid $10,000 for every four weeks he builds and nothing while he waits. Then he added a term of his own: "If Kim's money runs out first, my invoices can wait for your first customer."

Four roads lead out of this apartment. You can only start down one.

Six months started this morning.

You call Raul. "Start today."

By noon, Raul is at the keyboard.

You give yourself eight weeks. Kim's six months are running, and they go faster than they sound.

"If it isn't real in eight weeks, it isn't real," you tell him.

Raul doesn't argue.

For eight weeks, you and Raul build. You spec features based on everything you hated at Corvane. The integrations that didn't exist. The manual exports. The broken notifications. Raul codes in long, silent stretches with his headphones on. You handle design and product decisions, and pretend you know what you're doing.

Week four, you're eating cold pizza at 2 a.m., reviewing pull requests. Week six, Raul figures out a way to cut the Salesforce sync time from minutes to seconds. Week eight, you deploy to production and just... stare at it.

It works.

There's just one problem: you don't have any users.

You built what you thought customers wanted. But you haven't actually talked to a customer since you started.

Six weeks. No building. Just people.

LinkedIn messages. Cold emails. Friends of friends. Introductions from anyone who will make one. Anyone who might have the problem you think you're solving.

Old habits win the first round. For a dozen calls you keep sliding into describing the product, and it takes you a while to see why the calls are useless. They say it sounds great. Everybody is polite. Nobody is telling you anything.

On call thirteen you try something different. You stop describing and ask a warehouse manager to walk you through last Tuesday.

She talks for forty minutes.

By conversation fifty-two, your notebook is full.

The problem is real, and it isn't automation. Call after call, people describe the same thing in their own words. Teams don't know what other teams are doing. Work goes missing between them not because it's hard, but because nobody can see it. The word you keep underlining is visibility.

One conversation you keep coming back to is Marcus Thompson's, a name more than one person handed you. He runs operations at a logistics company of 200 people, and he talks about the problem like someone who has lost sleep over it.

"If you built something that showed me where work gets stuck... not just moved it around, but showed me... I'd pay for that the day it works." He pauses. "How soon can you show me something?"

Kim emails once while all this is going on. "Where are we?" You send her a list of names instead of a demo. She doesn't mention the six months, and neither do you.

You don't have anything to show Marcus that does what he just described. But now you know what to build.

You can't shake the feeling that you need a partner. Raul will build whatever you hand him, but nobody tells you when you've handed him the wrong thing.

Last night you spent an hour arguing with yourself about pricing, and lost. You're not technical enough to build, not salesy enough to close, not experienced enough to know what you don't know.

You spend eight weeks meeting potential co-founders. Coffees. Calls. Trial projects.

Three candidates emerge:

Raul Santos. You know him, and he's already yours by the month, waiting for something worth building. Solid engineer. Doesn't love the business side but respects that you do. Would trade the monthly deal for 30% equity and a smaller salary.

Alex Rivera. Your best friend. Business background, great with people. Has a stable job and a mortgage. Nervous about the risk but genuinely believes in you. Would want 50% equity.

Dana Park. Successful founder, sold her last company for $40 million. Offering to be an "active advisor" for 1% equity and a monthly call. Not a co-founder, but she has already made every mistake you're about to.

You've spent $16,000 of Kim's money, most of it on paid trial projects with people who didn't make this list. You're still alone.

Sell it before you build it.

You call Marcus Thompson. He runs operations for a logistics company of 200 people, and when you ask who has this problem worst, his is the name you keep being given.

You tell him what you want to fix: work going missing between systems, with nobody owning the gap. Then you ask him to put money on it before you build a thing.

He listens like a man hearing his own complaint read back to him. Then he laughs at the second part.

"I'll have the budget," Marcus says. "But I'm not paying for a roadmap. Make it work against our Salesforce data within four months and I'll wire you $25,000 for a pilot. Miss it and the deal's dead."

That $25,000 would be your first revenue. But it's one customer. One very specific use case. One deadline.

Is this a product, or a consulting gig in disguise?