Home Blog About
• 6 min read

A Budget 2026 Matrix for Real Investor Decisions

I built a public matrix that turns abstract Budget 2026 tax claims into concrete scenario-by-scenario decisions across investor archetypes and life stages.

TechnologyAIPublic PolicyData VisualizationOpen SourceSide Project

When tax policy gets debated online, most of the heat comes from compressed slogans.

“This will kill aspiration.” “This only hits the rich.” “Property investors will just adapt.” “Founders are finished.”

Those claims might contain a grain of truth, but they flatten a policy package that behaves very differently depending on who you are, what you own, and which version of the policy actually survives.

So I built a public tool to make those trade-offs visible:

Australia’s Budget 2026 Matrix

It asks a simple question:

If the policy lands in one of several plausible forms, what does a rational person in a specific position actually do next?

It sits alongside two related tools:

The fact-check site tells you what the source documents say. The calculator helps you stress-test assumptions. The matrix sits between them, turning policy variation into decision pressure.

Why I Built It

Most policy explainers stop at “here is what the rule says.” That is necessary, but not sufficient.

People do not experience tax reform as a block of legislation. They experience it as a decision problem:

  • Should I buy now or wait?
  • Does this still work if the headline concession disappears?
  • Am I actually grandfathered, or did I miss the window?
  • Is the benefit real, or is it just a short transition sugar hit?
  • Does my structure matter more than my asset choice?

Those questions are inherently conditional. They depend on timing, asset mix, legal carve-outs, and behavioural assumptions. A plain article can explain that in prose, but it is hard to scan. A calculator can model numbers, but it does not automatically tell you how the strategic pressure shifts across different kinds of people.

That is what the matrix is for.

What the Matrix Does

The tool maps 120 cells across three axes:

  • Archetype: passive investor, active investor, property investor, founder
  • Life stage: early career, mid-career first-home-buyer, peak earner, pre-retiree bridge, retiree decumulation
  • Scenario: six policy branches ranging from “passes as announced” to softened or repealed versions

Each cell contains:

  • a recommended action
  • the reasoning behind that action
  • the key assumption that could break it
  • the regret profile if the scenario resolves differently
  • a payoff direction from strongly positive to strongly negative

The interface deliberately stays compact. On desktop it renders as a 2×2 board, one panel per archetype, with coloured dots for each life-stage and scenario intersection. Clicking a dot opens a drawer from the right with the full details for that cell.

That design choice matters. I did not want a scrolling wall of cards. I wanted something that feels closer to scanning a strategy board than scrolling a blog archive.

The Hard Part Was Making the Content Honest

The visual layer came together quickly. The harder problem was making sure the matrix earned its granularity.

Early versions of the matrix had a common failure mode: the payoff colours were too repetitive. If scoring is mostly assigned at the archetype level, you end up with a pretty board that looks more granular than it really is. Different life stages appear distinct while quietly inheriting the same conclusion.

That is misleading.

I reworked the generator so payoff is computed per cell rather than by scenario label alone, and added validation so each archetype needs genuinely distinct life-stage patterns. That forced sharper distinctions:

  • a peak-earning property investor is not in the same position as a retiree with an existing holding
  • a founder with active-business relief is not the same case as a founder planning a plain vanilla exit
  • a passive ETF accumulator does not behave like a trust-heavy active strategy just because both sit under “investor”

The result is less visually neat, but much more useful.

One Spec Patch Changed a Lot

The most important correction involved negative gearing timing.

The first pass treated 1 July 2027 too loosely, as if it were the single decisive cutoff for property action. That was wrong. The actual logic had three relevant dates:

  • Budget night as the grandfathering cutoff
  • the grace window between Budget night and 30 June 2027
  • 1 July 2027 as the commencement date for the new regime

That distinction changes the action logic across a large slice of the property cells.

If Budget night has already passed, “buy before 1 July 2027 to preserve full grandfathering” is no longer a valid recommendation for a new buyer. The real strategic question becomes whether a property still works once post-2027 loss quarantining is the long-run baseline, with only a temporary grace-window deduction on the way in.

That single patch forced a regeneration of roughly thirty cells and made the property side of the matrix much more trustworthy.

Why the Tool Is Split Into Three Public Surfaces

I could have forced everything into one app. I think that would have made each part worse.

The separation is intentional:

  • Factual AU answers: what do the source documents and public claims actually say?
  • The calculator answers: what happens to the numbers if I vary dates, returns, inflation, or relief settings?
  • The matrix answers: given a scenario and a position, what strategic move is being implied?

Those are three different cognitive jobs. Keeping them separate makes each interface simpler, while links between them let you move from narrative, to calculation, to scenario pressure-testing.

Open Source and Agent-Readable by Default

All three surfaces are public and open source:

I also added lightweight agent-readable metadata to each site through /.well-known/ai-context.json and llms.txt. That gives visiting agents a structured description of what each surface is for, how to interpret it, and where the underlying data or methodology lives.

That is a small detail, but I expect more sites will need it. If a site is meant to inform both humans and software agents, the context layer should be explicit rather than inferred from random page scraping.

What I Like About the End Result

The thing I like most is that the matrix resists clean ideological storytelling.

It does not produce one universal verdict like “good policy” or “bad policy.” It shows that the same package can create:

  • mild friction for one cohort
  • a major behavioural shift for another
  • mostly headline panic for a third
  • and a genuine strategic cliff for a fourth

That is closer to how policy actually works.

If you want to explore it:

The underlying pattern feels reusable. A lot of public-policy communication problems are really scenario-mapping problems in disguise.

Once you see that, a matrix starts to feel more honest than a headline.

Share: