Build-in-Public Glossary: 20 Terms From MRR Screenshots to Ship Streaks

Marc Lou tweeted a Stripe screenshot at 2am. Big numbers. Within 48 hours, three founders DMed me asking what "LTV" meant in his follow-up thread. One had been building in public for eight months. Eight months! And still unclear on basic terms.

The build-in-public community has developed its own vocabulary — and honestly, half of it isn't documented anywhere. You're expected to absorb it by osmosis, scrolling through #buildinpublic threads until the jargon clicks. Which works. Eventually. But it's slow. Frustrating. And weirdly embarrassing when you have to ask basic questions publicly while pretending you're some experienced founder who definitely knows what "churn cohort analysis" means. (I still had to Google "churn" in 2024. Don't tell anyone.)

So here's the glossary I've been maintaining since we started building products at VDL. Twenty terms. Practical definitions. Opinions where they're warranted. Some of these will be obvious if you've been in the space for years. Others might clarify something you've been quietly confused about.

1. Build-in-Public (BIP)

The practice of sharing your startup journey publicly and in real-time. Revenue numbers, product decisions, failures, wins — all visible to your audience as they happen.

It's not marketing in the traditional sense. Marketing presents polished outcomes. BIP shares the process. The mess. The uncertainty. The "I have no idea if this will work" moments that traditional founders hide.

Pieter Levels popularized the modern version, but founders have been working transparently for decades. What changed is the platform — Twitter/X made real-time sharing easy, and the indie hacker community made it culturally acceptable to talk about money.

2. MRR Screenshot

A public share of your Monthly Recurring Revenue dashboard — usually a cropped image from Stripe, Paddle, or Gumroad showing revenue figures.

MRR screenshots are the currency of BIP credibility. They prove you're not just talking; you're earning. But — and I feel strongly about this — they've become a cesspool of dishonesty. Fake screenshots exist. Misleading crops exist. Screenshots showing impressive numbers while hiding massive churn right below the fold. Technically accurate. Deeply dishonest.

The credible founders show context: time period, growth rate, sometimes customer count. The vanity posters? Single number, zoomed way in, no axis labels. You learn to tell the difference. Eventually. After getting fooled a few times.

3. Ship Streak

A consecutive run of public shipping — days or weeks where you release something visible. A feature, a bug fix, a blog post, an update to your landing page. Anything countable.

Founders track ship streaks because consistency compounds. An audience that sees you shipping daily assumes you'll still be around in six months. Plus, the streak mechanic creates personal accountability. Breaking a 47-day streak feels terrible. That feeling keeps you working.

Popular formats: daily build logs, weekly changelog posts, monthly retrospectives. The cadence matters less than the consistency.

4. Launch Thread

A Twitter/X thread announcing a new product, feature, or milestone — structured to maximize engagement and shares.

The anatomy is predictable: hook tweet (the result), context tweets (the journey), feature tweets (what it does), social proof tweet (if any), and a call-to-action. Formulaic? Yes. Because the formula works. Some founders hit massive impression counts with these. Some of us... don't. (Our launch threads have performed somewhere between "modest" and "what even is the algorithm.")

Not every launch needs a thread. But if you're building in public and you ship something significant, a launch thread is how you convert your audience's attention into signups or sales.

5. Open Metrics

Publicly sharing your key business numbers — MRR, churn, customer count, traffic, conversion rates. The opposite of "stealth mode."

Open metrics go beyond occasional MRR screenshots. Some founders run public dashboards (Open Startup pages) showing live data. Others publish monthly reports with detailed breakdowns. The transparency builds trust. Provides accountability. And — let's be honest here — generates content without requiring new ideas. (I've used "here's our latest numbers" as a post when I had nothing else to say. It works.)

The transparency builds trust when done honestly. Many founders use privacy-focused analytics to track metrics without compromising user data. Open metrics only work if they're honest. A dashboard showing "200 customers" when 180 are on free trials isn't open — it's misleading.

6. Vanity Metrics

Numbers that look good but don't reflect business health. Follower counts, page views, free signups, newsletter subscribers (without open/click rates).

In BIP, the tension is constant: vanity metrics get engagement; real metrics get respect. A tweet about "10K followers!" outperforms a tweet about "2.4% conversion rate" every time. But experienced founders share both, explaining what the numbers actually mean.

The test: does this metric correlate with revenue? If not, it's probably vanity. (Though building an audience is legitimate work — followers aren't worthless, they're just not revenue.)

7. Launch Day

The coordinated public release of a product — usually hitting Product Hunt, Twitter, Hacker News, and relevant communities simultaneously.

Launch days are planned events. You line up supporters to upvote and share. You clear your calendar for customer support. You have a launch thread drafted and ready. And then... it either works or it doesn't. Most launches don't go viral. That's fine. The point is concentrated attention.

