Make
Zapier
12 CRMs
For Australian mortgage brokers
The date is already in the file. Be in front of it.
Ninety, sixty and thirty days before a client’s fixed-rate period ends, 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.
fixed-rate end date
covered
download
until you flip a switch
What lands on your desk
A diary event, handled before the loan reverts.
The engine does not decide fixed or variable. It gets you ready to have that conversation, three times, on the dates that matter.
Book the review. Look up the revert rate on this product, remaining term, offset and extra-repayment rules. Ask whether they might sell, renovate or pay a lump sum.
Do not recommend a path until the file has been run. Do not quote a rate the file has not given you.
Emailed to youHi James,
Your fixed period ends on 20 November. I wanted to get in front of it rather than talk after it has already reverted.
If nobody does anything, the loan stays with the same lender and reverts to that product’s variable rate. That is the default, not a recommendation.
Worth a review so we can walk through the file together?
The conversation belongs on the file, before the date, not after the revert.
The problem
The end date is sitting there. The review is not.
Every settled client on a fixed rate has a date. Most CRMs store it. Few of them put a task, a draft and a note on your desk at 90, 60 and 30 days out.
So the date arrives, the loan reverts to that product’s variable rate, and you are having the conversation after the fact. The file still needed the revert rate looked up, the offset rules checked, and a calm question about what the client actually wants next. None of that is a sale. All of it is work that has to happen on time.
Fixed ending is a diary event, not a pitch. The engine will not tell anyone they will be cheaper on variable, invent a saving, or quote a rate the file did not give it. If a draft ever does, you delete it.
One client, one window
Watch the date. 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 window cannot fire twice. The next window can, when its date arrives.
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”,
“fixed_expiry_date”: “2026-11-20”,
“tbt_last_window_sent”: “”,
“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.com
Import the outreach blueprint first so you have a webhook URL. Then import the watch for your CRM and paste that URL in. About twenty-five minutes for a native CRM. Longer if you are wiring HTTP for an API CRM.
- 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.
Zapier
Zapier cannot import a workflow file. The Zapier guide is click by click: Catch Hook, the consent and window filter, ChatGPT, Gmail to you, the task, the note, the stamp. Two Zaps, same split as Make. Longer than an import, and nothing is left to guess.
The middle of Zap B is identical for all twelve CRMs. Only the first step and the last step change.
Create the fields before you import. The watch blueprints are mapped to tbt_fixed_expiry_date, tbt_fixed_expiry_state, tbt_last_fixed_expiry_touch and tbt_last_window_sent. If those names are missing, the modules show as invalid. If your CRM already stores the fixed-rate end date under another name, map that field. Do not invent a second source of truth. Exact names per CRM are in the field map.
What lands in your inbox
Twenty-four 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 fixed-versus-variable 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
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 date 90, 60 or 30 days out. Run once. You should get a broker email, a task and a note. You should not get a client email. Run again: no second draft for that window.
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.
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 fixed expiry.
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 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.
✓Never quote a rate the file did not give you✓Never invent a dollar saving✓Never say they will be better off on variable✓Never tell them to break the fixed rate✓Never create urgency✓Existing clients only. Not a purchased list.
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 fixed-expiry 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 fixed-rate end date. 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 fixed rate, you are comfortable connecting Make or Zapier, and you want the 90 / 60 / 30 work 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, say the client will be better off on variable, tell them to break the fixed rate, 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. Twenty-four 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 before the loan reverts, with the file work already listed and the first lines already drafted.
A Tuesday morning. A 60-day window opened 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 before the fixed period ends.
Twenty-four files. Make import or Zapier click by click. ChatGPT and Claude skill included. One payment, instant download, yours to keep, and thirty days to change your mind.
Questions: matt@thebrokertimes.com.au
The Fixed Expiry 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.