Back to Blog
build in publicframeworksai brainindie hacker

Build in Public Frameworks: The 5 That Actually Work in 2026

FUEL, Fish Pond, Audience-First, I&You, AI Brain — the five frameworks that produce results in 2026, when to use each, and why most build-in-public frameworks fail at scale.

··7 min read

Build in Public Frameworks: The 5 That Actually Work in 2026

TL;DR

  • Five frameworks have survived contact with the 2026 build-in-public reality: FUEL (Cheung), Fish Pond (Cheung), I&You (Cheung), Audience-First (Kahl), and AI Brain (buildinpublic.so).
  • Each framework solves a different problem. Using the wrong one for your stage wastes energy on the wrong constraint.
  • The newest framework — AI Brain — addresses the 2026-specific problem that the older four did not: voice persistence across AI-generated content.

Build-in-public frameworks are the mental scaffolding founders use to think about audience, content, and distribution. Most frameworks proposed since 2018 have not survived contact with the 2026 reality (vibe coding, supply saturation, ghost mode). The five that have are worth knowing in detail because they cover different failure modes — picking the right framework for your specific problem matters more than picking "the best" framework abstractly.

This cluster sits inside our build in public pillar and complements builder mindset.

The five frameworks

Framework 1 — FUEL (Kevon Cheung)

Cheung's framework for what to share in build-in-public posts:

  • Feelings (your emotional state about the work)
  • Updates (what shipped, what changed)
  • Education (what you learned others can use)
  • Launches (releases, milestones, asks)

The framework's value: it gives you four reliable content buckets to rotate through, preventing the "I only post launches" failure mode. The limitation: FUEL was designed pre-2026 and predates the workflow-vs-performance split. It still works but needs adaptation — Feelings posts have to be specific, not performed; Launches should be small / honest, not promoted.

When to use FUEL: as a posting cadence framework when you are running out of ideas of what to post about.

Framework 2 — Fish Pond (Kevon Cheung)

The thesis that you should plant your build-in-public presence in the smallest possible audience pond where your buyers actually live, rather than the biggest possible pond where everyone broadcasts.

The mechanics:

  • Identify your "fish pond" — the specific subreddit, Discord, Slack, or community where your buyers congregate
  • Become a recognized voice in that pond before you ever post about your product
  • Launch into the pond first, only expand to bigger waters once you have established presence

The framework's value: it explicitly counters the broadcast-to-everyone failure mode. The limitation: works best for B2C and prosumer products where the buyer audience is identifiable; works less well for diffuse B2B products where buyers do not congregate.

When to use Fish Pond: pre-launch and weeks 0-12 post-launch.

Framework 3 — I & You (Kevon Cheung)

The framework for the conversational mode of build-in-public:

  • I mode: sharing your own work, struggles, learnings (founder-to-audience)
  • You mode: asking the audience questions, soliciting feedback, amplifying others (audience-to-founder)

The thesis: most founders run pure-I mode (broadcast) and wonder why no one engages. Mixing in You-mode posts (questions, amplifications, replies) trains the audience to participate.

The framework's value: actionable balance for founders whose accounts feel one-directional. The limitation: requires real engagement, not the manipulative "ask a question to game the algorithm" version which operators detect.

When to use I&You: ongoing, for tuning the engagement quality of your posts.

Framework 4 — Audience-First (Arvid Kahl)

Kahl's framework — articulated in The Embedded Entrepreneur — argues that founders should build an audience before building the product. The audience tells you what to build; the product is downstream.

The mechanics:

  • Pick a specific audience (a profession, a community, a use case)
  • Embed in that audience for months — listen, contribute, learn
  • The product idea emerges from the audience's expressed pain
  • Launch into an audience that already trusts you

The framework's value: avoids the most common solo-founder failure mode (building a product nobody wants). The limitation: assumes you have 6-12 months of patience to build the audience before product, which is increasingly rare in the vibe-coding era where build cycles are 3-30 days.

