Indie hacker UK: how to build in public as a solo founder

The indie hacker movement is thriving, but almost all the content around it is American. The case studies are from San Francisco. The revenue figures are in dollars. The tax advice assumes you file with the IRS. The communities skew Pacific Time.

If you are a UK-based solo founder building a product, this creates a persistent gap. The strategies are broadly the same, but the details -- where to post, how to handle tax transparency, what legal structures work, which communities actually respond -- are different enough to matter.

This post is the UK-specific guide to building in public. We cover what it means (and what it does not), where to share your journey, how to do it without looking like a spam account, UK-specific legal and financial considerations, and the tools that make shipping as a solo founder actually possible.

---

Key takeaways

• Building in public is about sharing your process, decisions, and numbers -- not performing success or posting motivational content
• UK platforms that work: Twitter/X, LinkedIn (surprisingly effective for B2B), Reddit (r/SideHustleUK, r/UKPF), and Indie Hackers
• GDPR applies to public metrics -- do not share customer data, even aggregated, without considering your obligations
• The UK VAT threshold (currently GBP90,000) is a real milestone to share publicly -- it shows traction without revealing sensitive detail
• Ship fast with AI-native tools (Claude Code, Lovable, Replit) and share the build process -- people engage with "how I built this" more than "look what I built"

---

What building in public actually means

Building in public is sharing the real process of creating a product: the decisions, the numbers, the mistakes, and the progress. It is not a marketing strategy (though it has marketing effects). It is a transparency practice that builds trust, attracts early customers, and creates accountability.

What it is:

• Sharing monthly revenue, user numbers, or growth metrics
• Posting about technical decisions and why you made them
• Being honest about failures, pivots, and things that did not work
• Showing your build process -- screenshots, demos, before-and-after
• Discussing pricing decisions, feature prioritisation, and customer feedback

What it is not:

• Posting motivational quotes with your MRR in the caption
• Creating a curated highlight reel that makes everything look easy
• Turning every interaction into a sales pitch
• Sharing confidential customer information
• Performing humility while bragging ("I am so grateful for this GBP50k month")

The best builders in public are genuinely useful. Their posts teach something, reveal something, or provoke a real discussion. The worst are self-promotional content dressed up as transparency.

---

Where UK indie hackers should build in public

Twitter/X

Still the primary platform for the indie hacker community globally. The UK subset is smaller than the US contingent but active and supportive.

What works:

• Short build updates with screenshots or metrics ("Week 12: launched the billing page. 3 paying customers. GBP147 MRR.")
• Technical threads explaining how you solved a specific problem
• Honest "this didn't work" posts -- these consistently outperform success posts in engagement
• Replying to and engaging with other builders (the community is reciprocal)

What does not work:

• Daily "Day 47 of building my SaaS" posts with no substance
• Threads that are thinly disguised sales pitches
• Engagement-bait questions ("What is the best tool for X?" when you sell a tool for X)

UK-specific tip: Post between 8am and 10am UK time. Most UK indie hackers check Twitter before starting work. The US audience wakes up around 2pm UK time, giving your post a second wave of engagement.

UK accounts worth following: Marc Sherwood (@marcsherwood_), who built and sold multiple micro-SaaS products from the UK. Ben Sherwood (@ben_shw), who shares transparent revenue data from his products. The UK indie hacker Twitter community is small enough that genuine engagement gets noticed.

LinkedIn

Underrated for building in public, especially for B2B products. LinkedIn's algorithm aggressively promotes personal stories and business updates, and the UK B2B audience is large and engaged.

What works:

• Monthly progress updates framed as business lessons
• "Here's what I learned building X this month" posts with specific numbers
• Posts about the transition from employment to solo founding
• Technical content that is accessible to non-technical business people

What does not work:

• The LinkedIn cringe format ("I got fired. But it was the best thing that ever happened to me. Here's why.")
• Posting too frequently (2-3 times per week maximum)
• Pure product promotion

UK-specific tip: LinkedIn has a disproportionately large UK professional audience compared to Twitter. If your product targets UK businesses, LinkedIn may be your best single platform.

Reddit

Reddit is where UK indie hackers go for honest feedback. The communities are smaller than Twitter but the discussions are deeper and more actionable.

