Defining Your Audience by Exclusion

Content aimed at everyone reaches no one. You already know this from BD: a pitch built to land with EA, Sony, Activision, and a mobile indie studio all at once lands with none of them, because the specifics that would make it resonate with any one of them get sanded off to avoid excluding the others. Content works the same way. The instinct is to keep the aperture wide so you don’t turn anyone away. That instinct is the single biggest reason creator content underperforms: a feed that could be for anyone reads as being for no one, and both the algorithm and the audience notice. Naming who you are not for is what makes the content sharp enough for the people you are for.

Start with the exclusion, not the inclusion. Most people try to write “who this is for” first and end up with something so broad it’s useless, something like “business leaders interested in growth.” Instead, list five people or roles adjacent to your real audience who might follow you but who you are not writing for. For a BD and revenue strategy content play, that exclusion list might read: junior sales reps looking for scripts, general hustle-culture content consumers, recruiters mining your feed for candidates, direct competitors doing competitive intelligence, and people who want motivational content with no operating substance behind it. Write the reason each one is excluded in a half sentence.

Once the exclusions are named, the inclusion gets easy: it’s whoever is left standing after you draw the exclusion lines. Write it as a single sentence with a role, a context, and a problem: “Revenue and BD leaders at mid-size companies who are past the individual-contributor stage and are now responsible for building a function, not just hitting a number themselves.”

Test it. Take five real or plausible content topic ideas and run each one against your definition: would this piece serve the included audience, or would it only serve one of the excluded groups? If you can’t confidently sort a topic, the definition isn’t specific enough yet. Tighten it and test again.