Build in Public
How to Build in Public and Create Investor-Ready Startup Evidence
Use build-in-public updates to document customer learning and execution for potential investors, while keeping financials and sensitive details private.
By Uriel Bitton · 4 min read
The short answer
Building in public can give investors a useful record of a SaaS founder’s decisions, customer learning, and follow-through. Publish customer-safe problems, hypotheses, releases, and outcomes in a durable sequence. Keep exact financials, runway, confidential customer information, and financing details in private investor updates. Public interest is not fundraising traction; evaluate whether the record helps real introductions and conversations.
Building in public can help investors understand how a SaaS startup learns and executes before a fundraising conversation. Publish a trail of customer problems, decisions, shipped changes, and evidence of progress. Keep detailed financials, runway, customer identities, and fundraising terms in private investor updates. A public build log is supporting evidence, not a substitute for a pitch, due diligence, or direct relationships.
Investors need a decision trail, not a feed of milestones
A launch announcement shows an event. A series of updates showing what customers needed, what you changed, and what happened next shows the thinking behind it. That distinction is useful to potential investors, but also to future hires, partners, and customers. It does not mean public posting guarantees investor interest.
The 1984 Ventures guide to monthly investor updates recommends consistent reporting of metrics, highlights, lowlights, and specific asks. Use that discipline as a model for truthful progress reporting, while keeping the full investor report private. Public posts should not become an alternative set of flattering numbers.
Use a two-layer update system
1. Publish the decision and customer problem
Start with a concrete problem rather than a victory claim. For a hypothetical SaaS serving agencies: “Users connect their billing data, but many still export it to spreadsheets before reviewing client margins. We are testing a native margin view.” That tells the reader who the product serves, what friction you observed, and what you intend to learn. It does not expose a customer or promise a result.
Keep a durable sequence: problem, hypothesis, release, observed outcome, next decision. Buildside’s guide to attracting opportunities through public work explains why a specific outcome and next action are more actionable than a generic progress post. For investor-facing credibility, the valuable addition is continuity: a reader can see whether the founder followed through.
2. Keep a private investor layer with the complete facts
Maintain the same underlying operating record, then create a private version for people who are entitled to it: comparable revenue or usage metrics, burn and runway, customer concentration where appropriate, setbacks, and concrete requests for introductions or advice. Visible’s investor-update guidance also treats structured metrics, highlights, lowlights, and asks as core update material. Do not assume public followers and existing investors should receive identical information.
If a public post says activation improved, the private report should preserve the denominator, timeframe, definition, and relevant caveats. If it is too early to know, say so in both places. A public claim that cannot survive private follow-up is worse than no claim.
3. Choose a disclosure boundary before publishing
Write the complete internal note first. Remove identifiable customer stories, individual negotiations, unreleased security work, financing terms, and metrics whose small sample would reveal private facts. GitLab’s confidentiality guidance is a useful example of being public by default while explicitly reserving internal and limited-access information. Transparency has boundaries.
If exact figures would expose too much, share the directional problem and what you are testing instead. Use Buildside’s SAFE disclosure test for SaaS metrics before posting numbers. Never imply that an illustrative example or unverified customer quote is measured traction.
4. Make the public trail easy to inspect
Give updates descriptive headings, a short explanation of the evidence, and links to earlier decisions or demos. Group the strongest entries on a product page or founder profile. Someone encountering your company for the first time should be able to answer: What market are you learning about? What shipped? Which hypothesis changed? What is still uncertain?
Do not mistake an investor follow for fundraising progress
A venture investor liking a post is not a financing commitment. Track real steps: qualified investor introductions, follow-up requests, substantive meetings, and diligence invitations. Keep these distinct from impressions and follower growth. The same attribution caution appears in Buildside’s framework for measuring building-in-public impact. A public history may help a conversation, but direct outreach and investment fit still matter.
A practical four-week experiment
In week one, publish one customer problem and the hypothesis you are testing. In week two, show what you shipped and the tradeoff you chose. In week three, explain an early signal and its limits; do not call a tiny test product-market fit. In week four, publish the next decision and connect it to the earlier posts.
Separately, send existing investors their normal confidential update and keep a private log of any meaningful investor conversations influenced by the public trail. If nothing changes after a month, you still have a clearer record of product learning. The objective is to make your judgment inspectable, not to perform progress for an audience.
Sources
Frequently asked questions
Can building in public help a SaaS startup attract investors?
It can make your decisions, execution, and customer understanding easier to evaluate, but posts do not guarantee investor interest or funding. An investor still needs market fit, a credible business, direct conversations, and appropriate private diligence.
Should I publish the same update I send to investors?
Usually not. Reuse the underlying facts, but make separate public and private versions. Investors may receive precise financials, runway, risks, and confidential asks. Public readers generally need the customer problem, decision, progress, and safe evidence.
What is worth sharing publicly before a fundraising round?
Useful material includes customer-safe product problems, experiments, shipping decisions, demonstrations, and lessons supported by evidence. Avoid confidential customer data, contract terms, unannounced financing details, and misleading traction claims.
How should I measure whether public updates help fundraising?
Track qualified investor introductions, substantive replies, meetings, and diligence conversations that reference the public record. Label influence conservatively. Likes, follows, and impressions are not investments or committed capital.
A note from Uriel Bitton
Public work is useful to investors when they can trace a decision from customer problem to experiment to what happened next. I would keep that story visible and keep sensitive financials and customer information in a separate investor report. The goal is evidence of judgment, not a fundraising performance.
Keep building with us
Get practical founder lessons and product updates in your inbox.