Superhuman combines writing, email and programmable team documents

Superhuman is a productivity suite spanning Grammarly, Superhuman Mail, Superhuman Docs and Go. It combines writing assistance, email, collaborative documents and agents that work with connected applications. For teams familiar with Coda, the important change is that the product became Superhuman Docs in July 2026. The buying decision now includes both the document workflow and the wider suite’s value.

01 / ProductOne company, with four products and a changed Docs identity

The current suite pricing page¹ presents Grammarly for writing, Mail for the inbox, Docs for collaborative work and Go for assistance across applications. These are related products with different interfaces and responsibilities. Buying a suite does not mean that every feature is available on every tier or that existing accounts automatically become one account.

The Coda-to-Docs announcement² dates the product rename to 8 July 2026. Existing tables, formulas, Packs and automations continue, with Docs moving to docs.superhuman.com and old document links redirecting. It is a product evolution within Superhuman.

Docs remains distinctive because a document can contain structured tables and executable workflow logic alongside prose. A team can keep a project brief, tracked requests and operating decisions together. The suite adds other ways to create, refine and act on information, but the document still needs a clear purpose and an owner.

02 / AudienceA fit when documents are part of how the team operates

Superhuman deserves consideration when a team’s work combines substantial communication with collaborative documents. A project group might need to turn incoming requests into structured work, discuss decisions and produce clear updates. The suite can be useful if several of those activities benefit from its products, rather than only one feature being attractive in isolation.

Docs is particularly relevant when a conventional text document is too passive but a dedicated application would be excessive. Tables, views and formulas can support a lightweight operating tool. Someone should nevertheless understand its structure, because a document that drives work can become as important as any other business system.

Existing Coda customers have a different decision from new buyers. They should first assess whether the current workspace already works well and what additional suite features would actually be used. A product rename alone is not a reason to change a functioning subscription or rebuild a workflow. The migration and billing implications deserve their own comparison.

03 / WorkflowTurn a project brief into structured work and a reviewed update

For a proposed pilot, choose a recurring project review. Create a Doc with the brief, a table of work items, owners, dates and an explicit status definition. Add the source notes used to make decisions. Keep the table as the authoritative project record rather than copying its contents into several unrelated summaries.

The Docs AI guide⁵ describes a chat interface that can draft content, build or update tables and work with comments. It also distinguishes AI columns, which operate across table rows, from AI blocks used for generated summaries or themes. Use the mode that fits the task: a row-level classification belongs near the data, while a project summary should reference the relevant table or page.

Begin with a limited change, such as proposing categories for new requests or drafting a weekly update. Compare the generated result with the underlying records and correct the source where necessary. If a date is missing, the summary should identify that gap rather than invent a commitment. Review a small batch before applying an action across the whole table.

For work across applications, the Go agents and connectors guide⁶ separates the agent’s instructions from the connector that supplies access to an app. A connector can enable actions as well as retrieval. Define the intended source and destination, and start with a draft update that a person reviews before it becomes a message or changes another system.

Use Grammarly to refine the final communication while checking that edits preserve the meaning of the project record. If Mail is part of the chosen plan, assess whether its inbox workflow helps the people who receive and respond to those requests. This is a proposed pilot across the suite, not a claim of private testing or measured time savings.

04 / PricingSuite seats and existing Docs billing need a careful comparison

On 15 September 2026, Superhuman’s plans page¹ displayed the following euro prices in the region accessed. They are not currency conversions. The Docs billing guide³ separately explains Maker billing and existing-workspace arrangements, so confirm the billable roles in the actual purchase flow.

The current Docs AI credit guidance⁴ says the previous credit system is paused during the beta. Paid Makers have generous limits; editors and free users have a limited trial. Do not use an old Coda AI credit allowance as the current basis for a purchase, or assume beta access defines permanent future pricing.

Also confirm monthly versus annual entitlements. The suite introduction⁷ describes a monthly Grammarly Pro add-on condition that is not equally explicit on the headline cards. Ask for the exact included products and roles in the quote. A bundle comparison is only useful when it uses the same people, features and billing term.

05 / DistinctionsStructured documents create a useful place for AI-assisted work

The strongest Docs use case is a shared document where the information and the action remain close together. A reviewer can read the brief, inspect the records and see the generated update in context. That can reduce the effort of reconstructing how a decision was made across separate spreadsheets, messages and notes.

AI that can change a table also changes the review requirement. It is useful to ask for a proposed structure or a small update, inspect it and then expand. A fluent explanation of what changed should be checked against the actual rows. The result matters more than the assistant’s description of its work.

Our Notion blueprint is a relevant comparison for collaborative knowledge and documents. Compare the structure needed for the team’s real operating process, including who maintains it. Our WRITER blueprint examines a different approach to enterprise AI and governed workflows. It is relevant when the requirement extends beyond personal productivity into centrally managed applications and content processes.

Keeping separate specialist tools is also a reasonable alternative. A suite can simplify purchasing and access, but only if its components fit the people using them. Evaluate the workflow benefit and the account arrangement together. Replacing a well-supported specialist application solely to reduce the number of logos can create more work than it removes.

06 / QuestionsExisting integrations and beta behaviour are material checks

For an existing Coda workspace, test the changed domain where it affects integrations. The transition guide says old document links redirect and existing API endpoints continue, but embedded content and domain-based controls may need the new Docs domain allowed. Check the actual places where documents appear, rather than assuming a working direct link proves every embed works.

Paid Packs are another migration consideration. The same guide says the bundle does not currently support individual paid Pack subscriptions in the same way as an existing standalone Docs arrangement. Inventory the Packs that power active workflows before changing plans. A cheaper-looking bundle is not a saving if it removes a dependency the team must replace.

Docs AI is still labelled beta, and its current access model is subject to change. Evaluate the functions available now, including the role restrictions described in the usage guide. A free editor trial should not be treated as ongoing paid Maker access, and a future capability should not be counted as a completed part of the buying case.

Across the suite, check what information an agent can access and where its output goes. A project summary, an email draft and a table update have different consequences. Keep review ownership clear, especially when a connector can take action in another application. The organisation should be able to explain the path from source information to final change.

07 / DecisionChoose the suite for workflows that benefit from its parts

Superhuman is worth evaluating when structured Docs, writing assistance and communication tools serve a common working process. Pilot one complete workflow, confirm the roles and entitlements, and measure whether people can maintain the result with less effort.

Compare specialist products when only one part of the suite is needed. Existing Coda users should assess the optional bundle against their current workflow and integrations. Prepare the document structure and migration inventory first when those remain unclear. The right purchase is the one that improves the team’s actual work without obscuring its ownership or cost.