A Deliberate Rep: Fixing AI's Generic Landing Page
Will Hyland · 2 min read · June 24, 2026
Ask AI for landing-page copy and you'll get something that sounds like a landing page and sells nothing. Fluent, confident, generic. Here's a deliberate rep that turns that default sludge into copy a real customer would respond to.
The task, and the bar
You need a hero section for a B2B product. Before prompting, set the bar — the three criteria a sharp marketer would hold:
- Leads with the customer's problem, not the product's features.
- The core claim is specific and provable — no "revolutionary," "seamless," "next-generation."
- One unambiguous call to action.
The vending-machine version
Prompt: "Write hero copy for our AI-powered analytics platform." The model delivers exactly what it always delivers:
Revolutionize your workflow with our seamless, AI-powered analytics platform. Unlock powerful insights and drive unprecedented growth. Get started today and transform your business!
Read it against the rubric: it leads with the product (fail); every claim is a banned adjective with nothing behind it (fail); "get started" and "transform your business" muddy the CTA (fail). 0 / 3. It feels like marketing, which is the trap — feeling like marketing is not the same as working.
The rep
Do it deliberately. Give the model the raw material it can't invent: the actual customer pain ("analysts spend two days a month hand-building the same board deck") and one real proof point ("teams cut that to an hour"). It improves — but it still opens with "Our platform empowers teams to…" and hedges the number into "save significant time."
Close the gap
The model can generate; it can't decide what matters. That's you:
- Flip to the problem first: open on the reader's pain, not your product.
- Make the claim specific and provable: replace "save significant time" with the real number.
- Cut to one CTA.
The result:
Your analysts lose two days a month rebuilding the same board deck. UofAi Analytics turns that into an hour — same numbers, same format, zero hand-assembly. See it on your data →
It names a problem the buyer feels, makes a claim they can check, and asks for exactly one thing.
What this rep proves
The model wrote the generic version and helped draft the good one — but the moves that made it convert were judgment calls it couldn't make: knowing the customer's real pain, refusing the empty adjective, choosing the single action. The AI's default voice is confident and generic. The rubric caught it; your understanding of the customer fixed it.
That's the capability worth proving — and the one that doesn't commoditize when everyone has the same model.
Run this rep on your own copy inside the method. Start free.
Put this into practice
Explore AI Productivity for Professionals or use the free AI Skill Map to find your next Rep.
Get new posts in your inbox
Applied-AI playbooks, deliberate-practice frameworks, and case studies. No spam — unsubscribe anytime.
Keep reading
A Deliberate Rep: Answering an Angry Customer Without Inventing Policy
A real deliberate rep, end to end: AI drafts a warm refund reply that invents a guarantee you never offered — and the rubric that catches it.
Will Hyland · 4 min read · Jul 17, 2026
Stop Claiming AI Skills — Start Proving Them
'Proficient with AI tools' means nothing when everyone writes it. Build a portfolio of evaluated artifacts that proves verified AI capability.
Will Hyland · 2 min read · Jun 24, 2026
A Deliberate Rep: Catching the Plausible-but-Wrong Code AI Loves to Write
AI writes code that looks right — that's the problem. A real deliberate rep: using rubric-as-tests to catch the silent bug before it ships.
Will Hyland · 2 min read · Jun 24, 2026