Custom web applications, internal tools and customer portals — built in Australia

A website presents information; a web application does work. If people log in, records are created and updated, permissions differ by role, or the thing has to talk to another system, it is an application. In practice that means internal staff tools and dashboards, customer portals, booking and scheduling systems, quoting and job-management systems, and data pipelines that feed reporting.

It is quoted per project, because a two-screen internal tool and a multi-tenant SaaS platform are not the same job. Fixed-scope website builds start at $4,995 + GST. Application work is scoped in a paid discovery, then quoted as a fixed number before any code is written — you never get an open-ended hourly meter.

A focused internal tool is typically 4–8 weeks. A customer-facing platform with auth, billing and multiple roles is 3–6 months. The variable is rarely the code — it is decisions: who can see what, what happens on an edge case, and which system is the source of truth. Those get settled in discovery so the build does not stall.

Yes. The repository is yours, in your own GitHub organisation, with the deployment pipeline attached. There is no proprietary runtime, no licence to keep paying, and nothing that stops another developer picking it up. That is deliberate: you should be able to leave.

TypeScript end to end, React or Astro on the front, Postgres via Supabase for the database and auth, deployed on Netlify. It matters for one commercial reason: these are mainstream, widely-known tools, so the pool of developers who can maintain your system is large. A clever niche stack is a hiring problem you inherit.

That is usually the point of the build. Existing integrations in production include Pipedrive, HubSpot and Attio for CRM, Stripe for payments and subscriptions, Google and Microsoft calendars, Google Maps and geocoding, Google Ads and BigQuery for reporting, and Zapier where a direct API is not available. If a system has an API, it can be connected; if it does not, that limitation gets named in the quote rather than discovered later.

Aiden Wood, directly. There is no account manager relaying messages to an offshore team, which is why capacity is capped rather than sold. The trade-off is honest: you get the person who wrote the code on the phone, and you wait for a slot.

Yes — application work is remote by nature and clients are Australia-wide. On-site discovery happens in person across the Gold Coast, Logan and Brisbane; everywhere else it is video, and it has never been the limiting factor.

Two options, both explicit. Take the repository and maintain it yourself, or keep a support arrangement for changes, monitoring and new features. Neither is a lock-in: the code and the deployment both stay in your accounts either way.