Supernormal underwent material product changes in 2026. An old article about an extension-only meeting notetaker would mislead readers now evaluating its desktop capture and client-work generation.
Product identity and supported workflows
The company’s April 2026 help page says its new desktop capture app replaced Norma and the Chrome extension, while meeting outputs remain accessible on app.supernormal.com. Its release log also says the Radiant name was folded back into Supernormal and reports a broader focus on documents, slides and client work.
Who it is for and the decision it addresses
Agencies can use a consented kickoff call to draft an internal creative brief or an initial client deck. That is a faster first draft, not assurance that quotes, branding, client instructions or licensing constraints have been interpreted correctly.
Step-by-step first evaluation
Install only the supported desktop client for your operating system, connect an authorized meeting and capture it with notice. Generate a draft brief. Compare the project goal, audience, sign-off person and exclusions with the original transcript; explicitly remove ideas that were brainstormed but never approved.
Failure modes and limitations
Platform changes can retire older extension workflows. Current vendor pages describe system requirements for macOS and Windows; any older how-to screenshots should be dated. Generating client-facing media from a meeting does not establish rights to images, logos or audio that participants happened to mention.
Privacy, permissions, licensing and governance
With local desktop capture, company device policy and participants’ recording consent remain central. Review workspace sharing, third-party integrations and any AI connections to mail or project files before using privileged client material.
Exports, retention and avoiding lock-in
Preserve approved briefs and slides as standalone documents. Meeting history and linked context can be proprietary to a workspace; verify bulk export and retention in the organization’s terms instead of assuming a lifetime archive.
Alternatives and team boundaries
Jamie emphasizes simple capture, while Sembly creates client deliverables. For agent execution beyond the meeting-to-document path, see the the agent-security and orchestration guide specialist coverage.
What remains unverified for each country, version and plan
This October 25, 2026 profile reflects dated first-party product documentation, not independent hands-on testing or an endorsement. Exact country availability, model versions, accessibility provisions, seat entitlements, enterprise residency, retention settings and the whole supported language matrix vary by configuration. Where a plan/region/date combination was not verified with its exact original source, it is left unknown, not assumed worldwide. The product may have changed since the documented feature appeared.
Pricing and evidence boundary
No subscription price, usage allowance, API token rate, special promotional plan, success benchmark or commercial license is asserted here. A dated pricing reference covers independently time-stamped pricing snapshots. Product brochures are supplier claims; human reviewers must check linked evidence against the actual source and retain their own decision trail. No screenshots, borrowed brand assets or pretend product tests are included. Specialist model, media, coding and autonomous-agent deep dives belong to their designated teams.
Sources & Further Reading
Primary vendor documentation accessed 2026-10-25; market-specific terms and feature rollout require additional verification. These sources support stated vendor-product claims, not an independent quality score.