Enterprise DNA

Instead of gradar

Stop renting gradar. Own your job evaluation workflow.

We build your version around the way you evaluate roles, bring across your exported gradar job records and run the agreed workflow for you. Every decision keeps its evidence.

gradar lists Enterprise Complete at US$15,000 a year and Ultimate at US$50,000 a year in its US price sheet. These are different licence tiers, not a claim about your current bill.

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 gradar bill buys

Choose the evaluation work your business needs

gradar Professional Complete lists US$10,500 a year, Enterprise Complete US$15,000 and Ultimate US$50,000. Its published plans combine job evaluation with compensation features and deployment allowances. Compare your actual use before choosing your version.

paid

An annual licence tier

The published US price sheet sets an annual fee for each edition. The right comparison starts with your edition and the work your team uses.

group

Editing access

Professional includes four editing users and Enterprise eight. Ultimate lists unlimited users within each included environment.

database

Separate environments

Ultimate includes three environments for production, testing or related businesses. The other listed editions include one.

tune

Custom evaluation wording

Enterprise and Ultimate support organisation-specific factor descriptions, with implementation effort charged separately where indicated.

analytics

Compensation comparisons

Salary survey data can be integrated, but third-party survey purchases remain separate. Agree whether those comparisons belong in your replacement scope.

sync

Connections to personnel records

The price sheet describes personnel-system integration with setup charges. Your owned version needs the connections that your business actually uses.

Your evaluation desk

From role evidence to a decision you can explain

Profiles

Describe the work before grading it

Keep purpose, duties and responsibility for review together.

  • check Group roles by family and business unit
  • check Give every profile an owner and review date
  • check Retain the profile version used for each evaluation
  • check Find the imported roles that still need evidence

Evaluation

Record the reason for every factor level

Use an explicit method that your evaluator can inspect and your business can adapt.

  • check Assess skills, effort, responsibility and conditions
  • check Keep rationale and evidence beside each factor level
  • check Preserve the method version behind each decision
  • check Bring overlooked demands into the panel discussion

Panel and appeals

Keep a grade tied to its reviewed basis

A changed role or an open challenge is visible before an old grade is reused.

  • check Separate evaluator and reviewer records
  • check Flag profiles changed after evaluation began
  • check Track appeals with an owner and due date
  • check Join stale profiles, missing evidence and appeals in one review

Records you own

Prepare the paperwork from the decision record

Your database supplies the profile, the panel pack and the appeal record.

  • check Create branded job profiles for review
  • check Show each factor and the recorded panel decision
  • check Compare current grades across families and units
  • check Keep original grading results alongside your local history

Make it yours

Design your own gradar replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Job Evaluation for Claude Code

Connected to your own database

Which roles need a review this week?

FIN-01

Name
Finance analyst
Review due
2026-11-16

LAB-01

Name
Laboratory technician
Owner
Ari
Review due
2026-11-09
Evaluation
EV-DEMO-3
Status
approved

OPS-01

Name
Operations coordinator
Owner
Mara
Review due
2026-11-25
Current grade
E2
Evaluation
EV-DEMO-1
Status
approved

OPS-02

Name
Senior operations coordinator
Owner
Tane
Review due
2026-10-18
Evaluation
EV-DEMO-2
Status
submitted

SUP-01

Name
Customer support specialist
Owner
Leah
Review due
2026-10-23
Evaluation
EV-DEMO-4
Status
draft

Ask it anything

Ten questions your evaluation desk answers

These questions run against the fictional demonstration records. They combine job evidence, review decisions and appeals.

chat_bubble Which jobs have no local evaluation?
chat_bubble Which approved grades have become stale?
chat_bubble Which profiles are overdue for review?
chat_bubble Which jobs lack purpose or responsibility evidence?
chat_bubble Which jobs have no review owner?
chat_bubble Which jobs are missing working-condition evidence?
chat_bubble Which evaluations await a panel decision?
chat_bubble Which jobs have an overdue appeal?
chat_bubble Which imported grades still need local evaluation?
chat_bubble Which current grades cross job families?

Switching

How to switch from gradar

