Cancel a SaaS subscription: Notion, Zapier, Calendly and Google Workspace preparation

A clean SaaS exit starts before anyone presses a downgrade or cancellation button. Build a small evidence folder containing the latest invoice, the current billing cycle, renewal timing, paid seat count, usage settings and any data that must survive the change. Then assign an owner to verify each item inside the account. This turns an emotional “cancel it now” request into a controlled offboarding process. The four products in this guide illustrate different risks: Notion has invoice-based refund windows; Zapier can introduce usage-based overages on eligible accounts; Calendly bills purchased seats even when they are empty; and Google Workspace cancellation can affect both contractual charges and stored user data. Do not assume one vendor’s logic applies to another. The practical sequence is export, inventory, verify, capture and change. Export important information, inventory users and integrations, verify billing terms, capture screenshots or invoices, and only then alter the subscription. This is an operational checklist, not a substitute for the current terms displayed in your account.

Notion: work backward from the invoice date

For Notion, the invoice date is the first detail to capture. Its refund page states that a full refund may be available when a monthly subscription is downgraded within three days of the invoice date. For annual billing, the documented window is 30 days from the invoice date. Accidentally added members require their own check: Notion says prorated member charges may be refunded if the member is removed and support is contacted within three days of the invoice date. Purchased credits follow a different rule. They are refundable only while unused; using any portion ends eligibility. The purchase channel matters too, because Apple App Store purchases must be handled through Apple. The operational takeaway is to avoid filing every billing issue under one generic “refund” request. Identify the billing cycle, invoice date, charge type and purchase channel first. Save the relevant invoice and describe the requested correction precisely. The supplied evidence covers refund eligibility, not Notion’s exact cancellation interface. Evidence: https://www.notion.com/help/refunds

Zapier: inspect pay-per-task exposure before changing the plan

Zapier requires a usage audit, not just a renewal-date check. Its documentation says eligible Professional, Team and Enterprise accounts automatically move to pay-per-task billing for the rest of the pay period after exceeding the monthly task limit; the page specifies this automatic behavior for accounts created after January 2024. The exact overage rate is not published on the supplied page because it depends on the plan and billing cycle. Zapier directs customers to Billing settings for their account’s rate. Usage is capped at three times the plan’s task limit, after which Zaps stop running. The pay-per-task option can be switched off in Billing settings, with the change taking effect immediately. Before changing anything, record current task usage, the base limit, the displayed overage rate and whether pay-per-task is enabled. Then identify which automations are operationally critical if runs stop. This produces a safer decision than simply lowering the plan and discovering the workflow impact later. The evidence does not supply Zapier’s full cancellation procedure. Evidence: https://help.zapier.com/hc/en-us/articles/15279018245901-How-pay-per-task-billing-works-in-Zapier

Calendly: compare purchased seats with actual users

Calendly’s billing model makes seat inventory the central pre-change task. Calendly defines a seat as a place for a person in the organization and says every seat is billed even when it is unfilled. Its example explains that an organization with five seats and four users still pays for five seats. That means removing a user and reducing paid capacity are not necessarily the same action. Timing also matters: upgrades and added seats take effect immediately, while downgrades and removed seats begin at the end of the current billing cycle. Monthly and yearly plans renew at the end of their respective billing cycles. Build a simple table listing purchased seats, assigned users, empty seats and the current cycle end. Mark seats that can be removed, but do not forecast immediate savings when the documented change starts only after the cycle ends. Also record upcoming hiring or contractor needs so useful capacity is not removed by accident. The supplied page supports this billing audit but does not provide a complete cancellation walkthrough. Evidence: https://calendly.com/help/billing-overview

Google Workspace: export first and identify the commitment

Google Workspace has the highest data-loss risk in this comparison. Google’s cancellation page states that users’ Google Workspace data is deleted after cancellation and cannot be restored. It recommends exporting Gmail, Calendar, Chat and Drive data first, with the Data Export tool described as the easiest method. Billing exposure depends on the plan. Under the Flexible Plan, charges cover the days the service was used; Google’s example describes cancellation halfway through a month producing a half-month charge. Under an Annual/Fixed-Term Plan, the remaining balance of an existing commitment can still be charged. Google also notes that service used since the last payment may create another charge. If funds remain after cancellation, the page directs the customer to contact Google to request a refund. Before proceeding, confirm the plan type, commitment balance, latest payment period, export completion and ownership of downloaded records. Cancellation should be the final step only after someone has verified that required user data is accessible outside Workspace. Evidence: https://knowledge.workspace.google.com/admin/billing/cancel-google-workspace?hl=en

A reusable five-step SaaS offboarding record

Turn these vendor-specific checks into one reusable operating procedure. First, export business-critical data and test that another authorized person can open it. Second, inventory users, seats, integrations and automations; note which services could fail after access changes. Third, inspect billing settings for the plan type, cycle end, invoice date, usage overages and commitment status. Fourth, save evidence before editing the account: download invoices and capture the settings that influenced the decision. Fifth, record the final action, its effective date and the person responsible for checking the next statement. Add a follow-up reminder after the expected change date rather than assuming the request completed correctly. For Notion, emphasize the invoice and refund category. For Zapier, emphasize task exposure and pay-per-task settings. For Calendly, reconcile purchased seats with assigned people. For Google Workspace, verify exports and commitment terms before cancellation. This shared framework prevents four common process failures: lost data, overlooked capacity, unexpected usage charges and undocumented account changes. Always confirm the current vendor page and in-account terms at the time of action.

Sources

Narration and illustrations in the companion video were generated with AI. Every claim above was checked against the linked pages on 2026-09-08. Article text expanded on 2026-09-08.

Spotted an error? Report it here. We fix it and list it, dated, on the Corrections page →