The Indie Hacker Portfolio Page: Everything You Need to Get Clients

You've shipped products. You've got side projects running. Maybe a few of them even make money. But when someone asks "do you have a website?" — what do you point them to?

A GitHub profile? A Notion page you built in 30 minutes? A half-finished personal site you've been meaning to update since last year?

That's the portfolio problem most indie hackers never solve. And it quietly costs them clients.

This post walks you through exactly what your portfolio page needs — not the generic "add an about section and some projects" advice, but what actually works when you're a solo developer who ships products and takes on client work.

TL;DR

If you build products and want clients, a generic portfolio won't cut it. You need a page built for the indie hacker context.

What you'll learn:

• Why your portfolio page is a fundamentally different challenge from a standard freelancer site
• The 7 elements that turn a project showcase into a client-acquisition tool
• The most common mistakes indie hackers make with their online presence
• Which tools actually make sense for your situation

Key insights:

• Clients don't hire based on resumes anymore — they hire based on demonstrated results (Twine, 2025)
• Showing 3–5 strong projects with context beats listing 20 without explanation (Twine, 2025)
• A slow or poorly structured portfolio page actively loses you opportunities (Twine, 2025)

Bottom line: Block 2 hours this week and build your page properly. One good client from it pays for the time ten times over.

Note: The strategies in this post are based on real-world experience building and shipping indie products — not a success guarantee. Every situation is different. For legal or tax questions around client contracts or business structure, talk to a professional.

Why Your Portfolio Page Is a Different Beast

Here's the thing most portfolio advice gets wrong: it's written for freelancers or job seekers. You're neither.

As an indie hacker, you're doing something more complicated. You're a builder who ships their own products and sometimes takes on client work. You have side projects with real users, real revenue, and real technical depth. You also have skills you're willing to apply for the right client at the right time.

That's a hard thing to communicate on a standard portfolio template.

A typical freelancer page says: here are services I offer, here's my rate, hire me. A typical developer portfolio says: here are projects I've built, here's my stack, offer me a job. Your page needs to do both — and it needs to do it without looking confused or desperate.

The good news is that being an indie hacker is actually a credibility advantage. You've shipped things. You understand product decisions, not just code. You know what it means to build something people actually use. That's exactly what the right clients are looking for — and your portfolio page is where you prove it.

The 7 Elements Every Indie Hacker Portfolio Page Needs

1. A Clear, Honest Hero Section

The top of your page has one job: tell the visitor exactly who you are, what you build, and who you help — in plain language.

Not a tagline. Not a punchline. A real sentence.

Bad: "I build things for the web." Good: "I'm a full-stack developer and indie hacker. I build my own SaaS products and take on development projects for early-stage founders."

That's it. Two sentences and the visitor knows if they're in the right place. Don't make them scroll to figure that out.

Add your name, a photo (yes, a real one — builders trust builders, not stock-image avatars), and a single primary CTA button. We'll get to what that CTA should say in a moment.

2. Your Projects — With Numbers, Not Just Screenshots

This is where most indie hacker pages fall apart. A grid of screenshots with project names and "view on GitHub" links tells the visitor almost nothing.

What actually builds trust is context. For each project you include, give the visitor:

• What problem it solves — one sentence, no jargon
• Who uses it — "500 active users" beats "a productivity tool for teams"
• Results or traction — MRR, user count, App Store ranking, whatever you've got
• Your tech stack — briefly, for the technically-minded client
• A live link — if it's live, link it

According to portfolio research from Twine (2025), adding short case studies with measurable results — like "improved site speed by 45%" — is one of the clearest ways to differentiate from other developers. The same principle applies to your own products.

Keep it to 3–5 projects. Your best work, properly explained, is far more effective than a complete archive of everything you've ever touched.

3. A Short "How I Work" or Services Section

This is the bridge between your product builder credibility and your commercial offer. Without it, potential clients don't know they can actually hire you — they just think you're a guy with some cool side projects.

Keep it short and direct. Two or three paragraphs, or a simple list. Cover:

• What kind of work you take on (full-stack development, MVPs, integrations, audits — whatever fits)
• What you don't do (setting expectations early saves everyone time)
• How the engagement typically works (do you do fixed scope, hourly, retainers?)
• Your current availability

