Enterprise DNA

Instead of Salesforce License and Permit Management

Stop renting Salesforce licensing. Own your licensing desk.

We build your internal casework system around your permit types and officer responsibilities, bring the agreed Salesforce records across, and run it for you. Start with the desk that handles applications and renewals.

Salesforce Public Sector Service Core lists US$275 per user per month, billed annually. That is US$3,300 a year for one user, before separately scoped services.

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 incumbent bill

A platform subscription around your licensing work

Salesforce sells a broader public-sector platform. Compare its subscription with the internal application work your team actually needs to carry out.

paid

A recurring price per user

Public Sector Service Core lists US$275 per user per month, billed annually.

layers

A higher edition price

Public Sector Service Advanced lists US$500 per user per month, billed annually.

event

An annual commitment

The listed monthly rates require annual billing and an annual contract.

assignment

A broader field-service option

Public Sector Foundation Advanced Field Service Enterprise lists US$350 per user per month, billed annually.

extension

Additional products to scope

Salesforce lists further products for service delivery and analytics. Confirm the actual package and quote.

folder

More than the internal desk

The platform spans several public-sector applications. This free version focuses on licensing casework, evidence, inspections and renewals.

The system you own

An application desk built around the next action

Intake

Know what is waiting and who owns it

Read the oldest applications, their internal target dates and the officer responsible.

  • check Applicants linked to each application
  • check Required evidence set by permit type
  • check Overdue targets alongside missing evidence
  • check Workload grouped by the actual officer

Evidence

Prepare the pack before the officer reviews it

Bring document checks and inspection outcomes into one review list.

  • check Missing, rejected, expired and stale evidence flagged
  • check Inspection dates, outcomes and report references
  • check Complete administrative packs listed for review
  • check Decision source, reason and review snapshot preserved

Renewals

See conditions alongside expiring licences

Connect upcoming renewals to unresolved conditions and the person who owns the review.

  • check Licences due in the next sixty days
  • check Expired records remain visible
  • check Conditions with owners and review dates
  • check New applications for renewed permissions

Working papers

Prepare the week from the records

Draft the internal papers the desk needs, with the same business name and branding throughout.

  • check Application review packs
  • check Evidence-request drafts for officer review
  • check Renewal review papers with conditions
  • check Weekly workload, attention and record checks together

Make it yours

Design your own Salesforce License and Permit 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 License and Permit 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 License and Permit 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 License and Permit 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 Licensing Desk for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Licensing Desk for Claude Code

Connected to your own database

Which records need attention today?

Applicant record review

Record
ORG-102
Owner
Owen
Due on
2026-10-11

Condition review overdue

Record
COND-101
Owner
Rina
Due on
2026-10-12

Application target overdue

Record
APP-101
Owner
Rina
Due on
2026-10-13

Evidence: Missing evidence

Record
APP-101
Owner
Rina
Due on
2026-10-13

Inspection fail

Record
IN-102
Owner
Tama
Due on
2026-10-13

Inspection pending

Record
IN-101
Owner
Tama
Due on
2026-10-14

Evidence: Evidence expired

Record
APP-102
Owner
Owen
Due on
2026-10-21

Evidence: Evidence not accepted

Record
APP-102
Owner
Owen
Due on
2026-10-21

Licence renewal review

Record
LIC-101
Owner
Rina
Due on
2026-11-10

Ask it anything

Ten questions beyond a fixed dashboard

These questions run against the free version today. Existing Salesforce reports can also be configured; the difference here is that you own and can change the underlying work.

chat_bubble Which owners have overdue applications and missing evidence?
chat_bubble Which applications are ready for an officer to review?
chat_bubble Which requirements are causing the most gaps?
chat_bubble Which applicants have multiple open applications?
chat_bubble Which upcoming renewals still have conditions to review?
chat_bubble Which inspections are holding up an otherwise complete evidence pack?
chat_bubble Which complete packs need an applicant accuracy review?
chat_bubble Which permit types lack a documented local policy?
chat_bubble Which approvals have no licence record yet?
chat_bubble Which expired evidence sits on an overdue application?

Switching

How to switch from Salesforce License and Permit Management

