Bloody good software.

For Australian businesses whose tools don't quite fit how they work. Client portals, internal tools and AI workflows, built in weeks and looked after once they're live.

Tell us what you're working on See the work
Recent work

Two subscriptions out. One portal in.

● live, in client use Bespoke client workApr → May 2026

Wealth Advisory Portal

A single-tenant adviser-and-client portal for an Australian financial advisory firm. It replaced two paid SaaS products outright, one for collecting client information, one for electronic signatures, and bolted AI document-extraction onto their existing CRM so the firm stops re-typing data they already have.

The pitch in plain English: a client gets a text-message-protected link, sees their information already filled in, confirms or corrects it, and signs the result. The adviser runs the review meeting against the same data. The signed bundle lands in the firm's filing system with a full audit trail.

  • 2
    SaaS subscriptions replaced
  • 24 days
    From first commit to launch
  • 30 days
    To first paying-client use
  • Built forAustralian financial advisory firm (AFSL)
  • Replacesmyprosperity & FuseSign
  • AugmentsExisting practice-management CRM
  • StatusLive, ongoing retainer
Read the technical case study → Try the walkthrough demo →

Run a financial advice firm? See the adviser portal page.

What we build, and what we don't leave behind.

// what we build
Client portalsInternal toolsAI-assisted workflowsMobile apps
production, end to end
// the work we replace
Manual data entryPDF & document handlingForm-collection toolsVendor SaaS you've outgrown
fewer subscriptions
// how we work
Paid discovery firstClear written specsWeekly demosSupport after launch
no black boxes
// if we part ways
Code in your repositoryDocumented deploysMainstream stackNo lock-in
nothing held hostage
How an engagement runs

Small steps, each one agreed.

// 01

Discovery

A short paid sprint. We map the workflow, review the systems involved, find the highest-leverage target, and test the riskiest assumption before anyone commits to a full build.

// 02

Scope

Discovery becomes a written plan: what we are building, what is out of scope, the delivery stages, acceptance criteria, and timeline. You review it before the build starts.

// 03

Build

We build in visible stages with regular demos and async updates. Code lives in your repository from day one, with deployment and operating notes documented as we go.

// 04

Care or handoff

You get the code, the deployment process, the docs, and 30 days of support. After that, keep us on the care retainer to run and improve it, the way our current portal client does, or take it over yourself: everything you need is already in your repository.

Services, scope and FAQs

Got a workflow held together by spreadsheets and goodwill?

Send through the workflow, the systems involved, and what currently breaks. We'll tell you quickly whether it's a readiness session, a discovery sprint, a build, or not a fit.

Get in touch → Read the case study