The takeaway: Pick a place where users can check whether your product is down, write three message templates now, and decide how often you will update during an outage. An hour of setup today saves you from improvising in public on your worst day.
Why silence costs more than the outage
Atlassian's incident communication guide makes the case plainly: customers who are kept informed during downtime react far less negatively than customers left guessing, and silence can cost more trust than the outage itself. For an early-stage product, that trust is the business - your first users are the ones telling other people about you.
The guide also notes that the work happens before the incident, not during one. When your product is down and your inbox is filling up, nobody writes their clearest copy.
What a status page is
A status page is a single public page that answers three questions: is everything working, what is affected right now, and when will the next update come. Atlassian recommends a dedicated status page as the primary incident channel - one clear source of truth that customers and teammates can check, instead of a thread of replies scattered across email and social.
You do not need to build one. Hosted status-page tools exist (Atlassian sells one, Statuspage; there are also free and open-source options), and some let users subscribe to updates by email or SMS. For a very early product, even a simple static page you can edit quickly can be enough to start. The point is that the page exists, is linked from your site, and is not hosted on the same infrastructure that might be down.
Set it up in an afternoon
Borrowing from Atlassian's preparation advice, scaled down for a small team:
- Define what counts as an incident. Many teams use a small set of severity levels with measurable thresholds - for example, "Sev 1: the product is unusable for everyone" versus "Sev 3: a minor feature is degraded for some users." Write yours down so "is this an incident?" has a fast answer.
- Choose your channels. Status page first. Email and social can support it, but Atlassian cautions against relying on any single social channel as your only means of communication.
- Write templates now. Three short drafts cover most situations: an acknowledgment ("We are investigating reports of X"), an update ("We have identified the cause and are working on a fix"), and a resolution ("X is resolved as of [time]; here is what happened"). Blanks to fill in, not prose to invent under pressure.
- Decide a cadence. Tell users when they will hear from you next - "next update in 30 minutes" - and then keep that promise even if the update is "still investigating." A predictable rhythm is what turns silence into communication.
Writing during the incident
The same principles as good error copy apply, and our post on writing error messages that help users fix the problem goes deeper on tone. In short: say what is affected in plain language, skip blame and jargon, and always end with the time of the next update. If the fix takes longer than expected, post anyway - a timestamped "no change yet" beats a gap.
After the incident
Close the loop. Atlassian's guide treats communication as continuing after resolution: post the all-clear, say what happened in honest, simple terms, and note what you are changing. For a small product, a short, candid follow-up can build more credibility than an incident-free month.
If your product is early enough that every user matters, this kind of visible reliability is part of the pitch. When you are ready for more of those users, you can launch your startup on Maidensail and put it in front of early adopters.
The takeaway
Downtime is a when, not an if. A status page, three templates, a severity definition and an update cadence - all chosen in a calm afternoon - are the difference between an outage that costs you trust and one that shows users you run a tight ship.
Your launch deserves users who trust you
Reliable communication is part of the product. When you are ready to grow, launch your startup on Maidensail and get in front of founders and early adopters.
Source: Atlassian - Incident communication best practices. Status-page tooling examples are named as they appear in the source; no tool endorsement is implied.

