A rebrand is news only when readers can understand what changed and why it matters to them. A new logo alone may warrant a note to customers; a new company name, product scope, or customer experience may require a fuller public announcement. The release should make the transition easy to follow, not fill the first paragraph with abstract claims about transformation.
Gather the facts before writing
Confirm the current and new legal or trading names, effective date, domains, product names, visual assets, and customer-support arrangements. Ask which contracts, invoices, app listings, subscriptions, and help pages will change. A reader should not need to guess whether an old account still works or whether a familiar product has disappeared.
Coordinate the release with the site, social profiles, email notices, sales material, and employee briefing. If the name change has legal or regulated implications, obtain specialist review. Do not publish a future transition as complete when customers will still encounter old branding in important places.
Build the announcement
01
Headline
State the observable change: '[Old Name] Becomes [New Name] on [Date].' Add a specific reason only if it is verifiable and relevant.
02
Lead
Answer who is changing, what changes, when it takes effect, and how customers or partners are affected.
03
Rationale
Explain the business or audience need behind the change without pretending that a new identity alone solves an old product problem.
04
Continuity
Say what remains the same: leadership, ownership, accounts, support contacts, or services, but only where confirmed.
05
Quote and contact
Use an approved spokesperson quote that adds context. End with a working media contact and a customer-facing transition page.
Fictional example
[OLD COMPANY NAME] today announced that it will operate as [NEW COMPANY NAME] beginning [DATE]. The updated name and visual identity reflect [VERIFIED REASON]. Existing customers can continue to use [CONFIRMED PRODUCT OR ACCOUNT ARRANGEMENT], while [SPECIFIC CHANGE] will take effect [TIMING].
[AUTHORIZED LEADER] said: '[APPROVED COMMENT ABOUT THE CUSTOMER NEED AND TRANSITION].' The company has published a transition guide at [REAL URL] covering accounts, invoices, support, and the rollout schedule. Media inquiries: [REAL CONTACT]. Replace every bracketed field with approved facts; this is a template, not a statement from an actual company.
After publication
Link the announcement from the old and new names so customers can verify the relationship. Keep redirects and contact channels working. Correct inconsistent naming in key help pages, email templates, and product listings, then review feedback for confusion or broken journeys.
Measure more than release pickup. Relevant questions include whether customers reach the correct destination, support inquiries about the change decline after clarification, and stakeholders recognize the new name. A rebrand release is an information tool; it does not guarantee attention or favorable coverage.