Skip to content
SaaSpocalyp.se

Methodology

Where every number comes from.

The Exit Brief — the priced read of your stack at the end of our twelve-minute interview — prints nothing we can't show the working for. This page is the working.

1 · The yearly cost: seats × list price

For each tool you name, the Brief computes a yearly cost at list: seats × the published list price of a named plan, USD, billed annually. The plan, price, source, and the date we checked it are in the table below — the same data the Brief uses, not a summary of it.

If you state what you actually pay, your number replaces ours — an invoice is truer than a list price. List prices are best read as a ceiling: most companies negotiate below them, which is exactly why we never dress this arithmetic up as a savings claim.

A patent-style engraving: one large coin riveted by a short chain to a small blank paper tag in blue ink, the chain measured link by link with drafted dimension lines
Every figure leaves this page chained to its source.

2 · The prices, cited

Six tools researched properly, not sixty scraped loosely. The registry grows one studied tool at a time; anything not in it is assessed, never guessed.

ToolPlan pricedPer seat / moPer seat / yrSourceChecked
SalesforceSales Cloud EnterpriseList price; large orgs typically negotiate below it. Your invoice beats our math — attach it.$175$2,100salesforce.com2026-07-09
HubSpotSales Hub Professional$90$1,080hubspot.com2026-07-09
ZendeskSuite Professional$115$1,380zendesk.com2026-07-09
Monday.comStandardThree-seat minimum, sold in seat tiers.$12$144monday.com2026-07-09
DocuSigneSignature Standard$30$360ecom.docusign.com2026-07-09
JiraPremiumPer-user monthly rate as published; annual billing is tiered and runs lower.$14.54$174.48atlassian.com2026-07-09

Prices are per seat, USD, billed annually, as published on the vendor’s public pricing page on the date shown. Vendors change prices; if a date here looks stale, assume the price moved and tell us.

3 · Coverage compounds, one studied tool at a time

The registry above covers six tools. That is the whole of it: each entry took real research — a named plan, a cited price, a lock-in judgment with a reason attached — and we add entries at the speed that standard allows, not at the speed a longer table would impress.

A tool outside the registry comes back marked assess — no number— rather than guessed. The consequence is worth stating plainly: if your stack runs long on tools we haven’t studied, an early Brief will carry more assess marks than priced lines. We’d rather hand you that than a page of invented figures.

Coverage only moves one way. Every paid Audit produces a versioned exit playbook for each tool it studies, and playbooks are reused — the next engagement that meets the same tool starts from what the last one learned. Each audit deepens the registry; nothing studied is studied from scratch twice.

4 · Lock-in and verdicts, with the reasoning attached

Lock-in is a judgment, so we publish it as one: for each tool, a level — high, medium, low — and a written reason you can argue with. High means leaving is a program (systems of record, custom code, years of history). Medium means the data leaves but the workflows must be rebuilt. Low means the data exports cleanly and the workflows are habits, not code.

Verdicts follow the same rule. Keep, renegotiate, or exit is our current default call for the tool, stated with its reasoning — a starting position for the paid Exit Audit, the full study, not a substitute for it. Assess is what every tool outside the registry gets: no number, no verdict — a research item, named as one.

Salesforcelock-in: high · renegotiate

System of record. Custom objects, Apex code, integrations, and years of pipeline history make leaving a program, not a project.

HubSpotlock-in: medium · renegotiate

Contact and deal records export cleanly, but sequences, automation, and attribution history are woven into the platform and don't travel.

Zendesklock-in: medium · exit

Tickets and help-center content export well; macros, triggers, and routing rules have to be rebuilt wherever you land.

Monday.comlock-in: low · exit

Boards export to spreadsheets and the workflows are conventions, not code. The data leaves easily; the habits take a fortnight.

DocuSignlock-in: low · exit

Completed envelopes are portable PDFs with audit trails — keep the archive forever. The live workflow itself is small.

Jiralock-in: medium · keep

Issues export; the gravity is in integrations, automation rules, and the habits of every team that lives in it.

5 · What the Brief refuses to estimate

A savings or “overspend” figure

Estimating what you could save requires knowing what your teams actually use, what you actually pay, and what a replacement actually costs to run. A twelve-minute interview establishes none of those. Any percentage we printed would be theater.

A build price

A fixed build price comes out of the paid Exit Audit, which studies your data, integrations, and compliance posture. The pricing page shows our current working bands; only the Audit turns a band into a number and a date.

Anything about a tool we haven’t studied

Unknown tools are marked assess and priced only by what you tell us you pay. Each one becomes a research item in the registry — the next Brief knows what this one didn’t.

The Brief is worth reading because of what it won’t say.

6 · How the paid Exit Audit works

Everything above describes the $0 Brief. The Exit Audit — the paid study, $2,500–$12,000 fixed and never credited toward a build — runs on evidence the twelve-minute interview cannot reach: your usage data, your invoices, and how your tools are actually wired together. The Brief prices a stack from published list prices and what you tell us; the Audit measures it.

The survey

Every tool, seat, and overlap in scope — cost from your invoices where you share them, list prices where you don’t.

The verdicts

A keep, renegotiate, or exit call on each tool, with the reasoning written down — the same rule as section 4, with measured evidence underneath it instead of defaults.

The roadmap and the price

An exit roadmap sequenced by risk, and a fixed build price for anything worth building — the number the working bands on the pricing page defer to.

The playbook

A versioned exit playbook per tool, yours to keep — whatever you decide to do with the findings, including nothing.

7 · What we hold, and how you get it deleted

The interview sits behind a sign-in: we email a link to your work address, and clicking it is the whole sign-in — no password, and personal email domains are declined. Before the first question, that address is all we have asked of you.

From there we keep what you tell the interview — your stack, seat counts, spend, and constraints — and use it to produce your Exit Brief and, where the interview qualifies, your written proposal. We do not sell your data. Anonymized, aggregate patterns may inform our published research; nothing that identifies you ever does.

Ask us to delete anything you’ve submitted and we will — any channel on the contact page reaches a person who can do it. The full statement is on the privacy page.

That is the method. The case for using it — what changed in the market, and why buying software is a decision again — runs longer than a methods page allows, so it stands as its own essay, every claim graded and cited.