In our experience, some launches pop while most are quiet. The quiet ones can still get initial customers — just not the dopamine hit of watching numbers climb. Launch day is one distribution channel, not the only one. And honestly? The launches we agonized over performed worse than the ones we threw up quickly. No idea why.

8. Maker Community

The ecosystem of indie hackers, solo founders, and small teams building products outside traditional startup culture. Indie Hackers, WIP, Twitter's #buildinpublic, certain Discord servers.

Maker communities are where build-in-public lives. The norms — transparency, mutual support, anti-hustle-culture — emerged from these spaces. If you're building in public without engaging these communities, you're missing the audience most receptive to your content.

The flip side: maker communities can become echo chambers. Everyone ships the same productivity tools to the same audience. Sometimes you need to look outside.

9. Default Alive vs. Default Dead

Paul Graham's framework: if your startup continues its current trajectory, will it survive (default alive) or run out of money (default dead)?

BIP founders use this as shorthand for financial sustainability. "We went default alive last month" means revenue now covers costs. It's a milestone — probably the most important one for bootstrappers. And sharing it publicly creates accountability and credibility.

The term cuts through the noise. Fundraising announcements are about potential. Default alive is about survival.

10. Ramen Profitable

Earning enough to cover your basic living expenses — but nothing more. The minimal viable income for a founder to keep building without a job.

The number varies wildly by location. $2K/month in Bali is comfortable. $2K/month in San Francisco is impossible. When founders announce ramen profitability, the context matters.

Ramen profitable is often the first BIP milestone worth celebrating. It means you've bought yourself time. Not comfort, not scaling, just time. And for early-stage founders, time is everything.

11. Solo Founder

A founder building alone — no co-founder, no employees. Common in the BIP community because transparency works best when there's one person making all the decisions.

Solo founding gets romanticized. "No meetings, no politics, ship whenever you want."

The reality? Lonelier and harder than that. You make every decision yourself. Nobody's around when things break at midnight. The freedom is real. So is the 3am panic when your payment integration fails and there's literally no one to call.

But solo founders also dominate BIP because the format rewards individual personality. An audience follows a person, not a committee. A structure like 1-founder + 1-manager + AI agents represents a solo founding model, scaled with automation — we've detailed how AI agents enable solo founders to ship like a team.

12. Indie Hacker

A founder building small, profitable businesses outside the venture-backed startup ecosystem. The term comes from the Indie Hackers community, founded by Courtland Allen.

Indie hackers aren't anti-VC on principle — some take money, some sell to acquirers. The distinction is mindset: profit over growth-at-all-costs, sustainability over blitzscaling, ownership over dilution. I've watched founders agonize over whether taking a $50K angel check disqualifies them from the "indie" label. It doesn't. Probably. Who knows. The boundary policing gets exhausting.

Build-in-public and indie hacking overlap almost completely. The BIP movement is essentially indie hackers with a content strategy.

13. Small Bet

A low-risk, fast-to-build product that tests an idea without major investment. Coined and popularized by Daniel Vassallo.

The strategy: instead of building one product for two years and praying, build many small products in weeks or months. Each is a "bet." Most lose, some break even, a few win big. The portfolio approach reduces risk.

BIP founders love small bets because each launch is content. Each failure? A lesson you can share. The strategy generates material while generating revenue. Or at least that's the theory. In practice, watching your fifth small bet fail in a row tests that optimism pretty hard.

14. Audience Building

The deliberate cultivation of followers, subscribers, and engaged readers before (or alongside) product development.

The thesis: distribution is harder than building. A product with no audience has no customers. So build the audience first, then build products for them. Marc Lou's trajectory is the poster example — hundreds of thousands of followers before his biggest product launches.

Not everyone agrees. Some founders argue products should come first, audience second. Honestly? They're wrong. Or at least, I think they're underestimating how brutal cold distribution is. The reality is probably both — parallel tracks, feeding each other — but if I had to pick one to start with, I'd pick audience every time.

15. Changelog

A public record of what's been shipped — features, fixes, improvements. Usually formatted as dated entries.

Changelogs serve double duty: they keep users informed and they create BIP content. A weekly changelog email is an excuse to stay visible, even when you're heads-down building.

Tools like JustEmails handle the delivery side — we've covered why flat-fee email beats per-mailbox pricing for growing teams. But the real work is having something to put in the changelog every week.

16. Waitlist

A signup form for users who want access to something not yet available. A pre-launch traction signal.

Waitlists measure interest before you've built anything. They're also BIP content: "1,000 people joined our waitlist" is a milestone worth sharing.

But here's the thing nobody wants to admit: waitlist signups are vanity until they convert. A 10,000-person waitlist with 2% activation isn't impressive — it's concerning. I've been on both sides of this. Celebrated a big waitlist number. Watched almost nobody show up when we launched. Humbling.

