The moment you decide to ship imperfectly, a question appears: to who?
Most builders answer with their target market. Their niche. The people who "should" care about what you're building. Wrong answer.
Your smallest audience isn't the people who fit your ideal customer profile. It's the people who are currently watching you, who trust you enough to take you seriously even when the thing you shipped is half-baked, and who will actually tell you what they think. That's a smaller group than you're probably thinking.
And that's exactly who should get version 0.1.
Who is your smallest audience (and why it's not who you think)
Your target market is a category. Your smallest audience is a list of actual people.
You might have 500 people on your email list. That does not mean your smallest audience is 500. Your smallest audience is the 12 who open every email. The 5 who forward them to others. The 2 who hit reply. Those are the people who've already signaled they're paying attention.
Look at your actual engagement, not your potential reach. The smallest audience is where the signal is already there.
How small is small enough
Small enough is: everyone in the group actively engages.
If you have to guess whether someone cares, you haven't found your smallest audience yet. You need people who are unmistakably interested. Who make time. Who respond.
That can be 3 people. It can be 15. The number does not matter. What matters is that every single person in the group has already opted in to paying attention to what you're doing.
Where to find and reach them
You already know who these people are.
They're the ones who comment. Who reply to your emails. Who message you asking when the next thing is coming. Who have referenced something you shipped in a conversation with someone else.
You do not need to recruit them or convince them. You need to look at your existing engagement and give feedback channels to the people who are already there.
If you have no engagement anywhere, you have not shipped enough yet to have an audience at all. Start shipping to yourself, publicly. Do that for a month. Then look at who shows up.
What incompleteness to ship to them
Ship the part that lets them give you the feedback you actually need.
This is not the same as "ship the minimum." It's not a one-liner or a wireframe or a vague description of what you are building. It's real enough that they can touch it, use it, or experience it.
For a SaaS feature, that might be a clunky flow that works but has no polish. For a writing project, it might be the first essay in rough form. For a product, it's the prototype that does the thing but feels fragile.
The bar is: can they tell you what doesn't work? If yes, you're ready to ship. If they can't even tell what they're looking at, wait one more day and add the minimum required clarity. Then ship.
What signals matter in their feedback
Not all feedback is equal.
The feedback that matters comes from people who actually tried the thing. Did they get stuck? Did they get bored? Did they misunderstand how it works? Did they ask for something that does not exist yet? That is signal.
Vanity feedback like "it's cool" or "I like it" is nice, but it does not help you. It feels good and changes nothing.
Frustration is signal. Confusion is signal. Requests for specific changes are signal. A note saying "I hit this error three times" is worth more than ten compliments.
Watch for what people did, not what they said. Did they come back? Did they use it again? Did they show anyone else? If the answer is no and they said it was great anyway, something does not add up.
When to expand beyond the smallest audience
Three things have to happen before you ship wider.
One: your smallest audience has stopped surfacing new problems or new feedback. They've cycled through the thing. They've told you what breaks. If they're still finding new issues, keep iterating with them.
Two: they're actively telling you to launch wider. Not politely. They're saying "this is ready" or "I'm telling everyone I know" or "you should charge for this." That's them signaling the work is done.
Three: you've actually shipped at least one version based on their input. Not someday. Not "I plan to." You've changed something and shipped the iteration. They've seen you iterate. That proves you actually care about the feedback.
All three together? You're done with your smallest audience. Time to widen.
Find your 5 people, ship something real to them this week. DM me if you test this, I want to hear what your smallest audience tells you.
FAQ
Q: Won't my smallest audience churn if I ship obviously broken features?
Your smallest audience is your most forgiving segment. They're early adopters who expect iteration and version 0.1 to feel like version 0.1. They'll churn if you ship nothing. They'll churn if you ship the same broken version twice with no changes based on their feedback. But they'll stay if you ship something real and iterate based on what they tell you.
Q: What if I ship and get no feedback at all?
Silence is a signal, but not the helpful kind. First move: be explicit about what you need. Don't just send it out. Say "I shipped this early to learn. Tell me where you got stuck." If you still get silence, either what you shipped isn't interactive enough yet, or you haven't found the right small group. Move on, ship again to a different set of people, and ask directly. Feedback requires them to do work. Make sure you're asking clearly and making it easy to respond.
Q: Should I explicitly tell my smallest audience the work is incomplete?
Yes. Tell them you're shipping early to learn from them, what specific feedback you're after, and how you plan to iterate. This frames imperfection as strategy, not failure. It focuses their feedback on what actually helps you instead of wasting time on polish. It also gives them permission to think like collaborators instead of consumers.
Q: What if my smallest audience is too small to give you actionable feedback?
If you have fewer than 5 people actively engaging, you've found a niche, not an audience. Density of feedback matters more than volume. You need at least enough people that you can spot patterns. If one person says "this is confusing," that is one data point. If three separate people get stuck in the same place, that is a pattern. Expand until you have patterns, not outliers.
Q: What if my smallest audience isn't ready for you to launch wider?
If you've shipped iterations, soaked in their feedback, but they keep saying "not quite," you're at an inflection point. Their job was to catch critical failures and surface patterns. If you've shipped at least once based on their input and the feedback has dried up, you've learned what you needed to learn. The next test is whether it works for a broader group. You don't need their blessing for that step. They're your first users, not your gatekeepers.