Penpot vs Figma — Deck Outline
Audience: design + product leadership Tone: confident, ambitious Target: 22 slides
Narrative arc:
- Title
- The strategic question (why this matters now)
- The Figma squeeze (post-Adobe, pricing, lock-in)
- Meet Penpot (open source) 5-6. Pillars: Open source / no lock-in, Design-dev native (specs/standards), Self-host & data sovereignty, Cost 7-12. Deep dives on each advantage
- Collaboration parity
- Plugin/extensibility
- Total cost of ownership
- Risk & governance / compliance
- Migration path
- Objections / honest tradeoffs
- Adoption roadmap
- Metrics / what success looks like
- Recommendation
- Call to action
Key facts to weave in:
- Penpot is fully open source (MPL 2.0), free to self-host
- Built on open web standards: SVG, CSS — design tokens, flex/grid layout native
- No vendor lock-in; data sovereignty via self-hosting
- Figma acquired-then-not by Adobe; pricing increased; concerns over roadmap control
- Penpot's design-dev workflow speaks the developer's language (CSS, flex layouts)
- Community-driven roadmap
- Honest tradeoffs: smaller plugin ecosystem, fewer mature integrations, smaller talent pool familiarity