Enterprise DNA

Instead of RepairDesk

Stop renting RepairDesk. Own your repair shop system.

We build your version around intake, bench work and handover, bring your RepairDesk records across, and run it for you. Your fields, your checks, your business.

RepairDesk starts at US$99 per store per month, or US$79 per month billed annually. Growth starts at US$149 monthly or US$119 on annual billing. Advanced is quoted privately.

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 subscription covers

A recurring bill around the repair counter

RepairDesk combines repair workflows with reporting and counter services. Decide which parts your shop needs before moving.

paid

A bill for each store

Essential starts at US$99 per store per month on monthly billing. The US$79 annual-billing rate comes to US$948 a year.

groups

Users tied to the plan

Essential lists five users per location. Growth lists eight, while Advanced lists unlimited users.

build

Ticket workflows

Repair workflows and unlimited tickets are listed in the plans. Your repair history is the information those screens organise.

dashboard

Reporting screens

The pricing comparison includes reporting and dashboards. Your owned version can change its questions as your operation changes.

extension

Paid additions

Appointments Pro and the phone system appear as paid additions in the pricing comparison. Check your actual package before comparing costs.

storefront

Counter services to account for

Payments and customer-facing tools are part of the wider product. Keep the services you rely on while your replacement is scoped.

Your shop’s version

From intake to collection, with the evidence attached

Bench

Start the day with the repairs that need attention

See promised dates, technician assignments and work waiting for parts together.

  • check Late jobs in promised-date order
  • check Repairs waiting for parts
  • check Customers without a recorded update for a week
  • check An intake condition and approval reference beside the device

Parts

Know what is on the shelf and where it went

Parts usage reduces the shop’s recorded stock and stays attached to the repair.

  • check Stock holdings and reorder points by shop
  • check A parts record for each repair
  • check Recorded parts costs beside invoice amounts
  • check Separate currencies for each shop

Handover

Keep ready devices and customer remedies visible

Quality evidence comes before collection. Customer remedy follow-ups stay visible alongside warranty dates.

  • check Ready devices waiting a week for pickup
  • check Recorded balances with unknown amounts marked
  • check A collection reminder prepared for review
  • check Open remedy claims with follow-up dates

Ownership

Change the checks and paperwork to fit your shop

Your database holds the records. The free version includes evidence checks, read-only reports and business paperwork.

  • check Australian repair-notice evidence checks
  • check New Zealand promised-date review flags
  • check Job cards, collection records and remedy documents in your brand
  • check Questions combining bench delays, customer contact and recorded costs

Make it yours

Design your own RepairDesk replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Repair Shop for Claude Code

Connected to your own database

Which repairs should we look at first?

R-1001

Stomer de
Alex Chen
Vice te
ThinkPad T14
Chnician st
Ravi
Atus du
assessment
E_on da
2026-10-01
Ys_late
6

R-1002

Stomer de
Moana Bell
Vice te
iPad Air
Chnician st
Jo
Atus du
approved
E_on da
2026-10-02
Ys_late
5

R-1003

Stomer de
Alex Morgan
Vice te
iPhone 13
Chnician st
Ravi
Atus du
repairing
E_on da
2026-10-03
Ys_late
4

R-1004

Stomer de
Alex Chen
Vice te
ThinkPad T14
Chnician st
Jo
Atus du
parts
E_on da
2026-10-04
Ys_late
3

R-1005

Stomer de
Moana Bell
Vice te
iPad Air
Chnician st
Ravi
Atus du
ready
E_on da
2026-10-05
Ys_late
2

R-1007

Stomer de
Alex Chen
Vice te
ThinkPad T14
Chnician st
Ravi
Atus du
repairing
E_on da
2026-10-07
Ys_late
0

R-1008

Stomer de
Moana Bell
Vice te
iPad Air
Chnician st
Jo
Atus du
ready
E_on da
2026-10-08
Ys_late
-1

R-1009

Stomer de
Alex Morgan
Vice te
iPhone 13
Chnician st
Ravi
Atus du
parts
E_on da
2026-10-09
Ys_late
-2

Ask it anything

Ten questions your repair records can answer

These questions run against the fictional demo today. Change them around the decisions your own shop needs to make.

