Under $35,000. One-off. Fixed before we start.
Most people in this category won't put a number on a page. We will, because the number is the whole argument, and because it saves us both a call that was never going to go anywhere.
Four things that don't move.
- Fixed means fixed
- Once discovery is done, the price for that stage is set in writing with the scope attached, and it does not move because the build turned out harder than we judged. That's our risk, not yours.
- The only thing that changes the number is you asking for something outside the agreed scope, and that gets quoted and agreed in writing before anyone starts work on it.
- No per-user fees
- At five staff or eighty. Put the whole floor on it. Give every customer a login to the portal. The number doesn't change, which means the system getting more useful never costs you more.
- Paid in stages, tied to stages delivered
- You're never paying ahead of the work. Each payment is released against something you can log into and click through, not against a date on a schedule.
- You own it on final payment
- The code, the database and the system are yours to own, change, copy and take anywhere, including to another developer. We keep ownership of our own general purpose tooling that pre-dates your project, and you get a perpetual, royalty free, transferable licence to it. Nothing we keep can stop your system running or stop you leaving.
- Every figure here is in Australian dollars
- We're an Australian company and we quote in AUD, including for New Zealand clients. Your proposal states the currency and the amount, so there is no conversion to work out after the fact.
Three shapes, and what sits in each.
Your number comes out of discovery, not off this page. These are the bands real builds land in, and what tends to be in them.
-
From $12,000Single site · near 30 days
The straightforward build
One location, a clean product list, no manufacturing depth. The operation is running on spreadsheets or an accounting package that has been asked to do too much.
- Inventory, live stock by location, committed versus available
- Sales, quoting and order entry
- Purchasing with supplier lead times and receipting
- Xero or MYOB integration
- Live dashboards, role-based access, mobile and tablet
-
$18,000 to $26,000Manufacturing depth · 40 to 50 days
The typical manufacturer
Everything above, plus the parts of the operation that spreadsheets stopped coping with. This is where most of our builds land.
- Multi-level bills of materials, made and bought, where-used, revisions
- Work orders raised from the BOM, floor tracking
- Job costing, real margin per job, per customer, per product
- Supplier performance, pricing and purchase history
- Compliance documents, certificates and audit evidence
- Data migration from your current system
-
Up to $35,000Multi-site · near 60 days
The full build
Everything above, across more than one site, with the scheduling and self-serve layers on top. This is the ceiling. We have not quoted above it.
- Multi-site inventory and transfers
- Production scheduling against capacity
- Forecast-driven purchasing
- Customer portal: order, track, request quotes, pay, self-serve
- Batch and lot traceability end to end
- Additional integrations beyond accounting
Four payments, each against something you can log into.
-
25%
On signing
After discovery, with the fixed price and the go-live date already agreed.
-
25%
Core system
Your data model, inventory and the main screens are live in your environment.
-
25%
Full build
Every agreed module is in and working, integrations connected.
-
25%
Go-live
You're running the business on it. Ownership of the code transfers here.
If a stage isn't delivered, it isn't invoiced. That's the whole mechanism, and it's the reason we can be relaxed about publishing the price.
The honest split.
Included in the build price
- Discovery and the fixed-price proposal
- Every module in the agreed scope
- Xero or MYOB integration
- Migration of your existing data
- Role-based access for floor, admin and ownership
- Mobile and tablet for shop-floor use
- Training your team on the system we built for them
- Go-live, on the tools, with you
- 30 days of hands-on support afterwards
- Transfer of the code and the repository to you
Genuinely extra
- Hosting and ongoing support, quoted in your proposal
- A new module added after go-live, scoped with your account manager
- Third-party licences you already pay for, Xero and the like
- Hardware, scanners, tablets, label printers
- Work outside the agreed scope, quoted and agreed in writing first
Small changes after go-live are not on this list. A field moved, a column added, a report changed, a screen laid out differently: request it from inside your system and it's turned around within 48 hours as part of support.
The comparison that actually matters.
Not build cost against build cost. Build cost against what the compromise is costing you every month, forever.
-
$18,000
A year, at $1,500 a month, is what one business we spoke to pays for inventory software that doesn't fit them. That's more than most of our builds cost, once.
-
8 licences
Another runs their whole operation on eight ERP licences and regularly hits the ceiling. Growing the team means buying permission to work.
-
$25k → $80k
A well-known CRM vendor quoted $25,000 for an integration, took the signature, then revised it to $80,000 after looking properly.
These are what we see in the market, from real conversations with Australian businesses. They are not case studies and we're not claiming them as clients.
When custom costs less than a few years of subscription fees, buying a compromise stops making sense.
Including the one nobody asks out loud.
What if it costs more than quoted?
It doesn't. Once discovery is done, the price for that stage is set in writing with the scope attached. If the build turns out harder than we judged, that's our risk, not yours.
The only thing that changes the number is you asking for something outside the agreed scope, and that's quoted and agreed in writing before anyone starts work on it. No surprise invoice, no revision after signature.
Who owns the code?
You do, on final payment. The code, the database and the system are yours to own, change, copy and take anywhere, including to another developer who competes with us.
Two things we're precise about, because a lawyer will ask. We keep ownership of our own general purpose tooling that pre-dates your project, and you get a perpetual, royalty free, transferable licence to it that survives us ceasing to trade. And your system uses open source components that stay under their own licences. Nothing we keep can stop your system running or stop you leaving.
What if we want to leave?
You take the system with you. There's nothing to extract and nothing to hand over, because the source code is already in your own GitHub repository and it already runs on your own Cloudflare account.
We'll help you transition to another developer or to your own team properly, and we won't hold your data while you do it. An exit that goes badly is worse for us than for you.
What if Praxa Tech goes under?
Everybody thinks it and almost nobody asks, so here's the straight answer: your system keeps running.
It isn't hosted by us on infrastructure you can't reach. The code is in your GitHub repository. It runs on your Cloudflare account. It's built on ordinary, widely used technology rather than anything proprietary to us, which means any competent developer can open it and understand it.
That's deliberate. We designed the arrangement so that our disappearing would be an inconvenience rather than a catastrophe, because a buyer who has to bet the operation on our survival shouldn't be buying from us.
The full answer, including what it would cost you and how long a system can run with nobody maintaining it, is on the continuity and security page.
What happens if we change the code ourselves?
You're allowed to. It's your code, and if you have a developer on staff or a contractor you trust, use them.
In practice we ask that changes go through a branch so we can see them, because if we're supporting the system we need to know what's in it. If you make changes we haven't seen and something breaks, we'll still help, but the time to work out what happened is chargeable. That's the only catch, and it's the same catch any developer would have.
How is ongoing support priced?
Hosting and support are quoted in your proposal as one ongoing figure, set against the size and shape of your system rather than your headcount. There are no per-user fees at any staff count.
We don't publish the figure because it genuinely depends on the build. What we'll commit to on a public page is this: it's a fraction of what a per-user subscription costs at the same headcount, it's fixed for the term, and it covers the help desk, the change portal and your account manager.
Is there a cheaper version if we only want part of it?
Yes, and that's the point of discovery. We'd rather build the three things that are actually hurting than the ten things that sound complete. A narrower build is a smaller number and a shorter timeline, and modules can be added later once you've seen the system working.
Do you take on work above $35,000?
We haven't yet. If discovery turns up an operation that genuinely needs more than this, we'll say so rather than squeeze it into the number, and we'll be honest about whether we're the right people for it.
See it before you spend anything.
We build a working demo of your business in a real system, in 48 hours, free. Then you'll know what the number is buying.