Can you drop Granola for client calls you do not host?

You can consider cancelling Granola when your existing suite reliably supplies the notes you need from client-hosted meetings, and your team can still retrieve its old records. Owning a suite does not establish either condition. Test the client calls where you are an ordinary external participant, not just the internal meeting where you control every setting.

This decision concerns a consultant, account manager or small team moving between clients' meeting platforms. If all your calls happen inside your own organisation, start with the built-in transcription guide. Here, the useful question is whether a separate capture and history service remains necessary for the calls you cannot administer.

Separate capture from entitlement and permission

Granola's desktop app uses microphone and system audio without a meeting bot. Its web interface can display and edit existing notes but cannot transcribe. Desktop capture also combines system audio rather than isolating one application. Close unrelated audio and test the actual headset and computer used for client work. Granola transcription documentation.

Device availability is not equivalent to call coverage. Granola lists iPhone and Android apps, but says they cannot transcribe virtual meetings inside other mobile apps. They support in-person notes; its documented outbound phone-call feature is iOS-specific. A successful laptop test therefore does not cover a Teams call taken entirely on a phone. Granola mobile guide.

For Meet's AI notes, the organiser needs an eligible entitlement. Host controls can restrict starting and stopping notes to hosts; the resulting document lives in the organiser's Drive and access follows sharing settings. Seeing a notes attachment on an invitation is not proof you can open it. Your own Workspace subscription does not settle the client's setup. Google's notes and access rules.

Teams has a similar external-participant boundary: Microsoft's role table says a participant from another tenant cannot start transcription or view or download the transcript after the meeting through that role. Organisers can arrange permitted sharing, but test that handoff explicitly. The same page says participants receive a transcription notification. Microsoft's transcript permissions.

Participant notice is a separate pass condition

Granola documents optional automated chat messages and a video watermark to indicate transcription. Their existence does not establish that either is enabled, visible on your particular call or sufficient for your organisation's process. Granola transparency options.

Agree with your organisation and the client what is allowed, how participants will be told, how required agreement will be obtained, and who can stop capture. Granola's own guidance directs users to their organisation's responsible team and says to obtain consent when transcribing others. Granola's consent guidance.

Run neither candidate when the agreed process fails. Use permitted manual notes or the client's approved record instead. No bot appearing in the participant list is not a reason to capture covertly. Include late arrivals and a mid-call request to stop in the rehearsal; a notice shown only at the beginning may not reach everyone who joins later. This guide does not determine legal sufficiency.

Run this unexecuted client-call pilot

This is an UNEXECUTED test plan, not a report of product testing. Choose six authorised calls covering your recurring client platforms, including at least one call hosted outside your organisation on each platform you depend on. Include your normal desktop and mobile situations. If a device cannot support the proposed route, record that as a gap rather than quietly moving the test to a laptop.

Before starting, name a notes owner and backup operator. Define the required output: reviewed decisions and actions, a searchable transcript, or both. Agree a delivery deadline and retrieval time limit appropriate to your team. Use this row for every call:

Record	What to write down
Setup	Date, client platform, organiser, your role, device and entitlement checked
Participant process	Approved method, notice observed, required agreement and stop procedure
Capture	Who starts it, missing segments, names or numbers needing correction
Delivery	Actual recipient, destination, access test and time until usable
Retrieval	Question answered, original source found, operator and elapsed time

Compare both routes only where parallel capture is authorised. Otherwise use comparable rehearsals or an approved reference record. Ask the responsible participants to check a decision, a qualification, an action owner and a deadline. Preserve uncertainty; a fluent summary does not establish what somebody promised.

Have the backup retrieve the result from their own account the next day, without help from the primary note taker. Ask a concrete question such as which delivery date the client accepted and whether it was conditional. Check the source passage as well as the summary. Repeat after the primary operator is unavailable, without deleting accounts to simulate absence.

Pass only if every essential call type has an approved route, required information is correct after review, recipients can open it, and the backup meets your retrieval deadline. Record correction and sharing time. If the client must manually email every transcript, that dependency belongs in the result. The meeting-notes workflow can structure the summarisation step once the source record is available.

Prove that history has a usable home

Granola's CSV export includes titles, summaries, transcripts and basic details, but only for notes you own in selected workspaces that have a summary. Deleted and unsummarized notes are excluded. Admins cannot export other members' private notes; Enterprise export also depends on an admin setting. Granola's export boundaries.

Before changing billing, inventory the historical client records people actually revisit. Have each responsible owner preserve permitted material and reconcile missing records. Check an old meeting, a shared note and a note owned by someone else separately. A CSV count alone is insufficient: the backup must locate the right client, date and source text in the proposed archive, with appropriate access.

Keep Granola when externally hosted calls routinely lack a dependable suite handoff, the archive remains operationally important, or the replacement requires more administration than the team can sustain. Keep the current arrangement while any critical history or participant-process test is unresolved.

For rollback, leave the existing process available during the pilot, record which notes each route owns, and nominate the person who resumes the approved route if capture or retrieval fails. Reconcile overlap before sharing follow-ups so clients do not receive conflicting action lists. Do not assume an export can be imported back with identical search and permissions.

Calculate the bill that changes

Use your actual Granola invoice and downgrade or renewal quote, matched to the same seats, currency and term. Record the effective date and any commitment that survives. Compare the current total with the remaining Granola charge plus only additional suite licensing, storage or other replacement costs.

Recurring reduction = current charge − retained charge − incremental replacement cost. Count an already retained suite once in the overall stack; do not charge its entire bill again for every meeting. If an annual commitment or retained seats leave the invoice unchanged, moving notes produces zero immediate contractual saving. Track one-time archiving and ongoing review effort separately.

Record the result in the subscription audit. For recurring review options and availability, see Stack Watch.