Key subreddits:

• r/SideHustleUK -- the largest UK-focused community for people building side projects and businesses. Good for sharing progress and getting feedback.
• r/UKPersonalFinance -- relevant if your product touches money, tax, or financial planning. Strong community but strict moderation -- only share if genuinely relevant to a discussion.
• r/Entrepreneur -- global but with active UK members. Better for strategy discussions than build updates.
• r/SaaS -- technical SaaS community. Good for product feedback and pricing discussions.
• r/IndieDev and r/SideProject -- for sharing what you have built and getting feedback.

What works on Reddit:

• Detailed posts explaining how you built something, with real numbers
• Asking for genuine feedback (not "check out my product" dressed as a question)
• Contributing to other people's threads before posting your own
• AMAs (Ask Me Anything) when you hit a milestone

What does not work:

• Self-promotion without contributing value first
• Posting the same update across multiple subreddits
• Being defensive about negative feedback

Indie Hackers

The original building-in-public platform. Indie Hackers (indiehackers.com) is a dedicated community of people building products, and it has a significant UK contingent.

What works:

• Revenue milestone posts ("GBP1k MRR -- here's how")
• Product launch posts with context on the build journey
• Asking for advice on specific challenges (pricing, marketing channels, tech stack)
• The "product" listing page -- create one and update it monthly with revenue data

UK-specific tip: Indie Hackers has a strong "show your numbers" culture. UK founders tend to be more reserved about sharing revenue publicly. Lean into it -- the community respects transparency, and your UK perspective is a differentiator in a US-dominated space.

---

How to share progress without looking like spam

The line between building in public and spamming is thinner than most people think. Here is how to stay on the right side:

The 5:1 rule

For every one post about your product, make five posts that are useful, interesting, or supportive of others. Comment on other builders' updates. Share someone else's launch. Answer a question. Write a short thread about something you learned that has nothing to do with your product.

This is not a formula -- it is a mindset. If 80% of your online presence is about your product, you are doing marketing, not building in public. If 80% is about the journey, the craft, and the community, the product promotion takes care of itself.

Share the process, not just the results

"We hit GBP5k MRR" is less interesting than "We hit GBP5k MRR. Here's the pricing change that got us there, the three things we tried that failed, and why we nearly gave up in month 4."

People engage with process. They learn from decisions. They remember stories. A screenshot of a Stripe dashboard is content. A screenshot of a Stripe dashboard with a 500-word thread explaining the strategy behind it is building in public.

Be genuinely honest

This is the hardest part. When something goes wrong -- a launch flops, a customer churns, a feature does not work -- the instinct is to stay quiet and only post again when things improve.

Resist that instinct. The most engaging building-in-public content is almost always about failures, pivots, and lessons learned. A thread about "why our Product Hunt launch got 12 upvotes and what we are doing differently" will outperform "we just launched on Product Hunt!" every single time.

If you are considering a Product Hunt launch, our UK-specific Product Hunt guide covers the timezone strategy and preparation.

Batch your updates

You do not need to post every day. A weekly or fortnightly update that covers meaningful progress is more sustainable and more useful than daily noise. Many successful UK indie hackers post a "weekly build log" on one platform and let it propagate naturally.

A good cadence:

• Weekly: one build update on Twitter/X with a screenshot or metric
• Fortnightly: one LinkedIn post reflecting on what you learned
• Monthly: one detailed Indie Hackers or Reddit post with full numbers

---

UK-specific considerations

GDPR and public metrics

You can share your own business metrics publicly. Your revenue, your user count, your conversion rates -- these are your data to share.

What you cannot do:

• Share individual customer data, even anonymised, without considering GDPR obligations
• Post screenshots of customer conversations without consent
• Share email addresses, names, or identifying information
• Use customer data in marketing materials without a legal basis

Practical guidance: share aggregate numbers (total users, MRR, churn rate) freely. Never share anything that could identify an individual customer. If you want to share a customer testimonial or case study, get written consent first. An email saying "yes, you can quote me" is sufficient.

Companies House transparency

If you operate through a UK limited company, your accounts are public record at Companies House. Anyone can look up your company number and see your filed accounts. This is actually an advantage for building in public -- you cannot fake the numbers because they are verifiable.

