Summarize with AI
To show who your product is for on your website, put one line directly under the headline that names the buyer by role, company size and the moment they need you. For example: For architects at 10 to 80 person firms submitting multifamily projects for permit. Then add a short line that says who the product is not for, and ask the same question on the demo form, so the sorting carries on after the click.
This matters most when you sell through calls. A homepage that speaks to everyone books everyone, and at an early-stage company the founder takes every one of those calls himself. You know exactly who your product is for. The page is the only place a stranger can find out, and when it does not say, your calendar does the sorting instead.
The hero that says Ship drawings with confidence
Picture an AI tool that reads a set of architectural drawings and flags what a city plan checker is likely to send back. This is an example, not a client. An architect uploads the PDF drawing set. The tool returns a list of probable comments, each pinned to a sheet. Sheet A-201: second floor corridor drawn at 40 inches against a 44 inch minimum. Sheet A-501: guard detail with no height noted. Every comment names the code section it comes from.
It is built for one kind of buyer. Mid-sized architecture firms that design apartment buildings and mixed-use projects lose time to correction rounds with the city. Each round can push back a start date, and the developer paying for the project notices.
The homepage says none of this. The headline reads Ship drawings with confidence. The subhead reads AI code review for the built environment. Two buttons of the same size sit side by side, Book a demo and See it in action. Under them is a rendering of a glass tower at dusk. The words architect, permit and plan check first appear in the third section, inside a card titled How it works.
Nine demos on the calendar, three worth having
Now look at the founder's calendar for one week. Nine demos came through that page. A homeowner wants to know whether his new deck needs a permit. A two-person design and build contractor wants a cheaper plan. A reviewer from a county building department asks if the county could license it. An innovation manager at a 5,000 person engineering firm wants a pilot, single sign-on and a security review before anyone sees the product. A student wants it for a thesis. An associate at a proptech fund is doing research.
Three of the nine are project architects at firms of 15 to 60 people, each with an apartment job going in for permit next month. Those are the calls the company exists for.
The founder takes all nine, because his cofounder is building the product. He has started asking how many people work at the firm in the first minute, before he shares his screen. Six of the nine records in the CRM now carry the note not a fit. He blocks Tuesday and Thursday afternoons for demos and moves product review to the evenings.
What an empty audience line costs a founder
Each of those calls takes around 45 minutes, plus the prep and the follow-up email. Six wrong calls a week is most of a working day spent explaining the product to people who were never going to buy it. That day comes out of the one person who understands the product best, which makes it the most expensive time in the company.
The damage spreads into the numbers too. The pipeline report shows nine demos and three possible deals, so the close rate looks weak and the product takes the blame. Across all sectors, the median gap between a seed round and a Series A is around 616 days, and roughly 70 percent of seed companies never raise a Series A. A founder who loses a fifth of every week to calls that cannot close is spending that runway on the wrong job.
Self-serve products pay a different way. A visitor who was never the buyer signs up, runs a few jobs and leaves. For an AI product each of those jobs costs inference, and AI product builders average around 52 percent gross margin against 70 to 80 percent for traditional software. A page that filters nobody makes you pay to serve people who were never going to stay.
Why saying who it is not for makes the page stronger
Most homepage advice says to speak to your ideal customer, then hedges. Keep the headline broad so nobody feels left out. Move the audience to a Solutions page. Founders follow it because a narrow line feels like it shrinks the market.
That fear has it backwards. The line does not change who can buy. It changes who books. The homeowner and the student were never going to pay, and the page had no way to tell them so. The three architects who did fit had to reach the third section to learn the product was for them. Any architect who left before that section never booked at all, and nobody counts those.
Here is the part most advice skips. Naming who the product is not for makes the page stronger for the people it is for. Readers recognise themselves faster by contrast. For architects at 10 to 80 person firms reads as a description. Add Not built for single-family homes or building departments, and the right architect reads it as proof that this company knows his work. A line that excludes someone shows that the team has made a decision, and buyers trust a company that has made one.
Role, company size or trigger: what the line should name
An audience line can name three things. The best lines usually name two of them.
- Role. The person who feels the problem and books the call. Project architect, not the built environment. A role tells the reader in two words whether to keep going.
- Company size, in people. Visitors know their headcount and rarely know where they sit on a revenue band. 10 to 80 person firms rules out the solo practice and the huge firm in one phrase.
- Trigger. The moment they need you: submitting for permit, just raised, moving to bigger clients. A trigger turns a description into a reason to act this month.
To choose, open your last twenty demo notes. If the bad calls were the wrong size, name the size. If they were the right size doing the wrong work, name the role. If they were the right people too early, name the trigger. If the buyer itself has changed recently, that is a bigger job, covered in what to change on your website when you reposition your ICP. This post assumes you already know the buyer and the page has not caught up.
Five places the line goes this week
Write the line once. Then put it in five places, in this order.
- Under the headline. Use the shape For [role] at [size] [trigger]. It replaces the vague subhead, not the headline, so the headline can still name the outcome. For how the headline, subhead and product image share that space, see the guide to SaaS hero section design.
- Next to the main button. One quiet line, such as Not built for single-family homes or building departments. Keep it plain and factual, never rude.
- In the demo form. Add one required question that matches the line, such as Firm size with four options: 1 to 9, 10 to 80, 81 to 500, more than 500. Send the first and last answers to a recorded walkthrough or a short reply instead of the calendar.
- In the browser tab title and the meta description. Searchers see these before they land, so the wrong visitor can skip the click.
- Beside your proof. Put the logo or quote from someone in the named audience closest to the line. Proof from the wrong kind of customer quietly undoes it.
Then check it. Read the next ten bookings against the line. If more than three are still the wrong fit, the line is too soft, so narrow it. If bookings stop entirely for two weeks, you named the wrong role, not too narrow a market.
Sales-led and self-serve put the line in different places
For a sales-led company the website is the whole revenue surface, so the audience line is a sales tool. It belongs in the hero, the demo form and the booking confirmation email. The founder's calendar is the scarce resource, and the page should guard it.
For a self-serve product the line sits under the headline and then shows up again just after signup. Ask the same question on the first screen of the product, so onboarding can fit the person. Fix the product first if it loses the right people after signup, because a sharper hero only sends more of them into the same gap.
Either way, the line has to be read, not just present. It sits in the most looked-at part of the page, so it needs real size and contrast and a place the eye reaches in the first few seconds. A small grey sentence under a large rendering is on the page and invisible to the reader. How the line is set is part of what tells a stranger this company knows its buyer. The Sathi website is a useful reference: the case study describes an affiliate platform for Shopify DTC brands that want affiliate to become a main revenue channel, which is a reader narrow enough to design a whole page around.
An audience line is one sentence of copy, and the work is where it sits, how it reads and what the form does with it. Studio Maydit designs and builds websites for AI founders in Framer, Webflow and custom code, so the hero, the form and the pages behind them change together. Fixed-scope projects run three to four weeks. If last month's demos held more people you would never sell to than people you would, bring that list to a 30 minute call.
