Most People Use Claude at 5% of Its Capacity – Here's How to Fix It

After 60+ hours testing prompts on Claude Opus 4.7 for his own businesses, Reddit user Appropriate_Barber_4 noticed a pattern: most people use Claude at about 5% of its actual capability. The problem isn't Claude — it's how people prompt it. Typing "Write me a landing page" produces generic output because the input is generic. Here's the five-step recipe that transforms output from advisory to actionable.

1. Assign a Role Before Anything Else

Don't say "write me copy." Say "You are a direct-response copywriter who has written landing pages for Stripe, Linear, and 20+ Y Combinator companies." The role activates a specific knowledge pattern — vocabulary, structure, and judgment all change.

2. Load Specific Context

Claude knows nothing about your business until you tell it. "I'm building a SaaS" produces garbage. "I'm building a SaaS for solo plumbers who hate ServiceTitan's $1K/month pricing, targeting 35-55 year olds running $50K-$200K businesses from a truck" produces gold. Specificity in = specificity out.

3. Set Explicit Constraints

The most common reason output feels generic is missing constraints. "Write a tweet" produces slop. "Write a tweet under 280 characters, hook on a contrarian claim, no emojis, include one specific number, no motivational language" produces something usable.

4. Define the Output Format Exactly

Don't let Claude pick the structure. Tell it: "Output in this format: headline (under 12 words), subhead (under 25 words), primary CTA (3-5 words), body section 1, body section 2." You get what you specify.

5. End Every Prompt with a Forcing Function

The biggest weakness of AI output is hedging. "It depends on your goals" is useless. End every prompt with "Give me your single recommendation for THIS context, no hedging." It transforms output from advisory to actionable.

The original post offers to go deeper on any of these points. The thread is full of additional prompt engineering lessons from the community.