Proprietary software development for South Australian business
There's a category of problem that no subscription product solves, because the thing you're doing differently is the thing that makes you money. A pricing model nobody else uses. A dataset built over fifteen years. A workflow that took a decade to refine. Proprietary software turns that advantage into a system instead of a person.
Build the thing nobody else can buy
You own it, it works the way you work, and nobody else gets to use it.
GOOD FIT FOR
BUILD WHEN
- The process is genuinely specific to your business and gives you an edge
- Subscription costs across multiple tools now exceed a build
- You are pushing data between systems that do not integrate
- Off-the-shelf software almost works, but the missing 10% is the important 10%
- Your data is the asset and letting it sit in someone else's product is a risk
- You need to license or resell the tool yourself
BUY WHEN
- A standard product solves 90% of the problem at a reasonable price
- The process is not actually unique, it is just familiar
- You need it in three weeks and it is a well-served category
- The cost of custom ownership is not justified by the advantage
WHAT WE BUILD
- Internal business systems: operations, logistics, scheduling, quality control, compliance
- Automation and workflow engines replacing manual data entry
- APIs and integration layers connecting systems
- Data pipelines and reporting
- Domain-specific calculation and engineering tools
- Licensed products you sell or license to others
WHAT YOU GET
- Architecture and data model designed before code
- Source in a private repository under your account
- Security, audit logging and dependency management
- Documentation, deployment runbooks and handover
Systems that carry the business
Internal tools, integration layers and products where the software itself is the advantage.
Architecture before code.
The difference between software that lasts ten years and software that needs rewriting in two is almost always the data model and the architecture. We spend time there before writing anything, because mistakes at that layer are the expensive ones.
Security-first, because of what we are building.
These systems hold business-critical data. Authentication, authorisation, audit logging, encryption at rest and in transit, input validation and dependency management are part of the architecture, not a later phase.
Private repository, client-owned.
Source sits in a private repo under your account. You have full access from day one. If we disappear tomorrow, you can hire any competent developer to continue.
Built to be maintained.
Clear structure, tests on critical paths, automated deployment and dependency management. Software that cannot be maintained is not finished.
We have talked clients out of builds before. If a standard product is the honest answer, we will say so.
Three ways to work
Fixed-scope projects, phased delivery or retained development. No hourly billing.
- Discovery and specification
- Fixed price
- Defined deliverable
- 8–20 weeks typical
- Independent value per phase
- Stop at any milestone
- Architecture and discovery first
- Longer engagements by design
- Monthly development block
- Defined period
- Planning and prioritisation
- Care and support available
ALL PRICES IN AUD · GST INCLUDED WHERE APPLICABLE · FIXED QUOTES AFTER DISCOVERY · NO LOCK-IN CONTRACTS
Software in production
We build and maintain production software from Adelaide.
HelperCrate, a 101-tool browser platform with WebAssembly media processing and on-device AI, is live and maintained. Read the case study for the technical detail.
Proprietary software is delivered to businesses across Adelaide and South Australia. See service areas.
Before you ask — probably answered here
DaltSync projects start at $8,000. Across the market, custom software typically runs $10,000 to $100,000+ depending on scope. The cost is driven by complexity of business logic, integration count, data migration volume and compliance requirements.
Yes. On final payment, full IP in the delivered software transfers to you: source code, documentation and everything else.
Whatever fits the problem. Typically TypeScript or Python on the backend, a relational database where the data model warrants it, and Cloudflare for the edge layer. We are not tied to a single stack.
Often, yes. We will review it first and give you an honest assessment — sometimes continuing an existing codebase is cheaper, sometimes it is not. We will tell you which.
Change requests are scoped and quoted separately, with the specification updated. Nothing proceeds without your approval.
Either you maintain it internally with full documentation, or we continue under a retained development agreement. Both are normal outcomes.
Yes. Standard practice for this type of work.
Is the process worth turning into software?
Tell us what the business does differently and where the workaround is costing you. We will tell you honestly whether to build, buy or leave it alone.