The Buildside Journal
Practical essays, experiments, and lessons for SaaS founders building products in public.
Latest · Build in Public
Explain internal SaaS maintenance without announcing benefits you have not measured. Use a public maintenance note, a fictional CSV-import example, and clear boundaries between work, release, and outcome evidence.
By Uriel Bitton · 9 min read
Build in Public
Compare the rules for public progress, feedback threads, product showcases, and private peer advice before choosing where to share your SaaS. Includes a practical routing note and fictional example.
By Uriel Bitton · 9 min read
Build in Public
Turn public product updates into relevant discovery conversations. Write a clear invitation, qualify volunteers, and keep recruitment context beside your findings.
By Uriel Bitton · 10 min read
Build in Public
Compare founder community formats against the time you actually have. Use a two-session rehearsal to see whether a useful conversation can continue between builds.
By Uriel Bitton · 9 min read
Build in Public
Review content portability before choosing a build-in-public platform. Use three updates to check text, media, decision context, import limits, and old links.
By Uriel Bitton · 9 min read
Build in Public
Publish SaaS speed improvements with a clear timing boundary, comparable conditions, failures, and slow-end results. Show what the test supports and what remains unmeasured.
By Uriel Bitton · 10 min read
Build in Public
Report founder feedback polls with the question, counts, participant limits, and next test. Use a worked example to avoid turning community preferences into market claims.
By Uriel Bitton · 10 min read
Build in Public
Turn a practical question on a public build update into a tested SaaS help article. Route bugs and feature requests separately, verify the steps, and keep one answer current.
By Uriel Bitton · 9 min read
Build in Public
A build-in-public platform makes selected product work visible. Separate your public story, source-code access, licensing, and working discussions with a practical publication map.
By Uriel Bitton · 9 min read
Build in Public
Use public SaaS updates to start relevant design-partner conversations. Qualify the workflow, agree the co-development work, and share learning without overstating results.
By Uriel Bitton · 9 min read
Build in Public
Read founder community reviews in context. Use dated member discussions to separate the help someone wanted, the experience they reported, and what you should check next.
By Uriel Bitton · 9 min read
Build in Public
Explain your SaaS pivot with a clear current state, a record of what changed, and an audit of earlier public promises. Keep the next hypothesis separate from results.
By Uriel Bitton · 9 min read
Get practical founder lessons and product updates in your inbox.