Run a One-Hour Rebrand Sweep for Onboarding, Decision Log, Stack Sheet

When a tool changes its name, the onboarding doc, decision log, stack sheet, and AI settings can still point at the old product. Run a one-hour sweep before the stale name causes confusion or a wrong renewal. The data may carry over, but the stale pointer can surface in onboarding, finance, or an AI session.

The rebrand is an ops incident

Coda became Superhuman Docs on July 8, 2026. Existing Coda documents converted automatically to Superhuman Docs on the first day of the rebrand. But a small company does not run on content alone. It runs on the places where people look for the current answer.

The rebrand also changed the access points. Superhuman Docs introduced Docs AI, an AI assistant that operates inside documents. Superhuman Docs made the Docs MCP available to all users for connecting documents to Claude, ChatGPT, and Cursor. Superhuman Databases, in closed beta, was described as handling up to 1,000,000 rows. Those are not marketing details. They are the settings your team may need to re-enable, re-test, or re-explain.

Superhuman Docs' paid tiers were renamed and repriced at higher prices than Coda's previous tiers. That changes the stack sheet line, the budget note, and the renewal reminder. Moving documents into a Superhuman workspace was not automatic. If your team uses a separate workspace, the sweep must include the move, not just the rename.

Run the sweep in a single sitting

Set a timer before you open the docs. The list below is the minimum, not a full migration. Each item is testable quickly, and each removes a stale pointer before a new hire or a new AI session hits it. If you find yourself explaining the rebrand to a teammate, stop and write the note in the doc instead.

• Repoint the team home URL to the current product domain.
• Update onboarding docs to the current product name and domain.
• Correct the decision log entry that names the old tool.
• Update the stack sheet with the current vendor, tier, and price.
• Reconnect AI/MCP access through the current assistant or connector settings.
• Confirm the workspace migration path for any docs that did not move.

Work the list in order. The home URL is the visible fix, and AI access is the least visible. The stack sheet is the one you cannot skip if time runs out; the cost line will appear in the next finance review before anyone notices the old name.

First, repoint the home URL, because a new person sees it before anything else. If it still points at the old domain, the onboarding doc becomes a problem. Add a short note to the onboarding docs: the tool has a new name and a new home.

Then fix the decision log, where the company records why it chose the tool. If the log still says the old name, the next reader assumes the decision is stale. Add a short addendum: the rebrand changed the product name and the access settings, not the underlying choice. That keeps the log useful without rewriting history.

Next, correct the stack sheet, the cost line. If the vendor name, tier, and price are still old, the finance note is wrong even if the tool still works. Update the line with the current name, the current tier, and the current price. Then set the renewal reminder to the current vendor name.

Finish with AI access, the quiet failure. If the assistant or connector still points at the old product, the model may read stale context or refuse the connection. Decide whether your team uses the in-document assistant or the connector, then reconnect the chosen path. Re-test with a real document. Ask it to summarize the decision log or pull the current pricing line. If it works, the access is current. If it does not, the sweep is not done.