| Industry Forms | Fergus | |
|---|---|---|
| Pricing | Transparent per-plan pricing, shown up front | Reviewers report real-world cost near $70/user/month after recent price rises |
| Calendar | Month, week, and day views | Reviewers report no month view and describe scheduling as limited |
| Files on a job | Photos and documents attach directly to the job record | Reviewers report no file/folder management inside a job |
| Reporting | Job costing — invoiced, paid, and still-to-invoice — built into every job | Reviewers ask for profit-by-job/by-rep reporting that isn’t available yet |
| Support | — | Reviewers report promised follow-up calls that don’t happen |
Switch without starting from zero
Our import tool brings your customers, price list, and job history straight in from Fergus — no re-typing your customer list from scratch.
Questions people switching from Fergus ask
Fergus is NZ-built too — what’s actually different?
Both understand the local trade workflow. The differences are concrete: simpler, more predictable pricing, a proper month-view calendar, files that live on the job itself, and job-level profit reporting out of the box.
Can I import my Fergus data?
Yes — our import tool is built to read a Fergus export directly, bringing your customers, price list, and job history with it.
Is this a bigger switch than staying with a NZ-built product?
No — the workflow (quote → job → schedule → invoice) is the same shape, and we’re NZ/AU-built and priced too. The import brings your existing data across rather than starting from zero.
Related guides