It's the third week of October and Craig Morrison hasn't taken a proper lunch break in eleven days. The window behind his desk in Subiaco frames a Perth afternoon so crisp it looks painted — but Craig is staring at a spreadsheet. Again.

Renewal season.

Craig runs Morrison Insurance Brokers, a general insurance brokerage he's built over fourteen years. Two brokers, one admin. Around 400 active policies across commercial property, public liability, professional indemnity, and personal lines. Solid business by any measure — the kind of client relationships that get built over years, not months.

But every year, from October through December, the whole operation nearly unravels under the weight of renewals. "It's like trying to juggle 400 plates at once," Craig told us. "And every year, a few of them hit the floor."

Last year, fifteen did. Fifteen policies that lapsed or moved to a competitor because renewals slipped through the cracks of a manual process that simply couldn't scale.

The Anatomy of a Renewal Nightmare

Insurance broking is fundamentally a relationship business built on trust and continuity. Clients stay with their broker year after year because they believe their broker is watching out for them. But watch-out-for-them, at scale, requires systems — and Craig's systems had been human ones for too long.

1. The Manual Tracking Problem

Four hundred policies. Four hundred different expiry dates, spread unevenly across the calendar but clustering heavily in the final quarter. Craig's admin was managing them in a shared spreadsheet: colour-coded tabs, conditional formatting, a column for "contacted" and another for "response received". It worked fine for a book of 150. At 400, it was a liability.

"We'd set reminders in our calendars for the big ones," Craig says. "But for the smaller personal lines clients, sometimes we'd look up and realise we had a policy expiring in four days and we hadn't sent anything yet."

2. Clients Who Don't Respond

Even when the outreach was timely, getting clients to actually engage with their renewal was a separate battle. Most people don't think about insurance until something goes wrong. A renewal notice sits in an inbox, gets buried under other emails, and by the time Craig's admin was calling to follow up — three, sometimes four calls per client for the stubborn ones — the window for a considered renewal conversation had passed.

Under ASIC's Regulatory Guide 175 and the General Insurance Code of Practice, brokers have genuine disclosure obligations around renewals. Sending a reminder isn't just courteous — it's a compliance requirement. Falling behind on outreach isn't just a retention problem; it's a documentation problem.

3. Eight Insurers, One Spreadsheet

For commercial clients especially, renewal isn't just a matter of renewing with the same insurer. It means getting quotes from up to eight different underwriters, comparing them across coverage terms and price, and presenting the client with a considered recommendation. Craig was doing this manually — exporting data, building comparison tables in Excel, writing up cover notes by hand. For a broker with a full pipeline, each commercial renewal was consuming two to three hours of professional time.

4. Compliance Documentation Falling Behind

Every client interaction needs a paper trail. Under Craig's AFSL obligations and the requirements of RG 175, Financial Services Guides and Product Disclosure Statements need to be current, acknowledged, and filed. As the policy book grew, so did the compliance admin — and it was falling further behind every quarter.

5. Claims Follow-Up as a Full-Time Job

On top of renewals, Craig's team was spending more than five hours a week simply chasing claim status updates and relaying them to clients. Ring the insurer. Wait on hold. Get an update. Email the client. Repeat. It was mechanical, time-consuming work with no leverage whatsoever.

400
Policies to track
15
Policies lost last year
5hrs+
Weekly claims follow-up

The Conversation That Changed Things

Craig isn't an early adopter by nature. He's watched plenty of software promises evaporate over the years, and he's careful about what he introduces into a business where trust is the product.

The conversation that shifted his thinking happened at an industry lunch in Perth's CBD in late 2025. A fellow broker — running a similarly sized book in Fremantle — mentioned she'd deployed an AI system through King Klaw and hadn't touched her renewal spreadsheet in three months.

"I almost didn't believe her," Craig admits. "My assumption was that it would work fine for some generic industry and fall apart the moment it hit insurance-specific complexity — AFSL compliance, the Code of Practice obligations, the way we have to document advice recommendations. I'd tried a couple of general AI tools before and they were completely useless for anything compliance-adjacent."

What changed his mind was learning that OpenClaw's platform was specifically configured for financial services regulatory contexts — not just generic task automation, but an AI that could work within the obligations framework of Australian insurance broking.

He booked a scoping call with the King Klaw team the following week.

The Deployment: Built Around Craig's Book

