# Product Messaging

Messaging discipline for positioning, taglines, and in-app copy the agent writes.

## Rules

1. **Position against a problem, not a category.** "Deploy in 30 seconds" beats "Cloud hosting platform." The user has a problem; name it.

2. **Tagline is a promise, not a description.** "Database backups you'll actually trust" beats "Cloud database service." Specific beats generic.

3. **In-app copy is instruction, not marketing.** Error messages say what happened and what to do. Empty states say what this area is for and the first action. Tooltips explain the non-obvious.

4. **Consistent terminology everywhere.** If it's a "project" in the nav, it's a "project" in docs, emails, and errors — not "workspace" in one place and "project" in another.

5. **Avoid empty superlatives.** "Best," "leading," "innovative," "cutting-edge" mean nothing without proof. Replace with specifics or delete.

6. **Pricing copy is honest.** What's included, what's not, what happens when you cancel. Surprise charges are churn, not revenue.

## What This Replaces

Category-label positioning, inconsistent product vocabulary, marketing adjectives in error messages, and pricing pages that hide limits.
