Enterprise DNA

Instead of ResDiary

Stop renting ResDiary. Own your guest book and service system.

We build your version around how your restaurant runs, map your ResDiary bookings and guest details, and run it for you through Omni by Enterprise DNA.

ResDiary Pro lists A$220 a month plus GST. Twelve monthly payments are A$2,640 before setup and add-ons.

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

A monthly plan, then the connections around it

ResDiary sells a working reservation service, including online bookings. Compare that service with the operating record you can own and the connections we build for your venue.

paid

A monthly subscription

The AUD price list starts Connect at A$115 a month plus GST.

groups

Booking allowances

Connect includes up to 150 bookings a month. Express lists A$170 for up to 500. Pro lists A$220 for unlimited bookings.

settings

A setup charge

The published setup fee is A$129, with prices subject to GST.

restaurant

A point-of-sale connection

POS integration is listed separately at A$20 a month.

calendar_month

Online booking channels

The core service includes a booking widget and commission-free bookings. Decide which channels your custom version must support.

support_agent

An operated service

The price list includes support and unlimited users. A switch needs an agreed support arrangement as well as your records.

Your own operating record

Run service from the history you already have

Before service

A briefing the team can use

Read the next arrivals alongside the details that need a decision.

  • check Covers and arrival times in venue local time
  • check Seating assignments checked for overlapping bookings
  • check Unassigned parties kept on the attention list
  • check Kitchen handovers shown beside declared dietary needs

Guest history

Remember the whole visit history

Combine recorded outcomes with the bookings still ahead.

  • check Completed visits and no-shows by guest
  • check Repeat missed visits beside upcoming reservations
  • check Previous diners with no future booking after a quiet spell
  • check Booking notes read before a confirmation is drafted

The week

Ask questions across venues

Use the same records for service, follow-ups and the weekly review.

  • check Expected covers by date, venue and source
  • check Group enquiries awaiting an answer
  • check Old services with no final outcome recorded
  • check Guest records due for a retention review

Your rules

Change the brief as the restaurant changes

Build reports around the decisions your team actually makes.

  • check Your name and colours on internal service sheets
  • check A named kitchen acknowledgement for each declared allergy
  • check Your own fields and new read-only briefings
  • check Your booking channels connected as agreed custom work

Make it yours

Design your own ResDiary replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Reservations for Claude Code

Connected to your own database

Who is due next, and what does the team need to know?

DEMO-101

Venue
Harbour Kitchen
Guest
Mere Wilson
Arrival
2026-10-01 11:17
Finish
13:17
Dining_table
Window 1
Covers
4
Status
confirmed
Allergy_note
Peanut allergy reported

DEMO-102

Venue
Harbour Kitchen
Guest
Alex Chen
Arrival
2026-10-01 11:17
Finish
13:17
Dining_table
UNASSIGNED
Covers
6
Status
confirmed

DEMO-103

Venue
Laneway Dining
Guest
Priya Shah
Arrival
2026-10-02 08:17
Finish
10:17
Dining_table
Courtyard
Covers
5
Status
enquiry

Ask it anything

Ten questions the working version answers

These questions run against the demo records below. Your version uses your guest history and house rules.

chat_bubble Which bookings still need a kitchen handover?
chat_bubble Who has missed visits and booked again?
chat_bubble Which upcoming parties have no seating assignment?
chat_bubble Which completed diners have been away for sixty days with no booking ahead?
chat_bubble Which channel brought the most covers at each venue?
chat_bubble Which past services still have no recorded outcome?
chat_bubble Which group enquiries are waiting for an answer?
chat_bubble Which guest records are past their retention review date?
chat_bubble What covers are expected by date, venue and booking source?
chat_bubble What are the booking history and notes behind this guest name?

Switching

How to switch from ResDiary

