Instead of XTRF
Stop renting XTRF. Own your translation agency system.
For translation and interpreting agencies in Australia and New Zealand. We build your version around how your project managers work, bring your XTRF clients, vendors and projects across, and run it for you for one setup fee, then a monthly retainer that does not grow with every project manager you hire.
XTM, which owns XTRF, publishes no price for it. The pricing page says it is tailored to your project, vendor and financial management requirements, so the bill is whatever your quote and your renewal say.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What you pay for
What the XTRF bill is really for
XTRF is priced privately, per organisation. Most of what the bill buys is screens over records that are already yours: clients, linguists, projects and invoices.
A price you only see in a quote
There is no public price list. The number arrives after a conversation with sales, and the renewal is the vendor’s to set.
Seats for project managers
The people who run your projects are the people who log in. As the team grows, so does the question of who gets access.
Portals and extras
Client and vendor portals, connections to translation tools and the reporting on top are the parts that make it feel like a product.
Reports someone else designed
Revenue by client and jobs by vendor are on the menu. What each client and language leaves after paying the linguists is the question you still answer in a spreadsheet.
Screens over your own records
Your clients, your linguist panel, your rates and your project history. What you rent is the view over them.
A rent that never stops
Every year you trade, the system that holds your clients and your linguists is rented back to you.
What you get instead
One system you own, with every rule checked before the work goes out
The panel
Who can take this job, today
Every linguist with the directions they work in, their NAATI credentials, competence record and confidentiality agreement.
- check Ask who can take Persian into English certified work and get the names that hold a current Certified Translator credential in that direction
- check Interpreters found by language, setting and time, with anyone already booked that hour named
- check NAATI credentials coming up for renewal named 90 days ahead, with the reminder drafted
- check Language pairs with only one linguist named, so a revision never has nobody to do it, which a vendor list does not tell you
The rules
NAATI and ISO 17100 checked before anything goes out
The rules an agency works under, built in as checks with their sources named.
- check Nobody revises their own translation, and nothing is delivered until a second linguist has finished revising it
- check A certified translation goes only to a NAATI Certified Translator in that direction, current on the due date
- check Court and legal bookings get a Certified Interpreter or above, and no interpreter is booked twice in the same hour
- check Nobody gets client documents or a session without a signed confidentiality agreement on file
The margin
What every client and language leaves after the linguists
What the client paid and what the linguists were paid, from the same records.
- check Each client’s work against what it cost in translators, revisers and interpreters, thinnest margin first
- check Every item under your target named, with the rate that put it there
- check Interpreting billed by the minimum then 15 minute steps, and late cancellations charged by your rules
- check Ask which language pairs make money and which only fill the diary
Billing and pay
Invoices and linguist pay from the same records
What the client is charged and what the linguist is paid follow the work that was done.
- check Draft invoices for delivered projects, finished sessions and late cancellations, one per client, with their order number on each line
- check A pay run per linguist for finished work, with remittance advice, and nobody paid twice
- check Certification statements for certified translations with the translator’s NAATI number, ready to sign and stamp
- check Quotes, booking confirmations, job offers and overdue reminders drafted for a person to send
Make it yours
Design your own XTRF replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from XTRF. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your XTRF 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 Translation Agency for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.
Translation Agency for Claude Code
Connected to your own database
What needs my attention this morning?
Needs a decision, worst first
[1] PAST DUE P-1006 Fernhill Wines Export price list, due 2026-10-16, 2 days late
[1] BOOKING UNCOVERED B-5004 Eastern Health Network Somali, onsite, medical, Mon 19 Oct 14:00
[1] INTERPRETER NOT CREDENTIALED B-5003 Collins Street Legal Lina Nguyen has only Certified Provisional Interpreter in Vietnamese; court work needs Certified Interpreter or above on 20 Oct
[1] CERTIFIED, TRANSLATOR NOT CERTIFIED P-1004 Kestrel Migration Reza Karimi: no current NAATI Certified Translator credential fa > en on 2026-10-20
[2] JOB LATE P-1006-T Fernhill Wines translation by Yuki Tanaka, due 2026-10-15
[2] DUE SOON, NOT READY P-1004 Kestrel Migration Police certificate and degree, due 2026-10-20: 1 job(s) with nobody on them, 1 in progress
[2] NO REVISER P-1007-T Collins Street Legal translation done 2026-10-17 by Hana Kim, its revision has nobody on it
Ask it anything
Questions XTRF cannot answer
Every one of these is a real question the demo answers today. Yours will be different, and that is the point.
Switching
How to switch from XTRF
A move involves exporting your client, vendor and project lists, testing the import, checking the records and entering some source information fresh.
- 1
Export core records
In XTRF, export the Clients, Vendors and Projects views as CSV. XTRF provides an Export button on every view. These are the lists the importer brings across, including vendor language combinations and projects. Before you begin, confirm you can access the views and export the records you need. Ask XTRF if your account does not allow it.
- 2
Run a test import
Have the XTRF records loaded with a test run first. The importer can match common column name variants, read vendors' language combinations as work directions, and split projects with several target languages into one project per language. A test run shows rows it cannot read, so you can review the result before the records are added for real.
- 3
Load the records
After the test looks right, run the import for real. It brings across clients, vendors and projects from the exported lists. The import runs as one transaction and can be repeated without creating duplicates, updating records instead. Do not expect credentials, competence records or confidentiality agreements to come across. Enter those fresh from the source records.
- 4
Check what needs attention
Review every row the test names as unreadable or skipped, and resolve any gaps before relying on the new records. Check that clients, vendor language directions and projects look right, including projects split by target language. Enter NAATI credentials, competence records and confidentiality agreements from their source records, since the system's checks rely on them.
- 5
Run both, then switch
Keep XTRF and the new system available side by side for a short period. Use that time to check the records and confirm your team can find the client, vendor and project information it needs in the new system. Once you are satisfied that the required records and fresh credentials are in place, move the work to the new system and switch off XTRF.
Where the real effort goes
The import covers clients, vendors and projects, not every part of your XTRF history. The work is usually deciding which history to bring, mapping your fields to the new records, and setting up your rules. NAATI credentials, competence records and confidentiality agreements need fresh entry from source records. Enterprise DNA handles this migration work when you have them install and run it.
Not ready for a call?
Get your XTRF switch plan by email
We will send you the step-by-step plan for moving your business off XTRF, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your XTRF switch plan is on its way.
Rather talk it through? Book a call arrow_forwardThree ways to run it
Run it yourself, have it shaped to your agency, or have it run for you
Open source
Do it yourself
Free
- 1 Clone the repo
- 2 npm run demo, then open the folder in Claude Code
- 3 Type /attention
- 4 Import your XTRF exports and point it at your own database
Built around your business
We customise it
One setup fee
- check Your languages, rate cards, client rates, cancellation rules and documents written in
- check Your XTRF clients, vendors and projects brought across, with every linguist’s NAATI credentials checked one by one
- check A client portal for uploads, a linguist portal for job offers, or a web front end for the office, if you want one
- check Handed over for your project managers to run
Omni by Enterprise DNA
We run it for you
One setup fee, then a monthly retainer
- check Everything in the customised version, installed and connected
- check The morning list, credential renewals, quote follow-ups, billing runs and linguist pay runs done for you
- check New linguists, languages and clients added as you grow, with no fee per project manager
- check It runs inside Omni, our managed Command Centre, with the rest of your business
Questions
Instead of XTRF, answered
Is the free version really free? expand_more
Yes. It is open source under the MIT licence. Run it on your own computer or your own database, change anything, and you never need an account with us.
Does it connect to our translation tools? expand_more
Not in the free version. Word counts are entered from your translation tool’s analysis, and the files stay where they are now. Pulling word counts and files across from your tools is part of a custom build.
What about the client and vendor portals? expand_more
The free version has none: clients email their files and linguists reply to job offers by email, which is how most small agencies already work. Enterprise DNA builds a portal for uploads or job offers into your version, writing into the same records.
Can we bring our history across from XTRF? expand_more
Clients, vendors with their language combinations, and projects come across from the lists XTRF lets you export, with a test run first that names every row it could not read. NAATI credentials, competence records and confidentiality agreements are entered fresh from the source, because every check rests on them.
Does it do our accounts or pay our linguists? expand_more
No, on purpose. It drafts the client invoices and the linguist pay runs from the finished work and keeps track of what is owed both ways. Sending invoices, paying people and the books stay in your accounts system and your bank.
Find out what XTRF costs your agency each year
Bring your last XTRF invoice or renewal. In 30 minutes Sam works out what you pay per year, what you actually use, and what one system you own would replace it with. If it is a fit, we build it and run it. If it is not, take the free version and run it yourself.
Translation Agency for Claude Code is free and open source, published by Enterprise DNA.
Done paying for XTRF?
Get your version built