The move involves exporting your job report, mapping your fields, checking the imported records and deciding what history to retain.

  1. 1

    Export the job report

    Use gradar’s job report CSV export to get the job records and grades you want to bring across. The import is built for that report, and imported grades remain historical results rather than grades under the new method. If you need attachments, older evaluation history or information outside the report, agree how to retain it separately. Check with gradar about anything your account cannot export in the report.

  2. 2

    Map fields and test the import

    Compare the headings in your report with the fields in the new database. If your headings are customised, map them before importing so each value lands in the right place. Run the import’s test first, then review its results before loading the records. If you have Enterprise DNA run the setup, they do this mapping with you.

  3. 3

    Review flags and reconcile records

    Read what the import flags before treating the records as ready. Check the imported count against the report, look for duplicates or other issues, and resolve any problems with the source data or field mapping. Confirm that the imported grades are retained as source history. Agree what happens to attachments and older history that was not in the job report.

  4. 4

    Run both side by side

    Keep gradar available while you check the new database against it using real job records. Confirm that profiles and source grades are present, and that your team can follow the evaluation and review process you have agreed. Do not treat an imported gradar grade as a current result under the new method. Have a competent evaluator validate or replace the illustrative method before business use.

  5. 5

    Switch off gradar

    Once you have reconciled the records and are ready to use the new process, arrange to end your gradar service. Keep the agreed copies of the report and any attachments or older history you need. Make sure your team knows where the records are held and who is responsible for the database. If you need a browser experience or connections, agree those requirements before retiring gradar.

construction

Where the real effort goes

The real work is usually mapping your own fields and rules, then deciding how much history to bring beyond the job report. Customised headings need mapping, and attachments or older evaluation history need a separate retention decision. You also need to validate or replace the illustrative evaluation method before business use. If Enterprise DNA runs the setup, they handle the mapping and reconciliation with you.

Not ready for a call?

Get your gradar switch plan by email

We will send you the step-by-step plan for moving your business off gradar, 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 Inspect the example method and agree your evaluation rules
  4. 4 Import your gradar job export, map any custom headings and reconcile the count
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your approved method, job fields and review rules
  • check Your gradar job records brought across and reconciled
  • check A web front end or different technology if your operation needs it
  • check Your own profile documents, panel packs and reports
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 Agreed connections to the rest of your business
  • check Backups, access controls and ongoing operation scoped with you
  • check Your team keeps responsibility for evaluation evidence and decisions
Book a call with Sam

Questions

Instead of gradar, answered

How much does gradar cost compared with an owned version? expand_more

The vendor-linked US price sheet lists Professional Complete at US$10,500 a year, Enterprise Complete at US$15,000 and Ultimate at US$50,000. Those editions include different allowances and a broader product. Enterprise DNA charges one setup fee, then a retainer for the work agreed with you.

Can we bring our job records and existing grades across? expand_more

Yes. The free version imports the job report export and preserves its source grades. Customised column headings need mapping first. We reconcile the records with you and agree how to retain attachments, older evaluation history and any other information outside that report.

Will the new system produce the same grades or prove equal pay? expand_more

No. Existing gradar grades remain historical results. The free version includes an illustrative method that your evaluator must validate or replace. It records the evidence and decisions but does not certify a method, establish equal value or prove legal compliance.

Can our team have its own screens and connections? expand_more

Yes. Enterprise DNA can build the browser experience, access model and connections your team needs. We agree those requirements, and any compensation analysis you need, before you retire the existing service.

What happens when a role changes or someone challenges its grade? expand_more

A changed profile needs a fresh evaluation before its grade is treated as current. An open appeal is shown with its owner and due date. Resolving it records the evidence and whether the decision stands or requires re-evaluation. Earlier decisions remain in the history.

Bring one job profile and your gradar bill

Book a 30-minute call with Sam. We will walk through the evidence your team keeps, the decisions you make and the version Enterprise DNA would build and run for you.

Book a call with Sam Get the free version

Job Evaluation for Claude Code is free and open source, published by Enterprise DNA.

Done paying for gradar?

Get your version built