Instead of DemandFarm
Stop renting DemandFarm. Own your key account planning system.
We build your version around how you grow existing accounts, map the DemandFarm records you want to keep and run it for you. Start with your review process and the commitments your team must deliver.
DemandFarm quotes its packages privately. Bring your annual agreement and we will compare the account-planning work your team actually uses.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
The recurring bill
What your DemandFarm agreement buys
DemandFarm packages account planning around company size and selected capabilities. Its pricing page asks buyers to request a quote. These are six parts of that planning work to compare with your own system.
Coverage across the account
The account heatmap records where products fit across the customer. Your own version keeps confirmed coverage, competitor-held areas and unknowns separate.
Relationship maps
DemandFarm maps the people in an account. Your version keeps their professional role, relationship owner and the evidence behind each assessment.
Growth planning
Growth planning turns account knowledge into work. Keep each play, its success measure, the responsible person and its next deadline together.
Account reviews
DemandFarm offers in-app reviews and exports for offline reviews. Your version prepares the agenda from current actions and saves the position at each review.
Leadership reporting
Portfolio reporting brings accounts into one view. Your version highlights missing decision-maker coverage alongside quiet relationships and overdue actions.
Connections and customisation
DemandFarm offers integrations and customisation in its packages. We scope the connections and working rules your business needs in the version you own.
Your account record
The weekly account review, built around your rules
Relationships
See where the buying group is still unclear
A job title is a starting point. Keep the evidence that explains the role each person plays in the account.
- check Record decision-makers, influencers and unknown roles
- check Assign an internal owner to each relationship
- check Flag contacts with no recorded interaction or a quiet month
- check Show accounts with missed actions and no recorded decision-maker together
Account coverage
Separate a real gap from a guess
Record the product position in each business unit. Keep an estimate distinct from money already earned.
- check Distinguish your service, a competitor, an unserved unit and an unknown
- check Keep the source and date of each assessment
- check Flag evidence that needs a fresh check
- check Keep each planning estimate in its own currency without adding unlike amounts
Follow-through
Give every growth play an owner and an outcome
An account plan is useful when the promised work happens. Bring the play and its next actions into the same review.
- check Define a measurable customer outcome for each play
- check Assign actions with dates and responsible people
- check Keep a play open until its outstanding actions are complete
- check Preserve the outcome of completed actions and the account position at review time
Your operating rules
Keep the record usable as the team changes
Read the plan, check its evidence and prepare the documents in your own business name.
- check Check contact-purpose, accuracy and retention-review evidence
- check Generate an account growth plan and quarterly review agenda
- check Read who recorded each change and its result
- check Change your fields and review rules with Enterprise DNA as the business changes
Make it yours
Design your own DemandFarm replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from DemandFarm. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your DemandFarm 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 Key Account Planning for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.
Key Account Planning for Claude Code
Connected to your own database
Which accounts have missed actions and no recorded decision-maker?
A-001
- Name
- Harbour Components
- Owner
- Mia
- Review status
- overdue
- Decision makers
- 0
- Quiet contacts
- 2
- Overdue actions
- 1
- Open plays
- 1
- Unknown cells
- 1
A-002
- Name
- Southern Distribution
- Owner
- Tom
- Review status
- scheduled
- Decision makers
- 1
- Quiet contacts
- 0
- Overdue actions
- 0
- Open plays
- 1
- Unknown cells
- 0
A-003
- Name
- Harbour Services
- Owner
- Mia
- Review status
- not scheduled
- Decision makers
- 0
- Quiet contacts
- 0
- Overdue actions
- 0
- Open plays
- 0
- Unknown cells
- 0
| Code | Name | Owner | Review status | Decision makers | Quiet contacts | Overdue actions | Open plays | Unknown cells |
|---|---|---|---|---|---|---|---|---|
| A-001 | Harbour Components | Mia | overdue | 0 | 2 | 1 | 1 | 1 |
| A-002 | Southern Distribution | Tom | scheduled | 1 | 0 | 0 | 1 | 0 |
| A-003 | Harbour Services | Mia | not scheduled | 0 | 0 | 0 | 0 | 0 |
Ask it anything
Ten questions your account records answer
These questions run against the working demonstration. Your own version can join the evidence and review rules that matter to your business.
Switching
How to switch from DemandFarm
A move usually involves exporting account and contact records, mapping any custom planning history, checking the import and comparing both systems before you switch.
- 1
Export your account records
For a Salesforce-native DemandFarm installation, start with Salesforce Account and Contact exports in CSV format. These provide the initial import. DemandFarm’s custom account plans, relationship attributes and coverage objects need separate mapping. If you need to export directly from DemandFarm, use what your account allows, usually CSV or Excel, and check with DemandFarm. A presentation export alone is not a complete migration.
- 2
Test the import first
Load the account and contact exports using the import process, and run a test before committing to the move. This gives you a chance to confirm that records and identifiers line up before the import changes the working database. Keep the original exports private. The import retains the original columns and CSV text to help you reconcile records against their source.
- 3
Review import flags
Check every issue the import reports before relying on the loaded records. Duplicate identifiers, contacts without a matching account and changed source rows can stop an import. Reconcile those records with the originals and correct the mapping or source data before trying again. Exact repeat imports are harmless, but imported contacts remain unverified, and owner IDs stay as IDs until you map them to people.
- 4
Run both systems side by side
Keep DemandFarm available for a short period while you compare real account plans, relationship coverage, actions and review history in the new system. Check that the records your team needs are present and that the agreed fields and rules behave as expected. Resolve gaps against the original records before asking the team to rely on the new system.
- 5
Switch off DemandFarm
Once you have checked the records and your team is ready to work in the new system, switch off DemandFarm. Keep a complete private snapshot of the new database and retain the original exports according to your own data policies. Make sure access, backups and recovery arrangements are agreed before the old service is no longer available.
Where the real effort goes
The real work is usually mapping your fields and account rules, then deciding which history to bring across. Salesforce account and contact records have an initial import path, but custom account plans, relationship attributes, coverage and review history need a reviewed mapping and checks against the originals. Enterprise DNA handles that mapping and checking when you have them install and run your version.
Not ready for a call?
Get your DemandFarm switch plan by email
We will send you the step-by-step plan for moving your business off DemandFarm, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your DemandFarm switch plan is on its way.
Rather talk it through? Book a call arrow_forwardThree ways to own it
Choose how much you want us to handle
Open source
Do it yourself
Free, open source
- 1 Clone the repo and run npm install, npm test and npm run demo
- 2 Open it in Claude Code, Codex, OpenCode or Cursor and ask for the account review
- 3 Test the Salesforce Account and Contact exports using the import guide, then map custom DemandFarm records separately
- 4 Set your branding, review rules and database access before using real records
Built around your business
We customise it
One setup fee, then a retainer for ongoing work
- check Your account tiers, buying roles and review rules
- check Your agreed DemandFarm history mapped and reconciled
- check Your own web front end or a different stack where needed
- check Connections to the systems your account team already uses
Omni by Enterprise DNA
We run it for you
One setup fee, then a retainer
- check Installed with access, backups and ownership agreed
- check Weekly review and quarterly account agendas prepared
- check Record checks and ongoing changes handled for your team
- check Run through Omni by Enterprise DNA beside the rest of your business
Questions
Instead of DemandFarm, answered
What does DemandFarm cost compared with this? expand_more
DemandFarm asks for a quote on its current pricing page. We do not substitute old directory prices for your agreement. The free version has no software licence fee, while hosting and agent subscriptions are separate. Enterprise DNA builds and runs your version for one setup fee, then a retainer.
Can you bring our DemandFarm history across? expand_more
Yes, with the mapping agreed first. For a Salesforce-native installation, the free version brings in account and contact exports. Custom account plans, buying roles, coverage and review history need a separate mapping and checks against the originals. We handle that work for an installed version. A presentation export alone is not a complete migration.
Will this fit how our account managers work? expand_more
The free version covers relationship reviews, account coverage, growth plays, assigned actions and quarterly reviews. We build your version around your fields and rules, including the shared screens, phone access and connections your team needs. Agree those requirements before replacing your existing service.
Can we trust the growth figures and contact checks? expand_more
Potential is a labelled planning estimate, with its source, date and currency kept beside it. Unknown values stay unknown. Contact checks flag missing purpose, stale verification and retention reviews. They support an operator review and do not certify legal compliance or turn a job title into buying authority.
What do we keep if we stop working with you? expand_more
You keep the database, your version and the account history. The working system exports a complete snapshot, including review records and original import files. We agree access, backups and recovery with you when setting it up, so ownership includes a practical way to keep operating.
Bring your account plan and your annual bill
Spend 30 minutes with Sam. We will look at the account reviews your team runs, the history you need to keep and what your own version should do first.
Key Account Planning for Claude Code is free and open source, published by Enterprise DNA.
Done paying for DemandFarm?
Get your version built