For brokers/The pack lenders act on
Fewer questions back.
The deal arrives however it arrives. It is read, classified, chased and assembled, and it leaves as a pack a credit officer can act on without coming back to you first.
One asset-finance deal, four hours in
23
Requirements branched from the deal’s type and tier before any request went out
14
Figures in the pack that carry the page they came from
2
Items outstanding and named: requested in your name, chased without you
Halden Freight — hire purchase
Ask
$1,240,000
The business
The asset
Pack readiness
Cover summary — draft
Halden Freight seeks $1,240,000 on hire purchase against 6 tractor units invoiced at $1,378,000, a 90.0% advance over 60 months. Serviceability covers the new commitment =2.18× on FY25 accounts. The debtor ledger disagrees between the aged report and the accounts; both figures are in the pack with their sources, so the lender is not left to find it.
A submission is a moment. A record is what the moment was drawn from.
If someone has to defend a number, to a lender, a client or a funder, it is built on the loan file.
A portal keeps what you sent. The record keeps what you sent, what it was read from, what was still missing when it left, and who asked for it.
Intake meets the deal where it actually happens.
A forwarded thread, six attachments, a photograph of a registration document, and what the client told you on the phone. It is read on arrival and classified before you have opened a spreadsheet.
$1,378,000
Supplier invoice, p. 1 · read 09:12 · sourced
$8,410,000
Statutory accounts FY25, p. 3 · read 09:19 · sourced
$1,180,400 ≠ $1,043,900 · raised
Aged debtor report, sheet 1 · $1,180,400 | Statutory accounts FY25, p. 9 · $1,043,900 · both kept, the pack shows the gap
=2.18× cover
Computed · EBITDA $1,062,000 against $487,000 of annual commitments including this facility · marked computed
3 · $2,090,000
Facility schedule, p. 1 · read 09:22 · three agreements, each one listed
read from photo
IMG_4471.HEIC · read 09:14 · the photograph is the source, and it stays in the file
— named 09:26
Named by the branched checklist before any request went out · tier 2 requires it
— named 09:26
Named by the branched checklist · one named item, not a generic document list
What’s missing is named on the first morning, not in the lender’s third question.
The requirement list branches from this deal’s type and tier, so the gap has a name before any request goes out. Where two documents disagree, both are kept and the disagreement is raised rather than averaged.
— requested 09:41
Sent to the client from your address, in your name · outstanding until a document carries it
— requested 09:41
Sent 09:41, in your name · one named item, and the client replies to you
sent 14:00
Went out on the record's clock, in your name. You did not draft it.
held for release
Drafted and waiting. Nothing leaves until you send it.
The chase runs itself. The relationship stays yours.
Requests go out in your name and land in your thread. Nothing leaves until you send it. What you stop doing is drafting the sixth chase email; the client still hears from you.
The pack leaves with its sources attached.
Nothing is estimated into the pack. Two documents that disagree are shown disagreeing, and your lender needs no account, no login and nothing from us.
Lender pack — Halden Freight
from the record · 13:08
The proposition
Halden Freight, trading 11 years, is replacing 6 tractor units invoiced at $1,378,000 on hire purchase over 60 months, with a client deposit of =10.0%. The replacement cycle was described on a call of 14 July and the note is in the file. FY25 turnover is $8,410,000 against EBITDA of $1,062,000.
Serviceability on the new commitment computes at =2.18×, taking EBITDA against $487,000 of annual commitments including the three existing facilities. One conflict is disclosed rather than resolved: the aged debtor report carries the ledger at $1,180,400 and the FY25 accounts at $1,043,900. Both pages are in the pack, and neither figure was overwritten by the other.
Two items are outstanding and named rather than estimated: Q2 management accounts and proof of deposit, both requested 09:41 and chased 14:00. Nothing in this pack stands in for them.
The borrower
The asset
Outstanding, and named
Every figure, and where it was read · 14 of 14
Demonstration file · a fixture, not a client deal
Fewer questions back is a mechanism, not a promise.
A question about a figure is a page the lender can already open.
09:26
Classified: asset finance, tier 2.
09:41
Two missing items requested, in your name.
11:35
The ledger conflict disclosed in the pack.
13:08
Pack out. Every figure names its page.
4
Approval letter, p. 2 · read 24 Jul · four conditions, each one named on the record
discharged 29 Jul
Registry records and identity documents, filed against the condition they discharge · 29 Jul
discharged 06 Aug
Executed hire purchase agreement, p. 1 · filed 06 Aug
discharged 14 Aug
Certificate, p. 1 · requested in your name 07 Aug, chased 12 Aug, filed 14 Aug
served 20 Aug
Drawn from the record and served on the lender · 20 Aug
=$1,240,200
Computed · $1,378,000 invoiced at a 90.0% advance · funds moved 22 Aug
— due 31 Oct
Requested in your name 23 Aug · outstanding until a document carries it
Approved is not drawn.
The conditions the lender attached sit on the same record, against the same sources, and they chase the same way. So do the items each drawdown needs and the documents due before funds move.
Today the record holds every condition against the file it belongs to. Watching them for you is next.
The record doesn’t get rebuilt. It was never taken apart.
Every broker carries a back book: files dead in a drawer because re-working them costs more than the deal pays. A file written from today forward stays assembled, and a returning client is how an old one re-enters the record.
Every broker will have the tools. Not every broker will have the record.
A file that keeps itself current between deals is what we are building next.
Every deal you write. Every asset class.
From asset and equipment finance to bridging and acquisition, the pack is assembled the same way.
We deploy with you, at your desks.
Week 0
It starts on your file
One of your live deals, branched against your own panel's document tiers before anything is signed. You see where it holds and where it breaks.
Weeks 1–6
Wired into the work
Mailbox, drive, CRM; each lender’s document tiers mapped into the checklist. We sit with your team until the workflow carries itself. The client still hears from you.
Ongoing
Accountable, in the room
On retainer for the connectors, a new lender joining the panel, and the next place AI earns its keep on your desk.
A deployment only counts when the team stops needing us in the room.
AI-ready, not AI-dependent.
What brokers ask us first.
Where does our material sit?
Do we own any of it, or are we licensing?
We have years of old files. What happens to them?
What happens when it reads a figure wrong?
Who sees my client’s material?
What is not built yet?
Watch a deal go lender-ready.
Thirty minutes, live, on a deal we bring: messy on arrival, a pack a lender can act on by the end, and an honest read on where it breaks. Nothing to install and nothing to prepare.
30 minutes · your panel · nothing to install