This section doesn't need to be a service catalog. It just needs to answer the question every serious client has before they reach out: "Can this person actually help me, and is it worth sending an email?"

4. Your Stack and What You Don't Do

Specificity is one of the most underused credibility signals in indie hacker portfolios. Clients who are a good fit want to know you work in their ecosystem. Clients who aren't a good fit should be filtered out before they even contact you.

List your tools honestly. Not everything you've ever touched — the stack you actually build in right now. For example:

• Frontend: Next.js, React, Tailwind CSS
• Backend: Node.js, PostgreSQL, Prisma
• Infrastructure: Vercel, Coolify, Hetzner VPS
• Tools: Stripe, Mautic, Payload CMS

Then add a short line about what you don't do. "I don't do WordPress customizations" or "I'm not currently taking on design-only projects" is honest and useful. It shows you know your lane, and it builds more trust than pretending you do everything.

5. Social Proof That Fits the Indie Context

You probably don't have a list of Fortune 500 logos to paste on your homepage. That's fine — that's not your audience anyway.

Indie-appropriate social proof looks like this:

• Testimonials from real people — a founder you helped, a client you shipped something for, a collaborator who can speak to your process. Keep them specific. "Max shipped our MVP in 3 weeks and actually understood the product decisions, not just the code" beats "Great developer, very professional."
• Community presence — links to your Indie Hackers profile, your X/Twitter build-in-public thread, your GitHub. These are visible proof you're active, real, and accountable.
• Revenue transparency (if you share it) — if you're comfortable sharing traction numbers from your own products, that's powerful social proof in the indie world. You've shipped things that people actually pay for.

What you want to avoid: fake logos, vague claims, or generic testimonials that say nothing about your actual work. Authenticity beats polish in this space every time.

6. One Clear CTA

This is where a lot of portfolios quietly die. The visitor is interested. They want to reach out. And then they're faced with four different options — email, a contact form, a Calendly link, a Twitter DM button, and a "work with me" page — and they close the tab instead.

Pick one primary action and make it obvious. Something like:

• "Book a 20-minute intro call" (low friction, specific, respects their time)
• "Send me an email" (if you actually respond quickly)
• "Fill out this short project form" (if you need context before you talk)

Put it in your hero section and repeat it at the bottom of the page. That's it. One CTA, two placements. Don't make the decision harder than it needs to be.

7. A Consistent URL You Actually Own

A Notion page, a GitHub profile, or a generic Linktree URL all say the same thing to a potential client: this person hasn't committed to their own presence online. That's a subtle trust signal, but it's real.

You need a URL that is yours. Ideally your name or your brand, on a domain you control.

For the actual page itself, you have a few paths. You can build it yourself — full control, most time — or you can use a tool that fits your context without overbuilding.

For the indie hacker use case specifically, I built SolopreneurPage to solve this exact problem. It's a GDPR-compliant, focused alternative to the Linktree-style tools that were designed for influencers, not builders. You get a clean, professional page under your own domain, no bloat, no third-party tracking nonsense, and a structure that actually makes sense for someone who has multiple products and wants to present themselves credibly to clients.

It's what I use for my own presence, and it's what I'd recommend if you want to get something solid up quickly without spending a week building it from scratch.

What Indie Hacker Portfolio Pages Usually Get Wrong

Even builders who put in the effort tend to make the same few mistakes. Here's what to watch for:

Burying the contact option. If someone has to scroll to the footer to find how to reach you, you've already lost half of them. Your CTA belongs above the fold and at the bottom — nowhere else is acceptable.

No narrative, just a list of links. A page that's just "here are 12 things I've built" with no context reads like a dump of your git history. Clients need to understand the story: what kind of problems you solve, what you care about, how you think.

Projects without outcomes. "I built a habit tracking app" is a feature description. "I built a habit tracking app that reached the top 10 in the Apple Store's Habits category and hit €15k MRR" — that's a result. Results are what get clients to reach out.

Trying to look like an agency. If you're a solo developer, present yourself as one. Trying to look bigger than you are backfires — the right clients specifically want someone senior, experienced, and hands-on. That's you.

