Seven minutes
to a number.
Or to an answer.
You built an engine that quotes in seven minutes, and that is genuinely rare. This is a concept for what else those same seven minutes could produce — not a faster decision, which you already have, but a decision the person actually understands when it lands.
“Fast like a fintech. Fair like a human.”
Nectar Money · nectar.co.nz, July 2026The seven minutes before the number
Someone is seven minutes from an answer that will shape their next three years. Right now those seven minutes are a progress bar. At the end of them a rate appears, and whether it is 9% or 27% they have no way to tell what produced it, what would move it, or what the thing actually costs them in total.
Your rate is personalised, fixed for the life of the loan, and can land anywhere between 7.95% and 29.95% p.a. That is a twenty-two point spread arriving as a single number, at the end of a seven-minute wait, to someone who is applying because something has already gone wrong.
What happens now
Seven minutes of nothing, then a number. The questions that number creates arrive afterwards, by phone or not at all.
What it costs
A rate nobody understands is a rate people re-shop. And an incomplete file spends your assessors’ time, not the applicant’s.
What the concept does
Spends the wait making the file complete and the offer legible, and stops. Your engine still 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.
One applicant. Four honest endings.
The same seven minutes, four situations. Not one of these predicts a rate, approves, declines or prices anything — your engine does that, and this concept never touches 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 lender ever reads it
Everything useful about this concept sits on the near side of the lending decision. The guards are where you can check it stays there.
Drafts are held against the Credit Contracts and Consumer Finance Act 2003 and the Responsible Lending Code, 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 seven minutes, across the queue
Illustrative and fictional. No production access is requested by this concept.
| Application | Volume | Prepared | Waiting on | Status |
|---|---|---|---|---|
| Complete on arrival | — | Offer explained, total cost shown | Your engine | Awaiting decision |
| One document short | — | The exact item named | Applicant to send it | Awaiting applicant |
| Other commitments disclosed | — | Flagged for an assessor | Assessor | Awaiting assessment |
| Language reads as hardship | — | Nothing drafted | A named person, urgently | Held — no draft |
| Term or amount still moving | — | No total displayed | Applicant to settle it | Parked |
| Identity not yet verified | — | Explanation held | ID verification | Parked |
Volumes are deliberately blank. This concept has no Nectar data of any kind and does not estimate how many applications 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
- Seven-minute explanation — complete file, offer legible
- Read
- Published rate ranges, fees and product facts from nectar.co.nz · application fields: submitted documents, stated commitments, requested amount and term, hardship-language flag. No credit file. No bank transactions. No affordability assessment.
- Rules held
- Credit Contracts and Consumer Finance Act 2003 · Responsible Lending Code · Privacy Act 2020 · Fair Trading Act 1986
- Refused
- No rate was predicted. No credit decision was made or implied. Nothing accrued in cash or points. Nothing was drafted for an application reading as hardship, and no total cost was shown where it could still change.
- 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
The seven minutes on one product, for opted-in applicants. Six weeks. It sits beside your approval tool and does not touch it — not the model, not pricing, not affordability, not the decision.
Access
Your published rate and fee tables, and the field names for submitted documents, requested amount and term, stated commitments and a hardship flag. No credit files. No bank statements. No applicant records leave your systems.
Scorecard
Files that arrived at an assessor complete first time. Applications that stopped being re-shopped after the offer landed. Held cases a person agreed should have been held. And the one that matters to you: whether an assessor can tell the difference between a file that went through this and one that did not.
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 Nectar 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.