Enterprise DNA

Instead of Salesforce Field Service

Stop renting Salesforce Field Service. Own your service department.

We build your version around how your service team runs: your contracts, your response times, your makers' warranty rules. We bring your Salesforce accounts, machines, contracts and work orders across and run it for you.

Salesforce lists Field Service Technician and Dispatcher licences at AU$245 per user per month, billed annually, on top of a Service Cloud licence. That is AU$2,940 a year for every technician and every dispatcher.

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 licences charge for

You pay per person to see your own service records

Field Service is sold per user, on an annual contract, beside the Service Cloud licence it needs. Most of what the licence buys is the dispatch console and the mobile screens over records you already own.

engineering

Every technician is a seat

AU$245 per technician per month, billed annually. A technician who services three machines a week costs the same as one on the road all day.

support_agent

Every dispatcher is another

The dispatch console is its own AU$245 licence per user. The office pays again to book the work the technicians do.

calendar_month

An annual contract

Salesforce says all per user products require an annual contract. A quiet winter with fewer technicians still pays for the full team.

hub

Service Cloud beside it

Field Service needs at least one Service Cloud licence before the first technician can log in.

layers

More for the full set

Field Service+ Core is AU$350 per user per month, and Field Service Max is AU$910. The deeper features cost more per head.

group_add

Contractors cost too

A subcontracted technician on Contractor Plus is AU$112 per user per month, for the people you do not even employ.

Your owned version

Built around the service department you already run

The installed base

Every machine, where it stands and what covers it

Each unit you sold or service, at each customer's site, with its serial, run hours, warranty and contract.

  • check Planned maintenance by date or run hours, whichever comes first
  • check Hour readings that can never go backwards
  • check Machines at contract customers that are not on the contract
  • check Statutory inspections due, with the rule behind each one

The contracts

What you promised, and whether it pays

Each service agreement with its units, its response time, its term and what it cost you to service this year.

  • check Margin per contract: labour at cost, parts at cost, warranty recoveries left out
  • check Breakdowns met and missed against each promised response time
  • check Renewals inside the notice window, with the year's record drafted
  • check Contracts that ended but are still being serviced for free

Warranty money

The repairs the maker still owes you for

Every repair on a machine still under the maker's warranty is checked for a claim, against that maker's own claim window.

  • check Days left to lodge each claim, maker by maker
  • check The claim drafted from the job: fault, hours, parts and labour
  • check Claims with the maker longest, ready to chase
  • check Each maker's rejection rate and the reasons given

The rules

The checks an auditor or a customer asks about

Maintenance as the manufacturer recommends, by a competent person, with the source of each rule named.

  • check Technicians booked on work their ticket no longer covers
  • check Licences and maker training expiring this month
  • check Installs closed with no commissioning checklist filed
  • check Service reports and contract schedules in your own brand

Make it yours

Design your own Salesforce Field Service replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Equipment Service for Claude Code

Connected to your own database

Which of our service contracts lost money over the last 12 months?

K-RIVER

Customer
Rivermill Bakery
Kind
Full service
Annual value
$4,800.00
Jobs 12 months
3
Labour cost
$910.00
Parts cost
$4,410.00
Margin
-$520.00
Margin pct
-11
Note
under a year old

K-ORCH

Customer
Orchard Hill Dairy
Kind
Planned maintenance
Annual value
$2,400.00
Jobs 12 months
1
Labour cost
$210.00
Parts cost
$0.00
Margin
$2,190.00
Margin pct
91

K-GREEN

Customer
Greenleaf Produce
Kind
Planned maintenance
Annual value
$3,900.00
Jobs 12 months
3
Labour cost
$699.00
Parts cost
$0.00
Margin
$3,201.00
Margin pct
82
Note
under a year old

K-NORTH

Customer
Northgate Logistics
Kind
Full service
Annual value
$12,000.00
Jobs 12 months
1
Labour cost
$325.00
Parts cost
$0.00
Margin
$11,675.00
Margin pct
97
Note
under a year old

K-HARB

Customer
Harbour Cold Stores
Kind
Full service
Annual value
$18,600.00
Jobs 12 months
5
Labour cost
$720.00
Parts cost
$2,671.00
Margin
$15,209.00
Margin pct
82
Note
under a year old

Ask it anything

Ten questions this build answers today

Each one runs against the included fictional equipment dealer. Ask them in plain words.

