How I built my starting framework before writing a single line of code

I wanted to start a project.

Not just any project — something that could fund my life without owning it. No investors. No employees. No meetings. Just enough recurring revenue to be free.

But every time I tried to start, I'd open a code editor, pick a tech stack, get three days in, and lose interest. Or I'd read someone's framework online, try to follow it, and realize it wasn't built for what I actually wanted.

So I backed up. Way up. And I started asking better questions.

---

The Two Frameworks Everyone Talks About

Two frameworks kept coming up in my research:

Marc Lou:

1. Find a market you care about
2. Copy a product people already pay for
3. Add your signature to make it yours

Peter Thiel (Zero to One):

1. Bet on a Contrarian Truth
2. Start by Dominating a Small Market
3. Strive to be a Monopoly

Most people treat these as competing philosophies. I started seeing them as two different phases of the same process.

Thiel helps you think before you build. Marc Lou helps you execute once you know what you're building.

The mistake I was making — and I think most solo devs make — is jumping straight to Marc Lou without doing the Thiel work first.

---

The Question Nobody Asks First

Before topics. Before markets. Before pain points.

The real first question is: what are you optimizing for?

Because "starting a project" means completely different things depending on the answer:

• Money fast → copy a proven product, charge immediately, keep scope tiny
• Equity / asset building → build something that compounds over time
• Learning a new skill → the project is the excuse, growth is the win
• Reputation / audience → build in public, the product is secondary to the signal
• Lifestyle / freedom → fund your life without owning it

Most advice assumes you're optimizing for growth or money. But those aren't the only games.

I'm optimizing for Lifestyle / Freedom. That changes everything downstream — the market I pick, the product I build, the tech stack I choose, the features I say no to.

---

You Can't Observe What You're Not Consuming

Here's where I got stuck next.

Peter Thiel asks: "What contrarian truth do you believe that most people don't?"

My honest answer was: I don't know yet. I haven't consumed enough signal to have a thesis.

Jeff Bezos didn't stumble on the statistic that the internet was growing 2,300% per year. He was deliberately consuming the right content at the right level. That input led to an observation. That observation led to a contrarian truth. That contrarian truth became Amazon.

Most people consume entertainment. The 0.1% consume signal.

Where signal lives:

• Hacker News
• Product Hunt
• YC, a16z, Sequoia blogs — they publish what they're betting on
• Reddit — specifically the 2 and 3 star complaints in niche subreddits
• G2 and App Store reviews — same idea
• Indie Hackers — builders sharing revenue and process
• Google Trends, Exploding Topics

The shift isn't consuming more — it's consuming with one question in mind:

"Where is something growing fast but being served poorly?"

---

Why I Start With a Market I Care About

Here's where I almost made the classic mistake.

Every framework I read told me to start with a pain point. Find a problem. Solve it.

But I've abandoned too many projects to believe that's the whole story. If I don't care about the space, I'll get bored before I get to revenue. Every experienced solo builder knows this pattern.

Marc Lou's first principle isn't "find a pain." It's "find a market you care about." He said it first for a reason.

Caring about the market is the fuel. It also focuses your input system — instead of consuming signal from everywhere, you're consuming from one space you already understand. That's a massive advantage.

---

The Sequence I Built

After all of this thinking, here's the sequence I landed on:

1. Market I care about — not a topic, not a technology, not a pain point. A space I'm genuinely interested in.
2. Build an input system inside that market — consume signal with a question in mind.
3. Observe — look for gaps between what exists and what's possible.
4. Form a contrarian truth — what do I believe that most people in this space haven't caught up to yet?
5. Validate — do people already pay for something here?
6. Filter through Lifestyle / Freedom — does building this add to my freedom or subtract from it?
7. Execute with Marc Lou's framework — copy a proven model, add my signature, ship.

I didn't get this from an article. I built it by questioning every assumption along the way.

---

The Part Most People Skip

Marc Lou's third principle: "Add your signature to make it yours."

Most people think that means design choices or feature differentiation. Maybe. But I think it starts earlier than that.

Your signature is how you think. It's the observations you make that others don't. It's the questions you ask before you write a line of code. It's the filter you run every decision through.

If you do the work before the work — the thinking before the building — your signature is already in the product before you've built anything.

That's the part that can't be copied.