chat_bubble Which late repairs are waiting for parts?
chat_bubble Which customers have not heard from us for a week?
chat_bubble Which finished devices have waited a week for collection?
chat_bubble Which technicians have overdue work?
chat_bubble Which Australian repairs lack notice evidence?
chat_bubble Which parts are at their reorder point?
chat_bubble Which repairs have recorded parts costs above their invoice?
chat_bubble What recorded balance is waiting at each shop?
chat_bubble Which customer remedy follow-ups are overdue?
chat_bubble Which imported repairs still need approval or condition evidence?

Switching

How to switch from RepairDesk

A move involves exporting and converting ticket records, checking the imported data, and deciding which parts of your RepairDesk history need separate work.

  1. 1

    Export your RepairDesk records

    Use RepairDesk’s documented ticket export to download the ticket workbook in Excel format, then convert it to the documented CSV import format. Export what your account allows, and check with RepairDesk if you need help or have other records to bring over. The documented path covers ticket rows, not every part of your history.

  2. 2

    Test the import

    Start with a test run of the converted ticket records before importing them for real. The import brings repair rows across and preserves original values and columns. Customers remain separate snapshots until identities are verified, so do not treat similarly named records as confirmed matches.

  3. 3

    Review the import findings

    Check what the test run reports, then review the imported records for gaps that matter to your shop. Payments, photos, approval evidence, parts usage and notice records need separate work. The import does not infer missing details, so decide how you will handle those records rather than assuming they came across with the tickets.

  4. 4

    Run both systems briefly

    Keep RepairDesk available while you use the new database for a short period and compare live repair work against the imported records. Check the bench queue and customer details, and keep your counter and payment services separate unless you have agreed different screens or connections. Record corrections in the right system so you do not lose changes.

  5. 5

    Switch off RepairDesk

    When you have checked the records and agreed how ongoing work will be recorded, stop using RepairDesk for new work. Keep any exports or account access you still need for reference, then close the service according to your RepairDesk account terms. Make sure your team knows where to record new repairs and customer updates.

construction

Where the real effort goes

The real work is usually mapping your own fields and shop rules, then choosing how much history to bring across. Ticket rows are documented, but payments, photos, approval evidence, parts usage and notice records need separate work. If you have Enterprise DNA build and run your version, they handle the mapping and checks as part of that work.

Not ready for a call?

Get your RepairDesk switch plan by email

We will send you the step-by-step plan for moving your business off RepairDesk, 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, MIT licence

  1. 1 Clone the repo and install its dependencies.
  2. 2 Run npm run demo and open the folder in Claude Code, Codex, OpenCode or Cursor.
  3. 3 Export RepairDesk tickets, convert the workbook to CSV and run the documented import with --dry-run.
  4. 4 Verify totals and missing evidence in a fresh database before moving your repair workflow.
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your intake fields, repair stages and evidence rules
  • check Your RepairDesk records mapped, brought across and checked
  • check A counter screen, phone tools or a different technical foundation scoped to your needs
  • check Your job cards and customer paperwork in your business’s name
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 Database access, backups and record migration set up for your business
  • check Agreed connections to your existing counter and accounting services
  • check Ongoing changes and support as your shops and repair process change
Book a call with Sam

Questions

Instead of RepairDesk, answered

Can I keep the counter and payment services we already use? expand_more

Yes. The free version handles repair records, parts and follow-ups. Keep your current counter and payment services. We agree which screens and connections your custom version needs before moving that work.

How does our RepairDesk history come across? expand_more

Export the ticket workbook and convert it to the documented import format. The free version brings in repair rows and preserves their original values. Payments, photos, approval evidence, parts usage and notice records need separate work. Enterprise DNA handles the mapping and checks as part of your version.

Does this decide whether a repair or warranty claim meets the law? expand_more

No. It flags missing evidence and overdue follow-ups for a person to review. Australian notice records are checked against acceptance times. A shop warranty date never automatically closes a customer’s remedy claim.

What does the free version cost to run? expand_more

The software has an MIT licence and no subscription fee. You cover your own hosting, agent access, backups and support. Enterprise DNA can install and operate your version for one setup fee, then a retainer.

What makes this worth changing for a small repair shop? expand_more

The choice depends on the workflow you need to own and change. RepairDesk already covers a broad counter operation. Start by comparing your actual bill and essential services with the repair process shown here, then agree the migration and custom work before switching.

Build around the way your repair shop works

Spend 30 minutes with Sam. Bring your RepairDesk bill and one repair that got stuck. We will map the records, checks and counter services your version needs.

Book a call with Sam Get the free version

Repair Shop for Claude Code is free and open source, published by Enterprise DNA.

Done paying for RepairDesk?

Get your version built