I'm David Webster, a ServiceM8 developer in Australia, where ServiceM8 is built and nearly all of its developers live. US partners pass me the client requests that need code, custom reports, API integrations, add-ons, and keep everything else: the client, the connection, the revenue share, and the training work that falls out of every build.
You do the setup, forms, training and support. We do the part that needs a developer, and only that part.
The document a client's customer, insurer or auditor expects, built from job, form and photo data through the API. The request every partner gets and few can build.
ServiceM8 talking to Xero beyond the standard sync, or to any system with an API: accounting, compliance registers, suppliers, industry software.
ServiceM8 15 lets clients draft their own add-ons, and ServiceM8 support will not troubleshoot them. We take the half-built ones to working, tested and installed.
Bulk changes, clean-ups and moves into ServiceM8 that are too big for the import screen: history, photos, open quotes, the lot.
Brisbane mornings overlap US afternoons: 2pm on the West Coast is 7am the next day here, so West Coast afternoons get live answers. Everywhere else, a brief sent at your end of day comes back worked by your next morning.
ServiceM8's listed developer directory has a single US entry. The developer bench for this platform lives in Australia; the work has always travelled, and fixed scope plus the overnight cycle is how it travels well.
Built so the client relationship never leaves your hands.
Forward the client request as they said it. We reply the same business day with whether it is buildable and what we would need to scope it.
You are on the call. We ask the technical questions; you keep owning the relationship. Then a fixed quote in writing, no hourly meter.
Access through an API key or a staff login the client can revoke. The client stays connected to your partner account, so your revenue share is untouched.
Every build lands with documentation and a walkthrough, and the training that falls out of it is yours, not ours. Setup and training enquiries we get in your region go to you.
You do, and the arrangement is built so that stays true: the client remains connected to your partner account, your revenue share keeps accruing, and our access is an API key or a staff login that can be revoked the day the build is done. We do not do setup, forms, training or support, so there is nothing for us to take over.
Only if you sell custom API development, in which case we are probably trading work already. FFP does not sell setup, conversions, training or admin support anywhere. The work that needs code is the whole business.
Quotes are written in Australian dollars with the USD equivalent shown on the day of the quote, and Australian GST generally does not apply to overseas clients, so what is quoted is what is paid. If your client prefers the quote to flow through you, that works too.
Fixed prices quoted in Australian dollars before work starts, with a 50% deposit. As a guide, a custom report starts around A$1,200 and an integration around A$2,000. Australian GST generally does not apply to work for businesses outside Australia, so the quoted figure is normally the whole figure. Any referral arrangement with a partner is disclosed on the client's quote.
Every build has a fix period after delivery. After that, optional monthly care covers monitoring and fixes when ServiceM8 or a connected system changes something. Either way the client's first call can stay with you; we sit behind it.
Tell us about the client request you cannot build in-house: the report they asked for, the system that will not talk to ServiceM8, the add-on that stalled. We reply the same business day with whether it is buildable, and a fixed quote follows a short scope call you are welcome on.
Your client stays yours: connected to your partner account, with your revenue share untouched. Setup and training that falls out of a build goes back to you.