The Superhuman Suite: build the tool, don't buy it.
How to use and set up Superhuman Mail, Grammarly, and Superhuman Docs, and how they combine into a build-not-buy platform for team productivity, with Docs at the center.
AI made individuals faster. It has not changed how teams work. Superhuman's own launch data says it plainly: 65% of workers say AI helped their personal productivity, but only 12% say it transformed how their team works.
Mail and Grammarly close the individual gap. Docs closes the team gap, which is why it is the one that lands an enterprise. And with Docs AI, Databases, and one-click MCP, it does something no doc did before: the tool a team would otherwise buy for one workflow becomes a Docs build, in plain language, connected to the data and the AI it already uses.
That is the whole shift. Docs is not competing as a better doc. It is competing against a team's next SaaS purchase, and winning on consolidation.
Every team with a painful spreadsheet is a landing spot.
Company OKRs, board prep, and the cross-functional operating cadence. The highest-leverage landing, because they expand it for you.
Roadmaps, PRDs, sprint planning, and GitHub PR tracking in one operating surface.
Hiring trackers, onboarding hubs, a headcount and staffing OS, performance and succession.
Budget trackers, financial models, and compliance, on Databases that scale to a million rows.
Support knowledge base, request intake, asset tracking, and runbooks.
The action layer over the CRM: deal rooms, campaign command centers, QBRs, and save plays.
The operator drowning in spreadsheets who builds the first Doc. Often the Chief of Staff or an ops-minded lead. Your internal seller.
VP Product, Head of People, Finance or RevOps lead. Owns the budget for their team's rollout.
Governs the enterprise rollout: SSO, admin, data governance, Databases at scale. The gatekeeper.
COO, CIO, or VP Ops who buys the consolidation story: we retired six point tools for one surface.
Set it up, then use it.
Superhuman Mail
The email client rebuilt for speed and relationships, not inbox archaeology. Keyboard-first and AI-assisted, built to get you to done and keep the relationship warm.
- 1Connect your Gmail or Outlook account and run the guided onboarding, which learns your workflow.
- 2Set up Split Inbox so VIPs, team, and noise land in separate lanes.
- 3Turn on follow-up reminders and Send Later so nothing you are waiting on slips.
- Triage fast with keyboard shortcuts and AI summaries of long threads.
- Use snippets for the messages you send constantly, personalized on the fly.
- Let AI draft and follow up, so the inbox becomes a relationship engine instead of a time sink.
Grammarly
The writing layer that learns your voice and rides along everywhere you type. In the suite, it is how one company voice shows up in every message, already installed across the enterprise.
- 1Install Grammarly across the surfaces your team writes in: browser, desktop, and mobile.
- 2Set up your style and brand-voice profile so suggestions match how you actually sound.
- 3For teams, roll out shared style guides so everyone writes on-brand by default.
- Get real-time clarity, tone, and correctness as you write, in your voice.
- Enforce one consistent company voice across every rep and every channel.
- Lean on its 40M-user distribution: it is already on enterprise machines, so adoption is not a new procurement fight.
Superhuman Docs
THE WEDGECoda, reborn AI-native. A plain-language prompt becomes drafted content, structured tables, and interactive views, backed by Databases that scale to a million rows and one-click MCP into Claude, ChatGPT, and Cursor. This is not a doc. It is where a team builds the tool it would otherwise buy.
- 1Start one doc for a real team ritual: a tracker, a launch plan, an OKR board.
- 2Ask Docs AI in plain language to build the tables, views, and automations you need.
- 3Add a Database for the data that has to scale, and connect your sources with Packs (Jira, Salesforce, Asana).
- 4Turn on MCP so Claude or ChatGPT can read and write to the doc and tables in real time.
- Replace a point tool with a build: describe the workflow and let Docs assemble it.
- Keep the team working in one surface. Review, assign, and act, instead of exporting to a spreadsheet.
- Let AI run the recurring work in the doc, or via MCP from your assistant: draft, track, update.
Build me a [workflow] operating surface for my [team]. Include: a table for [the records], the views we need ([by owner], [by status]), an automation that [does the recurring thing], and a summary section the team reads first. Ask me for anything you need before you build.
How Docs lands a team, and the suite follows.
The land-and-expand motion, in five moves. It is bottom-up on purpose.
Pick one team's most painful ritual, the thing they keep exporting to a spreadsheet, and rebuild it as a Docs plus Database operating surface. It becomes how that team works.
Because the workflow lives in the doc, the team has to use it. Engagement compounds, unlike a wiki nobody opens.
Databases turn the doc into the team's system of record; Packs connect the tools they already run.
MCP wires the doc into Claude and ChatGPT, so the team's AI works on real data instead of copy-paste.
The next team sees it and wants it, and the rest of the suite (Mail, Grammarly, Go) rides in behind the surface that already runs the work.
Nine ways to land Docs, one workflow at a time.
Each play solves a real workflow, plugs into the stack a team already runs, and splits the work between AI and the human. Every one uses a native Pack plus Docs AI. No code. Deal-related meetings write straight back to the CRM; internal and project meetings update the doc and the plan.
Deal meeting, CRM updated for you
Every deal call ends with the CRM already updated: next steps, risks, and stage, no manual logging.
- 1Add the Fireflies and Salesforce Packs to one deal-desk Doc.
- 2Fireflies syncs each call transcript into a table automatically.
- 3A Docs AI block pulls next steps, risks, and deal fields into columns.
- 4A Coda button writes the approved fields to the linked Salesforce opportunity.
- 5The Slack Pack posts the recap to the deal channel.
The internal meeting OS
Standups, 1:1s, and staff meetings run themselves: notes, action items, owners, and the next agenda.
- 1Create one Doc per recurring meeting.
- 2The Fireflies Pack pulls the transcript in.
- 3A Docs AI block generates the summary and an action-item table.
- 4An automation assigns owners and due dates and Slack-notifies them.
- 5Docs AI drafts the next agenda from the open items.
Project meeting to live status
Project syncs update the plan itself: task status, decisions, and risks land in the tracker as you talk.
- 1Build a project Doc with a Database (tasks, milestones) and the Jira Pack.
- 2Fireflies pulls the project meeting in.
- 3Docs AI updates task status and logs decisions and risks to the table.
- 4An automation flags blockers and sends a Slack digest to the team.
The self-enriching prospecting table
A target list that enriches itself and drafts the first touch, with Coda as the operating table.
- 1Pull target accounts into a Coda Database (Salesforce Pack or paste).
- 2Point Clay at the Coda table, or add the Apollo Enrichment Pack, to fill emails, phones, and firmographics.
- 3A Docs AI block drafts the first-touch message per contact from the enriched context.
- 4Approve, then the Salesforce Pack syncs the enriched, messaged records back.
The PLG to GTM auto-handoff
Product usage becomes qualified pipeline, with a handoff checklist that keeps both teams in sync.
- 1Product connects product-usage or signup data into a Coda Database.
- 2Clay enriches, and an ICP score is computed right in the table.
- 3When an account crosses the threshold, an automation creates the CRM opportunity and an owned handoff checklist.
- 4The Slack Pack notifies GTM with the context; the checklist tracks the SLA.
The RevOps command surface
Pipeline hygiene, routing, and forecast prep run on one doc instead of ten spreadsheets.
- 1Two-way sync the pipeline in with the Salesforce Pack.
- 2Docs AI blocks flag stale deals and missing fields.
- 3An automation nudges the owning rep in Slack.
- 4Docs AI drafts the forecast-call narrative for the leader to review.
The customized onboarding hub
A personalized onboarding Doc per hire: role-specific 30/60/90, people to meet, tasks that assign themselves.
- 1Build one onboarding template Doc with a Database for hires and tasks.
- 2Docs AI generates the role-specific 30/60/90 and people-to-meet from the role.
- 3Automations assign tasks with due dates and send Slack or Gmail intros.
- 4The Database tracks time-to-value and completion across every hire.
The customer onboarding doc
A success plan per account that starts from the kickoff call and tracks time-to-value.
- 1Fireflies pulls the kickoff call into the account Doc.
- 2Docs AI drafts the success plan and milestones.
- 3A Database tracks milestones and time-to-value.
- 4Automations create CSM tasks and Slack-nudge on risk.
The board and OKR operating doc
Board prep and company OKRs build themselves from the numbers, so the exec edits instead of assembles.
- 1Pipe metrics into a Database via the Salesforce, Sheets, and other Packs.
- 2Docs AI rolls up OKR progress from the team docs.
- 3Docs AI drafts the board narrative from the numbers.
- 4The exec reviews and edits in one surface.
Connect a few of these and Docs stops being a doc. It becomes the company's operating system, one surface where the AI keeps the work current and the humans make the calls.
Is all of this actually doable, without code?
Yes. Every play uses a native Coda Pack (Fireflies, Salesforce, Apollo, Clay, Slack, Jira) plus Docs AI and automations. You describe it in plain language; nothing here needs an engineer.
Is Superhuman Docs just for GTM teams?
No. It grew up in operations and product, and it is used across Chief of Staff, People, Finance, IT, and engineering. Any team with a painful spreadsheet ritual is a landing spot.
Why lead with Docs instead of Mail or Grammarly?
Mail and Grammarly are individual-productivity wins, bought seat by seat. Docs changes how a whole team works, so it lands a function and pulls the rest of the suite through.
What makes it a build-not-buy decision?
With Docs AI, Databases, and one-click MCP, the tool a team would otherwise buy for one workflow becomes a Docs build in plain language, connected to the data and the AI it already uses.
How does the AI actually help?
Docs AI can read, plan, write, track, and build inside the doc from plain-language prompts, and MCP lets Claude or ChatGPT read and write to your docs and tables in real time.
How do teams roll it out?
Bottom-up. One team builds one workflow, engagement compounds because the work lives there, then it expands department by department, usually with ROI inside 30 to 90 days.
Learn the spine, then wire up your stack.
This is one deep dive in the How to AI series. Start with the fundamentals, or see every tool worth knowing and how to connect it.