Moving off ResDiary means exporting your booking history, loading it into the new guest book as a preview first, checking what the import flags, and running both systems side by side before you cancel the ResDiary subscription.

  1. 1

    Export your booking history

    Export what your ResDiary account allows, usually CSV or Excel, using the booking details report ResDiary documents. Check with ResDiary support to confirm the exact export path for your plan, and include guest contact details in the columns you export if your account lets you choose them. This booking export is the entry point for everything that follows.

  2. 2

    Run a preview import first

    Load the export into the new system as a preview first, before anything is committed. The importer checks column headings and timestamps, and it can roll back the whole file if something looks wrong, so nothing half loads. This lets you see how your ResDiary bookings and guest details map into the new guest book without touching live records.

  3. 3

    Review what the import flags

    Once the preview runs, look at what it flags: columns it could not match, timestamps missing a clear time zone, or guest records it treated differently than expected. This is where you agree how your ResDiary headings map to the new fields, and what happens to older bookings, cancellations, and anything like marketing permissions or payment records that need their own separate handling.

  4. 4

    Run both systems side by side

    Keep taking bookings in ResDiary while the new guest book runs alongside it for a short period. Compare service sheets, covers, and guest notes between the two each service. This is how you catch anything the import missed or mapped wrong before staff rely on the new system on its own for a live service.

  5. 5

    Switch off ResDiary

    Once a full service has run cleanly on the new system and staff trust the guest history, seating, and kitchen handovers, cancel the ResDiary subscription. Keep your existing online booking channel connected until it is rebuilt into your custom version, so guests can still book without any gap in service.

construction

Where the real effort goes

The real work is in mapping your ResDiary columns to the new fields, deciding how much guest history to bring across, and handling separate records like marketing permissions or payments that need their own agreed migration. Enterprise DNA does this mapping and reconciliation for you when you have them install and run your version.

Not ready for a call?

Get your ResDiary switch plan by email

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

  1. 1 Clone Reservations for Claude Code and install the dependencies
  2. 2 Run npm run demo and open the folder in Claude Code, Codex, OpenCode or Cursor
  3. 3 Check your export headers, then run the documented import preview
  4. 4 Set up your real database, seating and booking channel before cutover
Get it on GitHub

Built around your business

We customise it

A scoped setup fee

  • check Your fields, house rules and service briefings
  • check Your ResDiary bookings and guest details mapped and checked
  • check A web front end or a different technology stack where you need it
  • check Booking channels and connections built to the agreed scope
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 migration checked against the original booking export
  • check Backups and operating support agreed for your venue
  • check Ongoing changes as your service and guest needs change
Book a call

Questions

Instead of ResDiary, answered

Does the free version replace our online booking widget? expand_more

It starts with your guest book, service sheets and follow-ups. Enterprise DNA builds the booking interface and channel connections your venue needs into your custom version. Keep your existing booking channel until the replacement is tested.

Can we bring our ResDiary history with us? expand_more

Yes, through the booking details export that ResDiary documents. The free version imports bookings and their guest contact details using selected columns. We check your actual export, map different headings and reconcile the dates and covers. Separate customer lists, marketing permissions and payment records need their own agreed migration work.

Will the kitchen know about a guest allergy? expand_more

Recorded dietary needs appear on the internal kitchen handover, with a named acknowledgement. This shows that the note was received. The kitchen still verifies ingredients and preparation with the guest before serving.

How does the cost compare with ResDiary? expand_more

ResDiary Express lists A$170 a month and Pro A$220, plus GST. The free version has no licence fee, while hosting and your chosen assistant have their own costs. Enterprise DNA charges an agreed setup fee followed by a retainer to operate your version.

Can we use our own screens and service rules? expand_more

Yes. We build your fields, seating rules, reports and staff interface around your restaurant. Start with the working guest book, agree the booking channels and connections, then test a service before switching.

Show Sam how your restaurant runs

Book a 30-minute call with Sam. Bring your ResDiary bill, an example of the booking export and the service decisions your team keeps chasing. We will agree what your version needs and how to bring the history across.

Book a call with Sam Get the free version

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

Done paying for ResDiary?

Get your version built