← cd ../services
05 / software/build● 14 platforms shippedTypeScript · Python · .NET

Software that fits your business.

Bespoke enterprise platforms, workflow automation, internal tools and integrations. Written in TypeScript, Python, .NET. Built to replace spreadsheets, not multiply them.

NodePython.NETPostgresKubernetes
Workflows3,842↑ 22%
Hours saved1,290↑ 18%
$ what we ship

Six kinds of bespoke build.

If your business runs on spreadsheets, email chains and one very stressed operations manager, this is the section for you. Real software, priced fixed, delivered against your actual workflow.

01
Internal ops platformsCustom back-office tools for the workflow no SaaS quite fits. Roles, audit logs, exports, approval trails, single-sign-on baked in.
02
Workflow automationAutomate the 40 repetitive things your team does every day — inbox triage, quote generation, PDF processing, CRM sync, scheduled reports.
03
Integration & middlewareStitch Xero, Salesforce, HubSpot, SAP, MYOB, Cin7 and legacy databases together. One source of truth, no more copy-paste.
04
Data platforms & dashboardsWarehouse the data you already have (BigQuery, Redshift, Snowflake), then surface it in dashboards your ops team actually opens on Monday morning.
05
Legacy modernisationAccess DB, VB6, old .NET Framework, Delphi — rebuilt in modern stacks with the same behaviour, without a scary big-bang cutover.
06
Multi-tenant SaaSBuilding a product for your industry? We handle billing, tenancy, RBAC, usage limits, admin, onboarding — the boring 40% that always eats budget.
$ our process

Six phases from workflow to warehouse.

Every engagement runs the same six phases, in the same order. Fixed scope, fixed timeline, fixed price — agreed in writing before we open the IDE.

  1. 01

    Discovery & workflow map

    Week 1 – 2

    We sit with the people who do the work today. Watch their screens, count their clicks, map their exceptions. The proposal that comes out of it reflects reality, not the org chart.

    • Stakeholder interviews with operators + management
    • Process shadowing + workflow diagram (Miro / Whimsical)
    • Data model draft + integration inventory
    • Fixed-price proposal with week-by-week milestones
  2. 02

    UX & architecture

    Week 2 – 4

    Wireframes for every screen, hi-fi Figma for the top five flows, plus an architecture doc your future CTO will thank us for. Databases, services, queues — drawn before any code.

    • Wireframes for every screen (desktop-first, mobile-aware)
    • Hi-fi Figma design system + component library
    • C4-model architecture diagrams + ADRs
    • Postgres schema draft + migration strategy
  3. 03

    Foundations & SSO

    Week 4 – 6

    Repo, CI, staging, SSO (Azure AD / Google Workspace / Okta), RBAC, base component library — everything before feature work. Getting foundations wrong is what makes rebuilds necessary.

    • GitHub / Azure DevOps repo with branch protection + CI
    • Staging environment live from day one
    • SSO + fine-grained role model (Casbin / Cerbos)
    • Audit-log pipeline + immutable event store
  4. 04

    Feature sprints

    Week 6 – 22

    Two-week sprints. Every Friday a demo on staging with real data, real users, no PowerPoint. Ops team invited to every one — they're the ones who'll live in it.

    • Weekly Friday demo call (30 min, recorded, ops invited)
    • Linear board you can see and comment on
    • Daily deploys to staging, feature flags for gated rollout
    • End-of-sprint retro + next-sprint plan
  5. 05

    Migration & hardening

    Week 22 – 26

    Data migration from the old system (Excel, Access, MYOB, whatever), pen test, load test, disaster-recovery drill. We break it in staging so nothing breaks in production.

    • ETL scripts for legacy data + reconciliation reports
    • Load testing (k6) at 5× projected peak
    • OWASP Top-10 review + third-party pen test
    • DR runbook + tested restore-from-backup drill
  6. 06

    Cutover & 90-day support

    Week 26 → 38

    Staged rollout by team, then org-wide cutover on a weekend. On-call for the first 90 days — bugs, tweaks, training questions, all included. Old system stays read-only for 6 months.

    • Staged rollout by department + rollback plan
    • End-user training sessions (in-person or Zoom)
    • Uptime + error monitoring (Sentry, Grafana, Datadog)
    • 90 days of bug fixes & tweaks — no ticket queues
$ what you own

What lands in your hands.

Final milestone paid, every artefact transfers. Source, cloud accounts, secrets, docs — no vendor lock-in, no rent-seeking, ever.

Full source repo

