Photo by James Harrison on Unsplash
In October 2025, Pieter Levels called out fake MRR screenshots on X. Marc Lou built TrustMRR in 48 hours to fix it: connect a read-only Stripe API key, get a page showing verified revenue pulled live from the source. It generated $18,000 in ad revenue within 48 hours of launching — because the appetite for verified proof over claimed numbers was that real.
That episode clarified something the indie hacker community had been circling for a while: a profile that claims numbers is noise. A profile that proves them is a different thing entirely.
An indie hacker profile is a public page where your shipped work, verified revenue, code activity, and identity come together on one URL — so when someone asks "what do you build?", the link does the answering. Done right, it compounds. Every tweet, cold email, and conference conversation can end with "here's my page." Done poorly, it is a list of claims with no receipts.
Two of the most-praised developer profile platforms — Polywork and Read.cv — shut down or were acquired in the first five months of 2025. Meanwhile, solo-founded startups rose from 23.7% of all new companies in 2019 to 36.3% by mid-2025, per Carta's Solo Founders Report. More founders means more noise. As of June 2026, standing out requires showing, not telling.
Here are the seven things an indie hacker profile needs to do that work.
Why 2025 Changed What an Indie Hacker Profile Needs to Do#
Two things happened in 2025 that shifted the baseline for what a credible indie hacker profile has to show.
First, the platforms disappeared. Polywork shut down January 31, 2025, after raising over $40 million. Read.cv was acquired by Perplexity AI and shut down by May 16, 2025. Both were widely praised by developers for their design and intent. When they closed, every profile on them vanished. A profile on a platform you do not control is a countdown timer, not an asset.
Second, the revenue screenshot stopped working. Pieter Levels calling out fake MRR numbers in late 2025 did not invent the problem — it surfaced it. Revenue screenshots had always been unverifiable. With AI image editing accessible to anyone, fabricating a Stripe dashboard takes minutes. The market responded: TrustMRR connects directly to payment processors and renders data on its own servers so the number cannot be edited, backdated, or rounded up. Over $1 billion in verified revenue is now on the platform.
Gartner predicts that by 2028, one in four candidate profiles globally will be fake. The value of authentic, hard-to-fabricate signals — a years-long commit history, a live payment gateway connection, a profile that updates itself — is increasing because trust is getting scarcer.
1. A Ship History with Live Stats (Not a Screenshot Gallery)#
The first thing someone scans on an indie hacker profile is the project list. Not your bio. Not your follower count. The things you have actually shipped.
A convincing project list and a weak one are separated by one thing: whether the metrics are live or static. "MyApp — a SaaS tool for freelancers, 2,000 users" is just text. The same card with a live GitHub star count, total commits, and current MRR from a connected payment gateway is a proof card. If your stars went from 40 to 800 after a Product Hunt launch, that shows up automatically. If your commit velocity has been consistent for 14 months, that shows up too.
Pieter Levels documented every step of fly.pieter.com publicly, from the first commit to $1M ARR in 17 days in March 2025. The public ship history was not incidental — it was the distribution strategy. As Levels wrote about building Hoodmaps in public: "Even better, just the fact that I built it in public is unique and is marketing."
What to include in your ship history:
Every live project, including ones at $0 revenue
One sentence on who it is for and what problem it solves
Your tech stack as tags, not a paragraph
A GitHub link for anything with public code
Live revenue for anything connected to a payment gateway
Setup: link each project's GitHub repository and connect a payment integration. The stats update on their own. You ship; the profile reflects it.
Thing 2: Verified Revenue — Not Screenshots, Actual Numbers#
Here's the problem with sharing a screenshot of your Stripe dashboard: anyone can fake one in five minutes. Your audience knows this. Prospects know this. And that gnawing suspicion quietly kills the trust you were trying to build.
Arvid Kahl, author of The Embedded Entrepreneur, is blunt about it: "Building in public is worthless if no one can verify what you're building toward. The founders who actually convert followers into customers are the ones who make their numbers impossible to dispute."
Verified revenue means connecting a real payment gateway via a read-only API key — no write access, no risk — so your profile can pull live MRR directly from the source. DevBio supports four payment providers: Stripe, Dodo Payments, LemonSqueezy, and Polar. Once connected, the Earnings component displays your live monthly recurring revenue on your public profile, updated automatically.
The signal this sends is entirely different from a screenshot. There's no "I could have doctored this" — the number comes straight from the processor.
When your connected MRR crosses zero, DevBio automatically grants you the Verified Founder Badge — a visual trust marker that appears on your profile without any manual review or application. It's the difference between saying "I make money from this" and having your payment processor say it for you.
If you want a deeper breakdown of how live MRR display works and why it converts, read our full guide: How to Show Live MRR on Your Developer Profile.
Thing 3: A GitHub Heatmap That Actually Shows Your Commits#
Every developer profile says "passionate builder." The GitHub contribution heatmap shows it.
GitHub has over 180 million registered developers. The heatmap — that grid of green squares representing daily commit activity — has become the universal shorthand for "this person ships consistently." Recruiters scan it. Potential co-founders look for it. Early customers use it as a proxy for "will this product be maintained?"
The catch: approximately 82% of developers keep their most significant work in private repositories. If your heatmap only reflects public activity, it's showing a fraction of the story — and often the less impressive fraction.
A profile setup worth its salt should display your full contribution heatmap, including private repos, so the picture is complete. This isn't about gaming optics; it's about not penalizing yourself for doing real work on paid client projects or pre-launch products.
On DevBio, the contribution-heatmap component pulls your entire contribution history (public + private, with private repo activity shown as activity without exposing repo names). The result is a timeline of work, not a curated highlight reel.
For the technical setup and why this matters for developer credibility, see: Why Your GitHub Contribution Heatmap Belongs on Your Developer Profile.
Thing 4: Skills as a Spec Sheet, Not a Tag Cloud#
Most profiles list skills like a dictionary entry: React, TypeScript, Node.js, PostgreSQL, Docker, AWS, GraphQL, Redis... The list goes on until the viewer's eyes glaze over.
The problem isn't the skills — it's the format. A tag cloud with 30 equal-weight technologies says nothing about what you're actually good at or what kind of work you want.
Think of your skills section as a spec sheet, not a keyword dump. The questions a serious client or collaborator is asking are:
What can you do right now, at production quality? (Core stack)
What are you actively learning or comfortable with? (Secondary tools)
What's your specialty within your stack? (The thing you're faster at than most)
That last one is the differentiator. "React developer" is a commodity. "React developer who specializes in performance-critical dashboards with real-time data" is a role someone is actively searching for.
For SEO, a well-structured skills section also helps your profile appear in long-tail searches like "hire TypeScript developer building in public" — the kind of intent-specific queries that convert at higher rates than broad searches.
On your skills component, keep the list to 8–12 technologies max, order by fluency (most confident first), and include a one-line specialty statement if your profile platform supports it. Cut anything you wouldn't be comfortable being interviewed on tomorrow.
Thing 5: An About Section That's a Story, Not a Bio#
"Experienced full-stack developer with 7 years in the industry, passionate about creating scalable solutions."
That sentence appears on roughly a third of all developer profiles. It says nothing, differentiates nothing, and convinces no one of anything.
Your About section is your one shot at narrative. It should answer three questions in under 200 words:
What problem do you exist to solve? Not "I build web apps" — what specific problem do your products address, and why does that problem matter to you?
What have you shipped that proves it? One or two concrete outputs with numbers attached: "Shipped [product] to 300 paying customers" or "Grew from 0 to $2,400 MRR in 8 months."
What do you want next? This is the hidden CTA. Are you open to freelance? Looking for a co-founder? Raising? Hiring? Saying nothing about what you want means visitors have to guess — and most won't bother.
The format that works: open with the problem (creates empathy), give your trajectory (creates credibility), close with a specific ask (creates conversion). Three paragraphs, under 200 words, no corporate-speak.
Specificity always outperforms breadth. "I'm building a scheduling tool for solo consultants" is more interesting than "I'm passionate about productivity software" — even though the second sounds more impressive on paper.
Thing 6: An OG Image That Shows Your Numbers When Shared#
Every time someone links to your profile on X, LinkedIn, or in a Slack channel, a preview card appears. For most developer profiles, that card is generic — a default avatar, maybe a site logo, and a blank background. It's a wasted impression.
An OG (Open Graph) image with a live KPI strip turns every share into a billboard. Instead of showing a static logo, it dynamically renders your current MRR, GitHub stars, recent commits, and subscriber count — pulled from your connected integrations the moment the preview is generated.
The compounding effect is significant. When someone shares your link and the preview shows "$3,200 MRR · 847 GitHub stars · 23 commits this week," that data does its own selling before anyone clicks through. You don't have to explain your traction — the preview explains it.
DevBio's OG image includes a live KPI strip that pulls from whatever integrations you've connected: Stripe/Dodo/LemonSqueezy/Polar for revenue figures, GitHub for activity metrics. The strip updates automatically, so it never shows stale data.
This is the kind of passive distribution most indie hackers leave on the table. Every social share is a mini-announcement — make it carry information worth seeing.
Thing 7: A Marketplace Listing with Your Asking Price#
This one surprises people, but it's one of the highest-leverage things on this list.
When you connect a product to a payment integration on DevBio, it's automatically listed on the DevBio Marketplace with live MRR attached. You can optionally set an asking price, making your product discoverable to acquisition buyers who are actively browsing for profitable micro-SaaS to purchase.
The solo founder exit market has grown substantially. Buyers on platforms like Acquire.com and MicroAcquire regularly pay 2–4× annual recurring revenue for bootstrapped products. Many of these acquisition buyers are looking for sub-$5K MRR products specifically because there's less competition from PE firms and strategic acquirers at that size.
Having a marketplace listing does three things:
Creates optionality — you're not committing to sell, just signaling that you're open
Adds credibility — a product with a listed asking price reads as a real business, not a side project
Attracts inbound interest — buyers find you instead of you pitching to them
Even if you're not planning to sell, the discipline of pricing your product forces you to think about it as an asset with a multiple — which tends to change how you build and grow it.
The combination of live MRR + marketplace listing on a single public profile is a trust signal stack that most indie hacker profiles don't have. It's also the combination that's hardest to fake.
The Ship-Prove-Grow Framework#
The 7 things above aren't a checklist to complete once and forget. They're a live system. Here's how they work together:
Ship — Your commit heatmap and project history show consistent output. This is the foundation. Visitors who arrive skeptical leave as believers when they can see you've shipped 40 consecutive weeks without a gap.
Prove — Verified revenue, the Verified Founder Badge, and your marketplace listing all say the same thing in different ways: this is a real business. Each element independently adds credibility; together they create a trust stack that's hard to argue with.
Grow — The OG image KPI strip, your About section's explicit ask, and your skills spec sheet all do active work converting visitors. They answer "why should I follow/hire/buy from this person?" before the visitor has to ask.
Most indie hacker profiles have Ship (GitHub link) and a weak version of Prove (screenshot), but almost none have the full Grow layer activated. That's the gap — and it's where profiles stall out at 400 followers instead of breaking through to the audience size that compounds into revenue.
How DevBio Compares for This Use Case#
Feature | DevBio | Linktree | Carrd | Bento |
|---|---|---|---|---|
Live MRR from payment processor | ✅ Stripe, Dodo, LS, Polar | ❌ | ❌ | ❌ |
GitHub heatmap (incl. private repos) | ✅ | ❌ | ❌ | Partial |
Verified Founder Badge (auto) | ✅ | ❌ | ❌ | ❌ |
OG image with live KPIs | ✅ | ❌ | ❌ | ❌ |
Auto marketplace listing | ✅ | ❌ | ❌ | ❌ |
Custom domain | ✅ Pro | ✅ | ✅ | ✅ |
Built for indie hackers specifically | ✅ | ❌ | ❌ | Partial |
The gap is primarily in data verification. Generic link-in-bio tools can display whatever you type — which is the problem. DevBio's distinguishing architecture is that the numbers come directly from connected APIs rather than manual input, making them independently verifiable.
What NOT to Put on Your Indie Hacker Profile#
Worth saying explicitly, because these mistakes are common:
Vanity metrics without context. "500K impressions" means nothing without conversion data. A customer or co-founder doesn't care about impressions — they care about what those impressions produced.
Testimonials without attribution. "This tool changed my workflow!" says nothing without a real name and company attached. Anonymous testimonials are treated as fabricated because they frequently are.
Technologies you'd fail an interview on. If you list "machine learning" because you completed a Coursera course, you will get burned when someone asks about it. Credibility is harder to rebuild than it was to establish.
A "coming soon" product. A profile listing a product that doesn't exist yet reads as the profile of someone who wants to be a founder, not someone who is one. Save the slot for something live. Waitlists are fine, but the product needs to exist enough to have a URL.
Your job title instead of your builder identity. "Senior Software Engineer at [Company]" tells visitors about your employer, not you. If you're building in public, lead with what you're building — the day job can be one line in your About section.
Frequently Asked Questions#
Do I need to be profitable to have an indie hacker profile?
No — but you need to be shipping. The profile isn't a trophy for hitting revenue milestones; it's a working document of your builder journey. The most compelling profiles often belong to founders in the $0–$500 MRR range who are documenting every step publicly. The verified revenue layer becomes more valuable once you have revenue, but consistent commits and a live project are enough to start building an audience before that.
What's the difference between an indie hacker profile and a traditional developer portfolio?
A developer portfolio is primarily backward-looking — it shows what you've built for others, usually for employers or clients. An indie hacker profile is forward-looking and live. It shows what you're building right now, with real traction signals (revenue, stars, commits) rather than static case studies. The audience for each is different: employers for portfolios, potential customers and co-founders for indie hacker profiles.
Should I show my MRR if it's very low — say, under $100?
Yes, with context. "$47 MRR" is more credible than most no-revenue profiles because it proves you have at least one paying customer. Frame it as Month X of building in public: "Month 4 · $47 MRR · 3 customers." The trajectory matters as much as the number. Hiding your early numbers means you also lose the narrative arc when the numbers get interesting.
How many projects should I list on my profile?
One to three, prioritized by ones with payment integrations and live data. More than three starts to read as scattered. If you've built more, keep the others in a portfolio section or a separate page — your profile should answer "what is this person building right now?" not "what have they ever built?"
Is the Verified Founder Badge automatic or do I apply for it?
It's automatic. On DevBio, connecting any payment integration (Stripe, Dodo, LemonSqueezy, or Polar) with MRR greater than zero triggers the badge without any review process. There's no application, no follower threshold, and no manual approval step.
What makes a GitHub heatmap actually impressive vs. just noise?
Consistency over density. A heatmap that shows 40 straight weeks of daily commits — even modest ones — reads as more credible than a heatmap with a few intense bursts and long gaps. Reviewers are looking for sustainable shipping cadence, not a single sprint. Including private repo activity is important here because most real work happens in private repos; a heatmap showing only public activity often looks sparse even for prolific builders.
Does it matter what platform I use for my indie hacker profile?
It matters if the platform verifies your data. A profile on a platform that displays only what you type is indistinguishable from a fabricated one. The value of platforms that pull directly from payment processors and GitHub APIs is that they make your numbers independently verifiable — which is what converts skeptical visitors into followers, customers, or collaborators.
Your Profile Is Your Pitch Deck#
Most founders spend months crafting a pitch deck they show to a handful of people. Your indie hacker profile is a pitch deck that runs 24/7, reaches anyone who finds you, and compounds over time as your numbers grow.
The seven elements above — ship history, verified revenue, GitHub heatmap, skills spec sheet, About narrative, OG KPI image, and marketplace listing — aren't features to collect. They're trust signals that answer every question a visitor might have before they ask it.
The founders who hit $10K MRR almost always say the same thing in retrospect: the audience came first, and the audience was built on credibility, not hype. Your profile is where that credibility lives.
Set up your indie hacker profile on DevBio →
Start with a free account. Connect your first payment integration. Watch the Verified Founder Badge appear. The rest compounds from there.