Enterprise DNA

Instead of Jambo

Stop renting Jambo. Own your stakeholder engagement system.

We build your version around the communities you work with, the promises you make and the reports you need. Enterprise DNA brings your Jambo records across and runs the system for you.

Jambo Professional starts at US$995 a month for five users. That is US$11,940 over twelve months, before its quoted onboarding fee.

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 buys

The records are yours. The package is rented.

Jambo bundles engagement work into a subscription with quoted higher plans and optional modules. Compare that package with the records and weekly process your team needs.

paid

The starting subscription

Professional starts at US$995 per month and includes five users.

groups

Growing the team

Jambo allows additional users and quotes custom packages as your work grows.

school

Getting started

Every plan has a separate one-time onboarding fee for setup, training and support.

dashboard

Reporting options

Its plan comparison lists Insights analytics and custom dashboards, including add-on availability.

map

Mapping modules

The comparison also lists optional land and map capabilities. Scope the mapping your projects actually need.

lock

Higher plan controls

Enterprise and Ultimate are quoted. The comparison distinguishes their security and access options.

Your own working records

Follow the concern through to the promise and the evidence

Promises

Know what is due and who owns it

Review the next fortnight and the overdue list from the same records. Completion needs evidence, so a status change has something behind it.

  • check Upcoming and overdue commitments by owner
  • check A separate completion evidence record
  • check Issues stay open while linked promises remain outstanding
  • check A workload summary for the weekly team meeting

Relationships

Find the conversations that need attention

Read a stakeholder history before planning the next contact. Your team records the sentiment and context it actually heard.

  • check Contact history with date, channel and recorded notes
  • check High-influence stakeholders with no recent contact
  • check The most recent negative feedback for follow-up
  • check Separate project records to keep consultation histories clear

Evidence

Prepare the review from what happened

Produce consultation reports and commitment follow-up drafts using your business name. Nothing is sent until a person reviews and handles it.

  • check Project scope, communications, issues and commitments together
  • check Private follow-up drafts for outstanding promises
  • check Purpose, retention and notice-evidence review prompts
  • check A dated history of actions recorded by the operator

Ownership

Change the process as your projects change

The free version supplies the records and recurring reviews. Enterprise DNA can build your specific fields, screens and connections around them.

  • check Mapped imports of Jambo contact and engagement reports
  • check A test run that saves nothing
  • check A private archive of your records and operation history
  • check Read-only weekly reports in your business colours

Make it yours

Design your own Jambo replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Stakeholder Engagement for Claude Code

Connected to your own database

Which promises and high-risk issues need attention?

issue

Project
Harbour access consultation
Stakeholder
Harbour Residents Group
Item
Access during works
Owner
Mara
Due_on
2026-10-09

commitment

Project
Harbour access consultation
Stakeholder
Harbour Residents Group
Item
Provide written access plan
Owner
Mara
Due_on
2026-10-10

Ask it anything

Questions your own records can answer

These answers come from the fictional demo records. Jambo also offers configurable reporting. Your own version lets you change the questions and the process.

chat_bubble Which promises are due in the next fortnight?
chat_bubble Which high-influence stakeholders have had no recent contact?
chat_bubble Which high-risk issues remain open?
chat_bubble Which owners have the most overdue promises?
chat_bubble Which open issues have no outstanding promise attached?
chat_bubble Whose latest recorded feedback was negative?
chat_bubble Which projects have overdue promises and recent engagement?
chat_bubble Which records need purpose or retention review?
chat_bubble Which stakeholder records lack notice evidence?
chat_bubble Who recorded the most recent changes?

Switching

How to switch from Jambo

A move usually involves exporting your Jambo records, mapping and testing them, reconciling any issues, then running both systems side by side before you switch.

  1. 1

    Export your Jambo records

    Jambo documents CSV exports. Export the contacts, communications, issues and commitments you want to bring across, and check with Jambo which export options are available for your account. Keep the original exports safe while you work. Configurable headings and relationship references need checking before the records can be mapped.

  2. 2

    Map and test the import

    Start with an empty database and create the project records you need. Map Jambo’s headings and relationship references to the fields in the new system, then run the import’s test option first. A test run saves nothing. When the mapping looks right, run the import to load the mapped contacts, communications, issues and commitments together.

  3. 3

    Review the flagged records

    Check the import results and reconcile anything it reports, including missing relationships, duplicate identifiers or changed source records. Do not assume imported Closed or Completed statuses prove work was completed in the new system. Attachments, access rules and historical activity logs need separate migration work, so decide how to handle them before relying on the new records.

  4. 4

    Run both systems together

    Keep Jambo available for a short period while you use the new database and Claude Code for current work. Compare important records and follow-ups in both systems, and check that your team can find the information it needs. Agree which system is the source of truth during this overlap, so updates do not become split between two copies.

  5. 5

    Switch off Jambo

    After your checks are complete and your team is working from the new setup, stop entering updates in Jambo and end its use under your account arrangements. Keep the exports or other records you need under your own access and retention rules. Confirm that any separately handled attachments, access rules and historical activity logs are covered before closing out the move.

construction

Where the real effort goes

The real work is usually mapping your own fields and relationship references, then deciding how much history to bring. Configurable Jambo headings need explicit mapping, and attachments, access rules and historical activity logs require separate migration work. Enterprise DNA handles the mapping and reconciliation when it builds and runs your version.

Not ready for a call?

Get your Jambo switch plan by email

We will send you the step-by-step plan for moving your business off Jambo, 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 run it

Choose who sets it up and keeps it running

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install
  2. 2 Run npm run demo, then open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Ask for /commitments-due and /engagement-gaps
  4. 4 Map your Jambo CSV reports and run import jambo --dry-run before saving records
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your consultation fields, ownership rules and report formats
  • check Your Jambo exports mapped and reconciled
  • check A web front end for the people who need one
  • check A different technical foundation where your business requires it
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a monthly retainer

  • check Installed and operated inside Omni by Enterprise DNA
  • check Connected to the records and communication sources you approve
  • check Access, backups and private evidence storage designed for your team
  • check Review packs and ongoing changes covered by the agreed service
Book a call

Questions

Instead of Jambo, answered

What does this replace in our Jambo work? expand_more

The free version covers project records, stakeholder histories, concerns, promises and recurring reviews. Jambo also provides configurable reports; the difference here is ownership and the ability to change your process. Simply Stakeholders and Borealis are other established options to compare.

Will our consultation history come across? expand_more

Jambo documents CSV exports. The free version imports mapped contacts, communications, issues and commitments together after a test run. Export headings and relationship references need checking first. Attachment files, access rules and historical activity logs need separate migration work. Enterprise DNA handles that mapping and reconciliation in your built version.

Does this prove we met our consultation obligations? expand_more

No. It records what happened and flags missing purpose, retention-review and notice evidence. People assess the applicable obligations and whether the consultation was adequate. A completed field is not legal assurance.

Can our team keep the screens and connections it needs? expand_more

We scope your shared access, mobile capture, maps and communication connections before building your version. The free version supplies private read-only reports. Enterprise DNA builds and supports the agreed screens and connections for your team.

What do we pay Enterprise DNA? expand_more

One setup fee for the agreed build and migration, then a retainer for ongoing operation and changes. The scope sets the price. The free version has no licence fee; hosting and the assistant you use are separately arranged.

Bring your Jambo bill and one consultation report

In a 30-minute call with Sam, we look at the records you keep, the promises you track and the reports your projects require. We agree what your own version needs and what it takes to run it.

Book a call with Sam Get the free version

Stakeholder Engagement for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Jambo?

Get your version built