The first thing King Klaw did wasn't show Craig a demo. It was ask him questions. What did his renewal workflow actually look like, step by step? How did he segment his clients? What did a good renewal outreach sequence feel like to him — not just functionally, but in terms of tone and relationship? What were his AFSL compliance non-negotiables?

"That scoping conversation took about two hours," Craig says. "And by the end of it I realised they weren't going to give me a generic system. They were going to build something that worked the way my business actually works."

The deployment took just over a week. Here's what went live.

What was deployed in week one
  • Automated renewal tracking across all 400 policies — expiry dates ingested, 90/60/30/14/7 day reminder sequences configured per client segment
  • Multi-touch outreach sequences: personalised email → SMS nudge → call reminder flag for the broker, escalating based on non-response
  • AI-drafted renewal summaries for each client, including a plain-English comparison of the incumbent insurer against market alternatives
  • Claims status monitoring — weekly automated updates to clients on active claims, pulling from insurer portals where API access exists
  • Compliance calendar: FSG and PDS version tracking, automatic distribution when regulatory updates require client re-disclosure
  • Post-interaction logging: every outreach, response, and renewal outcome automatically recorded to Craig's CRM for AFSL record-keeping

The compliance piece required particular care. Under ASIC's RG 175 and the General Insurance Code of Practice, renewal communications must meet specific disclosure standards — and the AI-drafted client communications were reviewed against these requirements before going live. The King Klaw team worked with Craig to ensure every templated communication met his AFSL obligations, with override controls so Craig or his brokers could review any client-facing content before it was sent.

"That was important to me," Craig says. "The system does the heavy lifting, but I'm still responsible for the advice that goes out under my licence. I needed to know I had visibility and control."

NemoClaw and ASIC Record-Keeping

One thing Craig didn't expect to care about going in was data security. But during the scoping conversations, the King Klaw team flagged something he hadn't fully considered: every client communication, every renewal recommendation, every compliance document that passes through his AI system is also a record-keeping obligation under his AFSL licence.

OpenClaw's March 2026 release included NemoClaw, a security hardening layer that encrypts data at rest and in transit and provides a tamper-evident audit trail of all AI-generated client interactions. For Craig, this meant every AI-drafted renewal summary, every automated outreach message, every claims status update — all timestamped, logged, and exportable in the format ASIC requires for record-keeping compliance.

Alongside NemoClaw, the release included a backup CLI specifically designed for financial services compliance use cases. Craig's team now runs a nightly export of all AI-generated records to an offline backup, satisfying the record-keeping requirements under his AFSL and the General Insurance Code of Practice without any manual work.

"It's not something I would have thought to ask for," Craig admits. "But now that I have it, I realise it's actually one of the most important pieces. If ASIC ever knocked on the door, I've got a complete, timestamped record of every client interaction the AI handled. That's real peace of mind."

The Numbers, Six Months On

We spoke with Craig at the six-month mark. The results were sharper than either he or the King Klaw team had projected.

Retention Rate: 89% to 97%

The headline number. Before OpenClaw, Craig's annual renewal retention rate sat at 89% — not bad by industry averages, but painful when you run the maths. Fifteen policies lost last year at an average commission of around $3,200 per policy: that's roughly $48,000 in annual commission walking out the door, not because clients were unhappy, but because renewals fell through the cracks.

Six months in, Craig is tracking at 97% retention. The systematic 90/60/30/14/7 day sequence means no policy reaches its expiry date without at least five substantive touchpoints. Clients who previously didn't respond until three phone calls in are now engaging at the first or second email — because the communication is personalised, timely, and gives them something genuinely useful: a clear comparison of their options.

"The renewal summaries are what clients comment on most," Craig says. "They get a one-page overview of their current cover, what we're recommending for renewal, and why. Written in plain English, not insurance jargon. A lot of them have said it's the first time they've actually understood what they're insured for."

32 Policies Saved: ~$48K in Annual Commission

Projecting forward from the six-month run rate, Craig expects to retain 32 more policies this renewal season than he did last year. At an average commission of around $1,500 per policy per year across his mixed book, that's approximately $48,000 in recovered annual commission — from a platform investment that costs a fraction of that.

Claims Follow-Up: Automated

The five-plus hours per week Craig's team was spending on claims follow-up has effectively disappeared. Clients with active claims now receive weekly automated status updates — pulled from insurer portals where possible, or flagged to a broker for manual update where they're not. Craig's team still handles the substantive claims conversations, but the mechanical "what's the status?" calls have stopped entirely.

