Prepared for Customer Experience · Hnry · Aotearoa New Zealand
The claimable question · a concept

Never think
about tax again.
Except this bit.

You have automated the hard half — income lands, the right tax comes out, the filing happens. What is left is the half a machine genuinely cannot do alone: whether a particular $180 was for the business. This is a concept for that one question, asked at the only moment the answer is easy to give.

“Never think about tax again®”

Hnry · hnry.co.nz, July 2026
See the moment
01 — THE WAIT
A Thursday, three weeks later

The charge nobody can place

A card charge sits in a list waiting to be classified. The sole trader cannot remember whether the hardware run was for the job or the house, and the honest answer is that at 4pm on a Thursday three weeks ago they knew exactly. Ask then and it takes four seconds. Ask now and it takes a guess.

Your own survey says Hnry customers spend 70% less time on tax and financial admin. The remaining time is almost entirely one thing: someone trying to remember, weeks later, what a charge was for. That is a memory problem, and memory decays by the hour.

Tap it — this is the wait itself, not a picture of it

What happens now

A queue of maybes classified from memory, weeks after the fact, by someone who is not enjoying it.

What it costs

The one part of the promise that still feels like admin — and a guess in a tax record is a risk for both of you.

What the concept does

Asks the one question while the answer is still fresh, and routes the decision to your own review. It never decides.

And the question is the point. One optional question, asked inside the wait, is the only part of this that sends something back the other way. Decline it and the work still gets prepared — just with less of them in it.

02 — THE WORK, PREPARED
The same situation, four ways

One charge. Four honest answers.

The same $180, four situations. Not one of these outputs decides whether something is claimable, calculates tax, or gives advice — that is a registered tax agent’s work, and this concept does not touch it.

WHY THIS ISN'T A TEMPLATE

A template sends the same thing to everyone and changes the name. What matters here is the case that should get something different — or nothing at all.

The rules beside each draft are placeholders. A pilot replaces them with your actual policies. We have not seen those, and this concept does not guess at them.

Nothing here sends
Every draft goes to a named person. No channel is connected by this concept.
03 — THE GUARD
Before a person ever reads it

The checks that run before a single question is asked

Hnry is a registered tax agent. Everything that makes this concept useful sits strictly on the near side of that line, and the guards are where you can see it.

Drafts are held against the tax-agent obligations of the Tax Administration Act 1994, the Financial Markets Conduct Act 2013 advice regime, the Privacy Act 2020, and the Fair Trading Act 1986.

Press run to see what it catches — and what it refuses to produce at all.

04 — ON ONE SCREEN
Nothing here has been sent

The queue, before anything is asked

Illustrative and fictional. No production access is requested by this concept.

ChargeCountPreparedWaiting onStatus
Matches one open jobOne question, same dayCustomer to answerAwaiting answer
Looks mixed-useFlagged mixed, not apportionedHnry to determineAwaiting review
First month, no patternOne question per merchant, onceCustomer to answerAwaiting answer
Account under reviewNothing askedA named personHeld — no prompt
Merchant never seen beforeQuestion drafted, no assumptionCustomer to answerAwaiting answer
Receipt image missingQuestion heldReceipt captureParked

Counts are deliberately blank. This concept has no Hnry data and does not estimate how many charges anything affects.

05 — HOW IT WAS MADE
Mana Receipt

Every draft carries its own working.

Not a log somebody has to go and find. The provenance travels with the work — what it read, which rules it held, who must approve it, and what it refused to do.

This matters most on the day someone asks why it said what it said.

Mana Receipt · draft
Artefact
Same-day expense question — trade supplier charge, one open job
Read
Published pricing, product and survey facts from hnry.co.nz · charge fields: merchant, amount, timestamp, open-job list, review flag. No bank credentials. No IRD correspondence. No tax computation.
Rules held
Tax Administration Act 1994 tax-agent obligations · Financial Markets Conduct Act 2013 advice regime · Privacy Act 2020 · Fair Trading Act 1986
Refused
No deductibility was determined. No tax, rate or refund was calculated. No mixed-use charge was apportioned. No prompt was generated for an account under review.
Approver
A named person. Unsent until then.
Prepared
Reference
06 — WHAT WE ARE ACTUALLY ASKING
The boundary

What this will never do

It does not send. It prepares, and a named person sends. It does not publish to any channel, commit spend, move money, or make a decision that belongs to a person. It does not pretend to be a person — every draft says it was prepared by a machine and approved by a human.

No production access is requested by this concept.

The pilot ask
1

Scope

One moment: the same-day expense question for opted-in sole traders using the Hnry Business Mastercard. Six weeks. Not deductibility, not tax calculation, not filing, not the review queue itself.

2

Access

Your published pricing and product facts, plus the field names for merchant, amount, timestamp, open jobs and review flag. No bank credentials. No IRD correspondence. No customer records leave your systems.

3

Scorecard

Charges answered on the day they happened. Questions avoided by a learned merchant pattern. Held cases a person agreed should have been held. And the honest one: whether an Hnry reviewer trusts a same-day answer more than a three-week-old one.

Fail any line of the scorecard and we change the design or stop.

Three ways to reply

Pick a verb.

Not “book a demo”. Any of these is a real next step, and the third is a perfectly good answer.

The unfinished pane

What is the one constraint we have got wrong?

Every concept is built from the outside. There is always something about how Hnry actually runs that we could not see. One line is enough.

Opens your mail app to assembl@assembl.co.nz. Nothing is collected by this page.

Hnry concept · it will say when it doesn't know