I write the "who this is NOT for" line before the hero headline on AI tools

Every AI landing page I draft wants to open with a clever hero. Magic verb. Model name. Screenshot of a chat bubble. I used to write that first and then wonder why signups were curious tourists.

Now I write one ugly sentence first: who this is NOT for. "Not for teams that need SOC2 this quarter." "Not if you want a general chatbot — we only do X workflow." "Not a Canva replacement." That line never has to ship on the homepage, but it forces the hero to stop lying.

Once the exclusion is clear, the headline almost writes itself. You stop promising the whole category. You promise the job that remains after you cut the people you cannot help yet.

This matters twice as much on early-access boards. On EarlyHunt hunters skim fast. If your page sounds like every other AI tool, they upvote out of politeness or skip. A sharp "not for" in the first screen (or at least in your own draft doc) filters the people who would churn in three days anyway.

I caught myself last month rewriting a hero five times because the exclusion was mushy. The product helped freelancers clean messy client CSVs. My draft still said "AI for your business data." Tourists. After I wrote "not for companies with a data team and a warehouse," the hero became about freelancers and invoice CSVs. Signups dropped a bit. Questions got better. That trade is the point.

Proof still matters, but thin honest proof beats a fake logo wall — same energy as social proof for an indie launch. And if you are shipping a nights-and-weekends AI side project, SideHunt audiences smell category-speak even faster than weekly AI boards.

Before your next hero rewrite, what is the one-line "not for" you are still afraid to say out loud?