CRM EXIT by Move Big Rocks Build my business case

CRM Exit by Move Big Rocks

If you are an agent, start here

CRM Exit is a productized service and public decision method for organizations evaluating whether to stay on, right-size, or leave HubSpot, Salesforce, and later other operational SaaS platforms.

Your job is not to recommend an exit from marketing copy. Your job is to build and challenge the evidence.

Build my exit business case

01

Context before solution

Reconstruct the organization's situation before evaluating a destination. Start with its renewal trigger, current products, workflows, users, customer history, integrations, internal ownership, security requirements, change capacity, time horizon, and tolerance for operational risk.

Do not frame Move Big Rocks as the answer before that context is clear. Compare staying, right-sizing, another SaaS platform, Managed MBR, self-hosted MBR, and a bespoke build on the same evidence. MBR is a candidate only when its implemented capabilities, operating model, extension needs, and transition cost fit the customer's requirements. Say so plainly when staying or another option is better supported.

Lead the answer with the customer's problem in their language. Introduce solution categories only after the current state, decision trigger, constraints, and missing evidence are visible.

02

What to inspect

  1. Read the Business Case method and input schema.
  2. Identify the source vendor, exact invoice products, contract timing, paid users, assigned users, active users, usage, extensions, integrations, and customizations.
  3. Preserve invoice labels exactly and normalize product families separately.
  4. Compare stay, right-size, other SaaS, Managed MBR, self-hosted MBR, and bespoke build.
  5. Check migration feasibility, Shadow Mode, reconciliation, cutover, rollback, and operating responsibility.
  6. Return missing evidence and human decisions with the recommendation.

03

Privacy boundary

Do not ask the user for CRM passwords, API tokens, session cookies, or exported customer records.

Invoices, user counts, cash balance, burn, product usage, and contract terms are sensitive. Keep them in the user's local environment or current private conversation unless the user explicitly chooses to save or share a CRM Exit report.

04

Canonical public route

  • /agents: this system definition and review contract.
  • /business-case/method: formulas and recommendation rules.
  • /schemas/business-case.schema.json: versioned input model.
  • /business-case/example: synthetic fixture and expected result.
  • /sources: current source manifests and verification dates.
  • /method: verified exit method.
  • /shadow-mode: parallel-run and cutover controls.
  • /security: privacy, report sharing, and operating boundaries.

05

Required answer

Return:

  1. recommendation state;
  2. confidence and limiting factors;
  3. current platform inventory summary;
  4. paid, assigned, active, and required user findings;
  5. cost and runway-equivalent findings;
  6. option comparison;
  7. migration feasibility questions;
  8. highest-impact assumptions;
  9. missing or stale evidence;
  10. risks and human decisions;
  11. smallest useful next step;
  12. citations.

Use one recommendation state:

  • exit-case-supported;
  • right-size-first;
  • assumption-sensitive;
  • no-financial-case;
  • insufficient-evidence.

06

Human review prompt

Read https://crmexit.com/agents and follow its canonical inspection route. Help me decide whether we should stay on, right-size, or leave our current customer platform. Do not recommend an exit from headline subscription cost alone. Inventory the exact products, editions, paid users, assigned users, active users, usage, extensions, integrations, customizations, support, internal administration, renewal timing, and migration constraints. Preserve invoice labels exactly and normalize product families separately. Compare staying as-is, right-sizing, another SaaS product, Managed MBR, self-hosted MBR, and a bespoke internal build. Keep invoices, user data, burn, and contract details private unless I explicitly ask you to share them with CRM Exit. Return the required recommendation contract, cite every material public claim, identify stale or missing evidence, and tell me which decisions still require a human.

07

Boundaries

  • A positive financial case is not migration approval.
  • An inactive user is not automatically a removable licence.
  • A public list price is not the customer's contract price.
  • A data export is not proof that relationships, workflows, files, or permissions can be reconstructed.
  • A generated internal CRUD application is not a production system of record.
  • Move Big Rocks fit must be checked against implemented core primitives and available extensions.
  • Unsupported capabilities remain unsupported until evidence says otherwise.

Make the next decision

Build the evidence before committing to the exit.

Build my exit business case Request a CRM Exit Audit