Simpro and AroFlo have the same owner. They do not have the same API.
Simpro acquired AroFlo in November 2021 and both still sell separately, and neither publishes a price. We have built against Simpro in production and never against AroFlo, so the AroFlo side of this page is its documentation. On that documentation the two differ most where it costs money later: webhooks and daily API caps.
They have been the same company since November 2021
Start here, because most comparisons of these two do not mention it. Simpro announced the acquisition of AroFlo on 24 November 2021, in the same release as a growth investment of more than US$350 million from K1 Investment Management (Simpro press release, 24 November 2021). AroFlo’s own about page now says it is “headquartered in Melbourne, Australia” and “part of the global Simpro Group” (AroFlo, fetched 3 September 2026).
Both companies said at the time that the leadership teams would “operate independently, including continued service on existing products” (Simpro, 24 November 2021), and AroFlo’s then CEO repeated it the next day (AroFlo blog, 25 November 2021). Nearly five years on, both products are still sold under their own names with their own pricing pages and their own developer documentation.
That matters for your decision in one specific way. A salesperson for either product is, ultimately, working for the same group. If you are told one is the natural upgrade path from the other, that is a group product strategy talking, and it may be right for you or it may not. Judge the two on what each publishes.
Neither publishes a price, and that is the first thing to know
Simpro’s Australian pricing page shows no dollar figures at all. It names a “Base Plan”, lists “Custom Training and Implementation” and “Professional Services” as options, and offers two buttons: “Request Pricing” and “Get Demo” (Simpro pricing, fetched 3 September 2026).
AroFlo’s pricing page is the same shape. One plan, “AroFlo Premium”, a list of inclusions, and “Request Pricing” or “Get a Free Demo” (AroFlo pricing, fetched 3 September 2026). No per-user figure, no minimum, no statement on GST.
So this page cannot tell you which is cheaper, and neither can any other page you will find. Anyone quoting you a “typical” Simpro or AroFlo price is quoting a number they were told in a sales call, on a date they have probably not given you. When you get your own quotes, ask for three lines separately: the monthly licence, the implementation fee, and what happens to the monthly figure when you add a user or a business unit. Compare those to the products in this category that do publish prices — ServiceM8 versus Simpro puts one of them beside a published price list.
Where they actually differ: what each API publishes
We have built against Simpro in production. We have never built against AroFlo, and everything in the AroFlo column below comes from AroFlo’s public API documentation, read on one day and linked. Both are real limitations on this page and we would rather name them than smooth them over.
The facts side by side are more interesting than the sales pages suggest. Simpro publishes about 110 webhook events, every one signed with an HMAC, a rate ceiling of 10 requests a second per customer build and no daily cap (Simpro developer centre, fetched 3 September 2026; full detail on our Simpro integration page). AroFlo publishes 120 calls a minute, a 3-requests-a-second ceiling, a 2,000-call daily limit with a secondary 20,000-call daily limit for single-record queries, a 3.5 MB per-request size limit and a 60-second query timeout, with limits resetting at midnight Melbourne time — and no webhooks anywhere in the document (AroFlo API documentation, fetched 3 September 2026).
| Simpro | AroFlo | |
|---|---|---|
| Price published | No No dollar figure on the Australian pricing page. “Request Pricing” or “Get Demo”. | No No dollar figure. One plan, “AroFlo Premium”, and “Request Pricing”. |
| Owner | Not assessed The Simpro Group. Head office Eight Mile Plains, Brisbane. | Not assessed The Simpro Group since 24 November 2021. Head office Melbourne. |
| Rate limit published | Yes 10 requests a second per customer build, 429 above it. No daily cap published. | Yes 120 a minute, 3 a second, and 2,000 calls a day (20,000 for single-record queries). |
| Webhooks | Yes About 110 events, each signed with an HMAC. No retry policy published. | No None documented. Change detection means polling against the daily cap. |
| Authentication | Partly OAuth 2.0 with refresh tokens that expire after 14 days. One hostname per customer. | Partly HMAC-SHA512 key signing on every request. Access switched on in Site Administration. |
| Response formats | Yes JSON. | Yes XML or JSON, your choice per request. |
| Assessed by us | Yes Built against in production. We know the API, not necessarily the product. | No Never built against. Everything in this column is AroFlo’s own documentation. |
The 2,000-call day is the whole AroFlo integration story
Two thousand calls a day is 83 an hour. That is not a lot once something is polling. Because AroFlo publishes no webhooks, the only way an outside system learns that a job changed is to ask, and every ask is a call. Check jobs, quotes and invoices every fifteen minutes and you have used 288 calls before anything else runs (arithmetic on the figures in AroFlo’s documentation, fetched 3 September 2026).
That is workable. It is how MYOB integrations run, and MYOB does not even publish the ceiling. But it means responsiveness is a dial you set against a budget, not a property you get. A customer portal that needs to show a job status within a minute is not a comfortable fit for a 2,000-call day.
Simpro has the opposite shape. Webhooks tell you when something changed, so an integration that does nothing costs nothing, and there is no published daily cap to budget against. What Simpro does not publish is a retry policy, so a webhook that arrives while your endpoint is down is not promised to come back. You build a reconciliation pass anyway. On Simpro that is good practice; on AroFlo it is the only mechanism.
Where AroFlo probably wins, and we would say so
Its published inclusions are broader than most products in this category at the single-plan level: inbuilt compliance and safety forms, project management with Gantt charts, inventory kits, schedule of rates and detailed stock control, multi business units, and access to more than 600 connected suppliers, all listed as part of AroFlo Premium (AroFlo pricing, fetched 3 September 2026). Whether they work well we cannot tell you, because we have not used them.
It is also a Melbourne company with about 91 staff serving “2.8K+ businesses” and “28K+ trade professionals” by its own count (AroFlo, fetched 3 September 2026). For a business that wants a local team on the phone and a product that has been on Australian job sites for a long time, that counts.
And for a business that will only ever run AroFlo plus its accounting package, the absence of webhooks is genuinely irrelevant. Accounting sync is a first-party feature on both products. The API only becomes the decision when a third system enters the picture.
Where Simpro probably wins
The API, for the reasons above. Signed webhooks with wide coverage and no daily cap make Simpro the easier of the two to build around, and that compounds: anything you want it to do that it does not do out of the box is buildable without asking the vendor. The capability register has the full published detail.
It is also a Brisbane company. Simpro’s Australian office is at Eight Mile Plains (Simpro Australia contact page, fetched 3 September 2026) and its origin story starts with “an electrical business owner” in 2002 (Simpro about page, fetched 3 September 2026). That is not a reason to buy it. It is a reason a Brisbane trade business might find people nearby who know it.
Neither of those is decisive on its own. If your business is mostly projects with stock and subcontractors, AroFlo’s inclusions list may matter more than Simpro’s webhooks. If your business is mostly service jobs and you already have three other systems, the webhooks matter more than the Gantt chart.
How to decide when nobody will tell you the price
Four steps, in this order. None of them is a demo, and the vendors will not suggest any of them.
- KNDR·011. Two quotes, same day, same shapeSame user count, implementation separated from licence, in writing. Then ask each what the monthly figure becomes with three more users and with a second business unit. The answers tell you more than the demo.
- KNDR·022. The integration question, asked of your systemsIs anything other than your accounting package ever going to read from or write to this? If yes, Simpro’s webhooks and AroFlo’s 2,000-call day outlast any discount. If no, choose on the product and ignore the API section entirely.
- KNDR·033. A fortnight of real workReal quotes, a real variation, a real invoice, on the trial of whichever the first two steps point at. Choosing job management software lists what to watch during that fortnight.
- KNDR·044. Stop reading comparisonsIncluding this one. A fortnight on the tool beats every page written about it, and the two vendors’ own documents — linked above — are the only sources that cannot go stale without you noticing.
What we have not assessed
We have never implemented against AroFlo. Everything on this page about it is its own published pricing page, about page and API documentation, fetched on one day and linked. We cannot tell you how its accounting sync behaves, how its mobile app performs on a bad connection, or what its data export looks like if you leave.
We have implemented against Simpro, which means we know its API and not necessarily its product. Whether the scheduling feels right to a sparkie at 7am, how the quoting module handles a variation, how either handles a progress claim — none of that is something an integration gives you an opinion on.
We have not measured either API under load. Documented behaviour is not observed behaviour, and when our measured register exists those figures go here with the date they were taken. We also have not compared either against ServiceM8, Tradify or Fergus on this page — the ServiceM8 alternatives page puts all five side by side on the facts they publish.
The questions people actually ask.
01If they are the same company, does the choice even matter?
Yes. They are separate products with separate codebases, separate documentation and, on the evidence of their own developer sites, quite different APIs. Common ownership tells you something about where the group might steer you. It tells you nothing about which product fits your business today.
02You have built on Simpro and not AroFlo. Is this page biased?
The bias is in what we can verify, not the conclusion. We have said plainly where AroFlo’s published inclusions look broader than Simpro’s, and we have not filled the gaps in our AroFlo knowledge with guesses. If AroFlo publishes webhooks or lifts the daily cap, tell us and we will change the table and the date.
03Why not just tell us what Simpro costs — you must know?
We have seen quotes, and a quote given to one business on one date is not a price list. Publishing it would be exactly the kind of stale, unsourced figure this site exists to avoid. Both vendors have chosen not to publish. We think that is a legitimate thing to hold against them, and we say so above.
Stop bending.
Start shipping.
Bring the one flow that keeps costing you a Tuesday afternoon. We map it live and tell you what we'd build, what we wouldn't, and what it costs.