HomeServicesInternal Business Systems
Internal Business Systems in New Zealand
The systems your staff use rather than your customers: job tracking, approvals, stock, compliance, reporting. Unglamorous, and usually the fastest-paying software a business builds.
$50k+
Typical project value
2 min
To post a project
What do you need built?
Start here and add detail as you go.
Free - No obligation - Your details stay private
What people usually mean by internal business systems
Internal systems succeed or fail on adoption. The best-designed system that is slower than the spreadsheet it replaced will be quietly abandoned within a month, so the people who will use it matter more here than in almost any other kind of project.
One process, properly
Approvals, onboarding, compliance records, stock counts — a single workflow taken off paper and email.
The operational hub
Several processes in one place, with roles, permissions and the reporting management actually wants.
Connecting what you already run
Your systems stay, and something sits over them so nobody re-keys between them.
What it costs
Indicative ranges from projects posted here. Use them to sense-check a quote, not to budget precisely.
Single process
One workflow, forms, notifications and a report.
$30k – $70k
Multi-process system
Several workflows, roles, permissions, dashboards and integrations.
$70k – $180k
Operations platform
Multi-site, mobile use, deep integration with finance and ERP.
$180k+
Questions worth asking a provider
·How will you involve the people who have to use this every day?
·What does it look like on a phone, and does it need to work offline?
·Which existing systems does it read from, and how often?
·What happens when someone needs an exception to the process?
·How do we change a form or a rule ourselves later?
Common questions
How much do internal business systems cost?
A single process — approvals, onboarding, compliance, stock counts — is $30,000 to $70,000. A multi-process system with roles, dashboards and integrations is $70,000 to $180,000. Multi-site operations platforms start around $180,000.
How do we make sure staff actually use it?
Involve them before it is built, not after. The single best predictor of adoption is whether the people doing the work were asked how they do it. The second is whether it is faster than what it replaces — if it is slower for the person entering data, it will be worked around, however good the reporting is.
What is the return?
Usually hours rather than revenue: time spent re-keying, chasing approvals, correcting errors and assembling reports by hand. Count those for a fortnight before you commission anything. It is a more reliable business case than any projection.
Should it be mobile?
If any of your people are not at a desk, yes, and it changes the design rather than being a setting. Decide early whether it must work with no signal, because retrofitting that is close to a rewrite.
How long does it take?
Two to three months for a single process, six months or more for a multi-process system. Roll out to one team first — the first fortnight of real use will change your priorities.
Related: Custom Business Software · Customer Portals · Supplier Portals · Workflow Systems · Booking Systems · CRM Development · ERP Extensions · Inventory Systems
Internal Business Systems projects open right now
Titles and categories are public. Full briefs, budgets, regions and buyer detail are visible to approved providers only.
Updated daily
No open projects in this category right now. New briefs are posted every week.
Adoption is the whole risk
Customer-facing software gets used because people want the thing behind it. Internal software gets used because it is easier than the alternative — or it does not get used at all, and your team quietly keeps the spreadsheet running beside it.
The strongest predictor of success is whether the people doing the work were asked how they do it before anything was designed. The second is whether the system is faster for the person entering the data, not just better for the person reading the reports. Those two are often in tension, and internal systems fail when the reporting wins.
Count the hours first
For a fortnight, count the time spent re-keying between systems, chasing approvals by email, correcting errors that came from a typo, and assembling a report by hand each month.
That number is the business case, and it is far more reliable than any projection about efficiency. Most businesses that do this exercise are surprised by how much of a full-time salary is going on work that produces nothing.
The exception is not an edge case
Every internal process has exceptions, and they are the reason people abandon systems. The urgent order that skips two approvals. The customer who gets different terms. The job booked before the paperwork exists.
If the software cannot express the exception, staff will do it outside the software — and then the system no longer reflects reality, which was the point of having it.
Ask each developer how exceptions are handled. An override with a reason recorded is a good answer, and far better than pretending the process is always followed.
Decide about phones early
If anyone using this is not at a desk — a warehouse, a site, a vehicle — mobile is a design decision rather than a setting, and offline capability roughly doubles the effort because reconnecting means resolving conflicting changes.
It has to be in the brief from the start. Added later, it is close to a rewrite.
Comparing quotes
- Who will they talk to? A developer planning to sit with your staff is building something different from one planning to meet management.
- Phase one. One process, live, in a couple of months.
- Exceptions and overrides. How, and who is allowed.
- What you can change yourselves — forms, rules, reports — and what will always need a developer.
Describe the process, who does it, and what it costs you in time. Five developers will tell you what it takes to fix.
Get up to 5 quotes for your internal business systems project
You choose who may contact you. Free to use, no obligation.