1. LandOffer
  2. Blog
  3. All articles
  4. Supernormal Review: Shared AI Credits, Meeting Notes, and Team Controls

AI at Work

Supernormal Review: Shared AI Credits, Meeting Notes, and Team Controls

Evaluate Supernormal’s shared credit pool and current monthly or annual billing. Three fictional workload budgets and a completed low-balance acceptance record separate documented features from untested usage, output quality and administrator controls.

10 min readLandOffer team

Evaluate Supernormal as a shared-credit workspace for meeting notes and follow-up artifacts, rather than multiplying an old per-seat price by your team size. Its current Team plan combines unlimited seats with a pooled allowance; Business adds organizational controls. The buying question is whether your actual capture and generation workload fits the pool, and whether the controls your organization requires are available and verified.

This documentation-based LandOffer.ai review checked official sources and the public pricing calculator on October 27, 2026. The worked budgets, meeting packet and acceptance record are fictional planning exercises. No Supernormal account, app, meeting capture, generated output, credit deduction or administrator control was tested. Only the public pricing display and our own arithmetic were observed.

Three people review a marked document, a landscape print and a gridded worksheet beside a shared tray of blue counters, with a conversation ribbon overhead.

Read the current allowance and billing term together

At the 50-credit selection, the public pricing page displayed Team at $20 per month and Business at $40 per month. Turning on Annual changed the displayed monthly equivalents to $18 and $36, explicitly billed annually. Twelve times those equivalents is $216 or $432; those are arithmetic equivalents, not invoices we obtained. Confirm currency, tax, renewal terms and the final quote before committing.

Free lists 15 monthly credits with a five-credit daily limit. Team removes that daily limit and allows unlimited seats to share credits. Business adds SSO, audit logs, data retention, member visibility and administrator controls. At the selected paid allowance, teammates draw from one 50-credit monthly pool; removing the daily cap does not remove that monthly constraint.

The official 2.0 plans guidance, dated May 19, 2026, distinguishes rollover by billing term: unused credits roll into the following month on monthly plans, or for up to two years on annual plans. Do not treat every unused balance as permanent or assume an annual payment makes a year's credits immediately available. Have the owner confirm the actual balance, renewal and credit-expiration treatment for the organization.

Legacy seat-based screenshots are a poor purchase calculator for this model. The current help guidance explains a transition to credits; existing accounts can also have migration or prorated balances that a new-customer price does not describe. We did not inspect a legacy subscription or its remaining entitlement.

Separate plan capability from purchased capacity so a required control does not conceal an insufficient credit pool. Choosing Business for SSO does not, at the base selection above, increase the listed 50 monthly credits. A team can need stronger administration and more credits for entirely different reasons. Additional-credit options and their final price should be confirmed in Billing rather than inferred from a linear price-per-credit calculation.

Check the capture path and the work produced afterward

Supernormal's current meeting-notetaker page describes desktop capture without a bot joining the call, followed by prompts that use meeting context to produce documents, slides and other work. It lists Apple Silicon with macOS 14.4.1 or later, or Windows 11 or later. Those are documented requirements, not a compatibility result from our review device.

For this evaluation, a fictional four-person operations team plans a 30-minute internal pilot-readiness call on supported, organization-approved equipment. The meeting concerns a training checklist and an unresolved manual-review dependency. It contains no real employee, customer or confidential operational data. Every scenario below repeats that same kind of packet rather than changing content complexity invisibly between comparisons.

The source packet records three points: Mina accepts a pilot checklist due November 6; Jules accepts investigating whether Building C needs manual review; no Building C rollout date is approved. A usable follow-up brief must retain those distinctions. A polished document that turns Jules's investigation into a promise to finish every Building C change by November 6 would fail the team's review.

The authored corrected brief reads: “Mina will deliver the pilot checklist by November 6. Jules will investigate Building C's manual-review requirement; no completion date for changes is agreed. Rollout remains pending that finding and the designated owner's approval.” This is our example of an acceptable output, not text generated by Supernormal or evidence of its accuracy.

Before evaluating capture, have the authorized owner confirm participant notice and the organization’s permitted setup. Supernormal's April 20 transition guidance assigns notification responsibility to the user and describes retiring its bot and extension. Verify the permitted capture approach before enabling it; a missing bot participant is not evidence that everyone knows capture is occurring. No meeting permissions or recording settings were changed here.

For the same packet, Saira also completes an artifact-review decision: retain Mina's accepted checklist, remove the invented Building C delivery promise, and send the revised draft back to the participants for confirmation before distribution. The example records no participant confirmation and no email is sent. A drafted follow-up and an accepted commitment remain separate states even when the software can produce both notes and a polished document.

That distinction belongs in a paid evaluation. Record whether correcting the brief requires editing an existing artifact, running another prompt or starting over, then check the corresponding usage in the authorized trial. This review does not assume that manual edits consume credits or that regenerations are free. The proposed test is useful precisely because the public task-complexity description does not settle those details.

Worked budget: three frequencies using one synthetic packet

The central uncertainty is credit consumption. Supernormal's Usage & Credits guidance says task type and complexity affect usage and does not publish a fixed output-per-credit breakdown. It also describes a shared base pool and owner/admin access to daily and monthly usage. Meeting duration alone therefore cannot establish how many credits a team will need.

For a sensitivity exercise only, assume 0.5 credits per capture-and-notes unit, two per first follow-up brief and one per revision task. These are invented planning coefficients, not Supernormal rates, measured costs or a promise about a 30-minute meeting. The “capture-and-notes unit” is our bookkeeping label, not a vendor billing category. Counts refer to the entire four-person team, with each meeting counted once.

