From 0→1 clarity to measurable ROI, tailored to your stage.
Most founders know they need design but don’t know where to start. Some overbuild too soon, others ignore it until it’s too late. I help startups avoid both mistakes by building design systems that align with your product stage, team, and goals.
Not one-size-fits-all.
Most founders know they need design but don’t know where to start. Some overbuild too soon, others ignore it until it’s too late. I help startups avoid both mistakes by building design systems that align with your product stage, team, and goals.
Not one-size-fits-all.
“We hire designers early not just for pixels, but to shape the product.”
“We hire designers early not just for pixels, but to shape the product.”
“We hire designers early not just for pixels, but to shape the product.”
—Brian Chesky, Airbnb
Early Teams (0→1)
For founders with a site, MVP, or seed-stage product.
For founders with a site, MVP, or seed-stage product.
→
Goal: Understand design, avoid waste, and set the right foundation.
1.
Clarity
Agree on what design is for your product and how to use it now.
• What design actually means for your product
• Where to start (without wasting time or budget)
• When and how to hire your first designer
You get:
• A Design 101 for Founders guide
• A simple priority map (what to do now vs. later)
• First-hire roadmap with next steps
2.
DesignOps
Lightweight workflows that make design easy to use, even without a team.
• Simple intake and review flow
• Early reusable patterns (no bloated kits)
• Dev-friendly handoff basics
You get:
• Starter workflows built for your roadmap
• A minimal, modular design system
• Founder-friendly tools for re-use
3.
Outcomes
Design that supports your product instead of slowing it down.
• Align design with product + engineering
• Prevent waste and rework
• Spot risks before they grow
You get:
• A clear design foundation
• Aligned team priorities
• Fewer redesigns, faster delivery
“Design is not just for products. It's at the core of how you build companies.”
—Reid Hoffman, LinkedIn
Scaling Teams (Post-MVP)
Scaling Teams (Post-MVP)
For startups past MVP, building fast, and needing proof for investors.
For startups past MVP, building fast, and needing proof for investors.
For startups past MVP, building fast, and needing proof for investors.
→
Goal: Connect design to business impact, measure it, and grow without chaos.
1.
Clarity
Align team on what good design looks like, and how to scale it cleanly.
• Define design’s role in product + eng
• Agree on “what good looks like”
• Spot scaling risks early
You get:
• Team alignment workshop
• Design priorities mapped to roadmap
• Early guardrails against debt
2.
DesignOps
Scalable, repeatable systems that keep teams efficient.
• Modular workflows that scale cleanly
• Intake + prioritization that matches velocity
• Engineering-ready handoff systems
You get:
• Ops playbook for design
• A lightweight, scalable design system
• Workflows tailored to your roadmap
3.
Outcomes
Show investors that design drives growth, not just pixels.
• Track reuse, velocity, ROI
• Reduce design debt + rework
• Investor-ready reporting
You get:
• Metrics dashboard (reuse, debt, velocity)
• Proof points for investor updates
• Scalable design tied to business goals
Why This Works
Because every startup has different needs. I don’t hand you another UI kit. I build the infrastructure and clarity so design works for your product and team stage — whether you’re just getting started, or proving ROI at scale.
