Who custom software is for
Custom software development for small business makes sense when the tools you can buy no longer match the way you work. Most businesses get there gradually: a spreadsheet becomes the job system, a second one tracks stock, and someone spends each Friday copying figures between them.
Typical situations we are asked to fix:
- A builder quoting from one spreadsheet, scheduling trades in another and invoicing from a third, with no single view of a job.
- A wholesaler taking orders by phone and email because the customer portal they need does not exist as a product.
- An accounting practice tracking client documents and deadlines across shared folders and inboxes.
- A clinic's front desk entering the same details into a booking tool, a form and a billing system.
- A business paying per-user fees for a large platform and using a small corner of it.
Before recommending a build we check whether an existing product, or an integration between the systems you already have, would solve the problem for less. If it would, we say so. The kinds of systems we have built are listed on our work page.
Problems custom software solves
A purpose-built system is worth its cost when it removes problems like these:
- The same customer, job or order typed into several places, with small differences each time
- A key spreadsheet that only one person understands, and that breaks when two people edit it together
- Staff phoning the office for information they could look up themselves
- Month-end reports assembled by hand from several exports
- A process that has outgrown the product you bought, so people work around the software instead of with it
What is included
Every build covers the full path, from a problem described on paper to a system your staff use each day.
Discovery and scoping
Sessions with the people who do the work, a written list of what the system must do, and a clear line around what is out of scope.
Interface design
Clickable screen designs you can try before anything is built, laid out for the devices your staff use, from office desktops to phones on site.
Web application build
A browser-based system with logins, roles and permissions, so each person sees only the records their job needs. Typical parts are customer and job records, quoting, scheduling, document storage, approvals and a history of who changed what.
Data migration
Customers, jobs, products and history moved out of spreadsheets or an old database, and checked against the source before go-live.
Connections to other systems
Links to accounting, payments, email and SMS through their APIs, so information is entered once.
Testing and security
Automated tests that run on every change, plus access control, encryption and backups set up from the first release.
What you hold at the end
Everything below is handed over in accounts registered to your business, not ours.
- The full source code, in a repository you control
- Administrator accounts for the application, hosting and domain
- A copy of your database and a documented way to export your data
- Technical documentation: how the system is structured, hosted and deployed
- A user guide written for your staff, and a training session
- The automated test suite and the results of the final test run
- A list of every third-party service the system depends on
- The backup schedule and the result of a restore test
- The agreed scope and screen designs, kept as a reference for later stages
Technologies we use and why
We choose widely used, well-documented tools so that any competent developer can maintain your system later.
TypeScript
A typed form of JavaScript that catches many mistakes before the software runs. We use it for both the screens and the server so one language covers the whole system.
React and Next.js
Common tools for building fast screens that adjust to any device. Because they are common, another developer can pick the work up, and you are not tied to us.
Node.js
Runs the server side: business rules, scheduled tasks and the API that other systems connect to. It runs well on modest hosting.
PostgreSQL
An open-source relational database, suited to records that must add up, such as orders, stock and invoices. There are no licence fees, and every major cloud offers it as a managed service.
Docker
Packages the application so it runs the same way in testing and in production. The system can move to another host without a rebuild.
Google Cloud, AWS or Azure
Hosting with managed backups, monitoring and a choice of Australian regions. You pay for what the system uses instead of buying and replacing a server.
How we deliver custom software
| Stage | What happens |
|---|---|
| 1. Discovery call | A free first conversation about the problem, who is affected and what you use today. We ask to see the spreadsheets and forms as they really are. |
| 2. Plan and quote | You receive a written scope, screen sketches and a fixed or staged quote. Nothing is built until you have agreed to it. |
| 3. Build and test | We build in stages and show you working software at regular demos. Each stage is covered by automated tests, and your feedback shapes the next one. |
| 4. Launch and train | We move your data across, go live on secure hosting and train your staff on the real system, with written guides to keep. |
| 5. Ongoing support | After launch we monitor the system, apply updates and make changes as your business changes. Support is optional, and the code is yours to take elsewhere. |
Engagement options
| Option | Suits | How it works |
|---|---|---|
| Fixed quote | A defined system with a clear list of features | We scope the work together, agree a written price and deliver that scope. Changes are quoted separately before they start. |
| Staged pricing | Larger systems, or projects where later needs are still forming | The work is split into stages, each with its own quote and demo. You approve each stage before the next begins. |
| Monthly plan | Systems already in use that need care and steady improvement | A set monthly arrangement covering monitoring, updates, fixes and an agreed amount of new work. |
Every option starts with a free consultation and a written quote agreed before work starts.
Security and data handling
- Access control and least privilege. Each person signs in with their own account, and a role opens only the records their job needs. Administrator rights are kept to a few named people.
- Sign-in. Multi-factor authentication, or single sign-on through the work accounts you already manage.
- Encryption and backups. Data is encrypted in transit and at rest. Backups run automatically, are stored apart from the live system and are restored as a test.
- Where data is stored. In a cloud account in your name, in the region you choose, recorded in the documentation.
- Audit trail. The system records who viewed or changed sensitive records.
The Australian Signals Directorate lists patching applications, multi-factor authentication, restricting administrative privileges and regular backups among the strategies of its Essential Eight. Where the Privacy Act covers your business, the OAIC's guidelines on Australian Privacy Principle 11 say reasonable steps to protect personal information include technical and organisational measures, and that an organisation must take reasonable steps to destroy or de-identify information it no longer needs. We agree retention rules with you during planning.
Support after launch
Software is not finished on launch day. On a monthly plan we watch the system for errors and failed tasks, apply security updates to the framework, database and hosting, fix faults, and make the small changes that surface once staff use it every day. Larger additions are scoped and quoted in writing, like any other stage.
You can reach us by email at hello@comingwave.com.au, by phone or through the enquiry form, and we reply within one business day. Support is optional: because you hold the code, the accounts and the documentation, upkeep can also pass to your own developer.
Industries this suits
Trades and construction
Quoting, scheduling, site photos and invoicing in one job system instead of separate spreadsheets.
Professional services
Client records, document requests and deadline tracking for accounting, legal and consulting practices.
Hospitality
Booking and guest record systems for hotels and venues, built around how your front desk works.
Logistics and transport
Booking, dispatch and delivery tracking for fleets, couriers and passenger transport.
Recruitment
Candidate and client tracking shaped to your own placement process, where a generic CRM falls short.
Australian context: ownership and privacy
Who owns commissioned software. Copyright covers computer programs and, as business.gov.au explains, protection is free and automatic under the Copyright Act 1968. Paying for software does not by itself make you the owner. IP Australia states that IP created by a contractor is the property of the contractor unless otherwise stated in the contract, and business.gov.au gives the same advice on preparing a contract: if the hirer wants to own the IP, the contract must state this. Our clients own their code, data and documentation, and we put that in writing before work starts. Whoever builds your software, read that clause.
Privacy by design. The Office of the Australian Information Commissioner (OAIC) describes privacy by design as a process for embedding good privacy practices into the design specifications of technologies, business practices and physical infrastructures. It recommends a privacy impact assessment early enough to influence how a project proceeds. In practice we map what personal information the system collects, who can see it and how long it is kept, during planning. This is general information, not legal advice.
Custom software questions
When does custom software make more sense than a subscription product?
If a product you can subscribe to covers most of what you need, use it. Custom software earns its place when your process is what sets you apart, when staff are re-keying data between tools, or when licence fees keep rising for features you do not use. We will tell you on the first call which way we would go.
Who owns the source code when the project is finished?
You do. Ownership of the code, data and documentation is set out in writing, and the repository is handed over to an account you control.
Can you take over or rebuild software another developer wrote?
Often, yes. We start by reviewing the code, hosting and data, then tell you whether it is sounder to keep improving it or to rebuild in stages. Either way your existing data is carried across.
What happens if our needs change part-way through the build?
That is normal, and building in stages allows for it. A change is described and quoted in writing before any work on it starts, so the cost of each decision is clear.
Will the system work on phones and tablets as well as desktops?
Yes. The systems we build run in a browser and adjust to the screen, so the same system works at a desk and on site. If staff need offline use or device features such as the camera, a mobile app may suit better.
How is the data in a custom system kept secure?
Access is controlled by role, sign-in can use multi-factor authentication or single sign-on, data is encrypted in transit and at rest, and backups run automatically. Our cyber security page covers the wider picture.
Can we start with a small first version and add to it later?
Yes, and it is often the sensible way. We agree the smallest version that removes the main problem, release it, and quote further stages once your staff have used it. The first version is structured so later features can be added without starting again.
