Yellow Brick Road

700 documents a month, handled — without the workflow your team hates

Your team handles around 700 client documents a month across three branches. Today that means hours of manual reading, relabelling and filing for every application. You've already seen what happens when that gets automated badly: a well-funded, AWS-backed build spent close to two years and a reported ~$170,000 and never got past the first stage. It broke on a single interstate licence, and every change meant going back to the vendor.

This proposal is different in one important way: the hard part is already proven. We ran your exact problem — the six situations that stalled the last build, plus six real phone-photo IDs — and it cleared all of them.

The budget was never the problem. The approach was.

You run a busy YBR franchise: 11 brokers, three branches, around 45 settlements a month and roughly 700 client documents flowing through a shared admin inbox. Every application means someone opening attachments, working out what each document is, renaming it to your convention, filing it into the right client folder, and checking it against a compliance checklist that changes regularly. It works, but it eats the time your team should be spending with clients.

You tried to fix this once already. The previous provider, brought in through AWS, invested close to two years and a reported ~$170,000. It never got past stage one. It broke when a Western Australian licence didn't match the format it expected, and adapting to anything new meant a fresh quote and a wait — sometimes months. A new compliance checklist landed the day before we first spoke, which is exactly the kind of change that approach can't keep up with.

A rigid system, in an industry where the rules never stop moving, was always going to stall.

We ran your problem first

Before asking you to spend anything, we built a realistic application pack and seeded it with the six situations that broke your last build — then ran six real phone-photo IDs through the same reading layer: three states, an overseas passport, a Medicare card.

Six real documents, photographed on a phone the way a client would. Each one identified and read correctly.

The six situations that stalled the last build — all cleared

An intake system that adapts instead of breaking

The difference between this and what you had is one word: adaptive. The old system worked off fixed rules, so every new bank layout, unusual document or compliance change meant going back to the vendor, paying more and waiting. This reasons about what it's looking at the way a trained admin would — so a new format or a new checklist is just another day. When compliance changes, it adapts. You don't lodge a change request, and you don't wait three months.

What the broker receives for every application. (Sample shown on synthetic data — fully tweakable to your format.)

How your clients' data is handled

You're handling identity documents and financial records, so this matters as much as the result.

• Processing happens inside your own Google Workspace — originals are only ever copied, never moved, renamed in place or deleted
• The reading is done by Claude, the AI built by Anthropic, under commercial terms where your data and your clients' data are never used to train any AI model
• Short, defined data retention, with stricter zero-retention handling available for sensitive use
• Least-privilege access you can revoke at any time
• A human stays in control — anything uncertain waits for a person, it is never auto-filed
• This is document intake and admin support, not a credit assessment or financial advice

A full Statement of Work will set out scope, data handling, responsibilities and terms — including that the AI is not responsible for credit, financial or compliance decisions, which remain with your qualified team — before any real documents are touched.

What this is worth to the branch

Illustrative, using your own numbers from our call. Final figures depend on your volumes and how you redeploy the time.

Conservative read: on reclaimed admin time alone the build pays for itself in roughly 9–10 months. Added client-facing commission brings payback to about 2–3. Figures are estimates and depend on how the reclaimed time is used.

Build your engagement

One build, delivered in two stages. Phase 2 follows a successful pilot. All prices + GST.

The road this opens up

The pilot and first deployment solve document intake. That same foundation is the start of a ladder you named yourself — scoped and quoted one build at a time, so you only ever pay for what's working:

• Cloud hosting plus a SalesTrekker API write-back — extracted data flows straight into your CRM and runs fully hands-off, once YBR's v2 API is available
• A fuller credit overview, built on top of the financial flags
• Rollout across all three branches and 11 brokers
• Ongoing adaptation as compliance and formats change

Australian businesses are already seeing results.

Every engagement starts with the same kind of proof you're reading now. Here's what that's led to for businesses like yours.

Trusted by

Ready when you are — live by the end of June

Email us to go ahead. We'll collect the initial pilot payment and sign a Statement of Work with you — including the confidentiality clauses that protect your clients' data — and start building straight away. Expected live by the end of June.

Chris Gulotta · NxtLayr AI · 0477 018 400 · hello@nxtlayrai.com