Salesforce to AI
You pay for Salesforce twice, and only one bill is on the contract
The license is the number people negotiate. Then there's the implementation, the administrator, the consultants, the managed packages, and the portal licenses for everyone outside the company. That second number is usually the larger one, and it doesn't stop when the project is done, because a heavily configured org needs somebody to keep it upright.
At the end of it you have a system shaped entirely around your business that you still don't own, plus a renewal every year to keep using it. This page is about that moment.
Where we stand
What we can honestly say about Salesforce
We were never a Salesforce partner and we're not going to imply otherwise. What we've done is integrate with it, connecting Salesforce to a client's project system so closed deals flow into delivery. That's a different kind of familiarity, and in this conversation it's the more useful one.
We were partners of other platforms, monday, Smartsheet, Wrike and Zoho among them, and we ended those partnerships to build replacements. That's the background to everything on this page. Salesforce is good software. The problem is that renting the system your company runs on has a cost structure that only moves in one direction.
Where we don't guess, we cite. The cost and timeline figures we publish for enterprise implementations are sourced page by page. Where the public data is thin, we say it's thin.
Your own arithmetic
What the renewal actually commits you to
Work these out for your own org before you compare it to anything. Every one of them is already sitting in your invoices and your org.
Seats, by edition, at next year's headcount
The edition ladder is where the real increases live. The capability you need next usually sits one tier up, and buying another add on doesn't get you there. Price the tier you'll actually be on, at the headcount you expect to have.
Everyone who isn't an employee
Customers, subcontractors, field crews and partners who need to see their own data cost extra, priced by member or by login. That's why so many companies with a serious CRM still email status updates as attachments.
The administrator and the consultants
A full time admin, or the fraction of several people, plus whatever you spend on outside help every time something structural changes. That cost is permanent. It runs as long as the platform does, so it belongs in the comparison.
The packages that became load bearing
Managed packages from the marketplace each carry their own subscription, their own renewal and their own upgrade risk. Count them. Most companies are surprised by how many there are, and by how much of the critical workflow now can't run without them.
The renewal window
What to settle before you sign again
None of this needs us, and all of it is worth doing whether you leave or stay.
Check the notice period
Enterprise agreements commonly auto renew unless written notice lands a set number of days ahead. Work backwards from that notice deadline. It's usually already inside your planning window.
Measure what you actually use
Run the reports on your own org. Look for objects with recent writes, fields nobody has opened in a year, flows firing into nothing, and packages nobody remembers installing. The gap between what the platform can do and what your team touches is almost always the whole argument.
Read the sourced implementation numbers
We publish average enterprise implementation cost and timeline by company headcount, with every figure cited. It's the most credible thing on this site precisely because it doesn't flatter us. Take it to your own leadership and it holds up.
Name the one workflow that hurts most
Nobody replaces an enterprise CRM in one move, and we wouldn't propose it. So the first question is which single part is costing you most right now. That's what gets built first, while everything else keeps running.
Leaving
What leaving actually involves
Salesforce is good at letting data out. Accounts, contacts, opportunities, activities, custom objects, notes, files and history come across through the API against a field by field mapping you approve before anything moves.
The migration doubles as the audit, and clients tell us that's the part they valued most. Fields nobody has written to in years, automations firing into nothing, duplicate records, three competing definitions of the same status. It all surfaces at once, and you decide what earns a place in the new system and what was only ever carried forward out of habit.
The replacement runs on accounts in your name (the repository, the database, the hosting, the email domain). We're invited in as administrators and you can remove us. Adding a person to the system stops being a purchasing decision, and there's no renewal at the end of the year because there's no vendor to renew with.
One time we said no to a renewal
$125,000 a year in licensing, replaced in six weeks for $85,000.
Another client was paying $125,000 a year to rent software that still needed workarounds. Six weeks and $85,000 later they owned the replacement outright, with no seat count and no renewal.
The honest case against
When staying is the right call
A large sales organization with the headcount to justify a dedicated administrator, deep in a platform specific ecosystem, running an industry cloud with real regulatory weight behind it, is usually better off fixing the configuration than leaving. We'll tell you that on the call. A bad replacement project is worse than an expensive renewal.
If you're mid implementation and it's going badly, that's a different conversation and a much more common one. Stopping early is often cheaper than finishing. Not always, though, and sometimes the honest answer is to finish the thing and fix it afterward.
Questions
What people ask before leaving Salesforce
Answered in full, including the cost and timing questions, which get a process rather than a figure.
Can a custom system really cover what we use Salesforce for today?
Not feature for feature, and it isn't trying to. Salesforce carries thousands of capabilities because it covers every industry at once, and your company uses a small fraction of them. We map your org first, so the comparison runs against what your team actually touches.
What happens to our administrator?
They usually get a lot more useful. The work stops being platform maintenance and becomes ownership of the system itself. What it should do next, what the data means, how the business actually wants to run. They know your process better than any consultant does, and that knowledge doesn't leave with the platform.
We have a heavily customized org. Does that make this harder or easier?
Easier to justify, and no harder to execute. Heavy customization means the standard product never fit you, which is the whole argument for building around your process. It also means your rules are written down somewhere, in flows, validation rules and code, and that's exactly what gets read during the mapping.
How long does an enterprise platform take to implement in the first place?
Longer than the sales cycle suggests, and it isn't usable until it's configured. The sourced ranges by company size live on a separate page, with every source cited so you can check them yourself.
How does the cost of replacing Salesforce compare with what we renew for?
It depends on how many clouds are genuinely in use, how much custom logic has to be rebuilt, and how many people need access, so we don't publish a rate card for our own work. We do publish sourced ranges for what a Salesforce implementation costs by company size, and that's a fair place to start. After a strategy call you get a written scope set against your renewal number.
Where is Salesforce genuinely the right platform?
Where the ecosystem is doing real work for you. If your industry has mature managed packages that encode regulation, or your auditors, insurers, or largest customers expect a named platform on the other end of an integration, that's value you'd have to reproduce yourself. Same goes for a company with a capable in-house admin team who have configured it well and aren't fighting it. We've integrated with Salesforce. We were never a partner, so there's nothing in it for us either way.
What actually comes out of Salesforce, and what has to be rebuilt?
Standard and custom objects, fields, and record history export through the Data Loader and the API, and they come out well. The logic doesn't. Flows, Apex classes and triggers, validation rules, page layouts, sharing rules, every report and dashboard, all of that is configuration. It gets read for the rule it encodes and rebuilt as tested code. Record ids matter here too, because Salesforce ids are what keep related records connected, and an export without them is a pile of lists.
What happens to our AppExchange packages?
Each one becomes its own decision, and some of them are the strongest argument for staying. A package doing genuinely specialized work (a regulatory filing engine, an industry-specific calculation) is worth replacing only if there's a real alternative or the logic is well understood. A package that turned out to be a form builder, a document generator, or a reporting layer is usually the cheapest thing on the list, and it's often a line on the bill you've stopped noticing.
From the knowledge base
Guides for people weighing up Salesforce
Reference pages, not sales pages. Each one is useful even if you decide to stay exactly where you are.
How to tell whether your business actually needs custom software
Seven tests you can run against your own operation this week. Most businesses that run them find a configuration problem, not a build.
Salesforce and NetSuite implementation cost and timeline, by company size
A sourced comparison table at 50, 100, 250, 500, and 1,000 employees. Every figure is cited and dated, and the thin-data cells say so.
Bring your renewal quote
Thirty minutes with your invoice and your seat count in front of you, and you will know whether replacing Salesforce is realistic for your company, including when the honest answer is that it is not.