Christchurch · Dunedin · Nationwide
Custom Software Development Services
Exodesk provides custom software development for New Zealand businesses. Our Christchurch and Dunedin developers design and build business applications and supported extensions where an existing product does not cover the requirements.
We start with the process and the alternatives. Where a build is justified, we agree what it must do, how it will be tested and who looks after it after launch.
Supporting New Zealand businesses since 1989
The short answer
What is custom software development?
Custom software development creates or extends an application to meet defined business requirements, with the screens, records, permissions and rules designed around the agreed work.
It can use existing frameworks and components, and it can extend an application you already run rather than starting from scratch. Bespoke software suits a requirement that matters to the business and that the available products, configuration or integration do not meet adequately.
Exodesk has supported New Zealand businesses since 1989. Today, our Christchurch and Dunedin teams support businesses nationwide, and our developers work alongside the business software team that builds and supports the Zinform products.
What we build
What custom software development covers
Custom application development starts from a defined business need. These are the kinds of work we scope.
Applications
Internal business tools
Desktop and web applications for quoting, jobs, bookings or records, with permissions and rules agreed for the work.
Spreadsheets
Replacing a critical spreadsheet
A process held together by a shared sheet moved into an application with validation, a shared record and controlled access.
Extensions
Adding to what you run
A new function added to an existing application where it supports extension, rather than replacing the whole system.
Confirmed examples include finPOWER Connect customisation for lenders, where Exodesk is an Authorised Reseller, and the Web Freight Scheduler for dispatch operators using Zinform Logistics. Connections to other systems are checked before they become part of any build.
Build or buy
Check the alternatives before building
Compare a suitable product, configuration, an integration, a supported extension and a new build against the requirements and the full running cost.
An existing product may be enough, and configuration can close a smaller gap. If the main problem is moving records between systems, our business software integration service may be the right starting point. Wider process steps and approvals are covered by our AI workflow automation service, with AI used where interpreting documents or language adds value.
A custom build is designed to meet agreed requirements, not to preserve every existing workaround. Expected users, data volumes, workload and planned changes are recorded at scope, because growth may later need architecture work, new infrastructure or further development.
Ownership and support
Software ownership, hosting and support
Rights, hosting and support are agreed in writing as part of the proposal. Ownership of code and a working support arrangement are separate decisions.
- Rights. The agreement identifies rights to project-specific code, documentation, reused components and third-party licences. The IPONZ guide to copyright ownership explains how commissioning and agreements affect who owns a work.
- Handover. Source access, build and deployment instructions, dependency information and data export are agreed to support a future transfer, subject to the rights, licences and expertise required.
- Hosting. The application can run in Exodesk’s environment or your own. Infrastructure patching, monitoring, backup and recovery are defined separately from the application itself.
- Support and change. Correcting agreed defects is distinguished from new features and from changes caused by supplier updates, with each handled under the agreed terms.
A custom application can still depend on per-user licences, commercial libraries, databases, APIs or hosting charges, and these are listed in the proposal.
Delivery
How the project is delivered
We map the process, users, data and dependencies, then agree a first scope and acceptance criteria. Required connections are checked during scope and design, before development begins.
Design sets out the screens, rules and permissions. The build is reviewed against real tasks with the people who will use it, and testing covers the agreed functions, errors, access and operating conditions.
Security is part of design and testing, in line with practices such as the NIST Secure Software Development Framework. Release, any data move, permissions and staff handover are planned before the application becomes part of daily work.
How it works
How a custom software project starts
Each custom software development project starts with the work the software needs to do.
Describe the work
Tell us the process, users, current applications and the problem you want to solve.
Compare the alternatives
Check products, configuration, integration and a build against the requirements and running cost.
Agree a first scope
Confirm functions, acceptance criteria, connections, rights, hosting and support for the first release.
Build, release and support
Deliver against the agreed milestones, hand over, then support and change the application as agreed.
Staged releases can suit larger projects, with each stage producing a usable result and its own acceptance. Payment terms are agreed separately in the proposal.
Cost
What affects custom software development cost?
Cost depends on the functions, interfaces, data, testing and support required. The proposal sets out milestones, exclusions and how changes are approved.
- Design and build. The agreed functions, screens, rules and testing.
- Migration and handover. Data preparation, release, training and documentation.
- Running costs. Hosting, licences, databases and third-party services, listed separately.
- Support and change. Ongoing maintenance and future changes under agreed terms.
Compare the complete cost with the existing process and the other options. Time recovered can improve capacity, and the expected benefit should reflect how your team will use it.
Questions
Custom software development questions
What is custom software development?
Custom software development creates or extends an application to meet defined business requirements. It can use existing frameworks and components, with functions, records, permissions and interfaces agreed for the project. It does not have to recreate everything from scratch.
Should we build custom software or buy an existing product?
Compare suitable products, configuration, integrations and a custom build against your requirements and full cost. An existing product may be sufficient. Building can be appropriate where the unmet need is important enough to justify development and ongoing support.
When should a business build custom software?
Consider building when a valuable requirement cannot be met adequately by the available alternatives. Record the gap, the affected users and the likely benefit first. A complicated spreadsheet or unusual process is a reason to investigate, not proof that a build will pay.
How much does custom software development cost?
Cost depends on scope, interfaces, data, testing and support. Compare design and build together with hosting, licences, migration, maintenance and future changes. A defined first scope allows a more useful proposal than an assumed price for the whole system.
How long does a custom software project take?
Timing depends on requirements, supplier access, decisions, testing and data preparation. Milestones are agreed once feasibility and scope are understood. Staged releases may suit, but each release needs an agreed usable result and acceptance process.
Can custom software connect to Xero or our CRM?
A connection may be possible where the application exposes suitable interfaces and the required access is available. Confirm fields, permitted actions, direction, timing, licence conditions and failure handling before an integration becomes part of the build.
Is custom development only for large companies?
No. A project can address one limited business requirement. Whether it is worthwhile depends on the problem, the alternatives and the complete running cost rather than company size. Start with a scope your team can review and support.
Who owns the software once it is built?
The agreement states the rights to project-specific code, reused components and documentation. Some third-party elements remain subject to their own licences. Confirm rights to use, change and maintain the software, together with source access and data export arrangements.
What if the original developer stops supporting it?
Continuity depends on the rights and handover arrangements, usable source, documentation, dependencies and available replacement expertise. Agree the access and information another provider would need before work starts. Code ownership alone does not guarantee a smooth transfer.
How do we get started with custom software development?
Describe the process, users, current applications and the outcome you need. Our Christchurch and Dunedin teams compare the alternatives and scope development for businesses nationwide. Support, hosting and handover are agreed as part of the proposal.
Next step
Tell us what the software needs to do
Describe the work, current applications, users and the problem you want to solve, and we can discuss whether a product, configuration, integration or a build is appropriate. Please keep customer records, source-code archives and passwords out of the enquiry form.
Get in touch
Talk to us about a software project
Tell us about the process, the applications you run now and what the software needs to do, and we will be in touch to arrange a time that suits.
Prefer to talk?
Christchurch
Level 1, 85 Riccarton Road
Christchurch 8011
03 343 3124
Dunedin
Level 3, Bartons Building
2 Stafford Street, Dunedin 9016
03 479 2941