Cadence: 1 post/week, fixed day (e.g. every Friday)
Use this when you want a recurring build-in-public post that gives people a clean view of progress without inventing a story every week. The structure works because it balances numbers with context. Revenue and users show the business movement. The best thing and worst thing keep the update human and operational. Next week gives the reader a reason to come back. A fixed day matters here because the format becomes a recognizable ritual. It also keeps you honest: if a week was slow, the update still has something useful to say because the struggle and focus fields are part of the template. Keep the numbers consistent from week to week so readers can track the arc.
Week [N] of building [PRODUCT] in public. Revenue: [$X] ([+/- vs last week]) Users: [N] ([new this week]) Best thing that happened: [WIN] Worst thing that happened: [STRUGGLE] Next week: [FOCUS]
Week 9 of building Loopwork in public. MRR: $412 (up from $290). Users: 61 total, 14 new. Best thing: a user asked to pay annually before I'd built the option. Worst thing: 3 days on a bug that was a timezone off-by-one. Next week: shipping the Android widget.
TimeToPost can turn real product activity into draft build-in-public posts, then route them through your approval queue.
Open Build-in-Public in TimeToPost1 post/week, fixed day (e.g. every Friday)
This template is written for X, LinkedIn. Adjust only the formatting details that each platform needs.
Replace every bracketed placeholder with a real product, audience, metric, offer, date, link, or example. Keep the structure, but make the details specific.