Introduction
Have you ever built an app and then realized you had no clear idea how to sell it?
That’s a common trap in indie development. Building the product is hard, but figuring out who it’s for, what value it creates, and how to communicate that value is often even harder.
I recently launched Focusnest, an iOS ambient sound mixer designed for focus, relaxation, and sleep.
On the product side, I felt pretty good about it. It supports mixing multiple sounds, saving presets, built-in timers, 1/f fluctuation for more natural sound movement, and full offline use. On paper, it seemed strong enough to compete.
But when I started thinking about go-to-market, I got stuck.
As an ambient sound app, the market is crowded. I could explain the features, but I wasn’t convinced they gave people a compelling reason to care.
So instead of jumping straight into promotion, I treated go-to-market itself as a set of hypotheses.
That process helped me realize something important: Focusnest probably shouldn’t be positioned as just an “ambient sound app.” It should be positioned as a focus-switching app — a tool that helps people enter deep work faster.
In this article, I’ll walk through how I organized those hypotheses, what changed in my thinking, and how that shaped the first version of my go-to-market strategy.
The App I Built: Focusnest
Focusnest is an iOS app for focus, relaxation, and sleep using customizable ambient soundscapes.
Its main features include:
- White noise, brown noise, and pink noise
- Natural sounds like rain, rivers, fire, waves, birds, wind, and thunder
- Mixing multiple sounds at the same time
- Saving and restoring presets
- A built-in Pomodoro-style timer
- 1/f fluctuation for more natural sound variation
- Full offline support
I felt confident about the product quality.
But product quality and go-to-market are two different problems.
That’s where many indie products get stuck: “I built it” does not automatically become “people want it.”
The First Feeling That Something Was Off
At first, I naturally tried to position it as an ambient sound app.
But something felt off.
- The ambient sound market is crowded
- Spotify and YouTube are viable substitutes
- Existing players like Noisli and Endel are already strong
- “This looks nice” didn’t feel like a strong enough reason to switch
In other words, I had built the product, but I still hadn’t found a clear market context for it.
That’s an easy place to stall.
You can keep polishing features forever, but if you haven’t clarified who it’s for and what job it really does, your messaging stays blurry.
The Real Mistake
The mistake was treating feature quality and buying motivation as if they were the same thing.
I could explain things like:
- You can mix sounds
- There’s a timer
- It uses 1/f fluctuation
Those are features.
But features alone don’t answer the question:
Why would someone want this now?
What users actually want is not the feature itself, but the change in state the product gives them.
So I Organized the Problem as Hypotheses
At that point, I used KaizenLab, a hypothesis validation tool, to structure my thinking.
Instead of treating go-to-market like a vague marketing task, I treated it like a set of testable assumptions.
Not:
- “How do I promote this?”
But:
- Who is this most likely to resonate with?
- Are users really looking for “sound,” or are they looking for something else?
- What makes this meaningfully different from substitutes?
- Which channel is most likely to create early traction?
- What framing makes the value obvious?
A rough summary looked like this:
| Area | Hypothesis |
|---|---|
| Target | Remote workers, students, and creators who struggle to switch into focus mode |
| Core problem | They are not looking for “nice sounds.” They are looking for a trigger to start work or study |
| Differentiation | Not the number of sounds, but the focus-onboarding experience created by mixing, presets, and timer integration |
| Channels | X, Zenn, Qiita, App Store ASO |
| Messaging | Use cases are stronger than feature lists |
Once I made it visible, “the market feels crowded” stopped being a vague concern.
It became a clearer strategic question:
Who is this for, what is it really helping them do, and through which channel should I explain that first?
The Key Insight: It’s Not Really an Ambient Sound App
This was the biggest shift.
At first, I saw Focusnest as:
Before
- An ambient sound app
- A relaxation app
- A noise playback app
But after organizing the hypotheses, a different framing emerged.
After
- A tool that reduces the friction of entering focus mode
- A portable deep work environment
- A personal switch for starting work or study
That change in wording is not just branding.
It changes:
- who the competitors are,
- who the message resonates with,
- and what kinds of content I should create.
For example, saying:
- “You can mix 16 different sounds”
is much weaker than saying:
- “Start coding faster with a rain + brown noise preset”
- “Recreate your ideal focus environment with one tap”
- “Shorten the ritual it takes to enter work mode”
The second version gives people a concrete reason to care.
The Marketing Hypotheses I Came Away With
After organizing everything, a few practical hypotheses stood out.
Hypothesis 1: The first users are probably not “people who love ambient sound”
The first people most likely to care may be knowledge workers who struggle with context switching.
For example:
- Remote workers
- Engineers
- Students
- Creators
These people are less interested in sound for its own sake.
They care about entering a focused state more easily.
Hypothesis 2: Use-case messaging will outperform feature messaging
Feature messaging still matters.
Things like offline support, 1/f fluctuation, and the number of sound sources are useful.
But on their own, they don’t create urgency.
Use cases probably work better:
- for coding
- for studying
- for reading
- for relaxing before sleep
- for starting work in the morning
That kind of framing makes the product feel immediately usable.
Hypothesis 3: Story-driven distribution is better than paid acquisition at this stage
At this point, I don’t think paid ads are the right first move.
What seems more promising is building context first.
That likely means channels like:
- use-case posts on X
- developer and validation stories on Zenn / Qiita
- improving App Store screenshots and description copy
In particular, I think the story of why I built it and how I’m figuring out how to sell it is more interesting than simple promotion.
The Initial Actions I Decided to Take
Once the hypotheses were clearer, the next actions also became clearer.
The goal is not to do everything at once.
It’s to test small moves and observe what resonates.
1. Shift the positioning from “ambient sound app” to “focus-switching app”
This affects everything:
- product description
- App Store copy
- screenshots
- social posts
The wording should consistently emphasize entering focus faster, not just listening to sounds.
2. Create use-case-based posts on X
For example:
- “Rain + brown noise is my coding preset”
- “I use one tap to switch into work mode every morning”
- “Different presets for focus, relaxation, and sleep”
These are stronger than generic feature announcements.
3. Turn the development and GTM thinking into content
Not just “I built an app,” but:
“I used hypothesis validation to figure out how to bring it to market.”
That kind of content does three things at once:
- it promotes Focusnest,
- it shares a practical process other builders can learn from,
- and it strengthens my own identity as someone who builds products through validation, not just intuition.
4. Delay Product Hunt for now
Product Hunt is attractive, but I don’t think it’s the right first move yet.
Before trying to launch broadly, I want stronger clarity on:
- who this is really for,
- what messaging works,
- and which channels give early traction.
In this case, building context first seems more valuable than chasing a big launch too early.
What I Learned
The biggest lesson was simple:
Building and selling are different jobs.
A good product is not enough.
The same product can feel irrelevant or compelling depending on:
- how you frame it,
- who you frame it for,
- and what context you place it in.
At first, I saw Focusnest as an ambient sound app.
But once I organized the go-to-market hypotheses, I realized its real value was reducing the cost of entering a focused state.
That clarity alone made the next moves much easier.
It also made something else clearer:
not just what I should do next, but what I shouldn’t do yet.
For example, instead of rushing into ads or Product Hunt, I now think it makes more sense to first build context, messaging, and initial traction.
Conclusion
A lot of indie builders hit the same wall:
They spend all their energy building, then get stuck at “Now how do I sell this?”
When that happens, it may be faster to stop adding tactics and start organizing the problem as hypotheses.
Questions like:
- Who is this really for?
- What problem does it actually solve?
- What is meaningfully different from substitutes?
- In what context does the value become obvious?
Once those become clearer, both your messaging and your product page tend to improve.
If you’ve built something but still don’t know how to bring it to market, it may help to treat go-to-market as a validation problem too.
I used KaizenLab to organize these hypotheses.
It worked not only for product ideas, but also for shaping go-to-market thinking around an actual indie product.
Top comments (0)