Simpro alternatives

Simpro, AroFlo, ServiceM8 and Tradify alternatives: should you switch?

If you're looking for a Simpro alternative, or one for AroFlo, ServiceM8 or Tradify, something has stopped working. Before you shortlist the replacement, work out what.

Nobody searches for a Simpro alternative, or a ServiceM8 alternative, when things are going well. Something's rubbing. Maybe it's been rubbing for a while.

First, though: all of these packages are competent. Simpro, AroFlo, ServiceM8 and Tradify are reliable, well-supported products, and when they're configured well they're very good. The businesses I see leaving them usually aren't leaving bad software. They've grown out of it.

So the useful question to start with is what's changed in your business that the software can't keep up with. Answer that and the alternative mostly picks itself. Sometimes it's a different package. Quite often it isn't.

Why businesses outgrow their job software

In my experience it comes down to a handful of reasons.

Something becomes core that the package doesn't do. A way of pricing, a compliance step, a kind of job you didn't used to do much of. At first it's a side thing and a spreadsheet covers it. Then it becomes key to the business, and the spreadsheet is now holding up something important.

The business gets clear on what it needs to control. This one's a good problem to have. The owner works out where the business really needs to focus, what has to be checked and signed off, which numbers matter. Then they find the system won't let them put those controls in place, or won't report the way they need to see it.

The business takes a turn. A new pillar gets added, or the work shifts in a different direction. A service business takes on bigger projects, or a project business starts a maintenance arm. The software suited the old business fine, but it isn't flexible enough to turn with the new one.

It's too complicated for what should be simple. This is mostly a Simpro and AroFlo complaint. There's a lot in them, and some teams feel the software makes a simple part of their day harder than it needs to be. ServiceM8 and Tradify tend to get the opposite complaint: they're simple, and the business has outgrown simple.

Businesses outgrow software when the business changes. The software usually didn't get any worse.

If you're coming from ServiceM8 or Tradify, the turn is often the shift from service jobs to projects. I wrote about that split, and which software suits which, in job management software for trades.

Before you switch: work down the list

There are a lot of answers to "what's the alternative to Simpro?" Moving off it is only one of them. I'd work down these in order.

  1. 1
    Ask the software again It changes all the time. Take the specific problem to someone who knows it well.
    Cheapest
  2. 2
    Build the missing piece on the side Keep the core system, connect the one thing it can't do.
  3. 3
    Move When the business has turned too far for the first two to work.
    Biggest change
Work down in order. If you reach step 3, you'll know exactly what the next system has to do.

1. Ask the software again

If you're already on the platform, it's worth the ask. These packages change and update all the time, and the thing you couldn't do two years ago might be a setting now. Sit down with someone who knows the software properly, explain the specific thing you're trying to solve, and see what comes back. It costs very little, and sometimes the answer is already sitting there.

2. Build the missing piece on the side

If the package can't do it, the next question is whether something next to it can. You keep the core system doing what it's good at and build the one piece that's missing, connected to it so nobody's re-keying.

Whether that's practical depends a lot on how open the software is:

Package Can you build around it?
Simpro Yes. A mature API that reaches all the major records, plus around 250 partner apps in its marketplace. It's extensive enough that building on the side is often the better answer to leaving
ServiceM8 Yes. A working API with webhooks, so other systems can react when a job changes
AroFlo Partly. There's an API, but it has a daily cap on calls. Fine for light syncing, awkward for anything heavy
Tradify Not really. No public API, no webhooks. Its accounting connections are about it

That's from our own reviews of each package, which go into more detail.

The cheapest switch is the one you don't have to make. Build the missing piece first, then decide.

3. Move

Sometimes the business has turned so far that you can't get what you need out of the software anymore, even with something built next to it. That's a valid reason to go. If you get here having tried the first two steps, you'll also know exactly what the next system has to do, which makes choosing it a lot easier.

Simpro vs AroFlo

