Build a Portfolio With Claude Code
To build a portfolio with Claude Code, you need three to four live, publicly accessible projects that each prove one thing: you can take a brief, build something real, deploy it, and hand it over. That is the entire bar for a first portfolio. You do not need polished design, ten projects, or impressive code - you need hosted URLs that a prospective client can click and use. Claude Code handles the implementation. Your job is to pick the right projects and ship them.
The desktop app is where you start. Open it, point it at a new project folder, and describe what you are building. Claude Code reads your description and builds the files. You review, steer, and deploy. No terminal configuration required - the app handles the shell access Claude needs to write and run code on your machine. If you have not set up the desktop app yet, the [Claude Code desktop app guide](/blog/claude-code-desktop-app) walks through the first-time setup.
The CCC Portfolio Stack: What to Build and in What Order
The CCC Portfolio Stack is a four-project sequence designed to get you from zero to a credible portfolio in under two weeks. Each project builds on the previous one and covers a different skill area that clients care about. The sequence matters - do not start with the hardest project.
- A landing page for a fake business. Pick an industry you understand - a local gym, a freelance photographer, a small accounting firm. Build a one-page site that shows the services, includes a contact form, and is deployed live on a real URL. This proves you can build and deploy a client-facing web page. Time: one afternoon.
- A utility tool you actually use. A script, a small app, or an automation that solves a problem you have today. A CSV cleaner, a link shortener, a time tracker, a daily standup generator. Real use = real proof the tool works. Deploy it publicly and use it for a week before adding it to the portfolio. Time: one to two days.
- A build for a real person. A landing page for a friend's side hustle, a booking widget for a family business, an invoice generator for a freelance contact. This project teaches you the client communication loop: briefing, delivering, revising, handing over. That loop is the actual skill you are selling. Time: two to three days.
- One project that matches your target client type. If you want to work with restaurants, build a reservation page. If you want to work with coaches, build a course waitlist and payment page. If you want to work with agencies, build a client reporting tool. This project is your strongest conversation starter because it demonstrates you understand their world specifically. Time: two to three days.
How to Deploy Each Project So It Has a Real URL
A portfolio piece without a live URL is a screenshot, not a project. The fastest zero-cost deployment path for Claude Code builds is Vercel for web apps and sites. Claude Code can generate the deployment configuration alongside the project, and Vercel's free tier gives you a public URL under vercel.app with no credit card required.
In practice: once your build is working locally, tell Claude Code you want to deploy it to Vercel. Claude will write or update the configuration files, point you to the Vercel CLI command or the drag-and-drop deploy option, and the result is a live URL in under five minutes. The [how to deploy an app with Claude Code](/blog/how-to-deploy-an-app-with-claude-code) guide covers every deployment path in detail, including Netlify and Railway for projects that need a backend or database.
Deployment options by project type
| Project type | Recommended host | Time to live URL |
|---|---|---|
| Landing page / static site | Vercel | Under 5 minutes |
| Web app with API routes | Vercel | Under 10 minutes |
| App with a database | Railway or Supabase + Vercel | 15-30 minutes |
| Utility script (not a web page) | GitHub repo with a README demo | Under 5 minutes |
What Your Portfolio Page Should Say
Your portfolio does not need to live on an expensive custom site. A single page - even a well-formatted Notion page or a simple HTML page you built with Claude Code - that lists your four projects with their URLs and one-sentence descriptions is enough to start. Add a short paragraph at the top that says who you help and what kind of builds you take on. Keep it plain. Clients do not read long bios.
For each project, write: the name of the project, a one-sentence description of what it does and who it is for, and the live URL. If the project was built for a real person, include their name and one sentence they said about working with you. If it was a self-initiated build, say so and describe what problem you were solving. That level of honesty works well - it shows you are not inflating experience you do not have.
The Portfolio Mistake That Costs Clients
The single most common portfolio mistake among new Claude Code builders is waiting until the work is polished. Most people spend three weeks refining project two while project one sits on localhost, never deployed. No client ever saw that project. The portfolio with three live but imperfect projects beats the one with one perfect project that took a month to finish.
A live URL that does what you said it would do is already a finished portfolio piece. Ship it, add it to your portfolio page, and start the next one. You can update any project later - and the practice of updating a deployed project is itself a skill worth demonstrating. The four-project sequence in the CCC Portfolio Stack is designed to be completable in under two weeks. The clock starts when you open the desktop app and begin project one.
- Never put a project in your portfolio that is not live. A GitHub link with no deployed URL is invisible to most clients.
- Never describe a project without naming the problem it solves. Technology names mean nothing to non-technical clients.
- Never wait for permission to build a self-initiated project. You do not need a client to build something portfolio-worthy.
- Never skip the handover step on the real-person project. The practice of explaining and handing over a build is the hardest skill and the most valuable one to demonstrate.
When Your Portfolio Is Enough to Start Taking On Clients
Your portfolio is ready to support a client conversation the moment you have two live URLs and a clear sentence about what you build. You do not need four projects to start outreach. You need enough to answer the question a prospective client will always ask: 'can you show me something you've built?'
Two deployed projects that are relevant to the type of client you are targeting are enough to have that conversation. Add the third and fourth while you are in early conversations. Every additional project you ship strengthens the next outreach. Inside Claude Code Club, members share their first portfolio projects, get feedback from the community, and find early clients without cold pitching. That combination - real projects, honest feedback, and warm introductions - shortens the gap from portfolio to first paid build significantly. Join for $9 a month at https://www.skool.com/claudecodeclub/about.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
What should I build for my Claude Code portfolio?
Follow the CCC Portfolio Stack: a landing page for a fake business, a utility tool you actually use, a build for a real person, and one project that matches your target client type. Every project must have a live, publicly accessible URL. Screenshots of local builds do not count as portfolio pieces - clients need to click and see it working.
How many projects do I need before I can get clients?
Two live projects that are relevant to your target client type is enough to start having conversations. You do not need a complete portfolio to begin outreach. Add the third and fourth project while you are in early conversations. Two deployed, relevant projects answer the first question every client asks: can you show me something you have built?
How do I deploy a Claude Code project for free?
Vercel is the fastest zero-cost path for web apps and sites. Once your build is working locally, tell Claude Code you want to deploy to Vercel - it will write or update the configuration files. Vercel's free tier gives you a live URL under vercel.app with no credit card required and deployment in under five minutes. For projects that need a database, Railway or Supabase paired with Vercel covers the full stack.
Can I build portfolio projects without real clients?
Yes - and you should. Invent a fake business, pick an industry you understand, and build the exact deliverable you want to sell. A landing page for a fake gym is as useful as a portfolio piece as one for a real gym. The goal is a live URL that demonstrates you can go from brief to deployed product. Self-initiated builds are entirely valid.
What should my portfolio page say?
For each project: the project name, a one-sentence description of what it does and who it is for, and the live URL. Add a short paragraph at the top naming who you help and what kind of builds you take on. If a project was built for a real person, include their name and a one-sentence comment. Keep it plain. Clients read for proof, not biography.
Last reviewed by David Iya on September 13, 2026
