Verified against ChatGPT · 2026-08-14
Draft a build-in-public update that shares the actual number instead of vague momentum language
Converts a raw progress note (a metric, a setback, a shipped feature) into a build-in-public post that names the real number and the real context behind it, avoiding the vague-positivity tone that makes most build-in-public posts blur together.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Draft a build-in-public update post for X based on what actually happened this week. I'll give you the real situation — including anything that didn't go well — and you turn it into a post that reads as an honest specific update, not generic startup-momentum language.
WHAT ACTUALLY HAPPENED THIS WEEK
Shipped CSV export after it sat in the backlog for two months; also lost our biggest customer to a competitor.
THE NUMBER OR METRIC BEHIND IT
12 of our 40 active users used the export feature within 48 hours of launch.
WHAT DIDN'T GO AS PLANNED, IF ANYTHING
The customer we lost was 18% of MRR; they left because we didn't have export until now.
WHAT'S NEXT
Auditing every other feature request tied to churned customers from the last quarter.
HARD RULES
Lead with the specific number or concrete fact, not a mood statement — "shipped the export feature, 12 people used it in the first 48 hours" beats "excited to share some progress this week" because the second sentence could describe literally any startup on any week and gives a reader nothing to react to. If there's a setback in what I gave you, include it plainly, in the same tone as the win — do not spin it into a disguised positive ("failing forward", "great learning experience") unless I've actually framed it that way myself; state what happened and, if I've given you one, what you're doing differently because of it. Do not manufacture optimism the update doesn't actually support — if the week was genuinely rough, the post can be honest about that without being self-pitying; match the actual weight of what happened rather than defaulting to upbeat framing regardless of the input. Keep the post to one clear beat: what happened, the number behind it, and what's next — do not pad it with a mission-statement reminder about the broader vision unless that context is genuinely necessary to make the number make sense.
WHAT NOT TO DO
Do not use build-in-public boilerplate ("grateful for this journey", "the grind continues", "day X of building") unless I've explicitly told you this account uses that framing. Do not add a call-to-action asking people to follow or share unless I ask for one separately — an honest update earns its own engagement without an appended ask.
OUTPUT FORMAT
One draft post under 280 characters. If the honest version doesn't fit in one post, offer a two-tweet version instead of cutting the honesty to make it fit, and say which parts you kept versus cut and why.Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
The build-in-public genre on X has become saturated with interchangeable momentum language precisely because most founders write the update from the vague feeling of the week rather than the specific fact of it, and GPT-5.1 asked for a generic "progress update" will default to that same register ("excited to share", "the journey continues") since it's the highest-frequency pattern for the genre in its training data — anchoring the prompt on a real number and requiring it to lead the post is what actually differentiates the output, because a concrete fact can't be interchanged with any other startup's update the way a mood statement can. The instruction to include a genuine setback in the same tone as the win, without spinning it into disguised positivity, targets a specific credibility problem: readers on X have seen enough "failing forward" framing to recognize it as a dodge, and a post that names a real loss (a churned customer, a missed number) plainly reads as more trustworthy than one that reflexively reframes every setback as growth, which paradoxically makes the wins in the same account's other posts more believable too. Capping the post to one beat (what happened, the number, what's next) rather than looping back to the broader mission statement matters because that reflexive vision-reminder is exactly the kind of padding that makes build-in-public updates blur together — a reader following an account across many weeks already knows the mission; what they're evaluating week to week is whether this specific update contains anything real, which is the one thing generic momentum language can never supply.
What you get back
"Shipped CSV export this week after it sat in the backlog two months. 12 of our 40 active users used it within 48 hours. Also lost our biggest customer — 18% of MRR — because we didn't have this sooner. Auditing every other churn-linked feature request now."
Verified against
ChatGPT GPT-5.1 · 2026-08-14
Changelog
- 2026-08-14 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