chat_bubble Which service contracts cost us more in labour and parts this year than the customer pays?
chat_bubble Which repairs on machines still under the maker's warranty have no claim lodged, and how many days are left to lodge each?
chat_bubble Which breakdowns did we reach after the response time the contract promises, and which customers keep getting the late visits?
chat_bubble Which machines are past their planned service by date or by run hours, and which of those has nobody booked?
chat_bubble Which customers have a contract with us but own machines that are not on it?
chat_bubble Which machines have broken down three or more times in a year, and which of those are still in warranty?
chat_bubble Which technicians are booked on work their licence or ticket no longer covers?
chat_bubble What share of each maker's warranty claims gets rejected, and why?
chat_bubble Which contracts end inside their renewal notice window, and which ended but are still being serviced?
chat_bubble Which chargeable jobs are done and still not invoiced?

Switching

How to switch from Salesforce Field Service

The move involves exporting your core service records, checking the import, and running both systems side by side before you switch.

  1. 1

    Export your Salesforce records

    Ask your Salesforce administrator to export Accounts, Assets, Service Contracts, Contract Line Items and Work Orders through Salesforce Data Export. If your account does not offer that path, check with Salesforce Field Service about what export options it allows. Keep the export files together so you can load the records in the required order.

  2. 2

    Dry-run each import

    Start with a test run of each import, in this order: accounts, assets, service contracts, contract lines and work orders. Map any column names that differ from the fields Equipment Service expects. Check the results before loading records for real, and make changes to the mapping or source data if needed.

  3. 3

    Load records and check flags

    After the test runs look right, import the records in the same order. Review anything the import flags, such as a row it cannot process, and correct the source data or mapping before relying on the imported records. Each record keeps its Salesforce reference, so you can bring a later export across without creating duplicates.

  4. 4

    Run both systems side by side

    Keep Salesforce Field Service available for a short period while you check that Equipment Service has the records your team needs. Compare key account, machine, contract and work order details, and confirm that maintenance plans and on-site times have been brought across as part of setup. Resolve gaps before you stop using Salesforce.

  5. 5

    Switch off Salesforce Field Service

    Once you have checked the imported records and are ready to work from Equipment Service, stop entering new service work in Salesforce Field Service. Keep any records you still need according to your own business requirements, then cancel or switch off the Salesforce service under your account arrangements.

construction

Where the real effort goes

The import is usually not the main work. You need to map your own field names and rules, and decide which history to bring across. Maintenance plans and on-site times need setup beyond the main export, so check those separately. If Enterprise DNA installs and runs Equipment Service for you, they handle this part of the move.

Not ready for a call?

Get your Salesforce Field Service switch plan by email

We will send you the step-by-step plan for moving your business off Salesforce Field Service, 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 service records

Open source

Do it yourself

Free, MIT licence

  1. 1 Clone the repo and run npm install
  2. 2 Run npm run demo to see a fictional equipment dealer
  3. 3 Open it in Claude Code, Codex, OpenCode or Cursor
  4. 4 Import your Salesforce Data Export, then run the Monday review
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your contract types, response times and makers' claim rules
  • check Your Salesforce accounts, machines, contracts and work orders brought across
  • check A technician phone app or web screens if your team wants them
  • check Service reports and renewal letters in your format
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and run inside Omni by Enterprise DNA
  • check Connected to your accounts system and parts stock
  • check The Monday service review ready before the meeting
  • check Changes, backups and support handled for you
Talk about your service team

Questions

Instead of Salesforce Field Service, answered

What does Salesforce Field Service cost? expand_more

Salesforce lists the Technician and Dispatcher licences at AU$245 (US$175) per user per month, billed annually, on an annual contract, and it needs at least one Service Cloud licence beside them. Field Service+ Core is AU$350 and Field Service Max is AU$910 per user per month. Your own contract may differ from the list price.

Our technicians live on their phones. What do they use? expand_more

The free version has no phone app: technicians ring or message the office, and the office records the visit by asking. Most dealers we build for want an app, so we build a small one for your technicians on top of your own database, with no charge per person.

Do our records come across from Salesforce? expand_more

Yes. Your administrator exports accounts, machines, service contracts, the contract lines and work orders from Salesforce's own data export, and they come across in that order, each keeping its Salesforce reference so nothing doubles up. Maintenance plans and on-site times sit elsewhere in Salesforce, and we bring those across as part of the setup.

Is this trades job management? expand_more

No. It is built for dealers and distributors who service the machines they sold: forklifts, compressors, generators, refrigeration, access and kitchen equipment. The record is the machine and its contract, not a one-off job for a homeowner.

What do we pay Enterprise DNA for? expand_more

One setup fee, then a retainer. We bring your Salesforce records across, set your contracts, response times and makers' claim rules, build the technician app if you want one and run the Monday review for you inside Omni. The free version costs nothing to use yourself.

Bring your seat count and last year's contracts

Spend 30 minutes with Sam going through how your service team runs, what Field Service costs you per technician, and which of your contracts your own version would show losing money on Monday morning.

Book 30 minutes with Sam Get the free version

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

Done paying for Salesforce Field Service?

Get your version built