BuildLog: Public Project Journals for Makers and Indie Hackers

The Idea

BuildLog is a structured platform where makers, developers, and craftspeople document their build process in sequential public chapters — and monetize by selling finished work directly to the audience that followed the journey.

Whether you're throwing a ceramic collection, building an indie SaaS from scratch, crafting a custom furniture piece, or assembling an analog synthesizer — you log the process in chapters, grow subscribers who follow along, and when the thing is done, sell it to the people already invested in its story.

Substack is for writers. Gumroad is for digital downloads. Etsy is an anonymous storefront. BuildLog is for the build — and the story creates the audience that buys the output.

The Problem You Solve

Two communities have no shared home:

Physical makers (potters, woodworkers, leather workers, jewelers) post their process on Instagram or TikTok, but those platforms are algorithmic, transient, and hard to monetize directly. There is no structured way to document a multi-week project in a way that builds lasting subscriber relationships.
Indie hackers and developers who "build in public" scatter their updates across Twitter/X threads, blog posts, and changelogs — but there is no dedicated, structured format designed for a build journal.

Neither group has a platform optimized for: project-first content, chapter-by-chapter documentation, subscriber notifications, and integrated product sales when the build is done.

Core Features (MVP)

Project creation — Title, description, category (physical / digital / hybrid), cover image
Chapter editor — Markdown-based log entries with photo uploads, timestamped, published as sequential chapters
Subscriber email capture — Visitors can subscribe to a project; get notified when a new chapter drops
Finished product listing — When the build completes, creator lists item(s) for sale directly on the project page with Stripe Checkout
Public creator profile — Lists all active and completed projects
Discovery feed — Curated feed of active builds across categories

Non-MVP (Phase 2): patronage/tip jar, custom domains, embeddable build widget for personal sites, native iOS app

Pricing

Creator Plans (monthly subscription):

Free — 1 active project, basic stats, email capture (up to 100 subscribers)
Builder — $19/month — Unlimited projects, unlimited subscribers, product listings (up to 10 active), custom project URL slug
Maker Pro — $39/month — Everything in Builder + custom domain, CSV export, priority support, early access to new features

Platform transaction fee: 5% on all product sales processed through BuildLog

Revenue mix target: 60% subscription / 40% transaction fees

Tech Stack

Frontend: Next.js + TypeScript (App Router, SSG for public project pages)
Backend/DB: Supabase (auth, postgres, storage for images)
Payments: Stripe (subscriptions + Checkout for product sales)
Email: Resend (subscriber notifications, chapter drop emails)
Hosting: Vercel
Editor: Tiptap or simple markdown with react-markdown rendering

How to Build MVP

Week 1–2:

Supabase schema: users, projects, chapters, subscribers, products
Auth (email + GitHub OAuth via Supabase)
Project creation and chapter editor (markdown + image upload to Supabase Storage)
Public project page (SSG via Next.js)

Week 3:

Email subscriber capture on public project pages
Resend integration: notify subscribers when creator publishes a new chapter
Creator dashboard: project list, chapter management, subscriber count

Week 4:

Stripe integration: Creator plans (Free / Builder / Maker Pro) via Stripe Billing
Product listing on completed projects with Stripe Checkout
5% platform fee via Stripe Connect or application fee

Week 5–6:

Discovery feed (manually curated initially, then by recency/activity)
Onboard 10–15 beta creators from pottery/ceramics community + indie hacker community (Twitter/X, Indie Hackers forum)
Collect feedback, fix top 5 friction points
Public launch (Product Hunt, Hacker News Show HN)

How to Get First Customers

Pottery and craft community (warm channel):

Post your own BuildLog project documenting a ceramic collection — use it as the product demo
Share in pottery subreddits, ceramics Facebook groups, local maker communities
DM potters and woodworkers on Instagram who already post process content: "I built a platform for this"

Indie hacker community (warm channel):

Post on Indie Hackers: "I built a 'build in public' platform — looking for beta creators"
Tweet the build process of building BuildLog on BuildLog — meta, recursive, perfect
Post in "building in public" Twitter/X community circles

Content flywheel:

Each creator's public project page is SEO-indexed — every build generates content
"How I built X" is highly searchable — a woodworker's project journal for a custom desk ranks organically

Revenue Math

Month 6 target (conservative):

80 Builder plan subscribers × $19 = $1,520/month
20 Maker Pro subscribers × $39 = $780/month
$25,000 GMV in product sales × 5% = $1,250/month
Total: ~$3,550/month

Month 12 target:

350 Builder subscribers × $19 = $6,650/month
80 Maker Pro subscribers × $39 = $3,120/month
$80,000 GMV × 5% = $4,000/month
Total: ~$13,770/month

Milestone: ~330 paying creators hits $10k/month. With two distinct communities to draw from (makers + indie hackers), this is achievable with consistent distribution.

Why This Is Different

Platform	What it's for	What's missing
Substack	Long-form essays	Not designed for builds or physical goods
Gumroad	Selling digital products	No process documentation, no subscriber journey
Etsy	Selling physical products	No story, no build log, algorithmic discovery
Twitter/X	Build-in-public threads	Ephemeral, no structure, no monetization
YouTube	Video content	High production bar, not text/photo native

BuildLog is the only platform where the documented build process is the product — and the audience you earn through the story is the customer base for what you sell.

Path to Quitting Day Job

Month 1–2: Build and soft-launch, onboard 10–20 beta creators for free
Month 3–4: Enable paid plans, target 50 paying creators
Month 6: $3,500–$5,000/month MRR — meaningful side income
Month 9: $7,000–$9,000/month — reduce freelance commitments or day job hours
Month 12: $10,000–$15,000/month — viable full-time replacement

The creator economy has proven willingness to pay for distribution and monetization tools. Substack grew by making existing writers more money. BuildLog does the same for physical and digital makers.

Risks & Mitigations

Risk: Low creator-side adoption — creators prefer Instagram/TikTok Mitigation: Target creators already frustrated with algorithmic platforms. Pottery and woodworking communities actively seek alternatives. Indie hackers are the most "building in public" motivated audience on the internet.

Risk: Low transaction volume makes 5% fee revenue thin Mitigation: Subscription revenue is the primary model. Transaction fees are upside, not the foundation.

Risk: Substack or Gumroad adds a "project journal" feature Mitigation: Neither serves physical makers well; both are structurally oriented around essays or digital files. Niche focus and community relationships create switching costs.

Risk: Marketplace chicken-and-egg (no creators = no buyers) Mitigation: Public project pages are SEO content that drives organic discovery. Creators benefit even before buyers arrive, because the platform builds their public portfolio.

Why This Works for You Specifically

You are the target user twice over:

As a potter, you already document your process mentally — BuildLog is the tool you'd want to log a glaze experiment series or a ceramic collection drop
As an indie hacker, you understand "building in public" culture from the inside — you know what the IndieHackers community wants and how to talk to them

You have all the technical pieces: Next.js, Supabase, Stripe, Resend. The MVP is well within your solo-build capability. And you have authentic credibility in both communities that no generic SaaS founder would have.

First Action

Start your own BuildLog project today — document the creation of BuildLog itself, in BuildLog, from day one. This is both your product demo and your launch marketing. Share the first chapter on Indie Hackers and Twitter/X this week.