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 2026Two waits, and the big one is not the application
Someone is seven minutes from an answer that will shape their next three years, and right now those seven minutes are a progress bar. But the seven minutes are not the wait. The wait is the three years that follow — up to two hundred and sixty payments during which the only thing you say to them is a direct debit. Tap between the two on the phone.
Your establishment fee is $240, and under the fees rules that figure has to be no more than what it actually costs you to process an application. A file that arrives complete costs less to process. So the wait can hand part of that fee back and the arithmetic still works — the applicant is paid for reducing your cost, not for borrowing.
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 a three-year silence is three years of a relationship you are paying to keep and choosing not to have.
What the concept does
Spends the wait making the file complete, hands back part of the establishment fee for the cost that saves, and stops.
Six waits, one pattern.
Each of these is a moment your customer already spends with you. Each can carry what the phone above shows: watch the work, earn the wait, answer one thing.
Be relevant — right thing, right moment · Be respectful — short, skippable, quiet by design · Be measurable — real impact, on the record · Be Aotearoa — built here, for how Kiwis actually wait
Every waiting moment in a personal loan
Six real gaps between wanting a loan and finishing one. Each is time the customer already spends, spent on nothing.
You find out where you stand before anything touches your credit file.
The wait builds a complete file, so nobody has to chase you for the same three documents tomorrow.
You can see which check is still running, so silence stops meaning something has gone wrong.
You know the day money arrives and the day the first payment leaves, before either happens.
Each payment tells you something about your own record instead of just disappearing.
You leave with written proof of how you paid, useful to any lender, not only this one.
Four steps, every time.
- The signalSomething in your own systems says a person is now waiting, and roughly how long for.
- The predictionHow long this one will really take — not the average, this one.
- The valueSomething worth their attention goes into that window: an answer, a credit, a thing prepared while they wait.
- The exchangeThey get value. You get a customer who stayed, and one optional answer you have always wanted.
This is the reward layer, running for real on this page. Drag to scratch it. Nothing is collected, nothing is sent — it is here so the idea is something you do, not something you read.
US retailers lose an estimated $37.7 billion a year to customers who abandon because of long queues, split roughly $15.8b to competitors and $21.9b abandoned outright (Adyen with 451 Research). The New York State Department of Labor reported a 48% reduction in hang-ups after introducing virtual queuing. Theme parks moving to virtual queues reported a 36% lift in per-capita spending, because guests spent the wait somewhere that sold something. A Seattle-Tacoma Airport study found 63% of passengers said they shopped or ate more because they saved time in the security queue.
Every figure on this page carries its source. Overseas figures are shown as overseas figures — we have not found a published New Zealand equivalent, and we will not invent one.
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. No interest-free period or rate concession was offered. The fee credit is capped and cost-justified, and it is earned by completing the file rather than by drawing down. 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
- —
Why this concept, for Nectar, now.
Nothing on this page is modelled, projected or borrowed from a slide. These are your own published facts, and the concept above is built on them.
The same evidence, on one page you can print or send: the one-pager →
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.
What a pilot actually asks of you.
Written out in full, because the honest version of this is short and most of it is your time, not your money.
One named person
The approver. Every draft stops with them and nothing reaches a customer until they say so. Expect about two hours a week — reading drafts, not managing a project.
One situation, not the business
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.
Read-only access, nothing that writes
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. No production credentials, no write permissions, no access to anything the pilot does not need.
Your actual rules
The policies, limits and words the drafts must be held against. Every rule on this page is a placeholder standing in for yours. An afternoon with whoever owns them is usually enough.
Six weeks, then a real decision
Scored on: 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 that and we change the design or stop. You keep everything drafted either way.
A fixed fee, agreed in writing first
No number is published on this page, because it depends on which situation you pick. Whatever it is, it is agreed before any work starts and it does not move.
Run the pilot.
Say yes to the six weeks above, and add anything you would change first. Nothing here is fixed — most pilots move a line or two before they start, and the notes below are how that happens.
Opens your mail app to assembl@assembl.co.nz with your notes in it. Nothing is collected by this page.
- Six weeks, one situation, scored against a written line
- Read-only access, nothing production
- A named approver — nothing sends without them
- A fixed fee, agreed in writing before anything starts
- Stop any time. You keep what was drafted
Pick a verb.
Not “book a demo”. Any of these is a real next step, and the last one 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.