Enterprise DNA

Instead of Salesforce Emergency Program Management

Stop renting Salesforce. Own your response desk.

We build your internal coordination desk, bring across your exported Salesforce request records and run it for you. Your team keeps control of response decisions and emergency communications.

Salesforce lists Public Sector Service Core at US$275 per user per month, billed annually: US$3,300 per user per year. This is the broader platform price, not a stand-alone Emergency Program Management quote.

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

The bill behind the platform

Price the coordination work you actually need

Salesforce sells a broader Public Sector platform. Compare the applications and services in your contract with the internal records your team needs to manage.

payments

A licence for each user

Service Core lists US$275 per user per month, billed annually. The published price is tied to users.

calendar_month

An annual commitment

The pricing page requires an annual contract. Compare the renewal with the work you intend to keep in Salesforce.

layers

A broader platform

Public Sector brings multiple applications together. Your resource coordination desk is one defined part of that scope.

assignment

Requests and approvals

Salesforce describes a shared view of emergency requests and approvals. These are central records to preserve when mapping a move.

public

A public service portal

Salesforce describes community requests and crisis updates through a portal. Keep that service in scope when deciding what to replace.

settings

Your configured processes

The free desk handles internal records. Enterprise DNA scopes your required interfaces, access controls and connections separately.

Your own coordination desk

Know what was asked for, promised and received

Requests

Every request has a named decision

Track the requested quantity, needed date and owner. Imported approvals remain source history until your team records a local decision.

  • check Requests linked to their programme and location
  • check Human approval with a recorded reason
  • check Original export status kept beside the new record
  • check Approved demand compared with reservations and receipts

Resources

Stop promising the same stock twice

Reservations check available quantities, matching units and the recorded inspection date before they are accepted.

  • check Declared stock, reserved stock and receipts shown together
  • check Requests cannot reserve more than they still need
  • check Overdue inspections block a new reservation
  • check Compare outstanding demand with inspected stock across locations

Evidence

Find the gaps before the next exercise

Check plan references and your chosen review dates, then follow the actions agreed after an exercise.

  • check References for evacuation, notification and medical assistance
  • check Communication, training and testing evidence prompts
  • check Testing dates calculated from the frequency in your plan
  • check Cross-check overdue requests against their owners' open actions

Records

Keep the handover and the reasons

Produce situation records, receipt records and plan review checklists from the same database.

  • check Receipt evidence retained with the quantity and recipient
  • check Programme closure waits for open work to finish
  • check A recorded history of decisions and changes
  • check Your name and colours on read-only reports and documents

Make it yours

Design your own Salesforce Emergency Program Management replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your Salesforce Emergency Program Management 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 Emergency Program Management 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 Emergency Coordination for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Emergency Coordination for Claude Code

Connected to your own database

Which requests still need supplies?

REQ-01

Name
Water for harbour exercise
Program
EX-01
Site
HUB
Quantity
60
Unit
carton
Status
approved
Reserved
20
Received
0
Unallocated
40
Due
2026-10-24

REQ-03

Name
Water for north exercise
Program
EX-02
Site
DEPOT
Quantity
70
Unit
carton
Status
new
Reserved
0
Received
0
Unallocated
70
Due
2026-10-27

REQ-02

Name
Blankets for harbour exercise
Program
EX-01
Site
HUB
Quantity
30
Unit
each
Status
new
Reserved
0
Received
0
Unallocated
30
Due
2026-10-28

Ask it anything

Ten questions this coordination desk answers

These answers come from the demo records today. They are included cross-record checks, not a claim that Salesforce cannot build equivalent custom reports.

chat_bubble Which approved requests still lack resources?
chat_bubble Which requests are past their needed date?
chat_bubble Which resources are reserved but not received?
chat_bubble Which stock has an overdue inspection?
chat_bubble Which sites have incomplete plan evidence?
chat_bubble Which sites missed their own testing interval?
chat_bubble Which exercise actions are overdue and who owns them?
chat_bubble Which imported requests still need a local decision?
chat_bubble Which owners have both overdue requests and open exercise actions?
chat_bubble Which item demand exceeds inspected available stock?

Switching

How to switch from Salesforce Emergency Program Management

A move like this usually depends on agreeing which records, fields, codes and history to bring across, then checking the imported records before you change operating systems.

  1. 1

    Prepare a Salesforce export

    Ask your Salesforce Emergency Program Management administrator to export a Details Only CSV request report. Choose UTF-8 and include stable record IDs and the fields you agree to carry across. Check how programme and location codes will match the new database. Salesforce export options can depend on your account, so check with Salesforce if you cannot produce this report.

  2. 2

    Test the import

    Start with a small copy of the report and use the import's test run before writing records to the database. Map the report headings and any different programme or location labels. The test checks the rows without importing them, so you can correct the mapping and try again before loading the agreed report.

  3. 3

    Review flagged records

    Check the import results and reconcile the row count, stable IDs, original statuses and source rows against Salesforce. Resolve any rows the import does not accept before loading the full report. Imported requests start as new local records, even if Salesforce marked them approved or delivered. Have a responsible person review those records and make any local decisions.

  4. 4

    Run both systems briefly

    For a short, agreed overlap, keep Salesforce as your current record while operators compare the new database with the work they do. Check requests, decisions, reservations, receipts and follow-up actions, and confirm owners know which system to update. Do not treat an imported approval as authority to release supplies. Keep established emergency communications and response systems in place.

  5. 5

    Switch off Salesforce

    Once your responsible team has checked the records and agreed the new coordination process is ready, stop using Salesforce Emergency Program Management for the work you have moved. The replacement covers internal coordination records, not alerts, dispatch, evacuation or emergency communications. Keep those established systems in place, and do not make a wider operational change without the responsible team’s review.

construction

Where the real effort goes

The real work is usually mapping your own fields, programme and location codes, and approval rules, then deciding how much closed history to bring. Attachments, permissions, message history, maps and delivery records are separate migration work. If you have Enterprise DNA install and run the system, Enterprise DNA handles the record mapping and migration as part of the agreed setup.

Not ready for a call?

Get your Salesforce Emergency Program Management switch plan by email

We will send you the step-by-step plan for moving your business off Salesforce Emergency Program Management, 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

Do it yourself, customise it, or have us run it

Open source

Do it yourself

Free and open source

  1. 1 Clone the repo and run npm install, npm test and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Review the operating scope and the fictional exercise records
  4. 4 Map your Salesforce report headings, do a test import and reconcile the records
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your request categories, approval rules and review process
  • check Your Salesforce request records mapped and reconciled
  • check A web front end or different technology where your operation needs it
  • check Your required reports, documents and service connections
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a monthly retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Access controls, backups and ongoing operation scoped with you
  • check Agreed connections to the rest of your organisation
  • check Your team retains authority over response decisions and procedures
Book a call with Sam

Questions

Instead of Salesforce Emergency Program Management, answered

Does this replace our entire emergency response platform? expand_more

The free version covers internal exercise and coordination records: requests, decisions, supply reservations, receipts and follow-up. It does not issue alerts, dispatch services, direct evacuation or replace your emergency communications. Enterprise DNA scopes the wider system with your responsible team before any operational change.

What comes across from Salesforce? expand_more

Export a Details Only CSV request report with stable record IDs and the agreed fields. Map its headings and match programme and location codes, then do a test import. The source status and original row are kept. Attachments, permissions, message history, maps and delivery records are separate migration work.

Can an imported approval release supplies? expand_more

No. Imported requests start as new local records. A person records the approval and its reason before a reservation is accepted. A receipt needs evidence, and received quantities cannot be cancelled as though they never arrived.

Does a complete checklist mean we comply with the law? expand_more

No. The checks find missing references and overdue dates. They include prompts based on New Zealand emergency plan duties and Australian model guidance, with sources in the free version. Your responsible professionals assess the plan, local duties and actual conditions. Testing frequency comes from your plan.

What would Enterprise DNA build and run for us? expand_more

We agree the coordination work to replace, map your records, configure your rules and scope the interfaces and connections your team needs. Omni by Enterprise DNA runs that agreed system for one setup fee and then a retainer. Your emergency management team keeps responsibility for response procedures and decisions.

Bring the renewal and a real request

Spend 30 minutes with Sam. Show us your Salesforce contract and how one request moves from intake to receipt. We will identify the coordination work you can own and the services your team needs to keep connected.

Book a call with Sam Get the free version

Emergency Coordination for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Salesforce Emergency Program Management?

Get your version built