Setting it up and forgetting it. Your portfolio page is not a one-time task. Whenever you ship something new, add it. Whenever your focus changes, update the services section. A page that looks current tells clients you're active. A page that hasn't moved in two years tells them you might not be either.

Tools and Platforms to Build Your Page

You've got real choices here, and the right one depends on how much time you want to spend versus how much control you need.

Build it yourself (Next.js, Astro, plain HTML) — This gives you total control over performance, design, and SEO. If you enjoy the process and have a weekend, it's the most customizable option. The tradeoff is time, and the risk is perfectionism paralysis. Many indie hackers never ship the custom site because it's never quite done.

Framer or Carrd — Fast to set up, look clean out of the box, and have good template ecosystems. Framer especially has strong options for developers. The limitation is that you're renting someone else's infrastructure, and customization has a ceiling. Fine for a starting point, but you'll eventually want more ownership.

SolopreneurPage — This is my own product, so I'll be transparent about that. I built it because I needed exactly this: a GDPR-compliant, no-bloat page for solopreneurs who have multiple products and want to present themselves credibly to clients — without spending a week coding or giving up data control. If that's your situation, it's worth a look: solopreneurpage.com.

Notion public pages — Useful for a rough draft or a quick "I need something up today" situation. Not suitable for serious client acquisition. No custom domain by default, limited design control, and it reads as temporary. Use it to think through your structure, then replace it.

A Real-World Example: What Works (and What Doesn't) at Pieter Levels' Scale

Pieter Levels' site at levelsio.com is often cited as the gold standard for indie hacker personal pages — and it's worth understanding what actually makes it work, because not all of it is transferable.

What you can take from his approach: radical transparency about numbers, a clear list of active products with traction, and no corporate pretense. He presents himself exactly as what he is — a solo developer who ships things and has the revenue to prove it. That directness is what builds trust with the right audience.

What only works at his scale: the minimal design, the lack of an explicit services section, the absence of a structured CTA. At his level of recognition, people already know who he is before they land on his page. You and I don't have that luxury yet. If you copy the aesthetic without the reputation behind it, you just get a sparse page that doesn't convert.

The takeaway: take his transparency and directness, but add the structure and clarity that a less well-known builder needs. Make it easy to understand who you are, what you've built, and how to hire you. That combination is what actually turns visitors into clients.

FAQ

Q: How long should my indie hacker portfolio page be?

Short enough to read in 3–5 minutes, long enough to answer the key questions. You don't need a 10-page site — one well-structured page covering your hero section, projects, services, stack, and CTA is enough to get clients. If you want to go deeper, a separate blog or build-in-public section can add depth without cluttering the main page. According to research on freelance developer portfolios, simplicity and clarity consistently outperform complexity in converting visitors (Twine, 2025).

Q: Should I show projects that didn't make money or failed?

Yes — if you frame them honestly. A project you shipped, learned from, and shut down shows initiative and self-awareness, which are both things good clients value. What you want to avoid is a graveyard of half-built things with no context. Briefly explain what you built, what you learned, and why you moved on. That's authentic, and authenticity builds trust in the indie hacker space.

Q: How many projects is too many to show on my portfolio page?

Three to five is the practical sweet spot for a portfolio page, based on what most client-focused portfolio research recommends (Twine, 2025). Beyond that, you risk diluting the impact of your best work. If you have more projects worth showcasing, link to a full archive or your Indie Hackers profile — but keep your featured section tight and curated.

Q: Do I need testimonials if I'm just starting out with client work?

Not necessarily, but they help significantly. If you don't have client testimonials yet, substitute with community credibility: your Indie Hackers profile, a GitHub history showing consistent shipping, or quotes from collaborators about your work style. A genuine statement from someone who's worked with you carries more weight than a blank testimonials section.

Q: Is it better to have a standalone portfolio site or use a platform like SolopreneurPage?

It depends on your priorities. A custom-built site gives you maximum flexibility and the ability to optimize for SEO exactly as you want. A purpose-built platform like SolopreneurPage gets you live faster with a structure already designed for the indie hacker context, GDPR compliance built in, and no infrastructure to manage yourself. If you're early stage and want to start getting clients this week rather than shipping your portfolio site in a month, a solid platform is the more pragmatic choice.