GitHub or Azure DevOps repo transferred to your org. Every commit, every PR, every review — yours.

Architecture & ADRs

C4-model diagrams, sequence diagrams, ADR log for every consequential decision. Written so a new hire can read one and move on.

Cloud accounts & secrets

AWS / Azure / GCP accounts registered under your name from day one. Vault or Doppler tenant with rotation policies.

Runbook & DR plan

Deployment runbook, on-call escalation, RTO/RPO, tested disaster-recovery playbook — not a wiki page nobody reads.

Test suites

Unit, integration, and Playwright E2E suites. Coverage report, mutation-testing baseline, CI running them on every push.

End-user training pack

Video walkthroughs, printable SOPs, in-app tour scripts — the stuff your ops team needs on day one, not month three.

$ tech stack

The stack we reach for.

Boring on purpose. Every tool here is battle-tested, actively maintained, and hire-able for anywhere in Brisbane, Sydney, Melbourne, Auckland or Wellington if you want to bring it in-house later.

Frontend
  • React
  • Next.js
  • TypeScript
  • TanStack Query
  • Radix UI
Backend
  • Node.js
  • Python (FastAPI)
  • .NET 8
  • NestJS
  • Temporal
Data
  • Postgres
  • Redis
  • BigQuery
  • Snowflake
  • Kafka
Auth & SSO
  • Azure AD / Entra
  • Okta
  • Auth0
  • Cerbos
Infra
  • AWS
  • Azure
  • Kubernetes
  • Terraform
  • GitHub Actions
Observability
  • Datadog
  • Sentry
  • Grafana
  • OpenTelemetry
$ timeline & investment

Rough shape of a software engagement.

Real numbers from the last dozen bespoke builds. Actual pricing lands after discovery — but this is the sensible band to plan around.

Typical timeline
00 weeks
Internal tool with 3 integrations: 10–14 weeks. Multi-tenant SaaS with billing: 18–26 weeks. Legacy modernisation with migration: 24–32 weeks.
Investment (AUD)
$0k – $0k
Fixed price, four milestone payments. Care plan from $450/mo covers dependency updates, minor tweaks, on-call.
0
Platforms shipped in 2025
0%
On-time launches
0%
Uptime SLA
0 min
Avg first reply
$ questions

The stuff every client asks first.

If your question isn't below, we'll answer it on the discovery call. No sales pitch — just an honest read on whether we're the right shop.

Should I buy off-the-shelf or build custom?
Buy off-the-shelf, always, if a SaaS covers 80%+ of your workflow. Custom software costs 10–50× a SaaS subscription over five years. We build custom when: (a) your process is your differentiator, (b) no SaaS fits without ugly workarounds, or (c) you've outgrown three SaaS options in a row. We'll tell you honestly which bucket you're in.
Can you integrate with our existing systems?
Almost always. We've integrated with Xero, MYOB, Salesforce, HubSpot, SAP, Cin7, NetSuite, Dynamics 365, Azure AD, Okta, and dozens of legacy SQL Server / Access databases. If your system has an API, a CSV export, or an ODBC driver, we can work with it.
What about hosting — on-prem, cloud, or hybrid?
Cloud by default (AWS, Azure or GCP — your choice). Sydney or Melbourne regions for AU data-residency, Auckland region for NZ. On-prem or hybrid where compliance (PCI, IRAP, health) demands it — we've done both. Every deployment is Terraformed and reproducible.
Who owns the code?
You do. On final milestone payment we transfer the repo, cloud accounts, DNS, secrets vault, license keys — everything. No vendor lock-in. If you decide to move to a different agency next year, we hand over a runbook that lets them start on day one.
How do you handle changing requirements?
Small changes (a field, a rule, a copy tweak) — included in the current sprint. Anything that shifts scope by more than half a sprint gets its own change order, priced fixed, before we do the work. You always know what the next invoice looks like.
Do you take over projects someone else started?
Often, yes. We run a paid 2-day audit — codebase health, tech-debt inventory, security posture, test coverage — and quote the continuation honestly. If the codebase is beyond rescue we'll say so and quote a rebuild with staged cutover, not a big-bang rewrite.
Do you work outside Brisbane?
Yes — every engagement runs remote-first from our Brisbane studio, with on-site availability across Sydney, Melbourne, Perth, Adelaide, Canberra, Auckland and Wellington. For enterprise engagements we do embedded weeks on-site during discovery and cutover.

Ready to replace the spreadsheet?

Free 30-minute discovery call. We'll reply within 1 business day.