Enterprise DNA

Instead of Totango

Stop renting Totango. Own your customer success system.

We build your version around how you retain customers, bring your Totango records across and run it for you. Your renewal rules and account reviews belong to your business.

Totango now points visitors to Odie. We could not verify a current public price. Compare your existing agreement with a system you own.

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

A customer success platform around your account records

For an existing Totango team, the comparison starts with the work you still need to do each week. Check your agreement for the actual bill and included services.

👥

An account portfolio

Totango segments account records for review. Keep the customer names, owners and selected contract facts together in your own database.

◉

Customer health profiles

Totango supports configurable health profiles and history. Your version uses rules you can inspect, with missing evidence called out explicitly.

📅

The renewal meeting

Upcoming terms and customer context drive the retention discussion. Own the dates, the agreed amounts and the evidence behind each decision.

✓

Tasks and touchpoints

Totango documents separate exports for tasks and conversations. Decide which history to bring across and reconcile it before changing systems.

▤

Segments and review views

Totango lets teams select attributes and filter accounts. Your weekly review can use your own definitions of overdue work and stale evidence.

↗

The move to another system

An account export is only part of a switch. Your health rules, other history and business connections need a migration plan agreed with your team.

Your version

A weekly retention routine built around your business

RENEWALS

Decisions with a record behind them

Put the renewal date beside the customer evidence before agreeing the next term.

  • check Overdue renewals and the next 90 days in one review
  • check Annual contract values kept separate by currency
  • check Renewal and cancellation decisions require evidence
  • check The old term remains available after the next term is recorded

ACCOUNT HEALTH

See what the label depends on

Use your own risk definitions and show the gaps behind every account review.

  • check Active users compared with licensed users
  • check Old usage evidence flagged for review
  • check Negative conversations and late promises visible together
  • check Your business owns and can change the definitions

CUSTOMER OUTCOMES

Keep promises attached to an owner

Move from a health colour to a specific follow-up and a customer outcome.

  • check Each follow-up has an owner and due date
  • check Overdue outcomes stay visible until resolved
  • check Completed actions need supporting evidence
  • check Quarterly reviews combine outcomes, conversations and next steps

YOUR RECORDS

Keep control of the operating record

Own the records and the review process around them.

  • check Original account export fields retained for reconciliation
  • check Customer information reviews flag missing assessments
  • check Branded success plans and renewal briefs generated from your records
  • check Take a complete record snapshot when you need one

Make it yours

Design your own Totango replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Customer Success for Claude Code

Connected to your own database

Which customer renewals are overdue or coming up?

Southern Data

Owner
Aroha
Renews_on
2026-10-04
Days_to_renewal
-7
Annual_value
12000.00
Currency
NZD
Health
unknown

Harbour Analytics

Owner
Aroha
Renews_on
2026-11-05
Days_to_renewal
25
Annual_value
24000.00
Currency
NZD
Health
at risk

Kauri Software

Owner
Ben
Renews_on
2026-12-05
Days_to_renewal
55
Annual_value
48000.00
Currency
AUD
Health
healthy

Ask it anything

Questions for your retention meeting

These questions run against the fictional demo today. Totango also supports custom reporting. Here, your business owns the records and the definitions.

chat_bubble Which renewals are overdue or due within 90 days?
chat_bubble Which customers have negative conversations and overdue promises?
chat_bubble Which apparently strong accounts have stale usage evidence?
chat_bubble Which customers have gone a month without a conversation?
chat_bubble Who owns the unresolved follow-ups?
chat_bubble Which agreed customer outcomes are overdue?
chat_bubble How much contracted annual value is at risk in each currency?
chat_bubble Which account lead has the largest overdue workload?
chat_bubble Which accounts need a privacy evidence review?
chat_bubble What should we discuss at the next quarterly customer review?

Switching

How to switch from Totango

