We get asked this often. “Why $1 per job? Wouldn’t it be simpler to charge per user, like everyone else?”
The honest answer is that we tried it. Per-user pricing made sense when we were running our own trade business and the team was static. The moment we started adding subbies, casuals, and apprentices for short stretches, the maths stopped working.
Where per-user pricing breaks
Picture a small business with 5 staff and 3 subbies who come on for various jobs. On a per-user platform charging $50 per user per month, that’s $400 a month, $4,800 a year. Bring on a fourth subbie for a 2-week project and you’ve paid them $50 for that 2 weeks, then another $50 the month after, then it auto-renews until you remember to cancel.
Most teams don’t remember to cancel. So per-user costs creep up.
Where per-job pricing works
The work is the thing you’re being paid for. So the work is the thing we charge against. Add as many staff and subbies as you need. Pay $1 per job created. If you run 100 jobs in a month, that’s $100. If you run 30 in a slow month, that’s $30.
It scales with the business, not the headcount.
A note on the plan tiers
Pro and Premium plans exist for features beyond the basics: advanced reporting, AI expense capture, compliance documentation. The per-job model holds across all tiers. The tier you pick is about features. The per-job spend is about volume.
Simple to forecast, simple to budget, no surprise per-user fees on the next invoice.