"One of my clients called last week to say she'd never felt so well looked after during a claim," Craig says. "She'd been getting weekly updates throughout a commercial property claim that took nine weeks to settle. She felt informed the whole way through. That kind of experience used to be impossible for us to deliver consistently — now it's the default."

15 Hours a Week Returned

Across Craig's three-person team, the time audit tells a clear story. Renewal tracking and outreach: from roughly eight hours per week to under one. Claims follow-up: from five-plus hours to under 30 minutes. Compliance documentation: from three hours to less than an hour. In total, more than 15 hours per week returned to the team — hours now going into new business development and client relationships that actually need a human touch.

97%
Renewal retention rate
$48K
Commission recovered
15hrs
Saved per week

"I took my first two-week holiday in five years in January. The book didn't miss a beat. That tells you everything."

— Craig Morrison, Principal Broker, Morrison Insurance Brokers

Compliance Without the Overhead

For insurance brokers operating under an AFSL, compliance isn't optional and it isn't light. ASIC's RG 175 sets out detailed obligations around how financial product advice must be given, documented, and disclosed. The General Insurance Code of Practice adds a further layer of conduct obligations around claims handling, renewals communication, and complaints. And the record-keeping requirements that run underneath all of it demand that brokers maintain detailed, accurate, and accessible records of every client interaction.

For a three-person brokerage, meeting these obligations comprehensively has always meant one of two things: significant administrative overhead, or risk. Craig was, by his own admission, living closer to the risk end of that spectrum than he was comfortable with.

OpenClaw's compliance module changes the calculus. Because every AI-generated action is logged with a timestamp and retained in the NemoClaw-secured audit trail, Craig now has a more complete and accurate compliance record than he did when the process was entirely manual. Ironically, deploying AI has made his compliance position stronger, not weaker.

"The FSG and PDS tracking is something I used to lose sleep over," Craig says. "When an insurer updates a PDS, I have to ensure all affected clients receive the updated disclosure. That used to be a manual audit — going through the book, identifying who has that product, generating and sending the updated document. Now the system detects the version change, identifies the affected clients, and handles the distribution automatically. I get a completion report when it's done."

What Didn't Go Perfectly

Craig is measured about the full picture.

The data migration was the roughest part. Fourteen years of client records, policy details, and expiry dates living across multiple systems needed to be consolidated before OpenClaw could take over tracking. That process took about two weeks and required more manual reconciliation than anyone would have liked.

"If you've got messy data going in, you get messy outputs coming out," Craig says. "We had to do a proper data audit first. It was tedious, but it was worth doing properly."

He also notes that the AI-drafted renewal summaries needed tuning in the early weeks. The first versions were technically accurate but felt a little generic for his more established clients — people he'd been looking after for a decade who expected communications that felt personal. It took a few iterations to get the tone right.

"For the complex commercial clients, I still write the renewal letter myself," Craig says. "Or at least, I heavily edit what the AI produces. Those relationships need a personal touch that you can't fully automate. But for the personal lines book — the home and contents, the landlord policies — the AI handles it completely and the clients are happy."

What Insurance Brokers Need to Know

Craig's situation isn't unusual. Talk to any insurance broker running a book of more than 200 policies and you'll hear variations on the same story: renewal season as organised chaos, compliance documentation as a low-grade constant anxiety, claims follow-up as a time sink that never quite gets emptied.

The structural problem is that insurance broking is a high-trust, high-compliance business that has traditionally required large amounts of mechanical, low-judgement work to operate. Brokers become brokers because they're good at understanding risk and building client relationships — not because they want to spend their days managing spreadsheets and chasing emails.

OpenClaw doesn't replace the relationship work. It removes the mechanical layer that sits underneath it, so the broker can spend their time on the parts of the job that actually require a human.

Craig puts it simply: "My clients aren't paying me to send them reminder emails. They're paying me to make sure they're properly covered when something goes wrong. I can focus on that now."

For brokers considering the move, Craig's advice is practical: start with your renewal tracking and outreach. It's the highest-impact, clearest-ROI application for a book of any size. Get that running cleanly, then layer in claims monitoring and compliance automation. Don't try to automate everything at once.

"Fifteen policies lost last year because of a process problem, not a relationship problem," Craig says. "That's what keeps you up at night as a broker. Knowing that clients left not because you let them down on the advice, but because the admin fell over. Fix the admin first."