Enterprise DNA

Instead of Lattice

Stop renting Lattice. Own your performance review system.

We build your version around your review process, map your Lattice history and run it for you. Review deadlines, manager conversations and development promises stay in a database you own.

Lattice Foundations is US$13 per seat per month. Grow adds US$4 per seat per month. Both are billed annually, with a US$4,000 minimum annual agreement.

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

Seats, a yearly commitment and another line for development

Compare the parts you use with the system you need. These are public US-dollar rates, checked 19 October 2026 on <a href="https://lattice.com/pricing">Lattice pricing</a>. Your agreement determines your actual bill.

paid

Foundations seats

US$13 per seat per month brings reviews and goals together. That is US$156 per seat over a year.

trending_up

Grow on top

Development planning is an add-on at US$4 per seat per month, or US$48 per seat over a year.

calendar_month

An annual agreement

Lattice bills annually and sets a US$4,000 minimum agreement. Check the products and seats in your contract.

forum

Manager tools in the package

Conversations, feedback and updates are included with its base products. Compare those with what your managers actually use.

fact_check

The review progress screens

Review-writing and packet-sharing reports show stages of a cycle. Your owned version keeps those handoffs alongside development actions.

settings

The wider enterprise setup

Enterprise pricing is quoted for your seats, complexity and scale. Scope the access rules and connections your own version needs.

What you own instead

A review process with follow-through

Reviews

Know whose review needs the next step

Writing the review, sharing it and recording receipt are separate steps. Each has its own evidence.

  • check See pending reviews by reviewer and due date
  • check Find completed writing that still needs sharing
  • check Record acknowledgement without treating it as agreement
  • check Correct a review while retaining its previous version

Goals

Bring stale goals into the conversation

A goal has an owner, a target, a unit and a last check-in. Missing progress stays unknown.

  • check Spot goals with no recent progress update
  • check Keep each goal against its own target
  • check Combine overdue reviews with stale goals for the same person
  • check Record completion with evidence of the agreed result

Development

Keep the promise after the review

Development actions keep their owner and due date after the review meeting ends.

  • check Find overdue actions owned by the manager
  • check Check missed conversation records alongside overdue actions
  • check Prepare a private development plan
  • check Follow actions independently of the review cycle

Your records

Prepare the paperwork from current facts

Private review packs and weekly views use your business name, logo and colours.

  • check Bring mapped Lattice progress records across
  • check Keep source status separate from verified review events
  • check Review purpose, notice and retention reminders
  • check Prepare read-only views and a weekly follow-up draft

Make it yours

Design your own Lattice replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Performance Reviews for Claude Code

Connected to your own database

Which reviews are waiting, and who owns the next step?

SPRING

Rson re
Alex Chen
Viewer ki
Morgan Bell
Nd st
manager
Ate du
submitted
E on ov
2026-10-16
Erdue id
false
30000000-0000-0000-0000-000000000002

SPRING

Rson re
Alex Lee
Viewer ki
Morgan Bell
Nd st
manager
Ate du
pending
E on ov
2026-10-16
Erdue id
true
30000000-0000-0000-0000-000000000001

NEW-START

Rson re
Robin West
Viewer ki
Robin West
Nd st
self
Ate du
pending
E on ov
2026-11-09
Erdue id
false
30000000-0000-0000-0000-000000000003

Ask it anything

Ten questions your own review desk answers

These combine the records in the working demo. Lattice also provides analytics. Your version can follow your own questions.

chat_bubble Which overdue reviews belong to people with stale goals?
chat_bubble Which submitted reviews still need to be shared?
chat_bubble Which shared reviews have no acknowledgement recorded?
chat_bubble Which active people have no conversation recorded?
chat_bubble Which overdue development actions are owned by someone else?
chat_bubble Which goals still have unknown progress?
chat_bubble Which review cycles have pending work past their deadline?
chat_bubble Which people have both an overdue action and a missed conversation?
chat_bubble Which imported review statuses still need verification?
chat_bubble Which people need a privacy record review?

Switching

How to switch from Lattice

