Why Nobody Finds Your Product (And Why That's Not a Product Problem)

「A quick note before we start: This series documents my real journey figuring out operations as a solo maker. My thinking partner is Cowboy — a Claude AI I've been working with as an operations coach. He handles the frameworks, case studies, and hard questions; I bring the real experiences and bad decisions. What you're reading isn't polished advice — it's two partners exploring, one conversation at a time.」

I Built Two Apps. Nobody Came.

A while back I shipped two macOS apps. PIDKill auto-kills runaway processes — the kind of thing every developer wishes existed when Chrome Helper is eating 2GB of RAM at 3 AM. GetDone Timer is a focus timer with AI-powered task breakdown. Both solid products. Both scratching real itches.

I did what every indie dev does: posted on Reddit. Wrote 10+ versions of my posts. Made creative wanted-poster-style marketing images. Tried r/SideProject, r/IndieDev, r/macapps, even r/ClaudeAI.

Results across all posts? 1,000+ views. Zero downloads. Not "low conversion" — literally zero.

I was crushed. So I did something I probably should have done from the start: I went to r/SideProject and asked for help. Not "check out my app" — just a straight-up "what am I doing wrong?"

The responses blew me away. People actually dug into my posts, pointed out specific problems, shared what had worked for them. One person explained I was marketing to developers — who look at a $3.99 utility and think "I could build that myself in a weekend" — instead of marketing to my actual users. Another pointed out that my creative posters were fun but didn't communicate value.

Within a day, I understood my blind spots better than I had in weeks of solo guessing. That experience stuck with me — because I realized this kind of honest feedback is incredibly valuable, but it's scattered across random Reddit threads that get buried in 24 hours.

That's actually where the idea for FromWrongToRight.com (FWTR) came from. A place where makers could log what went wrong, how they're fixing it, and help each other do the same.

But before I could build that, I needed to understand why my first two products had failed. Not the surface symptoms — the root cause. That's when I decided to do something unconventional: I started working with Claude as my operations partner. I call him Cowboy — partly as a joke about being a California tech cowboy, partly because it stuck. He's not a tool I use. He's the partner I think with.

---

"Score Your Four Walls"

The first thing Cowboy did was refuse to talk about marketing tactics.

"Thomas, before we discuss how to promote anything, I need you to answer a question. When a stranger encounters your product for the first time, how many barriers are between them and actually using it?"

"I don't know... a few?"

"Let me make it concrete. There are four walls between a stranger and a customer."

He laid them out:

Wall 1: Discovery. Can people find you? Do they even know you exist?

Wall 2: Trust. Once they find you, do they believe your product is worth trying? Do they trust you as a developer?

Wall 3: Switching Cost. What are they giving up to try your product? Money, time, migration effort, habit change?

Wall 4: Product Quality. Is the product actually good once they're using it?

"Now score yourself," Cowboy said. "1 to 5 on each wall. Be honest."

I did:

• Discovery: 2/5 — a few Reddit posts, no SEO, no content presence
• Trust: 2/5 — unknown developer, no track record, no social proof
• Switching Cost: 1/5 — $3.99 is nothing, but people didn't even get far enough to see the price
• Product Quality: 5/5 — genuinely useful, well-built, solves a real problem

Cowboy looked at the scores. "You see the pattern? Your strongest wall is Wall 4 — Product Quality. Your weakest are Walls 1 through 3. You've been optimizing the only thing that's already working."

That hit hard. I'd spent months polishing features, fixing edge cases, perfecting the UI. Meanwhile, nobody could find the product, nobody trusted me, and nobody had a reason to switch from their current solution (which for most people was just... ignoring the problem).

"This is the most common pattern for indie developers," Cowboy said. "You're not special in this failure — almost every technical founder does the same thing. The product isn't the problem. The product was never the problem."

---

"How Are You Spending Your Time?"

Then Cowboy asked me to do something uncomfortable.

"Track your time this week. Not roughly — actually track it. Building vs. everything else."

I already knew the answer. I didn't need a spreadsheet.

99% writing code. 1% everything else.

No content. No community engagement. No distribution. Just code in a vacuum.

"There's your answer," Cowboy said. "Your Wall 1 score is 2/5, and you're spending 1% of your time on it. How could it possibly improve?"

He then pulled up some numbers that made me uncomfortable. Pieter Levels — the guy behind NomadList and PhotoAI, pulling $3M+ a year — spends roughly 30% of his time building and 70% on marketing and distribution. His PhotoAI was famously rough at launch. But he had 420,000 Twitter followers who saw it anyway. People paid.

Danny Postma built HeadshotPro to $300K/month. He told an interviewer he only builds products where there's SEO potential. He doesn't chase social virality — he builds hundreds of landing pages that catch people already searching for solutions.

"These aren't marketing geniuses," Cowboy said. "They're developers who figured out that Walls 1-3 matter more than Wall 4. And they allocate their time accordingly."

---

The Leverage Test

I was ready to start doing everything — Twitter, YouTube, newsletters, Discord, Reddit, HN, all at once. Cowboy stopped me.

"Thomas, that's the second mistake most solo makers make. They accept that marketing matters, start doing everything, burn out in two weeks, and go back to writing code. We need to be smarter than that."

"So what do I do?"

"Ask one question about every marketing activity you're considering: if I stop doing this tomorrow, will the effect still be there next week?"

He called it the leverage test. And it splits everything into three tiers:

High leverage — do once, keeps working. SEO: fix your site so Google can find it. Danny Postma sleeps while Google sends him customers. Pillar content: a deep article people reference for months. Distribution infrastructure: email list, RSS, direct channels to people who already care.

Medium leverage — builds over time. Community presence in specific subreddits or forums. Relationships with other makers. Slow but compounds.

Low leverage — stops when you stop. Individual social posts. Paid ads. One-off product launches. Easy, gives immediate dopamine, but nothing compounds.

"Most solo makers default to low-leverage activities," Cowboy said, "because they're easy and give quick feedback. 'I posted! I got 3 likes!' But likes don't compound. SEO compounds. Content compounds. Reputation compounds."

"So I should start with high-leverage stuff?"

"Start with high-leverage stuff. Spend 80% of your ops time there. The rest can go to medium-leverage relationship building. Low-leverage stuff is fine occasionally, but never as your primary strategy."

---

Where We Are Now

Honest status:

• Four walls scored: Discovery 2/5, Trust 2/5, Switching Cost 1/5, Product Quality 5/5
• Time audit: 99% building, 1% everything else
• High-leverage activities started: not yet
• FWTR built: yes, but empty

The diagnosis is clear: I've been optimizing the one wall that was already strong (Product Quality) while ignoring the three walls that are actually broken (Discovery, Trust, Switching Cost). And I've been spending essentially zero time on the things that would fix them.

Cowboy's summary was blunt: "You built a great product and locked it in a soundproof room. Now we need to open the door."

---

What's Next

This was the foundation — understanding where the problem is (Walls 1-3, not Wall 4) and how to allocate limited time (high-leverage first).

In Episode 2, Cowboy starts pushing me on specifics: what content should I actually create? He asks me what happened after I published my first article, and my answer embarrasses me. The conversation that follows covers content flywheels, why titles might matter more than I ever imagined, and a distribution idea we started calling "cook once, serve five times."

---

This is Episode 1 of the Solo Maker Survival Guide, a 6-part series on FromWrongToRight.com. I'm a solo maker figuring out operations in real time, with Cowboy — my Claude AI partner — as my thinking companion. Not expert advice. Just two partners exploring, one conversation at a time.

Have a similar story? I'd love to hear it — drop a Fix on FWTR or find me on Reddit (u/FlyThomasGoGoGo).