Enterprise DNA

Instead of Veeva CRM

Stop renting Veeva CRM. Own your field force system.

We build your version around your territories, your call plan and your Code obligations, bring your Veeva CRM professionals, calls and sample history across and run it for you. Your company keeps every call, starter pack and payment record.

Veeva publishes no price for Veeva CRM or Vault CRM. Licences are quoted privately, per named user, and support for Veeva CRM on Salesforce ends on 31 December 2029, so every customer faces a move either way.

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 licence charges for

A named-user licence, and now a forced move

Veeva CRM is quoted, not listed, and it is changing platform under you. Veeva has set the end of support for Veeva CRM on Salesforce at 31 December 2029, so a migration project is coming whether you planned one or not. Compare that with your own field records, where another rep or another territory costs nothing to add.

request_quote

A quote, never a price list

There is no published price. You find out what each named user costs from the contract, and a small country team rarely has the leverage a global account does.

sync_problem

A migration you did not choose

Veeva CRM on Salesforce reaches the end of support on 31 December 2029. The move to Vault CRM is a project to plan, test and sign off, on Veeva's timetable rather than yours.

group_add

A bill that follows your headcount

Every rep, manager and medical liaison needs a named licence. A launch team or a contract sales force moves what you pay.

engineering

A partner for every change

A new segment, a new field on the call or a new report usually means a configuration request to an implementation partner.

bar_chart

The dashboards they chose to build

Coverage by territory is standard. Which practices have three prescribers and only one seen, or who took starter packs and has had no call since, depend on what you configure.

lock

Your professional records in their cloud

Call history, samples and payments are records you have to keep and stand behind. Today they sit in a system you rent rather than own.

Your own field force desk

Start with the call plan and the Code

Calls

The call plan and coverage, from your own segments

Every professional carries a segment and a call target for the cycle. Log a call once and the plan, coverage and follow-ups update.

  • check Each rep's week: who is behind target, follow-ups falling due, starter packs to deliver and events coming
  • check Reach and frequency against plan by territory and segment, this cycle
  • check A-segment specialists not seen this cycle at the top of the morning list
  • check A warning on any call where a product not yet registered was discussed, for your compliance lead to check

Samples

Starter packs that follow the Code

Every request, delivery and lot is recorded, and the system refuses what the Code does not allow.

  • check No starter pack before a written request with the name and address of the person supplied, in Australia
  • check In New Zealand: prescribers only, a rep on a current hawker's licence, and a signed receipt for every pack
  • check Stock in every rep's car by lot, with short-dated and expired packs flagged and never handed out
  • check A recall that lists every professional who received the lot and every rep still holding it, until each one is done

Events and payments

Hospitality and transfers of value checked as you record them

Events carry their education and what was spent on food and drink a head. Payments carry the date the professional was told they will be disclosed.

  • check Food and drink over the A$140 a head cap refused when planned, and kept on the record when the bill comes in over
  • check No entertainment, and no takeaway meals in New Zealand
  • check No payment to an Australian professional before their notice of disclosure, and six weeks for each to review their data
  • check The half-yearly report for Disclosure Australia written with the fields the Code lists, due 31 October and 30 April

Answers

Questions across every territory at once

Ask in plain English and get the answer from your own records.

  • check Which practices have several prescribers but only one of them seen this cycle
  • check Which prescribers took starter packs and have had no call since
  • check How much stock each rep holds that is short-dated, expired or recalled
  • check What each event cost per professional who came, against the cap

Make it yours

Design your own Veeva CRM replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your Veeva CRM 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 Veeva CRM data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from a fictional prescription medicines company with reps in Auckland, Christchurch, Sydney and Melbourne. Your field force manager asks the question and checks the records behind the answer.

forum

Pharma CRM for Claude Code

Connected to your own database

What needs my attention across the field force today?

breach: hospitality over the cap

Ref
E-01
Detail
Managing resistant hypertension in general practice: food and drink...

breach: professional has less than six weeks to review before the r...

Ref
T-0004
Detail
Dr Sophie Nguyen: send by 2026-09-19 for the report due 2026-10-31....

breach: professional has less than six weeks to review before the r...

Ref
T-0005
Detail
Dr Hannah Lee: send by 2026-09-19 for the report due 2026-10-31. Me...

breach: sample given to a health professional without prescribing r...

