Free tool, no signup, no org connection
Find out what your CPQ change breaks before you make it.
Every pricing rule, automation and integration you have added to Salesforce CPQ over the years is wired to something else. Submit a list of them and get back a map of what depends on what, and the count of components sitting on your quote-to-cash path.
Takes about two minutes. Your file is read in your browser, we never connect to your org, and we keep the component names you submit so we can count how many people ran it.
Dependency snapshot, sample org: 18 components, 11 objects
12 of 18 components touch quote-to-cash.
- SBQQ__Quote__c10 direct, 14 downstream
- SBQQ__QuoteLine__c6 direct, 14 downstream
- Product24 direct, 10 downstream
- Opportunity1 direct, 6 downstream
- Order2 direct, 5 downstream
3 integrations and 4 pricing rules sit on the path. Longest chain: 6 components.
What an unmapped dependency costs
Not the migration project. The migration project has a plan. What costs is the thing nobody put on the plan, because nobody knew it was attached.
It breaks after go-live, not during
A buyer who had already switched reported, four months after cutover, that journal entries could not be posted to their accounting system without timing out, and that there was still no resolution. The integration was not part of the cutover checklist, which is exactly why it survived it.
It is not only migrations
A reviewer of the successor product describes small adjustments to pricing logic or product rules having unintended impacts across the billing chain, and every change needing rigorous testing. That is a Tuesday, not a project.
The inventory is the first real step
Someone who came out the other side of this migration told the person starting it to inventory what depends on the current state of CPQ first: automations, custom fields, pricing, integrations. Doing that by hand is where the week goes.
Honest about the evidence: two of the three sources above are reviews on venues where reviews are often invited by the vendor, one of them explicitly incentivised, and we have not spoken to any of the authors. People complaining about a product is also evidence that a lot of people use it. This is why we think the problem is worth testing, not proof that it is.
What the snapshot gives you
- The headline count: how many of your automations, pricing rules and integrations sit on the quote-to-cash path.
- A blast radius per object: change this one thing, and here is what is directly attached plus everything downstream of it.
- Your longest dependency chain, named component by component, because that is the one nobody holds in their head.
- The integrations on the path, which are the dependencies that fail outside Salesforce where you will not see the error.
- A plain count of components that declared no dependencies at all, marked as unmapped rather than quietly counted as safe.
And what it does not give you
- A connection to your org. The snapshot reads a file you submit. It does not authenticate to Salesforce, does not call any API and is not an installed package.
- A fix. It shows you the radius of a change. It does not rewrite a rule, stage a deployment or resolve anything, and it will not tell you what to do about it.
- Dependencies your export did not carry. It maps what your file says. If a reference is missing from the export, it is missing from the map, and the tool says how many rows arrived that way.
- A product. Blast Radius is not built. This page exists to find out whether the problem is worth building for.
How Blast Radius would work
01
You submit a snapshot
The same export you can run today: your CPQ objects, pricing rules, automations and integrations, out of Setup and Object Manager or into the template.
02
It maps what depends on what
The map and the counts on this page, which is the whole of what exists today and is free.
03
You re-submit before a change
Ahead of a pricing-rule edit or a migration step, the new snapshot is diffed against the last one and the radius of the change is flagged before it is deployed.
04
It keeps watching
Every change gets checked against the map, so the surprise arrives before the deployment rather than four months after it.
Steps 3 and 4 describe the product we would build, at $299 a month for the whole organisation, flat, not per seat. Today only step 1 and step 2 exist, and they are free. Nothing here reads or writes anything inside your Salesforce org, in either the free tool or the product as described.
Why we think this is the sharp thing
We are not going to tell you nobody else touches this. Salesforce names partners who automate parts of a CPQ migration, and one of them, Prodly, publishes its own tiered pricing at $1,250, $2,084 and $4,167 a month, though buying still routes through a contact form. Two others named alongside it, Forsys RevRamp and IdeaHelix, publish no price at all. Migration tooling exists and we would rather you heard that from us.
What this argues is narrower. A migration tool is bought for a project with a start and an end. The thing we think is missing is a standing answer to one question, asked on an ordinary Tuesday by someone who has not decided anything: if I change this, what else is in the path.
There is also no forced migration deadline. Salesforce's own end-of-life page says so, and we read it twice on two separate fetches to be sure, because urgency is the easiest thing for a page like this to invent. You are not late. That is precisely why an ongoing check is a different purchase from a migration project.
On price: Salesforce Revenue Cloud lists $150 and $200 per user per month, and those are add-on prices that require a Sales Cloud, Service Cloud or CRM licence underneath, not a standalone entry price. Blast Radius would be $299 a month for your whole organisation, flat, however many people look at it. Per seat is the cost shape this corpus complains about, and we are not going to reproduce it.
What people said, in their own words
These are not our customers and not testimonials. They are public posts by people doing this work, quoted verbatim, found while researching whether this problem is real. Nobody was asked to say any of it and no usernames are reproduced. Where a venue invites or pays for reviews, it says so under the quote.
“you need to inventory what depends on the current state of CPQ: automations, custom fields, pricing, integrations”
“Technical Fragility: Small adjustments to pricing logic or product rules can have “unintended impacts” across the entire billing chain, demanding rigorous testing for every change.”
“Support is very present but largely unhelpful ... journal entries can’t even be posted to Netsuite without timing out because of volume ... 4 months since cutover and there has not been a resolution.”
Who is behind this
Dario Verghi, working alone at LeanAI Studio. I am not a Salesforce architect and I have never run a CPQ migration, so I am not going to tell you I know your org.
What I do is run a small studio that tests one idea at a time in the open. I read public forum threads and reviews from people moving off Salesforce CPQ, found the same complaint about unmapped dependencies in more than one venue, and wrote down in advance what result would make me build this and what result would make me drop it. The bar was set before the first message went out and it is not moving now.
If this test fails I will say so on this page rather than quietly leaving it up. You can write to me directly at dario@leanaistudio.com.
Straight answers
- Can I buy this today?
- No. The product does not exist yet. The Dependency Snapshot on this page is the whole of what is built, and the $299 a month is the price it would carry if it gets built.
- Do you connect to my Salesforce org?
- No, and not in the product as described either. There is no OAuth, no connected app, no AppExchange listing and no API call. You submit a file, we read the file. That is a deliberate design choice and it is why you can run this without asking anyone for permission.
- Do I have to sign up?
- No. There is no account, no email field and no cookie in the way. Paste or upload, press the button, and the map is on screen.
- What do you keep when I use it?
- The component names, kinds and objects in the file you submitted, the counts the tool derived, and the reference in the link if you arrived from a message we sent. Not your quotes, prices, customers or amounts, because we never ask for a file that carries them. Not your IP address, not a fingerprint, not your email unless you type it into the waitlist form.
- What if my export does not have a dependencies column?
- You get a map of what you did give us, and the tool tells you how many rows arrived with nothing declared instead of counting them as safe. A partial file is still worth mapping; a partial file described as complete is not.
- Is there a deadline to move off CPQ?
- Not one Salesforce has set. Their end-of-life page states there is no forced migration deadline, read twice on two separate days. Anyone telling you a clock is running should show you where it says so.
- What would you actually build first?
- The re-submit and diff: the same snapshot, taken again before a change, with the difference and its radius flagged before deployment. Everything else waits, and if this test does not clear the bar, none of it gets built.