Two Audiences, One Page: The Operator Door Pattern
Our /ai page has a clear audience: developers and technical builders who want a Claude Code skill for generating on-brand UI. The page is written for them. The copy assumes they know what a skill file is. The CTA says "Clone the Skill." It's focused on purpose.
The problem: that's not everyone who lands there.
Service business owners, the exact people we built the Operations Engine for, find the /ai URL through search, through social, through word of mouth. They click through, read the first paragraph, see "SKILL.md" and "four-command workflow," and leave. We gave them no other option. The page was technically working and still failing a whole segment of the right people.
The Wrong Fix
The obvious move is to expand the page. Add a section for service businesses. Write copy for both audiences. Make it longer.
That's the wrong move. The /ai page works because it stays focused. Adding a second pitch muddies the positioning and weakens the conversion path for the audience the page is actually built for. Two audiences trying to share one page usually means neither converts well.
We needed to acknowledge the second audience without absorbing them into the first page's flow.
The Operator Door
We added a single slim band between the hero and the problem section. It takes up about 80px of vertical space on desktop. It says:
"Run a service business instead? We install an AI operations engine into electrical, HVAC, plumbing, landscaping, and construction back offices."
A button links to /ai/operations-engine. That's the whole thing.
The band uses the same border-t border-border separator the rest of the page uses between sections. Same font-mono label style, same accent color for the link. It doesn't look like an ad or an intrusion. It reads like a quiet fork in the road.
The label above the headline is "Run a service business instead?" in a small all-caps mono treatment. That "instead?" does real work. It signals: this page isn't for you, but we see you, and we have something that is.
What We Didn't Do
We didn't add it to the nav. We didn't create a split hero with two CTAs. We didn't run A/B tests on whether to include it. The signal was clear enough: we were actively building a productized service for operators and pointing zero traffic to it from a page that operators were already landing on.
The band costs nothing in terms of page focus. If you're a developer, you read "service business," skip it in under a second, and keep reading. The main page flow is untouched.
The Broader Pattern
Any page that has a clear primary audience will occasionally attract a secondary one. The options are: ignore them, try to serve both in the same flow, or give them a door. Serving both in the same flow is almost always the worst option, because it dilutes the message for everyone.
The door pattern works when the secondary audience is substantial enough to warrant acknowledgment and when you actually have somewhere to send them. In this case, both were true.
We'll use this again. If /ai attracts a third distinct audience who isn't a developer or a field-service operator, they'll get a door too, not a paragraph.