HELLO PEOPLE is a Fergus integration company for trade businesses in Australia and New Zealand. We connect accepted quotes, finished jobs, invoices and payments in Fergus to your accounting, payments, reporting and customer portal.
Fergus opened its connection point to other software in 2025, so we test what your build depends on against your own account before quoting. Then a fixed price, and support as Fergus grows.
Built here. Your data stays here.
The problem
A quote is accepted in Fergus and the job runs. Then the paperwork begins again: typed into the accounting system, chased through the week, reconciled by somebody who would rather be out quoting the next one. The back office learns about a job a week after it happened.
What you already run
Uses the Fergus webhooks endpoint where it covers the change you care about, and a scheduled check where it does not. Every record is checked, variations are held for a person, and every step is logged.
Find out what yours needsWhat changes
Five connections along the Fergus cycle. Most businesses start with invoicing and add the rest once it has proved itself.
Fergus has a webhooks endpoint, which lets it tell other software that something changed instead of waiting to be asked. Where your account sends a notice for an accepted quote, we use it to start the next step at once: the customer confirmed, the job visible to whoever plans the week.
Where a notice is not available for what you need, a short scheduled check does the same job. Either way, nobody has to spot the acceptance in an inbox first.
When a job is marked finished, the invoice lands in your accounting system that afternoon rather than in a Friday catch-up. Line items, customer and tax treatment come from Fergus as entered.
Unquoted extra work is the one thing held back. A variation is a conversation with the customer, not something to bill automatically.
A payment received against an invoice closes the loop in Fergus, so the job list shows what is genuinely finished and paid, not just finished.
Part payments and deposits stay open with the balance showing, so nobody chases a customer who has already paid.
Fergus holds the whole cycle from quote to invoice. We report across it: quoted value, what has been invoiced so far, and what is left to bill on each open job.
That is the number an owner needs before month end, and the one that is hardest to see when half the jobs are part billed.
Quotes waiting for a decision, jobs booked, invoices to pay. Customers log in on your website and see only their own.
Status is read from Fergus as jobs move on, so the portal matches what the office sees.
Tested first, then a fixed price against a written scope. The testing is what keeps a newer connection point from turning into an open-ended bill.
Tell us what happens after a quote is accepted and after a job is finished. We will tell you what can be connected.
Because the Fergus connection point is new, we test the parts your build depends on against your own account before putting a price on it.
One price covers the build, testing and go-live. Support plans cover changes as Fergus adds to its connection point.
Why HELLO PEOPLE
Sometimes. The question is how well it copes with a connection point that only opened in 2025, and what it does with the jobs that need a person.
| Concern | HELLO PEOPLE | Zapier / Make | n8n / self-hosted | MuleSoft / Boomi |
|---|---|---|---|---|
| A connection point opened in 2025 | Behaviour checked against your account | Connector may lag behind | You read the reference yourself | New connector project |
| Acting when something happens in Fergus | Webhooks where available, checks otherwise | Depends on the connector | You build the listener | Supported, needs configuration |
| Variations and extra work | Held for a person | Billed if the rule fires | You write the rule | Configurable, needs specialists |
| Part billed jobs | Reported per job | Not their job | You build the report | Separate reporting product |
| Ongoing cost | One-off build plus optional support | Charged per task, every month | Hosting and upkeep are yours | Enterprise licence |
| Who you talk to | The person who built it | Chat support | Community forum | Enterprise support desk |
An Australian business running on five disconnected platforms, accounting, CRM, field-service, eCommerce, and reporting, was spending hours each day re-keying the same data. We connected the systems through their APIs so contacts, invoices, orders and payments flow automatically. Errors are visible and recoverable.
Read the full case studySix steps. The second one, testing the Fergus connection point against your own account, happens before we name a price.
From quote to paid, in your Fergus account. Where does somebody type something in twice?
We try the exact reads, writes and event notices your build needs against your own account, and note anything that behaves differently from the reference.
A written scope, a fixed price, and a clear line on what is held for a person.
Quoted jobs, do and charge jobs, deposits and variations from your own history.
The first week of invoices is checked side by side with what the office would have entered.
Fergus will keep adding to its connection point. Support plans cover adjusting the build as it does.
Today
After
Scoped and quoted before you commit. You own the code and the credentials.
Get a fixed-price scopeYes. Fergus opened its API (the published connection point other software uses) in 2025. It is documented in the OpenAPI format, a standard machine-readable description, and it has an endpoint for webhooks, which are notices Fergus sends the moment something happens. Both make a proper integration possible.
Because a new connection point has fewer worked examples, and the reference does not always tell you how it behaves with real data. A Fergus integration consultant checks the parts your build needs against your own account before anyone commits to a price.
We are an independent integration company. We do not sell Fergus, so our advice is about what connects well, not which subscription you are on.
Usually finished jobs into accounting as invoices, because that is where the most re-typing happens. Accepted quotes, payments and a customer portal follow once the first piece is proven.
As a fixed price against a written scope, after the connection point has been tested against your account. No hourly billing.
It is held for a person. A variation needs agreement with the customer first, so it is never billed automatically.
Yes. Tradify customers, sites and price lists come out through exports and load into Fergus, with job history kept alongside for reference.
Sending your details…
You can stay on this page while we send it.
Your accounting system, how customers pay, and where the office still types things in twice. We will come back with what it takes and a fixed price.
Prefer a quick chat? Call 0425 531 127. We answer the phone in Perth.
Thanks for reaching out. We will get back to you within one business day.
See what else we do