About
We didn't set out to build software. We set out to stop losing jobs in an inbox.
JobStack started inside a cabinet installation business in Melbourne's north. Crews on site every day, builders emailing at all hours, quotes going out at night, and a whiteboard in the office holding it all together — as long as nobody bumped it.
The tools on offer didn't fit. The big job-management platforms were built for someone with an office manager and a training budget. The simple ones were digital notepads. And none of them dealt with the actual centre of gravity of a trade business: the email inbox, where every job starts, changes and occasionally dies unread.
So we built our own. First a board to replace the whiteboard. Then email that filed itself. Then quoting that started from what the builder actually wrote rather than a blank page. Every feature was tested the honest way — on real jobs, by real installers, with real money at stake. Things that didn't survive a Tuesday on site got deleted.
Word got around, the way it does in the trades. Other businesses asked what we were using, and the answer stopped being "something we hacked together" and became JobStack.
What we believe
The rules we build by.
The AI is an apprentice, not the boss
It reads, drafts and suggests. It doesn't send, commit or spend. Anything it does is logged where you can see it, and the important stuff waits for your approval. Software that quietly acts on your behalf is software you eventually stop trusting.
If the crew won't use it, it doesn't ship
Plenty of job software works beautifully in a demo and dies on site. Our bar is an installer with dusty hands, one bar of reception and ninety seconds of patience. That's why the app caches the day and the interface says what it means.
One system beats five subscriptions
A CRM here, a scheduler there, quotes in a doc, photos in someone's camera roll. The value of JobStack isn't any single feature — it's that email, jobs, crews and money are the same system, so information flows instead of getting re-typed.
Plain pricing, plain words
One plan, everything in it, cancel from a button. And no jargon: a job is a job, a variation is a variation. You've got enough translation work dealing with architects.
How we got here
A short history.
-
The whiteboard years
We run installs across Melbourne on spreadsheets, group chats and memory. It works, mostly, until it doesn't — a missed enquiry here, a crew at the wrong site there.
-
The internal tool
We build a jobs board and email ingestion for ourselves. The morning routine changes: open the inbox queue, approve the suggestions, get on with the day.
-
Quotes, crews and money
AI quoting drafts from real email threads at our real rates. The crew calendar replaces the 6am texts. Job margins stop being a surprise.
-
JobStack goes public
Other trade businesses start asking for it, so we make it a product: multi-workspace, roles, a mobile app for the crew, and Stripe billing with a plan anyone can understand.
Made in Melbourne
Built where the jobs are.
We're based in Melbourne and JobStack is shaped by Australian trade businesses — GST on quotes, the way builders email, the rhythm of a Victorian build schedule. If you've got a question, you'll get a person who understands what a variation is, not a chatbot reading a script.