Aurum
Download

Founder Building in Public

A clear reason to share, a written line between public and private, a weekly build log and monthly numbers post, and the judgement to handle praise, copycats and pile-ons.

Free · Mac (Apple silicon) and Windows · v1.0.0 · Other platforms

Then open the Marketplace in the app, search for Founder Building in Public, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

201

Starter tasks

🚀 Founding & Startups

Founder Building in Public

Sharing the startup journey openly online to attract customers, talent and supporters while deciding what to keep private.

  1. Why we build in public, written in one page
  2. Public and private disclosure line
  3. Co-founder and team consent to share
  4. Investor and board expectations on public numbers
  5. Choosing two primary channels
  6. Founder profile and bio rewrite
  7. Origin post on why the company exists
  8. Post idea capture system
  9. Audience and inbound baseline
  10. Account security for a visible founder
  11. Friday build log
  12. Monthly numbers post
  13. Daily one-line capture
  14. Reply and engagement blocks
  15. Monthly founder newsletter
  16. Quarterly payback review
  17. Repurposing pipeline from one post to five
  18. Inbound routing from posts to pipeline
  19. Comment norms and moderation
  20. Public changelog page
  21. Writing a founder update people finish
  22. Telling a failure honestly
  23. Screenshots and short demo videos
  24. Sharing numbers without misleading
  25. Monthly live build session
  26. Studying ten founders who build in public
  27. Headlines and hooks without clickbait
  28. Guest appearances on podcasts and newsletters
  29. Open revenue dashboard decision
  30. Public roadmap and customer voting decision
  31. Post-to-signup attribution
  32. Dropping a channel that does not pay back
  33. Ghostwriter or editor decision
  34. Founder account versus company account
  35. Weekly time cap on public work
  36. Hiring through your public audience
  37. Thirty-day public build challenge
  38. Revenue milestone announcement
  39. Annual public letter
  40. Funding announcement coordinated with investors
  41. Conference talk on lessons from building in public
  42. Ask-me-anything session in a community
  43. Building in public while still employed
  44. Open startup as a bootstrapped solo founder
  45. Building in public for an enterprise market
  46. Sharing a pivot or hard month
  47. Building in public with long deep tech cycles
  48. Pile-on and criticism response plan
  49. Copycat and competitor disclosure review
  50. Publishing the company handbook and playbooks

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Why we build in public, written in one page

Founders who start posting without a reason drift into vanity metrics and stop after six weeks. Writing down who you want to reach (buyers, future hires, investors or other founders), what you want them to do and what you will not trade for attention gives every later post a test to pass.

First tasks

  • List the three groups you most want to notice the company
  • Choose one of them as the primary audience for the next six months
  • Write the single action you want a reader to take after a post
  • Write three things you will not post, however well they might perform

Public and private disclosure line

The hardest part of building in public is not writing, it is knowing what must never appear: customer names without permission, salaries, a staff member's struggles, the cash balance during a raise, security details. A written line, agreed before the first awkward moment, saves you deciding under pressure at eleven at night with a post half written.

First tasks

  • Write twenty kinds of company information on a page, from revenue to hiring plans
  • Sort each one into always, sometimes or never public
  • Search customer contracts and NDAs for publicity and confidentiality clauses
  • Name who approves each sometimes item before it goes out
  • Reread the disclosure line and update it for anything new @recurring(quarterly)

Co-founder and team consent to share

Your co-founder and early staff appear in your posts whether you name them or not, and a teammate who discovers their bug or their resignation in your thread will not forget it. Getting explicit agreement on how people are mentioned, and an easy way to opt out, keeps public sharing from eroding trust inside the company.

First tasks

  • Book thirty minutes with your co-founder to walk through the disclosure line
  • Ask each team member how they want to be named, tagged or pictured
  • Record each preference in a short shared note
  • Agree that any post naming a person is shown to them before it goes out

Make it yours.

Install Founder Building in Public, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.0 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.