01 Logo
Storm mark and wordmark
Clear space
Keep one bolt width around the mark and one cap-height around the wordmark. Give the logo quiet space so the lightning shape stays recognizable.
Minimum size
Use the full wordmark at 160px wide or larger. Below that, use the mark-only asset for app icons, favicons, and compact navigation.
Usage
Use the dark logo for immersive first screens and the light logo for documents, decks, whitepapers, and product surfaces.
02 Color
Electric, trusted, readable
03 Typography
Sora for impact, Inter for work
Display / Sora
Turn market signals into booked conversations.
Body / Inter
Leadstormer should read like a confident operating system for outbound teams: direct sentences, concrete claims, clear proof, and no inflated sales language.
Mono / IBM Plex Mono
LS-SIGNAL-042 / PRIORITY_ACCOUNT / 98%
04 Shape Language
Signals, not hatches
Use cyan and blue rhythm
Use short rounded rails, dots, progress strips, and data ticks for momentum. Keep them clean, horizontal, and system-like.
Use the mark as the icon base
For identity moments, use the official rounded mark tile. Do not substitute generic hexagons, badges, or ACE-style client marks.
Reserve amber for action
Pipeline Amber is for CTAs, warnings, and high-intent conversion moments. Do not use it for decorative stripe or hatch treatments.
05 Asset Direction
Patterns for the client page
Use data as texture
Prefer tables, score strips, signal cards, and timeline fragments over generic marketing illustrations.
Show momentum
Use signal rails, progress strips, and the official bolt tile to make progress visible without visual clutter.
Ground every claim
Pair bold statements with operational proof: account counts, conversion windows, source freshness, and approval status.