Pitch

Reference it for

• The sparkle keyframe family (sparkL, sparkM, sparkS, sparkHover) — small twinkling stars that surround UI elements. Adds playfulness without slowing the page. Each spark has a slightly different size + timing for organic feel.
• Animated cursor pointers (cursor_talking, cursor-1) — small avatars/cursors moving across product screenshots to demonstrate multiplayer. Pattern goes back to Figma's nameplate cursors but Pitch's are more performative.
• Four-step numbered walkthrough as the main capability section ("1 — Plan / 2 — Build / 3 — Pitch / 4 — Measure"), each step with its own headline + screenshot + 3-line explainer.
• Violet #6b53ff + yellow #ffd02c + warm-navy ink #2b2a35 — a memorable three-colour palette for B2B SaaS that needs to feel playful.
• A full-width violet banner top-of-page holding the nav + CTAs (gives the brand its instantly-recognisable colour without overpowering the white content area).
• Eina01 for body + Mark Pro as the two-face system. Both are paid faces but distinctive.
• 22 transitions with a strong 0.4s ease curve for opacity+transform reveals and 0.12s ease-in-out for snap-fast background changes.
• 4 gradient keyframes (gradient1 through gradient4) — likely animated gradient art on feature blocks.

Do not copy

• Eina01 / Mark Pro — both licensed; Mark Pro is FontFont, Eina01 is Mostardesign.
• The exact violet #6b53ff — strongly Pitch-coded; pick the client's own primary.
• Sparkles on a brand that needs to feel serious — they're playful by nature and undermine a corporate tone.
• The animated multiplayer cursor pattern unless the product is actually collaborative.
• 21 per-component CSS Module keyframes — borrow the patterns (sparkL/sparkM/sparkS) but write them globally with readable names.
• The "4 — Measure / Know what's working" cadence on a 2-step product — works only if there are genuinely 4 distinct stages.
• OneTrust cookie banner — heavy. Use a lighter consent component.