How to spot a fly-by-night job management app

When we were choosing a name for Service Ninja, we ran dozens of options through the trademark registers. Every single one was already taken by some piece of software. A lot of them were job management apps, and a lot of those looked like they'd popped up overnight. Not the established players you'd recognise. New ones. Dozens of them.

That's what AI coding tools have done to this market. Building an app has become cheap and easy. Building a good one still takes a lot of work and a lot of knowledge, and the gap between those two things is where the fly-by-nighters live.

There's now a Temu version of every job management app. Same screenshots, a third of the price, and about the same lifespan.

It matters more for job management than for almost any other software you'll buy, because the stakes are high. Your whole business runs on it. Quoting, scheduling, invoicing, timesheets, compliance. If it fails, the costs escalate fast. Downtime is not something a trade business can afford.

So before you move your business onto a new app, here's what to check.

1. Look at their website

This is the fastest tell. A job management app is a huge thing to build properly. Anyone who's done that work, and wants to launch it properly, will have taken the time to build a decent website. If all you find is a thin one-pager with no real information on it, the product behind it is probably just as thin.

2. Ask what problem they're solving

You want one clear sentence back. "Quotes take too long to build on site." "Compliance paperwork gets missed." "Owners spend every evening on admin." Something specific.

A new job management app should exist because there's a real gap in the market. These things are enormous to build, and the established products already do the basics well. Nobody sensible puts in that amount of work just to make another app that does what Tradify and Fergus already do, because there's no money in it. So if they can't name the gap they're filling, either they haven't thought about it, or the real plan is to be cheap.

Which brings me to price. I've sat through a demo where the entire pitch was that they were cheaper than everyone else. If price is the point of difference, there's a good chance nobody took the time to build something properly or work out what trade businesses actually need. They've slapped something together and they want to sell it and make a bit of money. That's not the same as solving your problem. It's Temu software: looks like the real thing in the listing, and you find out the difference after you've bought it.

3. Ask if they understand your market

Ask what Fergus does well. Ask where Simpro falls short. A team that's studied this market can answer with specifics, because that's how they worked out where they fit. A team that hasn't will say something about being modern and easy to use, which describes every app ever built.

4. Ask who's using it, and ask to talk to them

This is the big one. Ask which businesses are running on the app right now, and whether you can ring one of them.

Then ask where those businesses are. Businesses run differently in different countries. Different compliance, different tax rules, different ways of working. An app that's been battle-tested in Texas hasn't been battle-tested in Auckland. If you're going to run your business on something, you want to know it's got real users in your neighbourhood, hitting the same problems you'll hit, and that the developers have fixed them.

If they can't name anyone, you're the test site.

5. Ask how long it took and who built it

"A year, with experienced developers" is a different answer from "a few weeks." Not because slow is good, but because doing it properly takes time. Testing, fixing what breaks in real use, and building it so it stays up when six vans are relying on it. Ask whether the developers have built and supported production software before. You're not looking for a technical answer. You're looking for whether the answer comes easily.

What actually goes wrong

If you pick the wrong one, here's what you're signing up for.

It doesn't work well, and you're stuck with it. You've done the migration, you've trained the team, and you can't face doing it all again, so you put up with a crappy app. Most people don't realise the cost of not using a good one.

It goes down, and nobody's there to fix it. Bugs are inevitable in software. The question is whether there's someone on the other end who owns the problem and fixes it fast.

Improvements never come. There's always something that could be better, and a company that isn't charging enough to fund the work, or doesn't care enough to do it, won't make them.

It isn't safe. By safe I mean three things. Your data can't be lost, so if the company folds or a server dies, your customer list, your pricing and every quote you've ever sent don't go with it. Your data can't be stolen, so a breach doesn't hand your price book and your customer list to someone else. And the app is there when you need it, not down for a morning while your team stands around. Two easy checks: ask whether they'll put uptime in writing, and ask whether you can export everything and walk away any time. A company that's built things properly has good answers to both.

Where we stand

It's only fair to put Service Ninja through the same list, because we're a young company too.

I run Legacy Electrical, an electrical contracting business in Auckland. Over the years I've run it on four different job management apps, and every one of them left gaps. Service Ninja exists to close the ones that mattered most.

It's a partnership. I bring the trade side: years in the industry, a business to run it in, and enough time on the competing products to know where they're good and where they fall short. My co-founders are experienced software developers who've built and supported serious systems for a long time, and they own a real stake in this. Nobody's a contractor here. We've spent a year building it together, not a weekend, and it's been running inside Legacy on real jobs the whole way, with my staff finding the problems and the dev team fixing them.

Ask us the questions on a call. Then ask the next company the same ones. That's how you'll know whether you're buying the tool or the Temu version of it.

Alex is a registered electrical inspector and director of Legacy Electrical in Auckland. He's a co-founder of Service Ninja, which Legacy runs on every day.