People often compare these two, so it's worth knowing they're the same company now. Simpro bought AroFlo in 2021, in the same US$350 million K1 deal that took in ClockShark. AroFlo still runs under its own brand and team. They're similar pieces of software and I'd expect them to come together at some point.

The differences that matter day to day, from our reviews:

  • Simpro sits best with commercial electrical, plumbing, HVAC, fire and security businesses in the 20 to 50 staff range, especially ones running bigger commercial jobs with several cost centres and stages. Pricing isn't published, and contracts are commonly reported at three to five years, so check the exit terms before you sign.
  • AroFlo covers similar trades from a handful of staff up, at a published A$80 per user per month with a three-user minimum. It has Gantt views for project work and more than 600 supplier catalogues built in.

Both grew out of service work and stretch to cover projects. If your business is mostly projects, that's the thing to test hardest in a demo.

If you do switch

Work out which kind of job your business actually runs, then look in the right camp. For lots of short service jobs, Fergus and ServiceM8 are the usual names. For bigger service businesses, Simpro, AroFlo and Ascora. For project-first work, NextMinute, Workbench and the builder-focused tools. The job management software page lays out all four camps.

A commercial plumbing contractor tried to put AroFlo in for their project work and really struggled with it. It didn't cover the things they needed, so the project side ended up custom-built around how they run. When they later started doing service work, they bought Fergus off the shelf, because service plumbing is common enough that a package already does it well. Switching was right for one half of the business and wrong for the other.

Hyforce Engineering went the other way. They had a field service system that made them work its way and charged them for the privilege. They replaced it with one built around how they run, on the Office 365 they already paid for, and their licence costs went down.

Bring your people with you

There's one more thing to take into the search, and it's the one most often skipped.

When a business changes its software it's usually because of some kind of pressure, and the people doing the work feel that pressure too. So getting them on board usually isn't hard. What matters is understanding their take: what actually works in the current system and what doesn't. The person who uses it every day knows things the owner doesn't, and some of what they like about the current software you'll want to keep.

Have that with you when you go looking for an answer. It'll stop you swapping one set of problems for another. (There's more on this in the project failures I keep seeing in trades and construction businesses.)

The people using the software every day know what to keep. Ask them before you choose the next one.

Where to start

If you're not sure which of the three steps you're at, the fit check takes a few minutes and is a good place to start.

Or talk it through with us. Our work starts with a fixed-price entry package, from $10,000 ex GST: time in your business working out what's really going on, then hours on the first problem. That might be getting more out of the system you've got, building the piece it's missing, or choosing and moving to the next one. Get in touch and we'll have a chat.

Simpro alternatives: common questions

What's the best alternative to Simpro?

It depends on why you're leaving. If something specific is missing, check whether Simpro can do it now, then whether it can be built on the side through Simpro's API. If the business has changed direction, look at the camp that suits the work you do now: service apps like Fergus or ServiceM8, other platforms like AroFlo or Ascora, or project-first tools like NextMinute or Workbench.

Are Simpro and AroFlo the same company?

Yes. Simpro acquired AroFlo in 2021 and AroFlo still runs under its own brand and team.

What's a good alternative to ServiceM8 or Tradify?

If you've outgrown them because you're doing bigger, longer jobs, look at the bigger platforms or the project-first tools. If you're staying mostly service and just want something different, Fergus is the usual comparison. Bear in mind Tradify has no public API, so it's harder to build around than ServiceM8.

Can we keep Simpro and add what's missing?

Often, yes. Simpro's API is extensive enough that building the missing piece on the side is a real option, and it's usually cheaper and less disruptive than a migration.

How hard is it to move off Simpro or AroFlo?

Harder than getting on. AroFlo has no one-click full export, so expect to pull data out through reports or its API. With Simpro, check your contract's exit terms before anything else.

Not sure whether to switch?

Tell us what's stopped working. We'll tell you whether to get more out of what you've got, build the missing piece, or move.

Get in touch

Let’s talk about your business

Tell us what you’re working through and we’ll get back to you shortly.

Prefer email?
hello@thetechyside.com.au