Enterprise DNA

Instead of Tourwriter

Stop renting Tourwriter. Own your itinerary system.

We build around how your travel designers quote and prepare trips, map your Tourwriter history, and run your version through Omni by Enterprise DNA.

Tourwriter Pro starts at US$149 per user monthly, billed annually, excluding local sales tax. Premium is priced on request.

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

Your travel operation, priced by plan

Tourwriter bundles itinerary work into plans. The alternative is a version built around your own operating rules.

person

A plan for a solo designer

Starter is for one person, from US$99 per month billed annually, excluding local sales tax.

groups

A price for each team member

Pro covers teams of two to five. Twelve months at its starting rate is US$1,788 per user before tax.

route

Itinerary allowances

Starter lists up to 25 itineraries a year. Pro lists up to 50. Premium lists unlimited itineraries.

payments

Agency and accounting features

Pro includes agency commissions and bill and invoice exports for MYOB or QuickBooks.

insights

The Premium bundle

Business Intelligence, multiple brands and multi-language itineraries appear in Premium.

settings

Setup as well as subscription

Tourwriter lists a one-time setup package from US$1,199, excluding local sales tax.

Your own operation

From a seasonal rate to a departure-ready trip

Quote

Know the margin before the proposal goes out

Cost the actual services and deduct the agency commission agreed for that itinerary.

  • check Dated supplier rates with room, person, vehicle or group units
  • check Recorded exchange rates for supplier costs
  • check Margin after the agreed agency commission
  • check Imported totals kept separate from current costing

Prepare

See what can hold up a departure

Review confirmations, tasks, traveller counts and deposits together for each trip.

  • check Requested services with named suppliers and due dates
  • check Open preparation tasks assigned to a consultant
  • check Missing traveller names compared with the expected party
  • check Overdue deposits after externally reconciled receipts

Deliver

Produce the paperwork from the trip records

Generate draft quotations, travel itineraries and supplier paperwork in your business identity.

  • check Traveller quotations keep supplier costs private
  • check Confirmed-service vouchers retain the confirmation reference
  • check Rooming lists use recorded names and room assignments
  • check Supplier chase drafts stay unsent for review

Own

Change the records and the questions together

Tourwriter offers configurable reporting. With your own version, you can also change the underlying fields and rules.

  • check Combine your preparation policy with trip margins
  • check Set your own supplier evidence checks
  • check Keep operational bills separate from your accounting ledger
  • check Export the records and extend your reports without a plan upgrade

Make it yours

Design your own Tourwriter replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Itinerary for Claude Code

Connected to your own database

Which trips still need preparation work?

NZ101

Me tr
Southern Lakes Discovery
Avel_date co
2026-10-12
Nsultant cu
Mia
Rrency st
NZD
Atus aw
confirmed
Aiting_confirmation op
2
En_tasks un
1
Named_travellers ov
10
Erdue_deposit_cents te
NZD 1000.00
Rms_recorded
false

NZ103

Me tr
Alpine Spring Group
Avel_date co
2026-10-19
Nsultant cu
Mia
Rrency st
NZD
Atus aw
confirmed
Aiting_confirmation op
0
En_tasks un
0
Named_travellers ov
8
Erdue_deposit_cents te
NZD 0.00
Rms_recorded
true

Ask it anything

Ten questions this version answers

These run against the free version today. Tourwriter also offers configurable reporting. The difference here is ownership of the records and the rules.

chat_bubble Which trips combine unconfirmed services, open tasks and overdue deposits?
chat_bubble What margin remains after each itinerary’s agreed agency commission?
chat_bubble Which consultant has the most open preparation work in each currency?
chat_bubble Which supplier bills are overdue after recorded payments?
chat_bubble Which supplier rate seasons need replacing before the next quote?
chat_bubble Which requested services face an approaching cancellation deadline?
chat_bubble Which quotes have expired while the traveller has gone quiet?
chat_bubble Which departures still lack named travellers?
chat_bubble Which adventure supplier records lack registration evidence for the trip date?
chat_bubble How do imported itinerary totals compare with services we have costed locally?

Switching

How to switch from Tourwriter

