Start with billing units, not logos
A five-person company rarely buys five identical copies of every product. The useful unit of analysis is the unit the vendor actually invoices: member, editor, full seat, guest, workspace, site, account, or usage allowance. The pricing page must be read together with its annual-billing language, minimum-seat rules, and the permissions attached to each seat type. That distinction matters because a polished interface or familiar brand can hide the operating condition that determines whether the route works. Record one owner for each plan and write down exactly which of the five people need paid editing or administration rights. The review should leave an attributable record rather than a memory of what the page or demo appeared to say. Build the first ledger row from the official page, verification date, billing cadence, currency, quantity, and known monthly and annual outlay. This sequence keeps the decision testable by another person and makes later changes easier to audit.
- Do not multiply every headline price by five before checking the billing model.
- Keep guest, viewer, specialist, account, and per-user entitlements in separate columns.
- Mark a price as unknown when tax, region, quote requirements, or usage makes normalization unreliable.
Price the team that exists
Headcount is not the same as billable headcount, and the difference is often the largest source of avoidable spend. Start by examining a named seat map that connects each paid entitlement to a recurring job, deliverable, and accountable operator. A general office suite may cover all five people while a design, research, finance, or automation product may serve only one or two specialists. The purpose is not to reward the product with the longest feature list; it is to see whether a specific team can complete a specific job while preserving evidence, access, and recovery. If nobody can name the work that requires a premium entitlement, the seat belongs in the review queue rather than the baseline budget. Write the boundary before the trial so a convenient success cannot erase a serious failure. Model the current route and a lower-cost route side by side, preserving the people and outputs instead of merely deleting expensive rows. Keep the observed result, source date, owner, and unresolved questions together.
- Use named roles in the review copy even if the finance export uses anonymous license counts.
- Separate temporary project access from an entitlement that renews every month or year.
- Check whether a stronger plan is needed for one administrator while collaborators can use a lower tier.
Add commitment and cash-flow cost
A monthly equivalent can make two plans look comparable while hiding very different cash and cancellation conditions. In practice, the review covers monthly price, annualized cost, known upfront payment, first-year cash requirement, renewal date, and cancellation window as separate fields. Official pages frequently distinguish monthly billing from annual commitments, and some display a monthly rate that is available only when a full year is committed. These details turn a general product claim into an operating test with a clear input and output. Finance should approve the commitment that is actually signed, not the smaller monthly number used for visual comparison. Unknown conditions should remain visible instead of being converted into confident prose or a synthetic score. Show normalized monthly cost for comparison, but retain the invoice cadence and known upfront total beside every decision. A second reviewer should be able to reconstruct why the team accepted, restricted, postponed, or rejected the route.
- Never label an annual-commitment monthly equivalent as a cancel-anytime monthly plan.
- Put renewal and notice dates on the operating calendar, not only in the procurement file.
- Keep non-USD prices outside USD totals until a reviewed conversion policy exists.
Test overlap at the paid-plan level
Two products sharing a feature label are not automatically substitutes. The control surface here is the exact paid capability, permission, file format, integration, service level, and workflow stage that each plan covers. Storage, documents, meetings, AI assistance, project tracking, and publishing often appear in several subscriptions but differ in depth and operating responsibility. Procurement and workflow design meet at this point: commercial access is valuable only when the required behavior and responsibility exist in the purchased plan. Treat overlap as actionable only when a named workflow can move without losing a required capability, owner, source record, or recovery path. Document exceptions because they become the hidden source of extra tools and unsafe workarounds. Run the replacement on a bounded project, compare outputs and access controls, then document the plan change before canceling anything. The result should describe both the normal path and what happens when the service, network, data, or responsible person is unavailable.
- Shared capability strings are a research lead, not a cancellation rule.
- Compare the plans already purchased rather than the vendors' entire product families.
- Preserve a rollback route until files, permissions, integrations, and audit history are confirmed.
Count the work required to change
A cheaper license can create a more expensive first year when migration and retraining are omitted. A credible comparison therefore measures export, cleanup, conversion, permission remapping, integration rebuild, training, dual-running, support, and rollback labor. The relevant estimate comes from a small migration rehearsal with representative documents and users, not from a marketing claim that import is supported. List price or output appearance cannot carry the entire decision because change work, permissions, rights, and review obligations remain part of the system. Assign an hourly internal rate or a fixed change budget and compare it with the twelve-month license saving. Keep known values separate from unknown values and do not use invented precision to make uncertainty look resolved. Require a human owner, completion evidence, and a stop condition for every migration task before signing the replacement contract. Review the result against the same acceptance criteria used at the start.
- Include the cost of keeping both products active during a safe transition.
- Test complex files, automation, permissions, and external-sharing links, not only a clean sample.
- A migration that removes business evidence or recovery options is not a saving.
Approve a renewal decision, not a spreadsheet total
The final number matters only when the team can explain what it will keep, change, and review again. The release decision brings together a signed decision record containing current cost, target cost, plan changes, affected people, capability boundaries, risks, owners, and review dates. The official price pages establish the attributable snapshot, while the team's own workflow test establishes whether the route is operationally credible. This is where a research note becomes an accountable operating choice rather than a recommendation that nobody owns. Approve renew, resize, replace, or investigate for each plan; do not hide uncertain rows inside a single green saving figure. Preserve the source snapshot and local test so future reviewers can distinguish vendor change from an internal workflow change. Schedule a post-change review after one billing cycle and restore the old route if required outputs or controls deteriorate. Set a fresh evidence date and a rollback trigger; a decision that cannot be revisited safely is incomplete.
- Keep known totals separate from unknown or quote-only costs.
- Show annual savings only after change work and temporary dual-running are included.
- Record the next evidence date so the model does not become an undated price claim.