2025
Spekit
Rebuilt Spekit’s marketing web experience and product-storytelling system—pairing Webflow, motion, and clear diagrams to turn complex features into fast, high-intent conversions.
Rebrand
Website Design & Development
Know More
The only AI-powered sales enablement platform that surfaces personalized answers, content, and training where your reps work. Trusted by thousands.
Senior Brand Designer — Webflow Dev, Brand/Motion, Product Storytelling
Making a complex SaaS instantly legible—through systemized Webflow components, purposeful motion (AE → Lottie), and diagrammatic visuals that sell the product story at a glance.
Problem
Great product, fragmented story.
Spekit’s value lived across scattered visuals and ad-hoc pages. Complex features weren’t “readable” at a glance, and new launches required bespoke builds—slowing velocity and diluting brand consistency. Motion existed but wasn’t systemized, so assets were heavy and hard to reuse.
Solution
Turn understanding into a system.
Systemized Webflow: a modular page kit (hero → value stack → product proof → CTA) with CMS-driven sections for rapid launches.
Diagram language: a consistent visual grammar (modules, layers, spokes) to explain platform architecture in 3–5 seconds.
Motion with purpose: short AE → Lottie loops that demonstrate outcomes (not just UI chrome), reusable across site, decks, and paid.
Performance & access: semantic structure, keyboard-navigable controls, and trimmed payloads so pages stay fast under campaign traffic.
Conversion craft: tighter copy hierarchy, social proof near CTAs, and testable variants for messaging clarity.
Concept
Explain the invisible.
When SaaS gets dense, the job is translation. Start with decision clarity (what it does, why it matters), then layer progressive detail (how it works). Use motion to demonstrate cause → effect, not to decorate. Build it as a system so every future page inherits the same clarity and pace.
More Works
FAQ
01
What kind of work is in this portfolio?
02
How do you choose between Webflow, Framer, and React?
03
What was your role on these projects?
04
How do you approach accessibility and performance?
05
What’s a typical timeline shown here?
06
How do you measure success in these projects?
07
Can you work with an existing brand or do full rebrands?
2025
Spekit
Rebuilt Spekit’s marketing web experience and product-storytelling system—pairing Webflow, motion, and clear diagrams to turn complex features into fast, high-intent conversions.
Rebrand
Website Design & Development
Know More
The only AI-powered sales enablement platform that surfaces personalized answers, content, and training where your reps work. Trusted by thousands.
Senior Brand Designer — Webflow Dev, Brand/Motion, Product Storytelling
Making a complex SaaS instantly legible—through systemized Webflow components, purposeful motion (AE → Lottie), and diagrammatic visuals that sell the product story at a glance.
Problem
Great product, fragmented story.
Spekit’s value lived across scattered visuals and ad-hoc pages. Complex features weren’t “readable” at a glance, and new launches required bespoke builds—slowing velocity and diluting brand consistency. Motion existed but wasn’t systemized, so assets were heavy and hard to reuse.
Solution
Turn understanding into a system.
Systemized Webflow: a modular page kit (hero → value stack → product proof → CTA) with CMS-driven sections for rapid launches.
Diagram language: a consistent visual grammar (modules, layers, spokes) to explain platform architecture in 3–5 seconds.
Motion with purpose: short AE → Lottie loops that demonstrate outcomes (not just UI chrome), reusable across site, decks, and paid.
Performance & access: semantic structure, keyboard-navigable controls, and trimmed payloads so pages stay fast under campaign traffic.
Conversion craft: tighter copy hierarchy, social proof near CTAs, and testable variants for messaging clarity.
Concept
Explain the invisible.
When SaaS gets dense, the job is translation. Start with decision clarity (what it does, why it matters), then layer progressive detail (how it works). Use motion to demonstrate cause → effect, not to decorate. Build it as a system so every future page inherits the same clarity and pace.
More Works
FAQ
01
What kind of work is in this portfolio?
02
How do you choose between Webflow, Framer, and React?
03
What was your role on these projects?
04
How do you approach accessibility and performance?
05
What’s a typical timeline shown here?
06
How do you measure success in these projects?
07
Can you work with an existing brand or do full rebrands?
2025
Spekit
Rebuilt Spekit’s marketing web experience and product-storytelling system—pairing Webflow, motion, and clear diagrams to turn complex features into fast, high-intent conversions.
Rebrand
Website Design & Development
Know More
The only AI-powered sales enablement platform that surfaces personalized answers, content, and training where your reps work. Trusted by thousands.
Senior Brand Designer — Webflow Dev, Brand/Motion, Product Storytelling
Making a complex SaaS instantly legible—through systemized Webflow components, purposeful motion (AE → Lottie), and diagrammatic visuals that sell the product story at a glance.
Problem
Great product, fragmented story.
Spekit’s value lived across scattered visuals and ad-hoc pages. Complex features weren’t “readable” at a glance, and new launches required bespoke builds—slowing velocity and diluting brand consistency. Motion existed but wasn’t systemized, so assets were heavy and hard to reuse.
Solution
Turn understanding into a system.
Systemized Webflow: a modular page kit (hero → value stack → product proof → CTA) with CMS-driven sections for rapid launches.
Diagram language: a consistent visual grammar (modules, layers, spokes) to explain platform architecture in 3–5 seconds.
Motion with purpose: short AE → Lottie loops that demonstrate outcomes (not just UI chrome), reusable across site, decks, and paid.
Performance & access: semantic structure, keyboard-navigable controls, and trimmed payloads so pages stay fast under campaign traffic.
Conversion craft: tighter copy hierarchy, social proof near CTAs, and testable variants for messaging clarity.
Concept
Explain the invisible.
When SaaS gets dense, the job is translation. Start with decision clarity (what it does, why it matters), then layer progressive detail (how it works). Use motion to demonstrate cause → effect, not to decorate. Build it as a system so every future page inherits the same clarity and pace.
More Works
FAQ
What kind of work is in this portfolio?
How do you choose between Webflow, Framer, and React?
What was your role on these projects?
How do you approach accessibility and performance?
What’s a typical timeline shown here?
How do you measure success in these projects?
Can you work with an existing brand or do full rebrands?