A move usually involves exporting the review history you need, mapping it into prepared records, checking the results, then running both systems briefly before you switch.

  1. 1

    Export your Lattice records

    Ask Lattice for the review progress and response reports that contain the records you need, including review assignments and any history you intend to retain. Export what your account allows, usually CSV or Excel, and check with Lattice if you are unsure which reports are available. Responses, attachments and private feedback need separate mapping, so do not assume they are included in the progress export.

  2. 2

    Prepare and test the data

    Prepare the progress data as review-assignment records. Map each person's and reviewer's email and name, the review type, and the source status to the fields expected by the importer. Run the import as a trial first and check its mapping and record counts before loading live records. Set up the real review cycle for your work rather than relying on the fictional cycle in the demo.

  3. 3

    Check import results

    Review every item the import marks for checking, especially historical statuses and any mismatched or conflicting records. A source status of Complete is historical evidence only, not proof that a response was submitted or received. Resolve mapping problems before trying again. Identical repeat imports are skipped, while conflicts stop the whole batch, so investigate conflicts instead of assuming a partial import succeeded.

  4. 4

    Run both systems briefly

    Keep Lattice and the new system in use for a short overlap. Use that period to check that the review handoffs, goals, conversations and development actions you rely on are represented correctly, and that your team knows which system to update. Compare the records you need from both systems, including any separately mapped responses or private feedback, before you make the new process the source of truth.

  5. 5

    Switch off Lattice

    After the overlap, confirm that the required records and access rules are in place and that outstanding work has a clear home. Keep exported files and reports private. Then stop using Lattice for the process you have moved, and confirm any remaining Lattice-only work or history is handled before ending your use of it.

construction

Where the real effort goes

The time-consuming part is usually deciding how your own review fields, stages, statuses and access rules map, then choosing how much history to bring. Progress records have a defined import path, but responses, attachments and private feedback need separate mapping, and exported layouts vary. If Enterprise DNA installs and runs it for you, it scopes the process, maps the history you need and builds the access model as part of the work.

Not ready for a call?

Get your Lattice switch plan by email

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

Open source

Do it yourself

Free, MIT licensed

  1. 1 Clone the repo and install with Node 22
  2. 2 Run npm test and npm run demo
  3. 3 Open it in Claude Code, Codex, OpenCode or Cursor
  4. 4 Map your Lattice export, do a trial import and check the records
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your review stages, fields and development rules
  • check Your Lattice history mapped and reconciled
  • check Employee screens and access rules built to your brief
  • check Your chosen technology and connections
Get your version built

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 Your records kept in a database you own
  • check Backups, agreed access controls and ongoing changes
  • check Review follow-ups connected with the rest of your business
Talk to Sam

Questions

Instead of Lattice, answered

Can this replace the parts of Lattice we use? expand_more

Start with your actual review process. The free version covers the private operator desk for reviews, goals, conversations and development actions. Enterprise DNA scopes your employee screens, private feedback collection, access rules and connections before you switch.

Will our Lattice history come across? expand_more

The free version imports prepared review-assignment records from a mapped progress export. Report layouts and permissions vary. Historical statuses are kept for checking, and review responses, attachments and private feedback need separate mapping. We reconcile the history you need as part of your installation.

Can every manager and employee see their own records? expand_more

The free version is for one authorised operator. A shared installation needs verified sign-in and rules for who can see each review. Enterprise DNA builds that access model into your version. Private preparation packs are reviewed before anyone shares them.

Does it decide ratings, pay or promotions? expand_more

People make those decisions. This system records facts, agreed actions and evidence of review handoffs. Missing paperwork is a follow-up prompt. It is not an employee rating. Privacy reminders identify records to check and do not certify compliance.

What do we pay Enterprise DNA? expand_more

One setup fee, then a retainer for the agreed build and ongoing operation. Sam scopes it around your review process, migration and access needs. The open-source version is free to run yourself, with your own hosting and coding-agent costs.

Own the process after the review meeting

Spend 30 minutes with Sam. Bring your Lattice agreement and one review cycle. We will map the handoffs, history and access your team needs, then scope your version.

Book a 30-minute call Get the free version

Performance Reviews for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Lattice?

Get your version built