Skip to content

Founder content

How to Write a Weekly Build-in-Public Update for Your SaaS

Trender Editorial Team · Updated

A useful weekly build-in-public update does not need a dramatic launch or a big growth milestone. It needs one specific, true thing that happened while you were building your product—and enough context for a reader to understand why it matters. Choose a decision, a small improvement, a user problem you can discuss safely, or a lesson from the work. Then explain what changed, what remains uncertain, and what you plan to do next.

This approach is for SaaS founders and small product teams who want to share their work consistently without turning every post into a pitch. The example below is fictional and illustrative; it is not a customer story or an observed Trender output.

The basic structure: moment, meaning, status, next step

  1. Moment: Name the concrete event, decision, or problem. “We changed the first-run setup” is more useful than “Big week at the company.”
  2. Meaning: Explain the practical reason it mattered to the product or the people using it. Avoid claiming a benefit you have not verified.
  3. Status: Say whether the work is shipped, still in progress, or only being considered. Readers should not have to infer what is available.
  4. Next step: Share what you will check, decide, or work on next. This gives the update a natural ending without requiring a sales pitch.

The format is flexible. A short text post can use all four parts in a few sentences. A Reel can turn each part into a spoken beat. A carousel can give each part its own slide. The purpose is not to fill a content template mechanically; it is to make a real piece of work understandable.

Start with a safe, specific source

Before drafting, write down what actually happened in plain language. Useful sources might include a product decision you can explain, a workflow you are improving, a question that changed your priorities, or a small detail you learned while testing your own process. Separate what you observed from what you believe it means.

Then remove information that should not be public. Do not share private customer names, account details, confidential feedback, security-sensitive implementation details, or plans that are not yours to disclose. If the story depends on a customer’s words or experience, get appropriate permission and preserve their meaning; a generalized, non-identifying lesson may be a safer alternative.

Keep a simple note with three labels: confirmed, in progress, and possible. A feature can be confirmed as available, in progress without being ready to use, or merely a possibility under discussion. Do not describe the last two as shipped. This small status check makes it easier to write clearly and reduces the chance that a reader mistakes a roadmap thought for a product promise.

Illustrative example: from a product note to a finished update

Raw note: “New users aren’t sure what to do after creating an account. We’re revising the setup screen. We haven’t measured whether the revision helps yet.”

Finished illustrative post:

We’re revising the first setup screen in our fictional project-management app. The current version asks new users to make several choices before they have a clear sense of the workflow, so we’re trying a simpler first step.

The revised screen is still in progress, and we don’t yet know whether it will make setup easier. The next step is to review the flow with a small set of people and look for points where the instructions are unclear. If we change the process again, I’ll share what we learned.

Notice what the example does not say. It does not claim that onboarding improved, that users are happier, or that the change increased activation. It describes the problem the team is addressing, labels the work as unfinished, and names a reasonable next check. If you make objective claims about a product in promotional content, make sure you can support them; the Federal Trade Commission’s advertising and marketing guidance says advertising claims must be truthful and evidence-based.

Decide whether a customer quote belongs in the update

A product note and a testimonial do different jobs. You can describe a change your team is making in your own words. If you turn someone else's praise into promotional proof, review the exact quote and the claim it creates. The FTC's endorsement guidance says endorsements must reflect honest opinions. It also explains that unexpected connections that could affect how people evaluate an endorsement need clear disclosure.

Continue the fictional setup-screen example. Imagine one test participant wrote, “The new label helped me find the export button.” Before using that line, confirm the original wording, permission for the intended use, and the context. Was it a prototype or the released product? Was the person paid or otherwise connected to the business? Do not turn that single comment into “Our new setup makes every user more productive.” The comment does not establish that outcome.

Illustrative editorial decision: Leave the quote out of this week's public post while permission is unresolved. Keep the useful update: “We changed the export label in the prototype. Next, we will check whether people can find it without prompting.” This still gives readers a concrete product decision and a next step. It does not invent a testimonial or suggest that an unfinished test proved an improvement.

If you later share a real recommendation, retain its meaning and the context needed to understand it. Do not use the fictional participant or quotation in this example as a real customer endorsement.

Choose a format that suits the material

  • Use a text post when the point is a decision, a short lesson, or a clear explanation.
  • Use a Reel when showing a sequence, interface detail, or before-and-after workflow would make the update easier to follow. Explain only what the screen actually shows.
  • Use a carousel when the update needs several distinct steps—for example, the original problem, the decision, the current status, and the next check.

Do not force one update into every format just to increase the asset count. If you adapt it, preserve the same facts and status across versions. A short video should not make a tentative idea sound more certain than the accompanying text.

A quick review before you publish

  • Can you point to the real event, decision, or work behind the post?
  • Have you marked what is available versus still being explored?
  • Are claims about users, product impact, or performance supported by evidence?
  • Have you removed confidential details and checked permission for any customer material?
  • Does the next step follow from the update, rather than promising an outcome?
  • Would a reader who does not know your company still understand the point?

If the draft feels vague, add one concrete detail that is safe to share. If it sounds like an advertisement, replace broad praise with a description of the work. If it promises a result you have not measured, state what you will check instead. A dependable weekly update is a record of real product thinking—not a claim that every experiment succeeds.

Turn a rough founder note into a draft

Keep a running list of product moments, then choose one that is both useful to explain and appropriate to share. Bring the rough note or thesis into Trender’s Workshop to shape it into a platform-ready structure or script, then review every status, detail, and claim against what your team can confirm. You can start with your own idea; competitor research is not required.