A move like this involves exporting the records you need, mapping them to the new database, checking the import and running both systems side by side before you switch.

  1. 1

    Export your Tourwriter records

    Start with an Itineraries detail report, which Tourwriter reports can export to CSV. It includes itinerary headers and can include financial summaries. Supplier rates, services, allotments, traveller names and payment history need separate exports and mapping. Export what your account allows, usually CSV or Excel, and check with Tourwriter about how to export records that are not in the report.

  2. 2

    Load a mapped sample

    Map the selected report columns to the fields in the new database, then test the import before loading records for day-to-day use. The import accepts itinerary headers and optional financial summaries. A test run checks the mapping without keeping the imported records. Do not expect a summary report to bring across supplier details, services or passenger names.

  3. 3

    Review import results

    Check the import results and resolve anything that needs reconciliation before relying on the records. Identical records are skipped. If an existing record has changed, the import stops so you can review the difference. Check imported financial summaries separately from current service costing, and confirm that the records you need from separate exports have been mapped too.

  4. 4

    Run both systems side by side

    For a short period, keep Tourwriter available while you check the new database against your live work. Compare selected itineraries and financial summaries with Tourwriter, and verify separately imported supplier, service, passenger and payment records. Use the comparison to find missing records or mapping issues. Keep Tourwriter as your working system until you are satisfied the new records are usable.

  5. 5

    Switch off Tourwriter

    After you have reconciled the records you need and are ready to work in the new system, arrange the switch with your team and Tourwriter. Keep any exports and backups you need under your business’s data practices. Confirm that the new system covers the work you plan to move, and that any Tourwriter access or service can be closed without losing records you still need.

construction

Where the real effort goes

The work is usually in mapping your own fields and operating rules, then deciding how much history to bring across. The itinerary report covers headers and optional financial summaries, while supplier rates, services, allotments, passenger details and payment history need separate exports and mapping. If you have Enterprise DNA install and run it, they scope and handle this migration work with you.

Not ready for a call?

Get your Tourwriter switch plan by email

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

Choose who builds and runs your version

Open source

Do it yourself

Free code. Your hosting and agent costs.

  1. 1 Clone the repo and install its dependencies
  2. 2 Run npm run demo and inspect the fictional records
  3. 3 Use Claude Code, Codex, OpenCode or Cursor to follow the included commands
  4. 4 Read the switch guide, map your Tourwriter report columns and test the import
Get it on GitHub

Built around your business

We customise it

One setup fee, then an agreed retainer

  • check Your supplier fields, quote rules and document layouts
  • check Your Tourwriter exports mapped and reconciled
  • check A web front end or different technology where your team needs it
  • check Your agreed accounting and traveller connections built and tested
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 migration checked against the original records
  • check Staff permissions, backups and agreed connections configured
  • check Your weekly quotation and departure routine maintained
Talk to Sam

Questions

Instead of Tourwriter, answered

Can you bring our Tourwriter history across? expand_more

Yes, with a checked migration scope. Tourwriter reports export to CSV. The free import accepts itinerary headers and optional financial summaries after the selected columns are mapped. Supplier rates, itinerary services, traveller names and payment history need separate exports and mapping. We reconcile those as part of your setup.

Will our designers have to work without a traveller website? expand_more

Tell us how travellers receive itineraries today. We build the screens, mobile experience and connections your version needs. The free version produces branded itinerary and quotation drafts from its recorded services.

Can we trust the quote margin? expand_more

You can inspect every recorded cost, selling amount, exchange rate and agency commission. Missing services mean incomplete costing. Imported financial summaries remain separate, so an old total cannot silently replace the current trip detail. We agree and test your tax and commission treatment during setup.

Does it book suppliers or take payments for us? expand_more

The free version records confirmations and reconciled amounts and produces unsent drafts. We scope and test any supplier messaging, accounting or payment connections before they become part of your managed version.

What does Enterprise DNA charge? expand_more

One setup fee, then a retainer for the agreed work. Sam scopes the migration, customisation and operation with you. The code is free to run yourself, with your own hosting and support costs.

Show Sam a trip you are preparing

In a 30-minute call, walk through a quote, a supplier confirmation and the report you wish you had. Sam will scope your version and the work needed to bring your Tourwriter records across.

Book 30 minutes with Sam Get the free version

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

Done paying for Tourwriter?

Get your version built