Monthly frequency Captures First briefs Revision tasks Assumed total Planning consequence
Light 8 4 2 14 credits One below Free's monthly allowance, before daily concentration or actual usage is known
Working 20 10 5 35 credits Fifteen below a 50-credit pool under these assumptions
Heavy 40 20 10 70 credits Twenty above that pool; capacity or scope needs review

The working row is 20 × 0.5 + 10 × 2 + 5 × 1 = 35. If real unit consumption were twice those assumptions, the same workflow would require 70, exceeding 50 by twenty. The arithmetic can be exact while the assumed unit consumption remains unknown. Our isolated Decimal calculation verifies totals and sensitivity, not product metering.

The light row is not an unconditional Free-plan recommendation. Concentrating six hypothetical credits of work into one day would exceed the stated five-credit daily cap even if the month totaled only fourteen. Paid-plan rollover could alter a particular month's available pool, but this table deliberately assumes none. Check the usable balance rather than borrowing an unconfirmed future renewal or carryover.

Before purchase, an authorized evaluator should record usage before and after a small approved packet, including any reruns. Record the packet identifier, first-draft task, each regeneration and any concurrent teammate activity beside the before/after balance. If the usage page only provides aggregate changes, note that concurrent work makes attribution uncertain. Do not present a shared daily delta as the measured cost of one brief without isolating the other activity.

A person holds an unfinished landscape sketch behind a low wooden rail and points to a few blue counters beside a latched document box.

Worked acceptance record: low balance and team controls

The team's fictional readiness record starts with a 50-credit monthly base and 43 credits already used, leaving seven. No rollover or additional purchase is assumed. Owner Saira prioritizes the next meeting's usable notes and first brief over an optional revision. The following charges are a second invented scenario, deliberately different from the sensitivity coefficients; they are not measured deductions.

Proposed operation Fictional charge Paper decision Balance after that decision
Capture and notes 1.5 Reserve in the scenario 5.5
First follow-up brief 3.5 Reserve in the scenario 2
Optional revised brief 2.5 Hold: insufficient scenario balance 2

All three would total 7.5, half a credit more than seven. Our arithmetic check leaves the last task pending instead of creating a negative usable balance. This is the team's proposed allocation policy, not evidence that Supernormal blocks precisely this operation, preserves a draft at exhaustion or offers a particular automatic top-up behavior.

Saira's completed evaluation record makes the remaining questions explicit:

Requirement Evidence available in this review Completed assessment and next owner
Shared usage visibility Usage help describes owner/admin daily and monthly views Documented; Saira still needs an authorized account readback
Top-up authority and cost Billing guidance describes adjusting credit buckets and billing frequency No purchase approved; Saira must review the quote and organization's approval rules
Restrict each member's spending No verified per-member hard cap in this review Unverified; do not treat the paper allocation as an enforced limit
SSO, audit and retention needs Listed as Business additions Requirement points toward Business evaluation, not proof of configured enforcement
Private notes and deliberate sharing Dated transition help describes private-by-default notes Account access and recipient behavior untested; sharing review remains required
Brief fidelity Corrected authored brief preserves the unresolved Building C question Review criterion completed; no AI output assessed

The role guidance, dated January 26, 2026, distinguishes owner, admin and member. Owners manage organization settings, membership and billing; admins have comparable management access except ownership transfer. Verify actual current roles and usage access before changing membership; this older role page is documentation, not a readback of the evaluated organization. A pending invitation is also different from an accepted, active member.

The billing-adjustment guidance describes selecting credit buckets and monthly/yearly billing. That is a documented administrative path, not authorization for this evaluator to change a subscription. We did not open Billing, add a card, invite a member or modify any role.

The access review needs a similarly concrete record. Saira's proposed test uses the synthetic Building C packet with one intended reviewer and one teammate who should not receive it. The owner would inspect the current sharing choice, the intended recipient's view and the other teammate's access, then document results without involving real operational information. In this review all three observations remain unperformed. A pricing-page control name cannot stand in for those readbacks, and a private default does not describe every later sharing action.

Retention requires an agreed outcome as well as a setting label: which meeting-derived material is covered, what authorized administrators can configure and how the organization's policy maps to that behavior. Those questions stay in Saira's open record. No retention period, deletion outcome or audit-event coverage has been confirmed here.

Decide what must be true before using it for team work

Supernormal merits a closer evaluation when a team wants desktop notes and several kinds of downstream artifacts using one shared allowance. Its credit model can avoid paying separately for every seat, but the practical value depends on real consumption, the usefulness of reviewed outputs and the controls the organization needs. This review establishes no transcription benchmark, time saving or automatic follow-through.

For the fictional team, Saira keeps procurement open. A small approved packet on Free could answer basic capture and output questions if its limits and required approvals permit it. Team is a capacity-and-collaboration option when its shared pool and available controls suffice. If SSO, retention or audit controls are mandatory, Business needs a separate configuration and access review before real material is introduced. None of those decisions follows solely from the 35-credit scenario.

Keep acceptance evidence specific: device and app version, plan and billing term, before/after usage, the exact safe input, reviewed notes and artifact, intended recipients, and behavior when available credits are insufficient. Leave unknowns marked unknown. Annual rollover, private defaults and unlimited seats are distinct product promises; they do not establish who can see a particular meeting, who may spend a pool or what survives exhaustion.

For additional workplace guides, return to LandOffer.ai. Bring the representative packet, assumed shared-budget calculation, billing selection and unfinished access/usage checks to the authorized owner. That gives a team a defensible evaluation target before it commits money or relies on meeting-derived work.

Sources and Further Reading