Guide
Building a SaaS in public: a practical guide
By Uriel Bitton · Published · Updated
Editorial review status: This page remains outside search indexes until the reviewer and evidence thresholds are complete.
Direct answer
Building a SaaS in public means regularly sharing specific decisions, experiments, progress, and lessons where potential users and peers can respond. The useful version is not constant promotion: it gives readers enough context to understand the problem, what changed, what evidence appeared, and what the founder will try next while keeping customer and security details private.
Methodology
Review eligible public founder posts and linked product pages, code recurring update patterns, and compare response quality after excluding reposts, private activity, and system-generated launch notices.
Current qualifying sample: 3 records across 3 distinct founders or products. Publication threshold: 20 records across at least five founders or products.
Source-linked examples
| Example | Public evidence | Status |
|---|---|---|
| Buildside | A public product profile with founder context and ongoing progress. | Qualitative only |
| AppTruth | A public SaaS profile that explains its audience and product purpose. | Qualitative only |
| Galaxy Rift | A public product page connected to its founder and launch update. | Qualitative only |
Limitations
- The current review covers three public Buildside examples, below the 20-record publication threshold.
- The examples are observational and cannot establish a causal relationship with launch, revenue, or discovery outcomes.
- A different named reviewer with relevant credentials has not yet completed an independent review.
Related questions
- What should a founder share each week?
- Which SaaS details should remain private?
- How can feedback be turned into a product decision?