Salesforce Add-On Teardown. Built in your org. Owned by you.
Keep Salesforce. Stop renting the add-ons.
If you pay every year for Salesforce add-ons your team barely uses, we find them, rebuild the parts you actually use inside your own org, and hand you the source before your renewal.
Read-only. About a week. Free.
The problem
Where the money goes
Salesforce is the platform. Most of the creep is the tools bolted around it, renewed every year whether anyone needs them or not.
The whole product, a few features
Your team uses the quote template and the one calculator. You pay for the full suite, every seat, every year.
Seats for people who logged in twice
Licenses get assigned at rollout and never come back. Nobody checks who actually used them last quarter.
Renewals that roll on their own
Cutting anything takes a list, a plan and a decision 90 days out. Without that, the renewal signs itself.
How it works
Keep, cut, or rebuild
A Teardown sorts every add-on and seat type into one of three piles, each with the reason and the renewal date it hits.
- Keep
Keep it
Heavily used, compliance-critical, or too small to be worth rebuilding. We tell you to keep it, and why.
- Cut seats
Cut the seats
The tool earns its place, but you're paying for people who don't use it. Trim the seats or drop a tier at renewal.
- Rebuild
Rebuild it in your org
You use a handful of features. We rebuild exactly those inside Salesforce, so you can cancel the add-on at renewal.
Scope
What we rebuild, and what we don't
We rebuild third-party add-ons. Salesforce's own products we right-size, never replace.
What we rebuild
- Third-party quoting, pricing and deal calculators
- Document generation: quotes, letters, printable record views, PDFs
- Dashboards and analytics add-ons, where standard reports plus a component can do the job
- Forms and intake tools that just create or update records
- Data-quality and duplicate-checking tools
- Simple approval, routing and assignment add-ons
- File and PDF processing: reading values out of uploaded documents
- Unused or wrong-tier seats and editions (a cut, not a rebuild)
What we don't rebuild
- Security and compliance products: encryption, event monitoring, audit-trail retention, anything your auditor or regulator names
- E-signature. Its legal evidence trail is the product.
- Payment processing, or anything in PCI scope
- Anything covered by a Business Associate Agreement
- Salesforce licenses and Salesforce's own products. We right-size them; we don't replace them.
- Anything whose contract can't be cut until a later renewal. We plan for that renewal instead.
About contracts. Add-ons are often bundled or locked to multi-year terms. We read your order form with you and plan around your actual renewal date. We're not your lawyers: your legal and procurement teams make the contract call.
Why inside your org
Why build it inside your org
Rebuilds cost less because they use the platform you already pay for, cover only what you use, and go through a disciplined build and review process.
No new vendor, no new login
It's Flow, Apex, Lightning components and reports. Nothing new to buy, host or sign into.
Your admins can see it
It sits in Setup like everything else in your org. Your team can read it, change it and support it.
Your permissions still apply
It respects the profiles, permission sets and sharing you already have. No side door.
You own the source
The code lives in your org and in a git repository you control. No annual fee for it, ever.
Pricing
Pricing
The Teardown is free. Everything after it is a fixed price, quoted against a written feature list.
Step 1
Teardown
Free
About 1 week · no commitment
Find out what you're renting, what you use, and what to do about it before your renewal.
- Read-only review of installed packages, add-on licenses and seat usage
- Covers up to 10 add-ons or managed packages, and all seat types
- You share the order form or renewal date; we read it with you
- Output: a Keep / Cut seats / Rebuild list, each line with the reason and the renewal date it hits
- Access needed: a read-only login that can view Setup and login history
Step 2
Module Rebuild
From $15,000/ module
3 to 8 weeks · fixed price
The features your team actually uses, rebuilt inside your org and handed over before your renewal.
- Quoted after the Teardown as one fixed price per module. Most land between $15,000 and $40,000.
- Scope is a written list of the features you use, agreed before we start. We rebuild that list, not everything the old product could do.
- Moving the records you need out of the old add-on goes on the list too, so nothing gets stranded
- We build from your team's requirements, not by copying the product
- Built in a sandbox, through an independent review gate, then moved to production with a person on your side approving it
- Finished at least 30 days before your renewal, so you can run both side by side before you cancel
- 60-day fix warranty on the agreed feature list
- You own the source: in your org and in a git repository you control
Optional
Owned-Module Upkeep
$1,500/ month
Per org · month to month · no minimum
Your admins can maintain what we build. Upkeep is there if you'd rather they didn't.
- Covers up to 3 rebuilt modules for one fee
- Salesforce release checks three times a year
- Fixes and small changes
- Month to month, no minimum. No lock-in is the point.
- Included at no extra cost on the Claude-Ready Retainer (from $3,500/month)
- Scoped to modules we rebuilt for you. General admin support lives under Salesforce Optimization & Support.
Our pricing rule: If the rebuild won't cost less than about two years of the license it replaces, counting upkeep if you choose it, we'll tell you to keep the license.
Already on the Claude-Ready Retainer? Upkeep is included. See Claude-Ready Salesforce.
Need broader help with your org? See Salesforce Optimization & Support.
Process
How it works
Teardown
Read-only review of your add-ons, seats and renewal dates. You get the Keep / Cut seats / Rebuild list in about a week.
Fixed quote, written feature list
For each rebuild, the features your team uses, written down and agreed, with one fixed price. If it fails the pricing rule, we say so.
Build, review, you approve
Built in a sandbox and passed through an independent review gate. The move to production is approved by a person on your side.
Side by side, then cancel
The rebuild is live at least 30 days before renewal. Run both, confirm it works, then let the add-on lapse.
Fit
Who this is for
- CFOs and finance leads looking hard at the next Salesforce renewal
- Salesforce owners and admins tired of paying for tools nobody opens
- RevOps leaders who want fewer logins and fewer vendors
- Nonprofits and education organizations where every license dollar gets scrutinized
Background
Credentials
- JD
- AIGP
- CIPP/US (IAPP)
- Salesforce Consulting Partner
- Anthropic Claude Partner Network
Questions
FAQ
Is this leaving Salesforce?
No. The opposite. Salesforce stays the platform, and the rebuilt features live inside it. We're a Salesforce Consulting Partner. The goal is a right-sized org: the platform you rely on, without the add-ons you don't.
What do you need for the Teardown?
A read-only login that can view Setup and login history, your installed-package list, and the order form or renewal date for each add-on. We never change anything in your org during a Teardown.
What if we're mid-contract?
Then we plan for the renewal you actually have. Add-ons are often bundled or locked to multi-year terms. We read your order form with you and plan around your actual renewal date. We're not your lawyers: your legal and procurement teams make the contract call.
Who maintains it after you build it?
Your own admins can. It's standard Flow, Apex, components and reports, documented and in your org. If you'd rather not, Owned-Module Upkeep covers up to 3 modules for $1,500/month, month to month.
What if Salesforce changes something?
Native features follow Salesforce's own release cycle, so there's no outside product to fall out of step. Upkeep includes release checks three times a year. Without Upkeep, your admins test it the same way they test the rest of the org.
Do we get the code?
Yes. It lives in your org and in a git repository you control. No license key, no annual fee, nothing that stops working if we part ways.
What if the rebuild isn't worth it?
Then we tell you. If the rebuild won't cost less than about two years of the license it replaces, counting upkeep if you choose it, we'll tell you to keep the license. A Keep with a good reason is a fine outcome for a Teardown.
Can you rebuild e-signature, encryption or payments?
No. E-signature's legal evidence trail is the product. Encryption, event monitoring and audit retention are things auditors and regulators name. Payments bring PCI scope. Those stay with the specialists, and we'll say so in your Teardown.