When to use Audience-First: at the category decision (which space to enter) rather than at the product decision (what to ship inside that space). Works especially well as a meta-framework for which fish pond to swim in.

Framework 5 — AI Brain (buildinpublic.so, 2026)

The newest framework, addressing a 2026-specific problem: voice persistence across AI-generated content.

The thesis: as more of your content gets AI-drafted, the risk is voice drift — content across weeks reads as written by three different people because the AI has no memory of how you write. The AI Brain pattern solves this with a persistent memory layer that holds:

  • Your voice rules (words you use, words you avoid, sentence structures)
  • Your project context (what you are building, who buys it, what stage)
  • Your prior posts (what you have already said about what)
  • Your .cursorrules-equivalent voice scaffolding

When Loudy (or any ghostwriter) drafts a new post, it loads from AI Brain so the output stays voice-consistent.

The framework's value: solves the voice-drift problem that frequent AI-assisted posting otherwise creates. The limitation: requires tooling (it is not just a mental framework — you need a persistent memory store integrated with your ghostwriter).

When to use AI Brain: from day 1 if you plan to use AI for any portion of your content production.

How the five frameworks fit together

The frameworks are complementary, not competing:

  • Audience-First decides which fish pond to swim in
  • Fish Pond decides how to swim in it
  • FUEL decides what to post (the content buckets)
  • I & You decides the engagement mode of each post
  • AI Brain keeps the voice consistent as you scale posting frequency

A solo founder using all five gets: a defined audience (Audience-First), a specific community to embed in (Fish Pond), a rotation of content types (FUEL), a balance of broadcast vs participation (I & You), and voice consistency across AI-assisted output (AI Brain).

What does not work

Frameworks that did not survive 2026:

  • The MRR-Public framework. "Share your MRR daily to build trust." Worked in 2017-2020; produced more stress than signups by 2024.
  • The Pure-Hustle framework. "Ship daily, post constantly, sleep less." Burnout pipeline. Most founders running this quit by month 3.
  • The Founder-Story framework. "Tell your origin story to attract followers." Once worked; in 2026 every founder has the same story (laid off, learned to code with AI, shipped a SaaS). The story is no longer differentiating.

Sibling clusters

FAQ

Which framework should I start with? If you have no audience and no product: Audience-First (Kahl). If you have a product but no audience: Fish Pond (Cheung). If you have both and are running out of content ideas: FUEL (Cheung). If your posts get no engagement: I & You (Cheung). If you are using AI to draft and noticing voice drift: AI Brain (buildinpublic.so).

Are these frameworks mutually exclusive? No — they address different layers of the practice. Audience-First is a category decision, Fish Pond is a community decision, FUEL is a content-type decision, I & You is a tone decision, AI Brain is a voice-persistence decision. A founder running all five layers concurrently has the most coherent practice.

Why is AI Brain a 2026-specific framework? Because the problem it solves (voice drift across AI-assisted posts) did not meaningfully exist before 2023-2024. When most posts were human-written, voice persistence was natural — the same person wrote every post. As AI tooling took on more drafting, voice consistency became a structural problem requiring a structural answer.

Should I follow Kevon Cheung's Build in Public Mastery program? The program is well-regarded and Cheung's frameworks are the most-cited in the practice. Worth it if you prefer structured curriculum and community accountability. Not strictly necessary — the public frameworks (FUEL, Fish Pond, I&You) are documented across his blog, and you can implement them without the program. The program adds accountability and community, which some founders need and others do not.

What is the relationship between Kahl's Audience-First and Cheung's Fish Pond? Complementary. Kahl says "pick an audience first, build the product for them later." Cheung says "once you have picked the audience, embed in the specific small community where they live." Audience-First is the meta-decision; Fish Pond is the tactical implementation. Most founders need both decisions, made deliberately.

Building is no longer the bottleneck. Visibility is. buildinpublic.so is narrative infrastructure that runs inside your building workflow — AI Brain holds the persistent voice memory across weeks, Loudy drafts in that voice, and Dev Cards keeps the content engine running on commit-driven inputs.