Many founders find the number on the waitlist matters less than the conversion rate off it. Setting up proper email infrastructure early helps convert waitlist signups into engaged users.

17. Weekend Project

A product built in a weekend (or other short timeframe) — usually to test an idea quickly or generate BIP content.

Weekend projects are the small bets taken to the extreme. The constraints force simplicity. "What can I ship in 48 hours?" produces different products than "What should I build over six months?"

The risk: weekend projects become permanent products, held together with duct tape and prayer. Sometimes that's fine. Sometimes it creates technical debt that takes years to repay. Modern deployment platforms like Railway vs Vercel make weekend projects easier to maintain. Ask me how I know.

18. Revenue Share

A business model where collaborators split income instead of trading equity or salary. Common in BIP partnerships.

Revenue sharing works for short-term collaborations: "You design it, I code it, we split 50/50." It avoids the legal overhead of formal partnerships. But it also creates complexity — how do you split when one person does maintenance while the other moves on?

In BIP, revenue sharing arrangements are often public, which creates accountability. "I'm paying my co-creator 30% of all sales" is a commitment.

19. Build Log

A running journal of building progress — daily or weekly updates on what's been worked on, decisions made, problems solved.

Build logs are the raw material of BIP. They document the journey in real-time. They're content without requiring "ideas." And they create a record you can reference later — "here's the post where I decided to switch from Firebase to Postgres."

Formats range from simple Twitter threads to full blog posts to video journals. The medium matters less than the consistency.

20. Launch Fatigue

The exhaustion that sets in after repeated product launches without expected results. Also describes audience fatigue when founders launch too frequently.

BIP encourages constant shipping. But constant shipping without traction is demoralizing. And audiences notice when a founder launches their eighth product in three months — skepticism sets in.

The antidote? Ship fewer things, ship them better. Or accept that most launches are learning experiences, not inflection points.

Launch fatigue is real. I've felt it. The eighth product launch hits different than the first — more "here we go again" than "this is exciting." Managing expectations helps. So does taking breaks between launches, even when the BIP grind culture says otherwise.

Honorable Mentions

LTV (Lifetime Value): The total revenue a customer generates before churning. Critical for understanding whether acquisition costs make sense.

Churn: The percentage of customers who cancel over a period. The number everyone dreads sharing but the honest founders do.

ARR (Annual Recurring Revenue): MRR × 12, but only if your revenue is stable. Don't annualize a spike month.

Open Startup: A company that publishes all its metrics publicly, usually on a live dashboard. The most extreme form of open metrics.

Quick Verdict

Entering the build-in-public space? Five terms to internalize first: MRR screenshot (the credibility currency), ship streak (the consistency mechanic), vanity metrics (what to avoid celebrating), default alive (what to actually celebrate), and audience building (the distribution strategy that makes everything else work).

The rest? You'll absorb naturally. But those five will help you read the room when founders talk past each other using terminology nobody bothered to define. And trust me, they will talk past each other. Constantly.

And look — the vocabulary is just the surface. Solo founders increasingly lean on AI agents as virtual team members to ship faster while building in public. (We do. It works. Mostly.) We've written about how one founder built 9 SaaS products using this exact approach. The tradeoffs between transparency and traditional marketing matter. But the vocabulary is where understanding starts.

Frequently Asked Questions

What does MRR screenshot mean in build-in-public?

An MRR screenshot is a public share of your monthly recurring revenue dashboard — usually from Stripe, Paddle, or Gumroad. Founders post these to show progress, build credibility, and attract an audience. The term has become somewhat controversial because fake or misleading screenshots are common. Legitimate MRR screenshots include verifiable details and context, not just cropped numbers.

What is a ship streak and why do founders track them?

A ship streak is a consecutive run of days or weeks where a founder ships something publicly — a feature, fix, blog post, or update. Tracked to build consistency habits and demonstrate momentum to an audience. Popular formats include daily build logs and weekly changelog posts. The streak mechanic creates accountability and keeps founders visible in algorithmic feeds.

How is build-in-public different from traditional marketing?

Traditional marketing presents polished, finished narratives. Build-in-public shares the process as it happens — decisions, failures, revenue numbers, architecture choices. The audience follows the journey rather than just seeing outcomes. This creates trust through transparency but requires vulnerability that traditional marketing avoids.

What are vanity metrics in the build-in-public context?

Vanity metrics are numbers that look impressive but don't reflect business health — Twitter follower counts, page views, free signups without conversion data. In build-in-public, the contrast is between vanity metrics (followers, impressions) and real metrics (MRR, paying customers, churn rate). Experienced founders share both, with context explaining what the numbers actually mean.

---

Follow the Studio

Velocity Digital Labs is a multi-product studio building SaaS products with a 1-founder + 1-manager + N-AI-agents structure. Receipts, dollar-signs, cap-table-honest. No VC platform-play — just shipping.

See the products → · Browse all VDL blog posts