Visual Identity
Logo, color, typography, spacing, photography, data viz, and collateral rules for Hero®.
The Hero® mark reflects four core design themes.
Variants
Primary
Gradients
Secondary Accents
Pair with primary only. Max 2 per layout. Never standalone.
UI Tokens
| Token | Value | Usage |
|---|
All styles use Poppins (Google Fonts). 0.01em tracking unless noted.
4px base unit · Comfortable density.
Border Radius
| Variant | Value | Context |
|---|
Sizes
Border rings: Default · Primary · Voice. Pulse animation at xl and 2xl.
Sweet spot is Tier 2 + Maybe/Yes. Visuals should feel like the product without being the product.
| Tier | Fidelity | Reality | |
|---|---|---|---|
| Tier 1 | Abstract / conceptual | Hypothetical / future | Avoid |
| Tier 2 | Real UI, simplified | Plausibly possible | Recommended |
| Tier 3 | Literal screenshot | Exists today | Not for marketing |
Chart Color Sequence
| Type | Rule |
|---|---|
| Pie | Begin upper right, clockwise. Label largest → smallest. |
| Donut | Single metric callout. Amber signals positive momentum. |
| Clustered Bar | Multiple colors for clusters. Accent sparingly on key data. |
Max 2 decorative elements per layout. Elements support — never dominate.
Callout Stats
| Type | Format | Stage |
|---|---|---|
| Ads | Single visual | Awareness |
| Social Posts | Single visual / video | Awareness |
| Single column | Awareness | |
| E-Book | 4+ pages | Thought Leadership |
| Datasheet | 1–2 pages (V) | Evaluation |
| Whitepaper | 3–4+ pages (V) | Thought Leadership |
| Case Study | 4–5 pages (V) | Proof |
| Competitive Brief | ~3 pages (V) | Decision |
| Product Overview | Multi-page (V) | Discovery |
Voice & Language
Voice, tone, and writing standards ensuring consistency across every surface where Hero® appears.
Hero® is an AI Sales Teammate supporting sellers before, during, and after conversations. Most sales tech analyzes after the fact — Hero® participates during the moment itself.
Four Principles
| # | Principle | What It Means |
|---|
Test: swap Hero® with a colleague's name. If it doesn't read right, try again.
| Instead of… | Use… |
|---|---|
| engagement | conversation |
| interaction | experience |
| contact | connection |
Approved
Avoid
| # | Framework | Example | Best For |
|---|---|---|---|
| 01 | Verb→Task→Outcome | Respond faster → Answer questions → Keep deal moving | Ads, UI Copy |
| 02 | Pain→Solution→Outcome | Buyers lose patience → Hero® surfaces context → Conversations stay focused | Campaigns, Landing Pages |
| 03 | Problem→Shift→Hero® | Multi-threading isn't enough → Hero® helps win those moments | Homepage, Keynote |
| 04 | Feature→Benefit→Outcome | Whisper Mode → Instant context → Better performance | Product Pages, Demos |
| 05 | Need→Solution→Outcome | Teams need confidence → Hero® brings knowledge → Higher Win Rates | Sales Decks, Exec Messaging |
| 06 | Moment→Insight→Outcome | Buyer asks tough question → Hero® answers → Seller responds confidently | Homepage, Use Cases |
Metaphors should clarify the idea, not replace it.
Show the System in Action
Every visual must show an answer or an insight — reinforcing the concept of Winning the Moment.
Every visual must show a transformation. Hero proactively generates outcomes — not just responds to prompts.