What this means in practice:

• Your annual accounts (revenue, costs, profit) are public after filing
• Your registered address and director information are public
• Confirmation statements showing ownership are public

Some UK indie hackers lean into this transparency. Linking your Companies House record in your Indie Hackers profile signals that your numbers are real. It is a trust signal that US-based founders cannot easily replicate.

VAT threshold

The UK VAT threshold is currently GBP90,000 in taxable turnover (check HMRC for the latest figure). For a building-in-public indie hacker, this is a natural milestone to share and discuss.

Crossing the VAT threshold means:

• You must register for VAT
• You must charge VAT on UK sales (20%)
• You can reclaim VAT on business purchases
• Your effective pricing for UK B2C customers increases by 20% unless you absorb the cost

This is a real operational challenge that your audience will find interesting and useful. Write about it. Explain your decision (absorb the VAT or pass it to customers). Share the impact on your metrics. This is exactly the kind of UK-specific content that is missing from the global indie hacker conversation.

For broader guidance on pricing around these thresholds, see our SaaS pricing guide for UK founders.

Business bank accounts

UK business banking has improved dramatically. For solo founders building in public, having a clear separation between personal and business finances is essential -- both for Companies House compliance and for sharing clean revenue metrics.

Starling Business and Tide are the most popular choices among UK indie hackers. Both offer free accounts, both integrate well with accounting tools, and both provide the transaction exports you need for clean bookkeeping.

---

Tools for building in public as a UK solo founder

Shipping fast

The faster you ship, the more you have to share. The best building-in-public accounts post frequent, tangible progress because they are actually building frequently.

Claude Code is the most capable tool for solo founders who want to ship production-quality code quickly. It operates as an autonomous agent in your terminal -- you describe what you want, and it writes, tests, and commits the code. For a solo founder who needs to be both product manager and developer, Claude Code compresses weeks of work into days. See our beginner's guide to Claude Code and our comparison of Claude Code vs Cursor.

Lovable is the fastest path from idea to working page. For solo founders who need to build landing pages, MVPs, and prototypes quickly, Lovable produces deployable results in under an hour. It is particularly useful for building in public because you can share progress screenshots at every stage of the iteration. See our landing page tutorial with Lovable.

Replit is the best option for building tools and automations that run in the cloud. No server management, no DevOps -- just describe what you want and deploy. Good for the internal tools and automations that solo founders need but do not want to spend time on. See our Replit vs Lovable comparison.

Deploying

Vercel is the default deployment platform for most indie hackers. Free tier covers most early-stage products. Deploy with a git push and get a live URL in seconds. The UK CDN performance is strong.

Stripe handles payments. GBP-native, UK-registered, HMRC-compatible. Stripe's dashboard is also a common source of building-in-public screenshots -- just make sure you are not accidentally revealing customer information.

Tracking and sharing metrics

Plausible Analytics -- privacy-focused, GDPR-compliant, no cookie banner required. GBP7/month. Perfect for sharing traffic metrics publicly because you can make your dashboard public without exposing individual user data.

Simple Analytics -- similar to Plausible, slightly different feature set. Also GDPR-compliant and based in the EU.

Fathom -- another privacy-first analytics tool popular with indie hackers. Slightly more expensive but with some additional features around event tracking.

All three of these produce clean, shareable dashboards that work well for building-in-public posts.

---

Building in public: a realistic UK timeline

Here is what a realistic building-in-public journey looks like for a UK solo founder, from idea to traction.

Weeks 1-2: Idea and validation

• Post your idea publicly and ask for feedback
• Build a landing page with Lovable (share the process)
• Drive traffic from Reddit and Twitter to the landing page
• Share sign-up numbers honestly (even if they are low)
• Post: "Week 1: I'm building X. Here's why and here's the landing page. 14 sign-ups so far."

For a structured validation approach, see our guide to validating a SaaS idea with AI tools.

Weeks 3-6: Building the MVP

• Build with Claude Code or Lovable (share screenshots of the process)
• Post technical decisions: "I chose Supabase over Firebase because..."
• Share setbacks: "The auth flow broke and here's why"
• Post: "Week 4: MVP is nearly functional. 3 features done, 2 to go. Still at 14 sign-ups but I haven't done any marketing yet."

