Distribution Engine pricing, features and alternatives

The short answer

Buy Distribution Engine if Salesforce is where your records live, standard assignment rules no longer handle your round robins, capacity limits or rep availability, and you route more than leads: support cases and custom objects are in scope. G2 reviewers praise ease of setup and management, and above all fair distribution, which is the thing round-robin teams argue about most.

Skip it if routing has to happen before a record exists. Instant meeting booking off a web form is a different product, and a scheduling-first router such as Chili Piper owns that moment. Skip it too if your CRM is not Salesforce, or if native rules and Salesforce Flow already handle your assignment without an admin complaining about it.

Where Distribution Engine fits

Distribution Engine, built by NC Squared and now trading under the Distribution Engine name, is a routing app that runs natively inside Salesforce. That word native is the whole positioning. Routing logic and data stay in your org, which means your security review covers a managed package and its permissions rather than an external service receiving lead data. For an ops team that has spent a quarter getting a data processing agreement past legal for another vendor, that difference is worth real money, and it is the reason Salesforce-centred teams shortlist this over a platform that routes outside the CRM.

The fit test is whether your assignment rules have genuinely outgrown what Salesforce does for free. Native assignment rules handle a simple territory or source split perfectly well. They start failing when you need a round robin that respects capacity limits, skips a rep who is out, honours time zones, and does the same for support cases on a different object. That is the gap Distribution Engine is built for, and if you cannot describe your rules in those terms yet, buy nothing and write the rules down first. Our lead routing rules template and rules of engagement template exist for that step, because a tool configured from an unwritten policy produces an argument rather than a routing system.

Fairness is the feature reviewers keep returning to, and it is a political capability rather than a technical one. Several G2 reviews say the product ensures equal opportunities across reps, which matters because the real complaint in a round-robin team is never the algorithm: it is the suspicion that someone is getting the good leads. Ask what audit trail shows why a record went to a specific rep, then test it. A routing decision you can explain to the rep who did not get the lead is worth more than a routing decision that was marginally more optimal.

The limitation is structural and the source material names it plainly: because it lives entirely inside Salesforce, it will not help if routing needs to happen before a record exists. A prospect filling in a form and expecting a calendar to appear is a pre-record moment. Distribution Engine acts on records already in the org. Map where each routing decision happens in your funnel before you choose, because the honest answer for many teams is that they need both a scheduling-first tool at the form and a rules engine inside the CRM, and the budget conversation changes once you say that out loud.

One more thing to settle early: who owns the configuration. Routing rules are policy expressed as software, so they change when territories change, when someone goes on leave, and when a new segment appears. A Salesforce admin or RevOps owner needs this in their job description. Keep the rules mirroring your territory planning so ownership stays consistent across the CRM, and treat the licence as the cheaper half of the cost. Distribution Engine sits in our lead routing software catalogue alongside the platforms that take the opposite approach.

Distribution Engine pricing

Distribution Engine publishes its prices, which already separates it from most of this category. The rates verified in our September 2026 check are Starter at $20, Advanced at $35 and Unlimited at $55 per user per month billed annually, with a minimum order of five licences. Booking Engine, its separate scheduling product, starts at $10 per user per month, and Premier Support adds 20% to any plan. The detail that decides your bill is what a user means here: pricing is per user receiving routed work, so count the reps and support agents sitting in queues, not the admins who build the rules.

Plans and list rates

Starter

$20 per user per month, billed annually, minimum five licences. The floor contract is therefore 5 x $20 x 12 = $1,200 a year.

Advanced

$35 per user per month, billed annually, minimum five licences. This is the tier most teams with capacity and availability rules land on.

Unlimited

$55 per user per month, billed annually, minimum five licences. Ten routed users costs $55 x 10 x 12 = $6,600 a year.

Booking Engine Starter

$10 per user per month, billed annually. A separate scheduling product, not an add-on to the routing plans, so price it as a second line item.

Premier Support

Adds 20% to any plan. It is a surcharge on the subscription rather than a fixed fee, so it grows with your seat count.

What ten routed users cost

Ten routed users on Advanced is $35 x 10 x 12 = $4,200 a year, or $5,040 with Premier Support. The same ten users on Unlimited is $6,600, so the step up from Advanced costs $2,400 a year. That is the number to put against a named list of features rather than against a tier name: $20 a seat a month reads as a rounding error until you multiply it, and $2,400 is a figure a finance team will ask you to justify.

The five-licence minimum sets the floor. The smallest contract available is 5 x $20 x 12 = $1,200 a year on Starter, which means a three-person team pays for five seats. That is cheap in absolute terms and still worth knowing, because it changes the comparison for a three-person team: at that size the honest alternative is native Salesforce assignment rules, not a competing vendor.

If you also want scheduling, Booking Engine is priced separately at $10 per user per month, so ten users is $10 x 10 x 12 = $1,200 a year on top of the routing plan. Add it deliberately rather than assuming routing and booking come together, and remember Premier Support's 20% applies to the subscription it is attached to.

The comparison that matters is not against another vendor. It is against the cost of maintaining custom Flow or Apex routing yourself. Admin hours spent debugging homegrown assignment logic are a real cost even though they never appear on an invoice, and they arrive at the worst moments: a reorganization, a quarter close, a rep leaving. Count the hours your team spent on assignment bugs last quarter, cost them at a loaded rate, and put that next to $4,200. Our sales tool business case template is where to write that comparison down.