The work depends on how much history and custom logic you want to bring across, since the documented import covers selected account records and current annual contract facts while other data needs separate mapping.

  1. 1

    Export your account segment

    Use Totango’s documented account-segment CSV export. Select the accounts you want to move and include current annual contract facts if available. If you are unsure which fields your export includes or what your account allows, check with Totango before proceeding. This importer is for existing Totango account portfolios, not the new Odie platform.

  2. 2

    Test, then load the records

    Have the export tested before saving anything to the new database. The test validates the whole file without importing it. Once you have reviewed the results, load the records you selected. The import keeps the original source fields, skips exact repeats and rejects changed source IDs, so treat the test as a check before the full load.

  3. 3

    Check the import results

    Review the test results and resolve any issues before loading the records. Pay particular attention to rejected records, changed source IDs, unclear mappings and fields that did not come through as expected. The import supports custom heading mappings, but tasks, conversations, historic usage, health rules and connections need separate mapping. Imported health stays unknown until fresh evidence is recorded.

  4. 4

    Run both systems side by side

    Keep Totango available during a short overlap while you use the new database and Claude Code for account reviews. Check that the selected accounts and current annual contract facts match your expectations. Confirm that your team can find the information it needs, and record fresh evidence before relying on health status. Do not assume that separate history has moved across.

  5. 5

    Switch off Totango

    Turn off Totango only after you have checked the records you chose to move, agreed how to handle information that needs separate mapping, and completed the overlap with your team. Confirm that the new review process covers your needs before ending access. If the export or migration leaves important gaps, resolve them before cutover.

construction

Where the real effort goes

The import is only part of the work. Most effort usually goes into mapping your own fields and health rules, and deciding how much history to bring. The documented import covers selected account records and current annual contract facts. Conversations, tasks, historic usage, attachments and connections need separate mapping. If you have Enterprise DNA run it, they map your Totango records and agree the migration scope with you.

Not ready for a call?

Get your Totango switch plan by email

We will send you the step-by-step plan for moving your business off Totango, 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 how much you want us to handle

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and install its dependencies
  2. 2 Run npm run demo and open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Ask for /weekly-review and inspect the fictional accounts
  4. 4 Prepare the Totango account-segment CSV and test the documented import
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your account fields, health rules and review documents
  • check Your Totango exports mapped and reconciled
  • check A web front end and business connections if you need them
  • check Your preferred technology and operating process
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 Your account history brought across and checked
  • check Access, backups and operating responsibilities agreed with you
  • check Your review process maintained as the business changes
Book a call

Questions

Instead of Totango, answered

Is this for Totango or the new Odie platform? expand_more

This version is for an existing Totango account portfolio. Totango now announces Odie on its main website. The documented import uses Totango account exports. An Odie migration needs its own assessment.

Can we bring our history across in a day? expand_more

The free version brings across the selected account records and current annual contract facts in one import, after a test run. Conversations, tasks, health rules, attachments and business connections need separate mapping. Enterprise DNA checks your exports and agrees the full migration before setting a cutover date.

Does Totango already have health scores and reporting? expand_more

Yes. Totango documents configurable health profiles, account segments and reporting. The difference here is ownership of your records and review rules. The examples show this free version working on fictional accounts, not a claim that Totango lacks comparable reports.

What about live usage feeds and a website for the team? expand_more

Tell us which systems supply the evidence and who needs to see it. Enterprise DNA builds those connections and the web front end into your version. The free version works from imported records and observations entered by an operator.

What does Enterprise DNA charge, and who runs it? expand_more

We agree one setup fee, then a retainer for ongoing work. You can operate the free version yourself, have us customise it, or have us run it through Omni by Enterprise DNA. Your operating needs, migration and support determine the scope.

Bring your renewal review to a 30-minute call with Sam

Show us the account list, the customer evidence you trust and the work your team repeats each week. We will map the version your business needs and what it takes to bring your records across.

Book a call Get the free version

Customer Success for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Totango?

Get your version built