Product engineering
Whole builds, start to finish. Web applications, APIs, data models, the lot, structured so the second year of work on it is as easy as the first.
Dallatech takes work from a rough idea to something real people use. Architecture, code, cloud infrastructure, and all the unglamorous parts in between. We do this for clients, and we do it for our own products.
Engineering work, priced and scoped like a professional service. Most engagements are some combination of the six below.
Whole builds, start to finish. Web applications, APIs, data models, the lot, structured so the second year of work on it is as easy as the first.
Decide what to build on before the decision gets expensive to reverse. System design, stack choices, and an honest second opinion on a plan you're not sure about.
AWS, containers, CI/CD and deployments you can run without ceremony. Built to stay cheap at low traffic and to hold up when it isn't.
Inherited a codebase, or had a contractor leave mid-build? We pick up other people's code, work out what it actually does, and get it moving again.
Language-model features built into real products, with evaluation, guardrails and a sensible answer for when the model gets it wrong. Not a demo.
Senior engineering judgement for teams not ready for a full-time hire. Code review, technical direction, standards, and help hiring the people who come next.
Four commitments that shape every engagement. They're the reason clients come back.
The person you brief is the person who writes the code. There's no account layer, no handover to a team you've never met, and no game of telephone between you and the work. Staying small is a deliberate choice, not a stage we're trying to grow out of.
Tests, continuous integration and monitoring go in at the start, not as a cleanup pass that never quite gets scheduled. Software that only works on the machine it was written on isn't finished, and we don't call it finished.
Proven tools for the core of a system, novelty only where it clearly pays for itself. The interesting part of your product should be your product, not the infrastructure holding it up, and not a framework chosen because it was new that quarter.
Your code, your repositories, your cloud accounts, your keys, all documented well enough that another engineer could pick it up cold. We'd like to keep maintaining it, but nobody should stay with a studio because leaving would be expensive.
We run our own products alongside client work. It keeps us honest about what shipping actually costs.
Savings and share records for Australian families
Savings and shares in one permanent record: what you own, when you bought it, and why. For adults who want a clear ledger rather than an analytics terminal they'll never open, and for children who have never been able to see what's held in trust for them.
A second product is in early development. We'll put it here when there's something worth showing rather than something worth announcing.
Three shapes cover almost everything. If yours doesn't fit, say so and we'll work it out.
An agreed outcome, an agreed price and an agreed date. Best when you know what you need and want it built properly the first time.
A standing block of engineering time each month. Best for products that need continuous attention rather than one big push and a long silence.
A few days spent reviewing an architecture, a codebase or a plan, ending in a written recommendation specific enough to act on.
A couple of paragraphs is plenty: the problem, the deadline if there is one, and what's already been tried. We'll tell you honestly whether we're the right fit for it.
hello@dallatech.com.auMelbourne, Australia · AEST (UTC+10)