Enterprise DNA

Instead of Salesforce Sales Planning

Stop renting Salesforce Sales Planning. Own your territory and quota plan.

We build your version around who covers each account, how much work each rep can carry and how you agree quotas. We bring your Salesforce account records across, map the planning rules and run your version for you.

Salesforce lists Sales Planning at US$75 per user per month, billed annually. That is US$900 per licensed user per year.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

You pay for the planning system around your account records

Salesforce sells Sales Planning on an annual contract. The licence covers people using it and people receiving its planning output. The free base here concentrates on account allocations, workload and quota decisions.

users

A licensed user

The published price is US$75 per user per month, billed annually.

clipboard

Planning output

The licensing wording also covers a person receiving a territory or quota assignment.

layers

Hierarchy and segments

Hierarchy management and segment design are listed capabilities.

map

Territory planning

Territory carving and optimisation sit in the planning product.

target

Targets and quotas

Target allocation and quota refinement are included in the feature list.

calendar

An annual commitment

Salesforce also offers Sales Planning through broader product bundles. Compare the contract you hold with the planning work you need.

Your owned version

Start with the decisions your sales team makes each week

Coverage

Every account has a place in the plan

See uncovered accounts and the reason for each assignment. Keep alternative plans separate while you compare them.

  • check One territory assignment per account in each plan
  • check Country and segment carried from your account records
  • check A recorded reason when an account moves
  • check A comparison showing which accounts change hands

Workload

Balance the work across each rep’s territories

Set the effort your accounts need and the capacity each rep can carry. Review the total before approving the plan.

  • check Your own account workload scale
  • check Combined workload across a rep’s territories
  • check Overloads visible before the plan is signed off
  • check Separate plans for separate currencies

Quotas

Close the gap between the target and the allocations

Keep the plan target and territory quotas together. Approval checks the sum and preserves the reviewed decision.

  • check An exact check of allocated quotas against the target
  • check A second reviewer and a supporting evidence reference
  • check A frozen copy of approved assignments and quotas
  • check A new scenario for later changes to the plan

Your weekly review

Keep the reasons beside the numbers

Ask about late follow-ups, missing review evidence and the decisions behind the plan. Produce the paperwork in your business’s name.

  • check Account and rep accuracy-review reminders
  • check Retention-purpose checks with cited guidance
  • check Branded territory plans and approval records
  • check Questions that combine your own workload rules and assignment reasons

Make it yours

Design your own Salesforce Sales Planning replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Salesforce Sales Planning. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Salesforce Sales Planning replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Salesforce Sales Planning data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Sales Planning for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Sales Planning for Claude Code

Connected to your own database

Which accounts still need someone to cover them?

DEMO004

Account
Coastal Distribution
Workload
1

DEMO001

Account
Harbour Components
Territory
NORTH
Rep
Aroha North
Workload
3

DEMO002

Account
Northern Supply
Territory
NORTH
Rep
Aroha North
Workload
3

DEMO003

Account
Southern Precision
Territory
SOUTH
Rep
Ben South
Workload
2

Ask it anything

Ten questions this build answers today

These questions run against the included fictional records. They demonstrate the free base, without claiming Salesforce cannot answer them.

chat_bubble Which accounts have no territory in this plan?
chat_bubble Who is overloaded across more than one territory?
chat_bubble How much of the target has no quota allocation?
chat_bubble Which account moves between these two scenarios?
chat_bubble Which account review dates are overdue?
chat_bubble Which rep records lack a retention purpose?
chat_bubble What planning follow-ups are late?
chat_bubble What exactly did the second reviewer approve?
chat_bubble Who changed an allocation and why?
chat_bubble What needs a decision in Monday’s planning meeting?

Switching

How to switch from Salesforce Sales Planning

A move usually involves exporting account records, mapping your planning rules and chosen history, then checking the new database alongside Salesforce before you cut over.

  1. 1

    Export your account records

    Export Account records through Salesforce Data Export, then extract the account data for import. Include the fields you need, including custom fields. The import preserves source columns, but it does not bring over Sales Planning scenarios, hierarchy rules, quotas, permissions, calculated fields or attachments. Check with Salesforce if you are unsure which records or fields your account can export.

  2. 2

    Load the account data

    Load the account export into the new database using the supplied import process. Run its preview first to check the proposed changes without applying them. Confirm the currency choice before the live import. Rows with a currency field keep that currency, while rows without one use your Salesforce organisation's default currency. Keep the source export secure because it may contain personal information.

  3. 3

    Review the import results

    Check what the preview says would change, then inspect the imported accounts. New accounts start at one workload unit and need a review. If source values change, their accuracy review is cleared. OwnerId is retained as evidence, not converted into a rep assignment, so map owners and your territory, quota, hierarchy and scenario rules separately before relying on a plan.

  4. 4

    Run both systems side by side

    Keep using Salesforce Sales Planning for a short period while you check the new database against it. Reconcile account assignments, workload assumptions, quota totals and approval records against Salesforce and your agreed rules. Resolve differences before treating the new database as authoritative. Keep Salesforce available during this check so you can verify the source and continue your existing process.

  5. 5

    Switch off Salesforce Sales Planning

    Once your checks are complete and your team is ready, stop planning in Salesforce Sales Planning and use the new database and Claude Code for the agreed process. Keep any Salesforce records or exports you still need according to your retention policy. The account import does not carry over saved planning scenarios, hierarchy rules, quotas, permissions, calculated fields or attachments.

construction

Where the real effort goes

The import itself is only part of the work. Most effort goes into mapping your fields, territory and hierarchy rules, quotas, workload assumptions and approval process, then checking them. You also need to decide which history to bring, since Salesforce planning scenarios do not import automatically. If Enterprise DNA runs your version, it handles the agreed migration, including bringing across records and mapping rules.

Not ready for a call?

Get your Salesforce Sales Planning switch plan by email

We will send you the step-by-step plan for moving your business off Salesforce Sales Planning, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose who builds and operates your version

Open source

Do it yourself

Free, MIT licence

  1. 1 Clone the repo and install its dependencies
  2. 2 Run npm run demo and inspect the fictional planning records
  3. 3 Open it in Claude Code, Codex, OpenCode or Cursor
  4. 4 Preview your Salesforce Account export, then map and check your planning rules
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your segments, workload rules, quotas and review policy
  • check Your Salesforce account records and reviewed planning history brought across
  • check A web front end and agreed connections where your team needs them
  • check A different technical foundation when it fits your business
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Your sales plans alongside the rest of your business
  • check Agreed account updates and reporting connections built for your team
  • check Ongoing changes, backups and operational support
Talk about your sales plan

Questions

Instead of Salesforce Sales Planning, answered

What does Salesforce Sales Planning cost? expand_more

The published standalone price is US$75 per user per month on an annual contract, or US$900 per user per year. Your bundle and contract determine what you actually pay.

Does our existing Salesforce plan come across automatically? expand_more

The free version imports account records and keeps their original fields. Territories, quotas, hierarchy rules and saved planning scenarios need separate mapping and checking. Enterprise DNA handles the agreed migration as part of your version.

Can it handle the way we balance accounts? expand_more

The free version uses workload units you choose, combines them across each rep’s territories and checks quotas against the target. We build your own rules, required maps, screens and connections into the agreed version.

Can someone change a plan after it is approved? expand_more

The free version keeps a frozen copy of the approved allocations, quotas and workload. Later changes use a new scenario. For shared operation we set up access, backup and approval procedures around your team.

What do we pay Enterprise DNA for? expand_more

One setup fee, then a retainer for your agreed build and ongoing operation. We bring across the records, map the rules and support your version through Omni by Enterprise DNA. The open-source base is free to use yourself, with separate hosting and coding-assistant costs.

Bring your current sales plan and the bill

Spend 30 minutes with Sam reviewing your account coverage, territory rules and what you pay for planning. We will work through what your version needs, what carries across and how Enterprise DNA would run it.

Book 30 minutes with Sam Get the free version

Sales Planning for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Salesforce Sales Planning?

Get your version built