Weeks 7-10: Launch and first customers

• Launch on Product Hunt, Reddit, and Indie Hackers
• Share the launch numbers transparently
• Post about your first paying customer (with their permission)
• Post: "Week 8: launched last Tuesday. 47 Product Hunt upvotes, 3 paying customers, GBP36 MRR. Not life-changing but real."

Months 3-6: Growth and iteration

• Monthly revenue updates with context
• Feature decisions driven by customer feedback (share the feedback)
• Pricing experiments (share what you tested and what worked)
• Post: "Month 4: GBP890 MRR. Raised the price from GBP9 to GBP15/month. 2 customers churned but new conversion rate is higher. Net positive."

Months 6-12: Compounding

• By now, your building-in-public content itself drives traffic and sign-ups
• People follow your journey and become customers
• Other builders share your posts because they are genuinely useful
• Post: "Month 9: GBP3,200 MRR. 40% of new customers say they found us through Twitter. Building in public is now our primary acquisition channel."

This timeline is realistic, not aspirational. Many UK indie hackers take longer to reach meaningful revenue. The building-in-public practice makes the journey sustainable because the content creation is the progress, not an addition to it.

---

UK indie hackers to follow

The UK indie hacker scene is smaller than the US equivalent but growing quickly. Here are builders worth following for inspiration and practical learning:

Marc Sherwood -- has built and sold multiple micro-SaaS products from the UK. Posts transparent revenue updates and practical build advice on Twitter/X.

Ben Sherwood -- shares detailed revenue breakdowns and technical decisions. Particularly good on the operational side of running a solo SaaS from the UK.

Danny Postma -- while based in the Netherlands, his approach resonates strongly with UK builders. He builds AI tools, shares revenue publicly, and his content is practical rather than performative. Worth studying his approach even if he is not technically UK-based.

The UK community is small enough that if you start building in public genuinely, you will be noticed. Follow these builders, engage with their content, and you will find yourself part of a supportive network within weeks.

---

Frequently asked questions

Do I need to share my exact revenue to build in public?

No. Revenue sharing is common in the indie hacker community, but it is not required. You can build in public by sharing your process, decisions, technical challenges, and user metrics without revealing exact revenue figures. Some founders share revenue ranges ("between GBP1k and GBP5k MRR") or growth percentages ("revenue grew 30% this month") instead of exact numbers. Share what you are comfortable with -- authenticity matters more than specific numbers.

Is building in public risky for a UK sole trader?

The main risks are competitive (showing your hand to potential competitors) and personal (public failures). In practice, most UK solo founders find the benefits outweigh the risks. Competitors rarely target micro-SaaS products, and the goodwill from transparent failure is greater than the reputational cost. The bigger risk is not building in public and remaining invisible in a crowded market.

How do I handle negative feedback when building in public?

Treat it as free customer research. Most negative feedback contains a kernel of truth -- a feature gap, a positioning problem, or a UX issue you had not noticed. Respond professionally, thank the person for their input, and share what you plan to do about it. "Someone pointed out that our onboarding is confusing. They're right. Here's how we're fixing it" is excellent building-in-public content. Never get defensive publicly -- it reflects poorly and discourages future feedback.

Can I build in public with a full-time job?

Yes, and many UK indie hackers do. Be aware of your employment contract -- some UK contracts include clauses about side projects, intellectual property, or competing businesses. Check your contract before going public. Most employers are fine with side projects that do not compete with their business, but it is worth confirming. Many builders in this situation share their journey under a pseudonym or product name rather than their personal name until they are ready to go full-time.

How long before building in public generates customers?

Expect 3-6 months of consistent posting before building in public becomes a meaningful acquisition channel. The first few months are about building an audience and establishing trust. Customer acquisition accelerates once you have a track record of transparent updates and a product that people can see evolving. The compounding effect is real but slow to start -- stick with it through the early months when it feels like you are posting into a void.

---

Ready to find your next build?

Every Thursday, IdeaStack publishes a deeply researched UK business opportunity -- complete with keyword data, competitor analysis, and copy-paste builder prompts. Read this week's free report.