- Tools
- Claude Code, Vercel
- Time
- 4 hours to build v1
- Status
- Live, 34 portfolios
- Guardrails
- Design system, CLAUDE.md file and an overall project plan
7.8K
monthly users
66.4K
launch impressions



Context
While working on my own portfolio, I went looking for how other leaders built theirs. Every showcase I found was focused on IC design work, so I built one for leaders.
What I delegated, and the calls I made
Marked rows are key decisions.
- Building the site
Claude Code, from my plan
Mostly AI
- Reviewing submissions
A Claude skill drafts, I make the final call
Shared
- Writing annotations
Claude outlines, I edit or write
Mostly me
- Who counts as a leader Override
Claude’s first list left out Managers, Principals and Founders
All me
- Tradeoff:
- a broader scope to curate.
- Why:
- leadership portfolios come from more roles than Directors and VPs.
- Putting my name on it Decision
I’m the named curator
All me
- Tradeoff:
- my reputation rides on every pick.
- Why:
- a real person behind the site gives it more credibility.
Outcome
Dozens of submissions came in after launch. Next time, I’d build a backlog of portfolios and publish them on a steady cadence instead of launching with so many at once.
