The job costing dashboard: build it or subscribe to it?
Most trades software arguments happen in the abstract. This one doesn't have to: I built a live job profit dashboard and you can click around it right now, no signup. Then we can talk honestly about when a custom build beats a monthly subscription, and when it doesn't.
First, click the thing
The exhibit: a live job profit dashboard for a fictional plumbing outfit. Quote vs actual, labour burn, materials as they land, gross profit moving in real time, three days into the job. It is the screen that answers the only question that matters mid-job: are we still making money on this one?
That demo is real, running software. I built it because I wanted margin visibility in my own field-service businesses and did not want another subscription to get it.
The honest case for subscribing
Job costing modules inside the big platforms earn their keep in specific situations, and pretending otherwise would be salesmanship:
- You already run the platform deeply. If your timesheets, purchase orders and invoicing all live in one system already, its costing module inherits that data for free. Turning it on beats building anything.
- You need it tomorrow. A subscription switches on today. A build takes weeks.
- Your workflow is genuinely standard. If the vendor's model of a job matches yours, the fit costs you nothing.
The honest case for building
- Your data is scattered, permanently. Real shops run Xero plus a job app plus a supplier portal plus a spreadsheet. The subscription costing module wants everything inside its walls; a custom dashboard reads from where the data actually lives.
- You want your definition of margin. How you allocate the apprentice's hours, the ute, the supplier rebate: opinionated businesses fight the vendor's model forever. A build encodes your rules once.
- Fixed cost, not a forever tax. A dashboard build is a one-time fixed price (this class of build starts from $3,500 as the Profit Visibility Pack). Platform seats compound monthly, per user, per year, forever, with the annual increase letter.
- It becomes yours to extend. The weekly owner email, the quote-vs-actual view for the estimator, the "which job types actually make money" report: bolt-ons to a system shaped for you, not feature requests into a vendor queue.
All-in on one platform already: use its module. Running the normal Australian mixed stack (job app + Xero + spreadsheets): a built dashboard is cheaper over two years, matches how you actually cost jobs, and you are not renting your own margin numbers back.
Subscribe vs build, side by side
| Question | Subscribe (platform module) | Build (custom dashboard) |
|---|---|---|
| Best when | You already run one platform deeply | You run the mixed Aussie stack: job app + Xero + spreadsheets |
| Cost shape | Per seat, monthly, compounding | One-time fixed, from $3,500 |
| Your data | Must live inside the platform | Reads from where it already lives |
| Margin definition | The vendor's model of a job | Your rules, encoded once |
| Time to live | Today | Weeks, or inside 60 days on Ops Care |
| Ownership | Rented; feature requests join a queue | Licensed to you, yours to extend |
The maths worth doing
Skip the vendor ROI calculators and run one honest comparison. Take the monthly per-user price of the module tier you would need, times seats, times 24 months, plus the setup and training time nobody counts. Put that next to a fixed-price build plus an Ops Care plan if you want it maintained and extended monthly. For most 3-to-10-person shops the build side of that ledger wins before the second year is out, and the numbers on your screen are defined your way.
Do not take my word for the workflow: the demo is the argument. If the screen would change your Tuesday, the audit works out what your version needs to read from.
What your version would involve
The 30-minute Tech Leak Audit maps where your job costs actually live (Xero, the job app, the supplier invoices, the timesheets) and what a v1 dashboard reading from them looks like. Single-source v1s land as fixed-price builds from $3,500; multi-source versions are scoped honestly in the proposal. Or it ships inside the first 60 days of an Ops Care Standard plan and keeps growing monthly from there. Invisible margin is one of the leaks the State of Trades Admin 2026 data finds across the trade, and it is a common one for plumbing and service shops in particular.
Build vs buy a job costing dashboard: common questions.
Should I build or buy a job costing dashboard?
Buy the module if you already run one platform deeply, need it switched on tomorrow, and your workflow matches the vendor’s model. Build a custom dashboard if your data is scattered across Xero, a job app and spreadsheets, you cost jobs your own way, and you would rather pay once than rent your margin numbers back forever. For most mixed Australian stacks, building wins.
Isn’t a custom dashboard more expensive than a subscription?
Upfront, yes; over time, usually not. A build is a one-time fixed price, this class starts from $3,500 as the Profit Visibility Pack, while platform seats compound monthly, per user, per year, with the annual increase letter. Run the honest sum: monthly price times seats times 24 months plus setup, against a fixed build. For most 3-to-10-person shops the build side wins before the second year is out.
Can a custom dashboard read from Xero, my job app and my spreadsheets?
Yes, and that is the whole point of building instead of subscribing. A subscription costing module wants everything inside its own walls. A custom dashboard reads from where your data actually lives, so you get margin visibility without first migrating your whole business into one vendor.
What if my definition of margin is unusual?
That is often the strongest reason to build. How you allocate the apprentice’s hours, the ute, the supplier rebate: opinionated businesses fight a vendor’s fixed model forever. A build encodes your rules once, so the number on the screen is margin the way you actually calculate it.
How long does a job costing dashboard take to build?
Weeks, not the same afternoon a subscription switches on. A single-source v1 lands as a fixed-price build from $3,500; multi-source versions are scoped honestly in the proposal. Or it ships inside the first 60 days of an Ops Care Standard plan and keeps growing monthly from there.
Do I own the dashboard once it is built?
You own your data, your credentials and your platform accounts, exportable any day. The dashboard software itself is licensed: I keep it running and improving under Ops Care, and there is a source buyout price written into your agreement from day one if you ever want it outright. No hosting ransom, no lock-in on the data.
Not sure what fits your shop? Ask me, not a sales rep.
A 30-minute Tech Leak Audit and a one-page written finding inside 48 hours. Three prioritised fixes, no pitch, and the report is yours either way.