For Australian mortgage brokers
Make
Zapier
12 CRMs
The Loyalty Tax Engine · for every major broker CRM
The gap is already in the book. Put it on the desk.
When a settled client’s current variable rate sits above your new-money / retention reference, the engine writes a broker task, an outreach draft and a CRM note, and emails them to you. It does not email the client until you flip a switch.
gate
covered
download
since June
What lands on your desk
A rate gap on the book, handled before it walks.
The engine does not decide switch, reprice or refinance. It gets you ready to open the file when the gap clears your threshold.
Open the file. Confirm current rate and your new-money / retention reference. Check offset, extra-repayment rules, and whether the current lender will haggle before anyone talks refinance.
Do not recommend a path until the file has been run. Do not invent a rate or a dollar saving.
Emailed to youHi James,
I have been through your file. Your current rate sits above the new-money figure I hold for this product. I wanted to walk it with you rather than leave it sitting.
That does not mean you should switch. It means we open the file properly and I come back with numbers from your record.
Worth fifteen minutes this week?
The conversation belongs on the file, while the gap is still sitting there.
The problem
The gap is sitting there. The task is not.
Every settled client on a variable rate has a current price. Few CRMs put a task, a draft and a note on your desk when that price sits above new money.
So the loyalty tax sits in the book while new-money keeps cutting. Late August 2026 desk context from The Broker Times: 35 lenders have cut new-money variables since 1 June, and 52 offer at least one variable below 6%. That list is for your desk before 28 September — not a pressure line for the client. None of this is a sale. All of it is work that has to happen on the file.
A gap is a reason to open the file, not a pitch. The engine will not invent a rate or a saving, or tell anyone they should switch. If a draft ever does, you delete it.
The product, on the canvas
Watch. Outreach. Webhook. Already on the canvas.
Scroll the sequence. The screenshots pin and crossfade. Make watch, outreach and webhook first, then the Zapier watch.
Read the book. Gate the gap.
The HubSpot watch is already on the canvas: search contacts with a loyalty gap, filter, then POST the payload into outreach. You import the file. You do not drag a module.
Task, draft, note. Emailed to you.
Outreach writes the broker task, the outreach draft and the CRM note, then emails you. The client stays off until you flip auto_email_client.
Same middle, every CRM.
Only the first step and the last step touch your CRM. The webhook is the hand-off. Native, API or the Google Sheets bridge all land here.
Schedule the watch. POST the payload.
The HubSpot watch Zap is a daily schedule, then a webhook POST into outreach. Same split as Make: watch the book, then the middle. Zapier cannot import a workflow file — the guide walks this canvas click by click.
One client, one window
Watch the gap. Draft the pack. Email you.
Only the first step and the last step touch your CRM. The middle is the same for every system on the grid below.
A stamp is written so the same gap window cannot fire twice in a week. Refresh the rates and re-queue when you want it again.
The default, on purpose
It notifies you and drafts. It does not email the client.
Every watch in the pack sends auto_email_client = false. The client-email route exists. It does not run until you flip that switch, after you have tested the loop on yourself.
Until you do, nothing leaves your office except a broker task, a draft in your inbox, and a CRM note. That is the product. Not a campaign pointed at your book.
- ✓Existing clients only. If the record is not already a client, the gate drops it.
- ✓Opt-outs are held. A record stamped opt-out never gets a draft.
- ✓Same window, once. The stamp is the module you cannot skip.
“email_optout”: “false”,
“tbt_loyalty_gap_bps”: “50”,
“tbt_loyalty_state”: “due”,
“auto_email_client”: “false”
Flip the last line to true only after the pre-launch checklist passes on your own record. There is no reply-triage in this pack. If you cannot honour an unsubscribe the same day, leave it off.
The install
You import a file. You do not build this.
On Make, the watch and the outreach appear on the canvas already wired. On Zapier there is no import file, so the guide walks the identical build screen by screen.
Make outreach, already wired. Webhook in, AI draft, then broker email, optional client email, and CRM write-back. You import the file. You do not drag a module.
The webhook, on the canvas. Copy this URL, then paste it into the matching watch. Native, API or the Google Sheets bridge all land here.
Zapier outreach, click by click. Catch Hook, then the filter. Zapier cannot import a workflow file, so the guide walks this canvas.
Zapier watch, HubSpot. Schedule every day, then POST the payload into outreach. Same split as Make.
- Scenarios, then
Create a new scenario - The
...menu on the empty canvas, thenImport Blueprint - Choose the outreach file. Copy the webhook URL.
- Import the matching watch. Paste the URL. Sign in.
About twenty-five minutes for a native CRM. On Zapier there is no import file — Zapier does not allow it — so the Zapier guide walks the identical build screen by screen. Two Zaps, same split as Make. Longer, and nothing is left to guess.
Create the fields before you import. The watch blueprints are mapped to tbt_current_rate, tbt_new_money_rate, tbt_loyalty_gap_bps, tbt_loyalty_state and tbt_last_loyalty_touch. If those names are missing, the modules show as invalid. If your CRM already stores the current rate under another name, map that field. Do not invent a second source of truth. Exact names per CRM are in the field map.
$99 AUD · one-time · instant download
Open the box
This is what you are actually getting.
Not a course. Not a PDF of ideas. The working files, the finished scenarios and every word the system will ever say — already written, already tested, already wired up.
settled variable client.
Use: current rate, new-money,
gap bps — only if supplied.
Rules:
•
•
•
•
• Existing clients only.
new-money → tbt_new_money_rate
gap in bps → tbt_loyalty_gap_bps
state → tbt_loyalty_state
last touch → tbt_last_loyalty_touch
“email_optout”:
“tbt_loyalty_gap_bps”: “50”,
“tbt_loyalty_state”: “due”,
“auto_email_client”:
Flip the last line only after the
pre-launch checklist passes on you.
Example only
What is sitting in the book.
Your settled variable clients, times the gap you already know. Cited numbers only. Nothing leaves the browser, and this is not a saving calculator.
How many files would clear the gate?
Default gate is 25 bps. Type your own counts. The 35 and 52 figures below are late-August 2026 Broker Times desk context, not your book.
Desk context, late August 2026, The Broker Times: 35 lenders have cut new-money variables since 1 June, and 52 offer at least one variable below 6%. That list is for your desk. It is not a line for the client, and it is not a dollar saving.
What lands in your inbox
37 files. One ZIP. No waiting.
A complete do-it-yourself pack. Everything you need is in it, and there is nothing else to buy.
- ✓Five watch blueprints plus one outreach for HubSpot, Salesforce, Pipedrive, Zoho CRM and the Google Sheets bridge, with notes for the five API CRMs.
- ✓The complete Make guide, import first, then connect, then test on yourself.
- ✓The complete Zapier guide, click by click, because Zapier cannot import a workflow file.
- ✓The ChatGPT and Claude skill for the loyalty-tax conversation, ready to paste.
- ✓The compliance pack: consent and opt-out, what the AI must never say, and a pre-launch checklist.
- ✓Field map, sheet template and sample clients so you can prove the loop before anyone else is in the set.
How the setup goes
Five steps. Same middle for every CRM.
Create the fields
Or map the ones you already have. Do this before you import, or the modules will be red.
Import the watch
Outreach first on Make, so you have a webhook. Then the watch for your CRM. Or open the Zapier guide and build both Zaps.
Leave the client switch off
Replace your name, business and mailbox. Leave
auto_email_clientas false.Test it on yourself
Add yourself as a client with a gap at or above 25 bps. You should get a broker email, a task and a note. Not a client email.
Read the first week
Broker judgement stays human. If a draft quotes a rate or invents a saving, delete it and do not send it.
$99 AUD · one-time · instant download · 30-day money-back
ChatGPT and Claude
The same conversation, in the chat tools you already open.
The skill is in the zip twice: a ready-to-paste ChatGPT version and a ready-to-paste Claude version. Load it when you are preparing a review, a call, a CRM note or a client email about a loyalty tax.
It drafts talking points, a task, a note and (only if you ask) a client email. It will not invent a rate, a saving, or a switch recommendation. It will tell you what still has to be looked up on the file.
ChatGPT
Paste 03-skill/chatgpt.md into a custom GPT or a project instruction.
Claude
Paste 03-skill/claude.md, or drop the .SKILL.md into a Claude project.
The skill pane from the pack. Same rules whether you paste into ChatGPT or Claude.
Compatibility
It runs on the CRM you already have
Only the first step and the last step touch your CRM. Everything in between is identical no matter what you run.
Straight answer about the closed ones. Some aggregator-owned platforms will not let an automation read them directly, and that access is granted by the aggregator, not by you. For those, the pack ships the bridge method: you export contacts that have a loyalty-tax date to a Google Sheet and the engine reads that instead. Everything downstream is identical, and the sheet is also the fallback if a native or API connection is blocked.
Who made this
Built by The Broker Times, for the book you already have.
The Broker Times writes for Australian brokers: aggregator platforms, compliance, lender policy, and the work that sits in the CRM between settlements.
This engine came out of that. It is built around existing clients, Australian language, and the specific fact of a loyalty-tax gap. Not a generic nurture sequence with the word mortgage pasted in.
Same middle whether you run one CRM or you add a second later.
Buy this if
You have settled clients on a variable rate, you are comfortable connecting Make or Zapier, and you want the gap of 25 bps or more on your desk without the engine talking to clients first.
Do not buy this if
You want somebody to install it for you. This is deliberately do-it-yourself, which is the only reason it is $99. Also skip it if you were hoping it would email the book on day one, or quote rates. It will not do that.
DAY
Read it, build it, and if it is not for you, tell us.
Email matt@thebrokertimes.com.au within 30 days of purchase and we will refund you in full. You keep the files. We would rather you had a good experience than $99 of ours you resent, and it is the same guarantee we put on everything else in the shop.
Before you buy
Straight answers
Do I need to be technical?
No, but you do need to be the kind of person who has connected two accounts together before, or is willing to follow a guide carefully. If that is not you, this is not the right product and we would rather tell you now.
Will it email my clients?
Not unless you flip the switch. The default is notify you and draft. Every watch sends auto_email_client as false. Flip it only after you have tested the loop on yourself. There is no reply-triage in this pack, so if you cannot honour an unsubscribe the same day, leave it off.
Does it work with my CRM?
See the grid above. Native sign-in for Salesforce, HubSpot, Pipedrive and Zoho CRM. HTTP plus a field map for Salestrekker, Connective, LMG MyCRM, Effi and Finsure Infynity, subject to your aggregator granting access. A Google Sheets bridge for ActivePipe, BrokerEngine and AFG Suite360, and as the fallback for any of the others.
Make or Zapier?
If you use Make, you import two blueprints. If you use Zapier, you follow the click-by-click guide, because Zapier cannot import a workflow file. The engine is the same either way: a watch, then the same middle, then a task, a note and a stamp.
What does the AI refuse to say?
It must not quote a rate, invent a saving, tell anyone they should switch, reprice or refinance, or manufacture urgency. Before you go live you run it on yourself and read the output. A prompt is a strong instruction, not a hard control, which is why the default is email you, not the client.
What exactly do I receive, and when?
A ZIP, on screen the moment you pay, and emailed as well. 37 files: the Make blueprints, both setup guides, the ChatGPT and Claude skill, the compliance pack, the field map, the sheet template and the sample clients. Bookmark the download page and you can re-download any time.
Do you install it for me?
No. We have kept it do-it-yourself on purpose so the price stays where it is. Everything you need is in the guides. If a file will not open, email matt@thebrokertimes.com.au and we will sort that out.
Is this advice?
No. This is an implementation toolkit. It is not legal, compliance, credit or financial advice. You remain responsible for consent, suppression, sender identification and unsubscribe, and for reviewing what the system drafts on your behalf. The database is yours and the licence is yours.
What it is all for
It ends in a review, not a dashboard.
Every file in this pack exists to put a calm conversation on your calendar while the gap is still on the book, with the file work already listed and the first lines already drafted.
A Tuesday morning. A gap cleared overnight. The task is in the CRM, the draft is in your inbox, the note is on the record. The client has not been emailed. You decide what happens next.
The date is already in the file
Be on the desk while the gap is still sitting there.
37 files. Make import or Zapier click by click. ChatGPT and Claude skill included. One payment, instant download, yours to keep. Thirty-day money-back guarantee: email us within 30 days and we refund you in full. You keep the files.
Questions: matt@thebrokertimes.com.au
The Loyalty Tax Engine is an educational and productivity product. It is not legal, compliance, credit or financial advice. You remain responsible for your own compliance with the Spam Act 2003, the Privacy Act 1988 and the Do Not Call Register Act 2006, and for reviewing what the system drafts on your behalf. Make, Zapier, ChatGPT, Claude, HubSpot, Salesforce, Pipedrive, Zoho, Salestrekker, Connective, LMG, Effi, Finsure, ActivePipe, BrokerEngine, AFG, OpenAI and Stripe are the property of their respective owners and are shown to indicate compatibility only. The Broker Times is not affiliated with or endorsed by them. Example messages shown on this page are illustrative output from the engine and do not depict real clients.