This is one of the few routing products you can price without a sales call, so use that. Confirm three things before you order: which objects are included in your quote and what adding cases or custom objects costs, whether every user in a queue needs a licence or only those receiving routed work, and whether Premier Support is necessary for your rule complexity. Then read how we review software for what we verify and what we do not.

What Distribution Engine gives up

You give up pre-record routing entirely. Distribution Engine acts on records inside Salesforce, so the moment between a prospect submitting a form and a calendar appearing belongs to another tool. If speed to meeting is the metric your board watches, this product improves the hour after the handoff rather than the thirty seconds before it.

You give up CRM portability. It is built for Salesforce environments, so a migration to another CRM means replacing the routing layer as well. That is a reasonable trade for a committed Salesforce estate and an expensive one for a company mid-way through evaluating a change of platform.

You give up the simplicity of doing nothing. If native assignment rules or Flow already handle your routing without an admin complaining, adding a managed package adds a security review, a package upgrade cycle and another thing to document. The source material says this plainly, and it is the recommendation most vendors will not make.

You give up lead-to-account matching as the headline capability. Reviewers praise fair distribution, and that is what this product is known for. If your harder problem is reliably matching an inbound lead to an existing account and owner before assignment, LeanData is the usual comparison for exactly that, and you should decide which of the two problems is yours before you shortlist either.

You give up a licence-free scheduling layer. Booking Engine is a separate product at $10 per user per month rather than a feature of the routing plans, so a team that wants both is signing two lines. Price them together from the start, because discovering the second line after the business case is approved is how a $4,200 purchase becomes a $5,400 one.

How Distribution Engine compares

This shortlist splits on where the routing decision happens and what you are willing to pay for it. Distribution Engine and LeanData both live in and around Salesforce and compete on rule depth, with one publishing rates and the other quoting. Chili Piper competes at the form, where instant scheduling matters more than queue fairness, and it prices in annual bundles rather than per seat. Lead Assign is the other Salesforce-centred assignment option with published figures. Salesforce Flow is the do-it-yourself route, free with Sales Cloud and paid for in admin hours. Every published figure traces to our September 2026 pricing check.

What to test in a Distribution Engine trial

Test in a Salesforce sandbox with realistic lead volume before any rollout, and run the trial against your written rules rather than against a demo scenario. The steps below each produce an answer you can show a sales leader, which matters more here than in most purchases: routing changes who gets paid, so the rollout needs evidence rather than assurances.

1. Install the managed package in a sandbox and have your Salesforce admin and security reviewer read its permissions. Do this first, because a package that fails security review ends the evaluation regardless of the routing quality.
2. Run a full week of real inbound volume through your rules and check whether distribution matched your policy when reps were out, at capacity or in another time zone. Those three conditions are where native rules fail and where this product has to earn its price.
3. Test lead-to-account matching and conversion on the way in: how an incoming lead is matched to an existing account and owner, and what happens with duplicates. If matching is your harder problem, you have learned you are shortlisting the wrong tool.
4. Route a second object, usually support cases, and confirm it is covered by your quote. Adding objects after the order form is a common cost surprise, so ask what cases or custom objects cost before signing.
5. Pull the audit trail for ten routed records and read it as if you were the rep who did not get the lead. If it does not explain the decision in plain terms, fairness will stay an argument no matter how good the algorithm is.
6. Count the licences you need by listing only the users receiving routed work, then price Starter, Advanced and Unlimited at that count: $1,200 is the floor on Starter, $4,200 is ten users on Advanced, and $6,600 is ten on Unlimited. Decide whether Premier Support's 20% is warranted by your rule complexity.

Distribution Engine questions buyers ask

What is Distribution Engine?

Distribution Engine is a routing application built natively on Salesforce by NC Squared. It assigns leads, cases, and other records to the right people based on rules you set.

How much does Distribution Engine cost?

Distribution Engine costs $20 (Starter), $35 (Advanced) or $55 (Unlimited) per user per month, billed annually, with a 5-license minimum. Premier Support adds 20%.

How does Distribution Engine compare with Chili Piper?

Both replace manual assignment with rules. The main difference is where the data lives and what you route: Distribution Engine works inside Salesforce, while Chili Piper focuses on form conversion and instant scheduling.

Is Distribution Engine easy to set up?

G2 reviewers highlight ease of setup and management. Complex rule sets still need careful testing before going live.

Is there a free trial for Distribution Engine?

Check with Distribution Engine (the company formerly branded NC Squared) about trial options, and test in a Salesforce sandbox with realistic lead volume before rollout.

Related

If Distribution Engine is on your shortlist, the comparison depends on which problem is harder: LeanData where lead-to-account matching decides it, Chili Piper where speed to meeting is the metric, and RevenueHero where inbound scheduling is priced per user. The full field sits in our lead routing software directory, with the adjacent CRM software shelf if Salesforce itself is still in question, and our Chili Piper against LeanData comparison explains the scheduling-first versus matching-first split in more detail.

Distribution Engine sits in our Lead Routing Software directory.