Ref
S-0003
Detail
Rachel Kemp: nurse, Cardovex 10 mg x2 on 2026-09-23. Medicines NZ C...

breach: sample given without a signed receipt

Ref
S-0002
Detail
Dr Michael Oduya: Glyzera 500 mg x2 delivered 2026-10-15 by Aroha N...

breach: sample issued by a rep without a current licence

Ref
S-0004
Detail
Kate Robson: licence HL-19982 expired 2026-10-28, issued 2026-10-31...

breach: starter pack supplied without a written request first

Ref
S-0005
Detail
Dr Emily Carter: Cardovex 10 mg x4 delivered 2026-10-18, no request...

breach: takeaway meal at a company meeting

Ref
E-03
Detail
Cardiovascular risk update: held 2026-10-19. Medicines NZ Code of P...

breach: transfer of value made before the professional was given no...

Ref
T-0002
Detail
Dr Mei Tan: speaker-fee AUD 1200.00 paid 2026-09-25, notice 2026-09...

breach: transfer of value made before the professional was given no...

Ref
T-0003
Detail
Dr Mei Tan: travel AUD 180.00 paid 2026-09-25, notice 2026-09-28. M...

breach: transparency report to Disclosure Australia

Ref
H1-2026
Detail
Disclosure Australia: 2 transfers for 2026-01-01 to 2026-06-30, due...

act now: expired sample stock still with a rep

Ref
R3301
Detail
Luke Daniels: Respiflo 100 mcg x7 expired 2026-10-23. Medicines Aus...

act now: professional given a recalled lot not yet told

Ref
S-0002
Detail
Dr Michael Oduya: lot G1187 (Glyzera 500 mg) recalled 2026-10-30, d...

act now: professional given a recalled lot not yet told

Ref
S-0007
Detail
Dr Sophie Nguyen: lot G1187 (Glyzera 500 mg) recalled 2026-10-30, d...

act now: recalled lot still in a rep's stock

Ref
G1187
Detail
Priya Raman: Glyzera 500 mg x10 recalled 2026-10-30. Medicines NZ C...

act now: recalled lot still in a rep's stock

Ref
G1187
Detail
Aroha Ngata: Glyzera 500 mg x8 recalled 2026-10-30. Medicines NZ Co...

starter packs waiting

Ref
S-0006
Detail
Dr Hannah Lee (SYD): Glyzera 500 mg x4 requested 2026-10-24, 9 days...

follow-up overdue

Ref
C-0004
Detail
Dr Grace Liu (AKL): Send the full paper through medical information...

follow-up overdue

Ref
C-0005
Detail
Dr Michael Oduya (AKL): Check how the first patients are going, was...

follow-up overdue

Ref
C-0009
Detail
Dr Paul Henare (CHC): Confirm the talk outline, was due 2026-09-03,...

follow-up overdue

Ref
C-0013
Detail
Dr Raj Menon (SYD): Send the advisory board agreement, was due 2026...

follow-up overdue

Ref
C-0015
Detail
Dr Hannah Lee (SYD): Deliver the starter packs, was due 2026-10-31,...

Ask it anything

Questions answered from your field records

These examples combine your own records across every territory, rep and professional at once. They are not a claim that Veeva CRM cannot produce a similar report.

chat_bubble Which A-segment professionals have not been seen this cycle, by territory?
chat_bubble How does reach and frequency compare with the plan, by territory and segment?
chat_bubble Which products were detailed most in the last 90 days, by specialty?
chat_bubble Which prescribers took starter packs and have had no call since?
chat_bubble How many days from a starter pack request to delivery, by rep?
chat_bubble How much sample stock is short-dated, expired or recalled, by rep?
chat_bubble Who received the most in transfers of value in the last 12 months, and for what?
chat_bubble What did each event cost per professional who came, against the hospitality cap?
chat_bubble Which A and B professionals have gone quiet after being seen before?
chat_bubble Which practices have several prescribers but only one of them seen this cycle?

Switching

How to switch from Veeva CRM

A move like this involves exporting your records, mapping them to the new database, checking the import, and running both systems side by side before you stop using Veeva CRM.

  1. 1

    Export your Veeva records

    Use Veeva CRM reports or Data Loader to export accounts and addresses, professionals, submitted calls, and call samples. Export them as comma-separated files where your account allows, and check with Veeva CRM about the available export options. Planned calls do not come across, so identify any call planning information you need to retain before you start.

  2. 2

    Load the records in order

    Import accounts first, then professionals, calls, and call samples. Run a test import before loading the records for real. The test run keeps nothing, so use it to check how your data will fit before committing the import. If your files use different headings from the importer, map those fields as part of the setup.

  3. 3

    Review the import findings

    Check the test results for rows that need attention, including fields that do not match and records that may be repeats. Repeated rows are skipped, and one bad row stops the whole file, so correct issues before you run the import again. Confirm that accounts, professionals, submitted calls, and call samples have come across in the expected order.

  4. 4

    Run both systems side by side

    Keep using Veeva CRM while your team checks the new records and carries out its usual work in the new system. Compare the records your team relies on, including call and sample history, and resolve any gaps before the move is complete. This gives you a chance to catch problems while Veeva CRM is still available to your team.

  5. 5

    Switch off Veeva CRM

    Once your team has checked the imported records and is ready to work in the new system, stop entering new activity in Veeva CRM. Arrange to end its use with Veeva after the side by side period. Make sure your team knows where to work from then on and that any outstanding records you chose to bring have been checked.

construction

Where the real effort goes

The real work is usually mapping your own fields and rules, then deciding which history to bring. Practices, professionals, submitted calls, and call samples come across in that order. Planned calls are left behind, while events and payments from the open half-year are brought across as part of setup. If you have Enterprise DNA run it, they handle this mapping and migration work.

Not ready for a call?

Get your Veeva CRM switch plan by email

We will send you the step-by-step plan for moving your business off Veeva CRM, 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 make it yours

Start with the free field force desk or have your version built

Open source

Do it yourself

Free code

  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 Export accounts, professionals, calls and call samples from Veeva CRM with Data Loader and import them with a dry run first.
  4. 4 Add your territories, reps and products, then run /attention and /call-plan.
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your segments, call targets, territories and the fields your sales and medical teams already use
  • check The State and Territory sampling rules that apply to you, on top of the Code
  • check Your Veeva CRM history brought across and checked, including events and payments in the open half-year
  • check A phone app for reps between calls, and a web front end for managers, if you want them

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 Access for every rep, manager and compliance reviewer with no charge per user, plus backups and restore checks
  • check Recalls, missing receipts, late reviews and the half-yearly report raised every morning
  • check The rules kept current as Medicines Australia and Medicines New Zealand change their Codes
Book a call with Sam

Questions

Instead of Veeva CRM, answered

Should we do this instead of moving to Vault CRM? expand_more

If you are a country team of 5 to 60 reps, the move Veeva has scheduled is a good moment to ask what you need. The free version covers the call plan, coverage, starter packs, rep stock, recalls, events and transfers of value. It has no approved presentations or approved email inside the call and no phone app. If you need those, we build what you use on the same records, or you keep that piece where it is.

Can we trust the Code checks? expand_more

Each check is written beside the section of the Medicines Australia Code of Conduct (Edition 20) or the Medicines New Zealand Code of Practice (Edition 17) it comes from, and the full list with sources ships with the free version so your compliance lead can check it. The system records and checks. Your medical and compliance people still approve material and decide what is reasonable.

What happens to our history in Veeva CRM? expand_more

Practices, professionals, submitted calls and call samples export from Veeva CRM and come across in that order, with a test run first that keeps nothing. Planned calls are left behind. Events and payments in the open half-year are brought across as part of the setup, so the next transparency report is complete.

Who can see these records? expand_more

They sit in a database your company owns, not a vendor's cloud. Calls, samples, stock movements and payments cannot be deleted, every change is logged with who made it, and nothing is ever sent from the system: follow-ups, recall letters, review letters and the report are drafts a person checks and sends.

What do we pay Enterprise DNA? expand_more

One setup fee to build your version and bring your Veeva CRM records across, then a monthly retainer if we run it for you. There is no named-user licence and no charge per rep. Book a call and we will price it against your Veeva renewal and migration quote.

Own the records behind every call and every starter pack

Take 30 minutes with Sam to go through your Veeva CRM renewal, your territories and your Code obligations. We map how your field force works and agree what your version needs before you change systems.

Book a 30-minute call with Sam Get the free version

Pharma CRM for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Veeva CRM?

Get your version built