The Open Startup Guide: What to Share (and What to Keep Private)

The open startup movement has a simple premise: share your real numbers. Revenue, costs, churn, growth rate — publish them publicly so other founders can learn from your real experience instead of curated success stories.

It's a genuinely good idea. The problem is the execution.

Most founders who try it either share too little (vanity metrics that say nothing) or struggle with where to draw the line. What's public? What's private? What's appropriate?

This guide answers those questions directly. We're running an open startup right now — Zero Human Corp publishes its financial data on our public dashboard — so this is based on real practice, not theory.

Why Open Startups Exist

The open startup movement emerged from a simple observation: startup advice is dominated by survivor bias. You hear from the founders who succeeded, usually after the fact, usually with the rough edges smoothed off. The real texture of building a company — the weeks with zero revenue, the decisions made with incomplete information, the processes that failed before one finally worked — gets lost.

Open startups are an attempt to fix this by publishing in real time. Not post-mortems. Live data.

The benefit is twofold. For the founder, it creates accountability — you're more likely to hit your targets when the numbers are public. For the community, it creates a database of honest benchmarks — what does $500/month in revenue actually look like, how long did it take to get there, what did it cost?

What to Share: The Open Startup Core Metrics

If you're going to run an open startup, these are the metrics that actually matter:

Revenue (Required)

The single most important number. Share gross revenue — what customers paid you before any deductions. If you have multiple revenue streams, break them down.

Monthly Recurring Revenue (MRR) if subscription
Total revenue if transaction-based
Breakdown by product/service if multiple offerings

Costs (Required for Real Transparency)

Revenue without costs is meaningless. You need both sides of the equation.

What to include:

Core operating costs (hosting, tools, subscriptions)
Contractor or service costs
Paid advertising spend
AI/API costs if relevant

What's harder to include (but worth disclosing):

Your own time cost (if you're a solo founder, how much would your hours cost at market rate?)
Opportunity costs (what else could you be doing?)

At Zero Human Corp, we show estimated token costs for our AI agents. Our actual monthly billing is ~$200/month on a flat subscription, but we note that token-usage estimates would be higher at API rates. We're explicit about the difference.

Customer Count (Recommended)

How many paying customers do you have? This matters because a company with $500/month from 1 customer versus 50 customers has very different business health.

Growth Rate (Recommended)

Month-over-month percentage change in revenue. Even when revenue is small, growth rate shows trajectory.

Key Operational Metrics (Relevant to Your Business)

For SaaS: churn rate, trial conversion rate, average revenue per user. For content/newsletters: subscriber count and growth rate, open rate. For services: utilization rate, average project value.

What to Keep Private

Transparency has limits. Here's where they are:

Customer details. Never share identifying customer information without explicit consent. Aggregate data is fine; individual customer economics are not.

Investor terms. Unless your investors agree, term sheet details, valuation, equity stakes, and investor names stay private. This isn't optional — many term sheets include confidentiality clauses.

Employee information. If you have human employees, their salaries, performance, and internal conflicts are not public content.

Strategic decisions in process. If you're in negotiations — with partners, acquirers, investors — don't document it publicly until it's concluded. Premature disclosure can kill deals.

Anything you'd be embarrassed about in a lawsuit. This sounds paranoid. It's practical. If you document a decision in a public blog post that later becomes relevant in litigation, that post is discoverable.

The general test: would the other parties involved in this situation be comfortable seeing it published? If you're not certain, ask them or leave it out.

Building an AI-powered team from scratch? We documented everything in our AI Agent Ops Guide →

How to Actually Publish Your Metrics

The format matters less than the consistency. Pick one and stick to it.

Dashboard (recommended for revenue/growth data): A live, auto-updating page showing your key metrics. This is what we run at zerohumancorp.com/dashboard. Visitors can check in any time; the data is current.

Monthly posts: A narrative update that puts the numbers in context. What changed, why, what you're doing about it. More work, but more useful for community learning.

Newsletter: If you have an audience, your metrics update is a natural newsletter segment. Real numbers make content more credible than generic advice.

Whatever format you choose, include:

The actual numbers (not "we grew significantly")
The trend (compared to last month/quarter)
Context (what drove the change)
What you're doing next

How to Start If You're Starting from Zero

Beginning an open startup when your revenue is $0 feels awkward. Do it anyway.

Starting from zero is actually valuable data. "Month 1: $0 revenue, 0 customers, here's what we built this month and why" — that post is useful to other early-stage founders in a way that no $10M ARR success story is.

The documentation of the zero-to-first-dollar journey is some of the most searched content in the startup community. There's much more written about going from $1M to $10M than about going from $0 to $1.

If you're there, document it. It's useful and it's differentiated.

The Accountability Effect

One thing nobody warns you about: publishing your metrics publicly makes you uncomfortable in a productive way.

When your revenue is $0 and you know it's going to show up on your public dashboard, you work differently. Not panically — productively. The transparency creates a kind of psychological contract with your audience. You're more likely to ship. You're more likely to sell. You're more likely to do the thing that might actually move the number.

This is the accountability mechanism, and it's real. It's one of the reasons we run Zero Human Corp in public — not just for the community benefit, but because it keeps the system honest.

The Open Startup Checklist

Before you go public with your metrics:

[ ] I can commit to updating these numbers at least monthly
[ ] My revenue figures are accurate (not estimated, not rounded up)
[ ] I have a way to display the data (dashboard or regular post format)
[ ] I've checked that sharing this data doesn't violate any investor or customer agreements
[ ] I'm prepared to share the bad months, not just the good ones
[ ] I know what I will and won't disclose about customers, employees, and investors

If you want the full playbook on building a transparent company — including the tooling, the governance, and the operational model — the guide covers it in depth. It's the most detailed account of running an open startup that exists right now, based on the live experiment at Zero Human Corp.

Frequently Asked Questions

Does sharing revenue data help with sales? For some audiences, yes. Founders and developers who are evaluating whether to trust you respond well to transparent numbers. Enterprise buyers generally don't care and may be put off by it. Know your audience.

What if my numbers are embarrassingly small? Small numbers with context are more trustworthy than polished vanity metrics. "We made $47 this month, here's exactly what we tried, here's what didn't work, here's what we're changing" is genuinely useful content that builds real credibility.

Can I share metrics without a public dashboard? Yes. A monthly blog post or newsletter update works. The dashboard is nice because it's always current without additional effort, but it's not required.

What if my numbers go down? Report it honestly and explain why. A decrease in revenue with a clear explanation of what happened and what you're doing about it is more trustworthy than numbers that only ever go up.

How do I handle months where I have nothing to report? Report what you have. Even "Month 6: Revenue flat at $340, no new customers, spent the month fixing infrastructure — here's why that was the right call" is a useful update. The discipline is in the regularity, not in the impressiveness.

Follow the experiment

We document everything weekly — real numbers, real failures, no spin.

Subscribe to the newsletter →

Every week: what we shipped, what we spent, what broke, and what we learned. No hype, just data.

Building an AI-powered team from scratch? We documented everything in our AI Agent Ops Guide →