Enterprise DNA

Instead of Tallyfy

Stop renting Tallyfy. Own your procedure execution system.

We build your version around the work your team repeats, bring your Tallyfy records across and run it for you. Your review steps and evidence stay in a database you own.

Tallyfy lists US$300 per Full Seat per year, US$100 per Light Seat per year and a US$20 per seat yearly Data Feed add-on. These are annual billing rates.

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

Seats for the people. A separate charge for the reporting feed.

Your seat mix and reporting needs determine the subscription. Compare that bill with owning the procedure records and paying for the work needed to run your version.

group

People who create procedures

Full Seats cost US$300 per person a year on annual billing. These seats can create and edit templates.

task_alt

People who complete assigned work

Light Seats cost US$100 per person a year on annual billing. They are intended for task completion rather than template creation.

bar_chart

The reporting feed

The Data Feed add-on is US$20 per seat per year and applies to all seats. Your owned version queries its own records.

event_repeat

An annual seat commitment

Tallyfy describes annual plans as a twelve-month commitment. Review the renewal terms alongside the current seat count.

checklist

Templates and running procedures

Tallyfy turns procedure templates into assigned work. The records worth carrying forward are the steps, owners, deadlines and evidence.

database

History behind the status

Its process export includes task records, form answers and comments. Bring the original evidence across and check it before starting your local procedures.

Your own procedure desk

The step, the owner and the evidence in one place

Execution

Keep each run tied to its approved instructions

A new procedure version changes future work while existing runs retain their original steps.

  • check Named owners and ordered steps
  • check Evidence required before a step closes
  • check Blocked work released with a recorded reason
  • check Waivers shown separately from completed work

Handover

Find the exact step that can move next

Join unfinished tasks, their owners and overdue reviews into the same Monday conversation.

  • check Ready work separated from waiting work
  • check A visible reason for each blocked step
  • check Overdue workload compared across owners
  • check Quiet runs shown beside procedure and retention reviews

Source history

Keep the original Tallyfy evidence intact

Imported records stay separate until you define and test the rules for new work.

  • check Task counts checked before an import lands
  • check Hidden steps distinguished from completed steps
  • check Original form answers and comments retained
  • check Successive exports kept for comparison

Paperwork

Produce the procedure pack in your own name

Your own review rules and recorded exceptions appear together in the documents you hand over.

  • check Approved procedure sheets with review evidence
  • check Execution records with each step and its evidence
  • check Read-only handover and attention reports
  • check Retention and access review prompts with their sources

Make it yours

Design your own Tallyfy replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Procedure Runs for Claude Code

Connected to your own database

What can move next, and what is blocked?

RUN-101

Position
2
Name
Reconcile review pack
Owner
Ben Patel
Readiness
blocked
Due on
2026-11-02
Overdue days
8
Block reason
Waiting for supplier statement

RUN-102

Position
1
Name
Check supplied records
Owner
Ben Patel
Readiness
ready
Due on
2026-11-08
Overdue days
2

RUN-103

Position
1
Name
Collect ledger evidence
Owner
Ana Lee
Readiness
ready
Due on
2026-11-13
Overdue days
0

Ask it anything

Ten questions your own procedure desk answers

These questions work on the demo records today. Your version can add the evidence and checks specific to your business.

chat_bubble Which step can each owner take next?
chat_bubble What is blocking the October close?
chat_bubble Which unresolved tasks are overdue?
chat_bubble Which active run has been quiet for a week?
chat_bubble Who has the most overdue steps?
chat_bubble Which approved version did this run follow?
chat_bubble Which steps were waived and why?
chat_bubble Which records need a retention or access review?
chat_bubble Which imported tasks were hidden rather than completed?
chat_bubble What source snapshots do we hold for this procedure run?

Switching

How to switch from Tallyfy

A move usually involves exporting and reconciling your history, rebuilding and testing operating rules, then running both systems side by side before you retire Tallyfy.

  1. 1

    Export your Tallyfy records

    Use Tallyfy’s documented process CSV export to bring out the tasks, form answers and comments you want to keep. Check that the export covers the records you need. Files attached to tasks need to be retrieved separately, because the import keeps file names rather than the files themselves. If you are unsure what your account can export, check with Tallyfy.

  2. 2

    Test the import first

    Load your export using the import’s test run before bringing the records into regular use. The test checks task counts, hidden task states, completion timestamps and links between child rows. Review its results against Tallyfy so you can spot gaps or mismatches before you proceed with the full import.

  3. 3

    Review and reconcile the results

    Check what the import flags, including differences in task counts, hidden states, completed timestamps and child row references. Confirm that the imported form answers and comments are readable, and retrieve any attached files separately if you need them. Imported history stays in a separate evidence register. It does not mean that an old procedure has been newly approved.

  4. 4

    Run both systems side by side

    Keep Tallyfy running while you use Procedure Runs for a short period. Compare active work, owners, completion records and evidence in both systems, and check that your procedure steps and operating rules behave as intended. This gives you a chance to catch missing records or rules that need adjustment before Tallyfy is no longer your working system.

  5. 5

    Switch off Tallyfy

    Retire Tallyfy after you have reconciled the imported records, retrieved any files you need and tested the procedures and rules your team will use. Make sure the people responsible for the work know where to find the current procedure and how to record completion and evidence. Keep the Tallyfy export and any separately retrieved files according to your own retention requirements.

construction

Where the real effort goes

The import brings over history, but your approved steps, conditional rules, permissions, schedules and connections need to be mapped, rebuilt and tested. The work also depends on which history and attached files you choose to bring across. If you have Enterprise DNA run the replacement, Enterprise DNA handles bringing your records across and building the fields, deadlines and connections for your version.

Not ready for a call?

Get your Tallyfy switch plan by email

We will send you the step-by-step plan for moving your business off Tallyfy, 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, open source

  1. 1 Clone the repo and run npm install, then npm run demo
  2. 2 Open the folder in Claude Code, Codex, OpenCode or Cursor and ask for the handover
  3. 3 Export your Tallyfy processes, preview the import and reconcile the source records
  4. 4 Author your procedure versions, test the sequence and set up private backups
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your procedure steps, fields, deadlines and evidence rules
  • check Your Tallyfy history mapped across and checked against the source
  • check Shared screens, identity controls and connections built for your team
  • check A different technical foundation where your business needs one
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with access and backups set up
  • check Procedure reviews and handover packs prepared for your team
  • check Connections and operating routines kept working as your process changes
  • check Run through Omni by Enterprise DNA beside the rest of your business
Talk to Sam

Questions

Instead of Tallyfy, answered

Can we bring our existing Tallyfy history across? expand_more

Yes. Tallyfy documents a process export that includes tasks, form answers and comments. The free version checks the task counts and keeps that original evidence. Files attached to a task need separate retrieval. We bring your records across and reconcile them as part of your version.

Will importing history recreate every automation? expand_more

The history and the operating rules are separate. Your approved procedure steps, conditional branches, permissions, schedules and connections need to be set up and tested for your version. We scope that work before you retire the existing service.

What does the free version do today? expand_more

It runs ordered checklists from approved versions, requires evidence for completion, records blockers and waivers, and produces handover reports. It also reads imported source history. Shared sign-in, guest access and automated reminders are features we can build and test for your team.

Does a completed step prove that the work was checked? expand_more

It records the operator, their completion statement and the evidence reference. It does not independently inspect the underlying work or authenticate a signature. Your version can add the reviewer checks and access controls you require. Privacy and retention prompts help identify records needing review.

How do we compare the cost with Tallyfy? expand_more

Start with the Full Seats, Light Seats and reporting add-ons on your current bill. Then scope the migration, shared access and ongoing operation of your own version. Enterprise DNA charges one setup fee, then a retainer. Hosting and the tools you use to operate the free version remain your costs.

Bring the procedure your team keeps chasing

Spend 30 minutes with Sam. We look at your Tallyfy bill, one recurring job and the evidence your team needs at handover. Then we scope the records, controls and connections for a version built around your business.

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

Procedure Runs for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Tallyfy?

Get your version built