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 2026The 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.
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.
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.
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.
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.
One room. Your people, your agents, every action on the record.
Every concept on this page would run inside a private room like this: your team and the agents in the same space, drafts appearing with receipts, a named person saying yes. It runs on infrastructure you approve — and what is said in the room stays in it.
receipt sources: your rate card · rules: yours · held for approval
Client information stays in your room. Six months later, “where did this come from?” is one line, not a search.
Yours
Runs where you approve — your own room, your own record. Nothing in it leaves it.
On the record
Every agent action lands as a line a person can read — not a log only a vendor can open.
People decide
Drafts wait for a named person. The room shows who said yes, and when.
This panel is a concept picture, not a live room — a pilot stands up the real one, on infrastructure you approve.
The queue, before anything is asked
Illustrative and fictional. No production access is requested by this concept.
| Charge | Count | Prepared | Waiting on | Status |
|---|---|---|---|---|
| Matches one open job | — | One question, same day | Customer to answer | Awaiting answer |
| Looks mixed-use | — | Flagged mixed, not apportioned | Hnry to determine | Awaiting review |
| First month, no pattern | — | One question per merchant, once | Customer to answer | Awaiting answer |
| Account under review | — | Nothing asked | A named person | Held — no prompt |
| Merchant never seen before | — | Question drafted, no assumption | Customer to answer | Awaiting answer |
| Receipt image missing | — | Question held | Receipt capture | Parked |
Counts are deliberately blank. This concept has no Hnry data and does not estimate how many charges anything affects.
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.
- 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
- —
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.
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.
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.
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.
Pick a verb.
Not “book a demo”. Any of these is a real next step, and the third is a perfectly good answer.
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.