A move involves exporting mapped Salesforce reports, reviewing the records and rules you need, and checking the new database alongside Salesforce before you switch.

  1. 1

    Export your core reports

    Export Details Only CSV reports for applicants, permit types and applications. These are the documented reports the importer uses. The move does not automatically bring across arbitrary Salesforce backups or all your history. List the other records you want to bring, such as decisions, licences, inspections, evidence and fees, so you can plan their mapping separately.

  2. 2

    Map and test the import

    Match the fields in your reports to the new database before loading them. The importer expects mapped reports, so your field names and values may need local mapping. Have the person setting up the database run a test import first. This checks the batch without changing records, giving you a chance to address mapping issues before loading the records for use.

  3. 3

    Review the import results

    Check what the import flags and confirm the records are complete and correctly matched before relying on them. Applicants start unverified, permit types start unconfigured and applications start open, so review applicant accuracy and configure each permit type against your local policy. Historic decisions, licences, inspections, evidence, fees and legacy history need separately reviewed mapping if you want them included.

  4. 4

    Run both systems side by side

    Keep Salesforce in use while your team checks the new database against current work for a short period. Compare the applications, evidence, inspections and renewal records you have mapped, and confirm staff can find the information they need. Treat Salesforce as the working system until the records and agreed processes have been reviewed and your team is ready to move.

  5. 5

    Switch off Salesforce

    Once you have reviewed the imported records and your team is ready to work from the new database, stop using Salesforce License and Permit Management for this casework. Keep any records you still need according to your authority's retention requirements. The new system covers internal licensing casework, not public portals, payments or statutory decision automation.

construction

Where the real effort goes

The real work is usually mapping your own fields and permit rules, then deciding which history to bring and reviewing how it maps. The core import covers applicants, permit types and applications. Older decisions, licences, inspections, evidence, fees and legacy history need separate review. When you have Enterprise DNA install and run your version, they handle this migration work as part of the agreed scope.

Not ready for a call?

Get your Salesforce License and Permit Management switch plan by email

We will send you the step-by-step plan for moving your business off Salesforce License and Permit 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

Choose who builds and runs your version

Open source

Do it yourself

Free code

  1. 1 Clone the repo and install its dependencies.
  2. 2 Run npm test and npm run demo, then open it in Claude Code, Codex, OpenCode or Cursor.
  3. 3 Map your Salesforce Details Only CSV reports and trial-import them with the documented command.
  4. 4 Set your permit rules, access controls and backups before using live records.
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your permit types, fields, evidence rules and officer responsibilities
  • check Your agreed Salesforce records mapped and reconciled
  • check A web front end or different stack when your workflow needs one
  • check Branded working papers and connections scoped for your team
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and connected through Omni by Enterprise DNA
  • check Your agreed records brought across and checked with your team
  • check Access, backups and ongoing operation set up for the agreed scope
  • check One supported system for the internal licensing desk
Book a call

Questions

Instead of Salesforce License and Permit Management, answered

Does this replace all of Salesforce Public Sector? expand_more

The free version covers internal licensing casework: applicants, permit types, applications, evidence, inspections, decision records, licence records and conditions. We scope your public intake, field work, connections and additional history when we build your version.

Can it decide whether someone receives a licence? expand_more

The responsible officer makes that decision. The system prepares the evidence pack and records the decision with its reason and source. It checks required administrative records before an approval is recorded. It does not grant statutory authority, issue a legal instrument or calculate statutory deadlines.

What happens to our Salesforce history? expand_more

Start with mapped detail reports for applicants, permit types and applications. The free import checks the whole batch and preserves the original rows. Historic decisions, licences, inspections and documents need separately reviewed mapping, which Enterprise DNA can include in your migration.

Will this fit our authority and records duties? expand_more

We build your version around the permit rules, responsibilities and record controls you agree. The free version includes record accuracy checks, retention review reminders and a decision history. The responsible team reviews jurisdiction-specific rules, access and retention before operational use.

What do we pay Enterprise DNA? expand_more

One setup fee, then a retainer for the agreed customisation and operation. We look at your current licensing work and Salesforce bill with you before defining the scope. The open-source code is free to run yourself; hosting and the tools you choose have their own costs.

Own the desk that keeps applications moving

Spend 30 minutes with Sam. Bring your Salesforce bill and one application journey. We will identify the internal casework worth replacing, the records to bring across and the version Enterprise DNA would build and run.

Book a call with Sam Get the free version

Licensing Desk for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Salesforce License and Permit Management?

Get your version built