MHC Intelligence

Hi Saurav,<br><br>Chris here from MHC Automation.<br><br>Given your role leading enterprise data and AI platforms at AmeriLife, I wanted to ask something that comes up a lot with teams like yours. With the PlanetPress end-of-life announcement, has your team started evaluating what replaces it, or is that still in the planning stage?<br><br>Where we usually see this become a real problem is when the document production layer becomes a blocker for broader modernization work. If your AI and data initiatives are moving forward but the composition layer still depends on a platform that's being sunset, that friction shows up fast, especially when you're also integrating acquired advisory firms with their own document environments.<br><br>We work with 60+ insurance organizations on their document infrastructure, including Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>Happy to have a chat and see how we can help get that layer off your critical path. If you're not the right person for this, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Saurav,<br><br>Following up on what I sent about the document platform piece.<br><br>One thing worth sharing: Guardian Life, Allstate, Intact Financial, and Acuity Insurance all run their policyholder communications on MHC. That's alongside 60+ other insurance organizations. The pattern we see is consistent: the insurer moves to MHC, the business side starts managing templates directly, and IT stops being the bottleneck for every document change.<br><br>For a team running an enterprise AI and data transformation, that matters more than it might seem. If your document composition layer still requires developer involvement for every template update, it becomes one more dependency sitting between your data platform investments and actual customer output. With AmeriLife's acquisition pace, you're also inheriting document environments that need to be consolidated, not just migrated.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls IT needs.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Saurav,<br><br>Sent you a couple of notes about the document platform situation at AmeriLife. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become a friction point in your AI and data roadmap, feel free to reach out.

Saurav, good to be connected. Sent you a few notes over email about the PlanetPress end-of-life question. At MHC we help insurers move template ownership off IT and onto the business side when a platform like that reaches end of support. Guardian, Allstate, and Intact have all gone through that transition with us, and we've worked with 25+ carriers on the same problem. Given your role across data and architecture at AmeriLife, figured LinkedIn might be a better place to land. Happy to reconnect here if the timing ever works. Chris

Hi Sulabh,<br><br>Chris here from MHC Automation.<br><br>Given your role as CIO at AmeriLife, I wanted to ask about something that keeps coming up with insurance organizations right now. With PlanetPress moving toward end of life, has your team started evaluating what comes next, or is that conversation still in early stages?<br><br>The reason I ask is that a lot of IT leaders in your position are getting pitched the vendor's own upgrade path as the default move. That's not always the wrong call, but it's worth knowing what else is out there before the decision gets made.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a quick chat and see if there's a fit, even if just to give you another data point for the evaluation. If you're not the right person for this conversation, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Sulabh,<br><br>Following up on what I sent about the PlanetPress sunset piece.<br><br>I want to be straightforward: we don't have a single insurance case study with a specific metric I can drop in here. What I can tell you is the pattern across Guardian Life, Allstate, Intact Financial, and Acuity. The insurer moves to MHC, the business side starts managing templates directly, and IT stops being the bottleneck for every document change.<br><br>For a company like AmeriLife, especially as you're expanding through acquisitions, that matters. Every new advisory firm you bring in likely has its own document outputs. Reconciling those across a legacy composition tool is slow work. On MHC NorthStar CCM, your compliance and ops teams handle changes directly, with controls in place, rather than waiting on a developer who knows the system.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Sulabh,<br><br>Sent you a couple of notes about the PlanetPress situation at AmeriLife. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If the timing is off or this isn't a priority right now, no problem. Feel free to reach out whenever it makes sense.

Sulabh, appreciated you connecting. Sent you a few emails recently around the platform end-of-life question I raised. At MHC we help insurers move template ownership off IT and to the business side when a vendor sunset forces a platform decision anyway. Worth mentioning that carriers like Allstate and Acuity have gone through this same transition. The migration piece tends to move faster than most CIOs expect once the business case is already made by the sunset itself. Worth a quick conversation to see if any of this is relevant? Chris

&mdash;

&mdash;

&mdash;

&mdash;

Hi Rhonda,<br><br>Chris here from MHC Automation.<br><br>Given your role leading operations and transformation at AmeriLife, I wanted to ask about something that's come up a lot lately with insurance organizations your size. With Quadient sunsetting PlanetPress, has your team started evaluating what comes next, or is that still in the planning stage?<br><br>The reason I ask: a lot of ops leaders we talk to are getting pressure to move fast, but the default path is just upgrading to OL Connect. That's the path of least resistance, but it's also a chance to step back and ask whether the next platform gives the business side more control over document changes, or just recreates the same IT dependency in a newer wrapper.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>I'd be happy to have a chat and see how we can help you use this transition as a real step forward for your document operations. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Rhonda,<br><br>Following up on what I sent about the PlanetPress transition.<br><br>Guardian Life, Allstate, Intact Financial, and Acuity Insurance run their policyholder communications on MHC. That's alongside 60+ other insurance organizations. The pattern we see consistently: the insurer moves to MHC, the compliance and ops teams start managing templates directly, and the wait for IT to make a document change disappears.<br><br>With AmeriLife expanding through acquisitions, that matters more than it might have a year ago. Every new advisory firm you bring in likely has its own document outputs, its own templates, its own compliance language. Reconciling all of that through a system only a developer can touch is going to slow down the integration work your team is already doing.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Rhonda,<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction during your transformation work, feel free to reach out.

Rhonda, glad you connected. I sent a few emails recently about the PlanetPress sunset and figured LinkedIn might be a better place to continue the conversation. At MHC we help insurers move template ownership off IT and onto the business side, so teams aren't waiting on developer queues every time something needs to change. Guardian and Allstate are both running on MHC now, along with 25+ other carriers who've made the same move. Worth a quick conversation to see if any of this is relevant? Chris

Hi Wendy,<br><br>Chris here from MHC Automation.<br><br>Given your role leading operations and transformation at AmeriLife, I wanted to ask about something that's come up a lot lately. With PlanetPress heading toward end-of-life, has your team started evaluating what comes next, or is that still in the planning stage?<br><br>The reason I ask is that most teams in your position are weighing two paths right now. The default is to move to OL Connect, which is the vendor's own upgrade path. The risk is you carry forward the same limitations, just on a newer platform. Developer-dependent template changes, IT as the bottleneck for anything compliance or ops needs to update.<br><br>We work with 60+ insurance organizations on their document infrastructure, including Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to chat and see if there's a better path for your team. If you're not the right person for this, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Wendy,<br><br>Following up on what I sent about the PlanetPress sunset.<br><br>One thing I should have included: Guardian Life, Allstate, Intact Financial, and Acuity run their policyholder communications on MHC. The pattern we see consistently is that once an insurer moves over, the compliance and ops teams start managing template changes directly. The wait for a developer to touch a document disappears.<br><br>That matters especially when a regulatory change hits and policy notices or renewal communications have to go out accurately, fast, across your full book of business. With your distribution scale, that change process needs to move without a ticket queue in the middle of it.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path, with approval workflows and controls still in place.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Wendy,<br><br>Sent you a couple of notes about the PlanetPress transition at AmeriLife. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If the timing is off right now, no problem. Happy to reconnect whenever it makes sense.

Wendy, good to connect. I sent a few emails about the platform end-of-life question, so you've seen some of what we do at MHC, helping insurers get template ownership off the developer queue and onto the business side. The reason I kept coming back to it is that a lot of teams migrating off PlanetPress end up rebuilding the same constraints on the other side. Guardian and Allstate have both worked through this with us, and MHC was ranked #1 in the mid-market by Aspire for insurers running high-volume compliance communications. Happy to reconnect here if the timing ever works. Chris

Hi Todd,<br><br>Chris here from MHC Automation.<br><br>Given your role in procurement at AmeriLife, I wanted to ask about something that's coming up a lot right now across insurance organizations your size. With Objectif Lune sunsetting the legacy PlanetPress Suite, are you already in active evaluation mode, or is that still getting prioritized?<br><br>The reason I ask: at companies running PlanetPress for policyholder communications, the EOL announcement tends to create a short window where the default path is just to take the vendor's own upgrade. That's not always the wrong call, but it can lock you into the same IT-dependent model for another decade.<br><br>With AmeriLife expanding through acquisitions, that dependency compounds fast. Every new agency or advisory firm that comes in brings its own document templates and workflows. Merging those into a legacy system usually means more IT tickets, not fewer.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to chat and see how we can help you evaluate your options before the upgrade path gets decided. If you're not the right person for this conversation, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Todd,<br><br>Following up on what I sent about the PlanetPress EOL piece.<br><br>One thing worth sharing: Acuity and Allstate both run their policyholder communications on MHC NorthStar CCM. The pattern we see at insurers like these is consistent. When they move off a legacy platform, the compliance and ops teams start managing templates directly, and the wait for IT to make a document change stops being part of the process.<br><br>That matters more when you're in acquisition mode. Each firm you bring in adds templates, plan types, and communication workflows. If those all have to route through a developer to get updated, the backlog builds quickly. Policy notices, renewal letters, certificates of insurance, cancellation notices — these can't sit in a queue when a regulatory change hits or a newly acquired book of business needs to get onboarded fast.<br><br>With your member base, that kind of flexibility is the difference between a smooth integration and a six-month IT project every time you close a deal.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Todd,<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If the timing is off or this isn't on your radar right now, no problem. Happy to reconnect whenever it makes sense.

Hey Todd, glad to be connected. Sent you a few emails recently about the PlanetPress end-of-life situation and figured LinkedIn might be a better place to continue the conversation. At MHC we help insurers move template ownership to the business side so document changes stop sitting in IT queues. Acuity and Allstate both run high-volume insurance communications through MHC without the bottleneck. Worth a quick conversation to see if any of this is relevant? Chris

Hi Jay,<br><br>Chris here from MHC Automation.<br><br>Given your role running infrastructure and operations at AmeriLife, I wanted to ask about something that's come up a lot lately in insurance IT circles. With the PlanetPress sunset on the horizon, has your team started evaluating where to land, or is that still in early planning?<br><br>The reason I ask: we're talking to a lot of insurance IT directors right now who are in the same spot. The vendor is pushing their own upgrade path, but it's worth knowing what else is out there before that decision gets made. Especially at AmeriLife's scale, with the number of agencies and advisory firms you've brought on through acquisitions, the document infrastructure question gets more complicated fast.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>I'd be happy to have a chat and see how we can help you evaluate your options before the window closes. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Jay,<br><br>One more thought on the platform evaluation piece I mentioned.<br><br>Guardian Life and Allstate both went through this same crossroads. Rather than defaulting to the vendor's recommended upgrade path, they evaluated alternatives and moved to a model where business users manage templates directly. IT stopped being the bottleneck for every document change.<br><br>That matters a lot when you're absorbing new agencies through acquisition. Each one comes in with its own document workflows, its own carrier relationships, its own compliance requirements. On most legacy systems, that means more IT tickets, more custom work, more developer time. That's what MHC NorthStar CCM does differently: the compliance or ops team at each affiliate makes the change directly, with controls in place, without waiting on a developer.<br><br>With your member base and the pace of acquisitions at AmeriLife, that kind of flexibility adds up fast.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Jay,<br><br>Sent you a couple of notes about the PlanetPress sunset and what that means for AmeriLife's document infrastructure. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If the timing is off or this isn't a priority right now, no problem. Happy to reconnect whenever it makes sense.

Hey Jay, appreciated you connecting. Sent you a few emails recently about the platform end-of-life question I raised. Didn't want to just let the connection sit without saying something here too. At MHC we help insurers move template ownership off IT queues to the business side. Guardian and Allstate both made that shift when they migrated off legacy document platforms, and the IT dependency piece dropped significantly after. If AmeriLife has something similar on the horizon, I'm happy to reconnect here if the timing ever works. Chris

Hi Leon,<br><br>Chris here from MHC Automation.<br><br>Given your role overseeing IT delivery at AmeriLife, I wanted to ask about something that's come up a lot lately with insurance organizations your size. With PlanetPress approaching end of life, has your team started evaluating what comes next, or is that still in the planning stage?<br><br>The reason I ask: the default move is usually to follow the vendor's upgrade path. But a lot of IT leaders we talk to are using this moment to actually evaluate alternatives before locking in, especially when the document portfolio has gotten more complex over time through acquisitions.<br><br>AmeriLife has been expanding its distribution platform through a lot of strategic deals. That usually means more carrier relationships, more policy types, more document variants. If your production environment is already carrying that complexity, the last thing you want is to rebuild it on a platform that's just the next version of the same architecture.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a quick chat and see how we can help you think through the evaluation before a vendor decision gets made. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Leon,<br><br>One more thought on the platform evaluation piece I mentioned.<br><br>We work with Guardian Life, Allstate, Intact Financial, and Acuity Insurance on their policyholder communications, alongside 60+ other insurers. I'll be honest: I don't have a single insurance case study with a specific metric to drop here. What I can tell you is the pattern.<br><br>The insurer moves to MHC NorthStar CCM, the business side starts managing templates directly, and IT stops being the bottleneck on every document change. For a distribution organization like AmeriLife, that matters more as you add carrier relationships and plan types through acquisitions. Each new deal can add a new set of document variants. If the people who know what those documents need to say are waiting on a developer every time something changes, that's going to slow things down.<br><br>What MHC does differently is it removes the developer from the day-to-day change path without removing the controls IT needs to stay in place.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Leon,<br><br>Sent you a couple of notes about the PlanetPress transition at AmeriLife. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become a friction point as you work through the EOL timeline, feel free to reach out.

Leon, appreciate you connecting. I sent a few emails recently about the PlanetPress end-of-life question and figured LinkedIn might be a better place to continue the conversation. At MHC we help insurers move off legacy document platforms so business teams own template changes without routing everything through IT. Guardian and Allstate both made that shift with us, running 200-plus complex policy and insurance templates through MHC now. Given your role across EPMO and IT delivery, the migration and ownership model side of this might be the more relevant angle. Worth a quick conversation to see if any of this is relevant? Chris

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

Hi Aaron,<br><br>Chris here from MHC Automation.<br><br>Given your role leading digital marketing at Physicians Mutual, I wanted to ask something that comes up a lot with health and life insurers your size. When you're building out the digital journey for Medicare supplement and senior product holders, how much of that experience is still bottlenecked by the document production layer?<br><br>I ask because the AI-powered engagement and texting CTAs that drive a senior member to act, those are only as good as what happens when the document lands. If the policyholder communication on the back end still requires a developer to update a template, the whole experience breaks down at the last mile.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>I'd be happy to have a chat and see how we can help your team close that gap between the digital experience you're building and the documents that follow it. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Aaron,<br><br>Following up on what I sent about the document layer piece.<br><br>Something I should have included in my last note: Guardian Life, Allstate, Intact Financial, and Acuity Insurance all run their policyholder communications on MHC. The pattern across all of them is similar. The insurer moves to MHC NorthStar CCM, the compliance or marketing team starts managing templates directly, and IT stops being the bottleneck on every document change.<br><br>For a team focused on digital engagement with Medicare supplement and senior product holders, that matters. When a product update, rate change, or regulatory disclosure has to reach your member base fast, the last thing you want is a developer queue standing between the decision and the outbound communication.<br><br>The people who know what those documents should say end up being the ones who can actually update them. That's what changes.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Aaron,<br><br>Sent you a couple of notes about the document infrastructure piece at Physicians Mutual. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction as you build out the digital experience, feel free to reach out.

Hey Aaron, saw you accepted the connection and wanted to say hi properly. I sent a few emails recently about the PlanetPress end-of-life question and how that sits against a broader digital journey buildout. At MHC we help insurers move document template ownership off IT and onto the business side, which tends to matter a lot when a platform deadline forces the architecture conversation anyway. Guardian and Allstate both worked through something similar with us and ended up clearing a fair amount of legacy document debt in the process. If any of this lands, feel free to reach out whenever. Chris

Hi Emmett,<br><br>Chris here from MHC Automation.<br><br>Given your role in strategy and corporate development at Physicians Mutual, I wanted to ask about something that comes up a lot at insurers your size. With Ricoh WFA in the mix, has your team started evaluating what the document production layer looks like going forward, or is that still on the roadmap?<br><br>The reason I ask: when insurers are expanding product lines and digital engagement channels, the document infrastructure often becomes the bottleneck. Policy communications, renewal notices, member correspondence, these still have to get out the door accurately and on time, and on a lot of legacy platforms, that means a developer is involved in every change.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>I'd be happy to have a chat and see how we can help reduce that friction as you modernize. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Emmett,<br><br>Following up on what I sent about the document infrastructure piece.<br><br>One thing I should have included: across the 60+ insurance organizations we work with, the pattern is consistent. The insurer moves away from a legacy or vendor-dependent document platform, the compliance and ops teams start managing templates directly, and the wait disappears. Changes happen the same day instead of sitting in a queue.<br><br>That matters especially when you're expanding product lines. Every new Medicare supplement offering, every updated renewal notice, every cross-sell communication has to be accurate and compliant before it goes out. On most legacy systems, that's a developer project.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path with approval workflows built in, so the people who know what the document should say can handle it directly.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Emmett,<br><br>Sent you a couple of notes about document infrastructure at Physicians Mutual. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become a friction point as you expand, feel free to reach out.

Emmett, appreciate you connecting. Sent you a few emails recently around the platform end-of-life question I raised, so figured LinkedIn was worth a shot since email can get noisy. At MHC we help insurers move template ownership off IT queues to the business side. We've worked through similar transitions with 25+ carriers, and Aspire ranked us the top mid-market CCM platform, which tends to matter when teams are evaluating replacements under a deadline. Happy to reconnect here if the timing ever works. Chris

Hi Nathan,<br><br>Chris here from MHC Automation.<br><br>Given your role leading enterprise architecture at Physicians Mutual, I wanted to ask about something we're seeing come up across a lot of insurance organizations right now. With PlanetPress heading toward end of life, has your team started evaluating what comes next, or is that still in the planning stage?<br><br>The reason I ask is that the path of least resistance is usually the incumbent vendor's upgrade. But that's not always the right call, especially when you're also dealing with AI-powered engagement and expanding product lines on the digital side. The document layer has to keep up with that.<br><br>We work with 60+ insurance organizations on their document infrastructure, including Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>Happy to have a chat and see if there's a fit. If you're not the right person for this conversation, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Nathan,<br><br>One more thought on the platform evaluation piece I mentioned.<br><br>We recently helped Intact Financial migrate off a legacy composition platform. Their compliance team now manages policy document templates directly, without waiting on a developer. Changes that used to take weeks happen the same day.<br><br>That matters a lot when you're running Medicare supplement products. Regulatory notice language changes, state-specific disclosure requirements, policyholder correspondence that has to go out accurately to your member base. On most legacy platforms, any of that is a developer project. On MHC NorthStar CCM, the people who own the compliance language make the change themselves, with approval workflows built in.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Nathan,<br><br>Sent you a couple of notes about the document platform question at Physicians Mutual. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become a friction point as you're expanding the digital side of things, feel free to reach out.

Hey Nathan, appreciate the connection. Sent you a few emails about the PlanetPress end-of-life question and figured LinkedIn might be a better place to continue the conversation. At MHC we help insurers move off legacy document platforms and get template ownership to the business side, away from IT queues. Carriers like Acuity and Intact have gone through that same transition recently, so there's some relevant ground to cover. Worth a quick conversation to see if any of this is relevant? Chris

Hi Aji,<br><br>Chris here from MHC Automation.<br><br>Given your role overseeing document processing at Physicians Mutual, I wanted to ask about something that comes up a lot with insurers managing high-volume print operations. With the changes happening around Ricoh's WFA platform, has your team started evaluating what the migration path looks like, or is that still in early planning?<br><br>The reason I ask: when a document platform hits end-of-life, the default move is usually to follow the vendor's recommended upgrade path. That's fine if it actually fits where the business is going. But we've seen cases where that default path locks a team into the same constraints they were already living with, just on newer infrastructure.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help you evaluate your options before that decision gets made for you. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Aji,<br><br>One more thought on the platform evaluation piece I mentioned.<br><br>Guardian Life, Allstate, Intact Financial, and Acuity Insurance run their policyholder communications on MHC. That's alongside 60+ other insurance carriers. The pattern we see consistently: the insurer moves over, the compliance and ops teams start managing templates directly, and IT stops being the bottleneck for every document change.<br><br>For an organization like Physicians Mutual, with your member base and the complexity of Medicare supplement and senior product communications, that matters. Policy documents, renewal notices, premium correspondence, any of those template changes currently sitting in an IT queue could be handled same-day on the business side.<br><br>Your signals around AI-powered digital engagement are interesting too. That kind of front-end modernization tends to run faster when the document layer underneath it isn't a manual bottleneck.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Aji,<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction, feel free to reach out.

Aji, good to be connected. I sent a few emails about the PlanetPress end-of-life situation and the pressure that puts on your print operations, so I won't rehash all of that here. At MHC we help insurers move off legacy document platforms before deadlines force the issue. Guardian and Allstate have both used us to manage complex, high-volume template environments without the manual bottlenecks that tend to build up over time. Given what you manage at Physicians Mutual, it felt worth reaching out on a different channel. Happy to reconnect here if the timing ever works. Chris

Hi Biswa,<br><br>Chris here from MHC Automation.<br><br>Given your role leading application development at Physicians Mutual, I wanted to ask about something that keeps coming up with IT directors at insurance companies your size. With Ricoh WFA in the mix, has your team started evaluating what comes next on the document platform side, or is that still in planning?<br><br>The reason I ask: when a document platform hits end of life, the default move is usually to follow the vendor's recommended upgrade path. That works for some teams. But we see a lot of IT directors realize mid-evaluation that they're basically buying a new dependency from the same vendor, and that's when they start looking at alternatives.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to chat and see if there's a fit. If you're not the right person on this, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Biswa,<br><br>One more thought on the platform evaluation piece I mentioned.<br><br>Guardian Life and Allstate both run their policyholder communications on MHC. The pattern we see with insurers their size is consistent: once business users can manage templates directly, the IT ticket queue for document changes stops being a problem. Compliance makes updates the same day instead of waiting on a developer who knows the system.<br><br>That matters a lot when you're expanding Medicare supplement products. Policy documents, renewal notices, and coverage correspondence all have to keep pace with product changes, and on most legacy platforms that's a developer project every time.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls IT needs.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Biswa,<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction, feel free to reach out.

Biswa, appreciate you connecting. I sent a few emails over the past couple weeks about the platform end-of-life question I raised, so figured LinkedIn was worth a try. At MHC we help insurers move template ownership off IT queues and onto the business side. Guardian and Allstate both went through that transition and it changed how their teams handled the EOL migration entirely. Given your role at Physicians Mutual, there may be some overlap with what you're working through. Worth a quick conversation to see if any of this is relevant? Chris

Hi Lori,<br><br>Chris here from MHC Automation.<br><br>Given your role as CIO at Physicians Mutual, I wanted to ask about something we're seeing come up across the insurance space right now. With Quadient sunsetting PlanetPress, has your team started evaluating what comes next, or is that still in early planning?<br><br>From what we see, the default move is to follow the vendor's upgrade path to OL Connect. That's not always the wrong call, but it's worth at least knowing what else is out there before you commit. Especially when a platform migration is also a chance to get off a model where every template change still runs through a developer.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>Happy to have a quick chat and see if there's a fit. If you're not the right person for this, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Lori,<br><br>Following up on what I sent about the platform EOL piece.<br><br>One thing I should have mentioned: the insurers we work with that go through a migration like this almost always say the same thing afterward. The win wasn't just replacing the platform. It was that the business side, compliance, product, communications, stopped waiting on IT for every document change.<br><br>Guardian Life, Allstate, Intact Financial, and Acuity are all running their policyholder communications on MHC now. That's alongside 60+ other insurance organizations. The pattern we see: insurer moves over, the people who know what the document should say start handling updates directly, and IT stops being the bottleneck for routine template changes.<br><br>That's what MHC NorthStar CCM does differently. It removes the developer from the day-to-day change path without removing the controls.<br><br>Given Physicians Mutual's footprint in Medicare supplement and senior products, I'd imagine you have a fairly significant volume of policyholder and member-facing documents where that kind of flexibility matters.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Lori,<br><br>Sent you a couple of notes about the document platform situation at Physicians Mutual. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If the timing isn't right, no problem. Happy to reconnect whenever it makes sense.

Lori, good to be connected. I sent a few emails about the platform end-of-life question I raised, so no need to rehash that here. At MHC we help insurers move template ownership off IT and onto the business side. Guardian, Allstate, and a few dozen others have gone through that transition, mostly when an EOL deadline forced the conversation. If any of this lands, feel free to reach out whenever. Chris

Hi Jeff,<br><br>Chris here from MHC Automation.<br><br>Given your role in customer experience at Physicians Mutual, I wanted to ask about something that comes up a lot with insurers your size. Has your team started evaluating alternatives for your document platform, or is that still in the planning stage?<br><br>I ask because we're seeing a lot of insurers get pushed toward their current vendor's upgrade path before they've had a chance to look around. The CX implications are real. When the team responsible for journey mapping and member communications can't update a notice or letter without waiting on a developer, the experience suffers before the customer even picks up the phone.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to chat and see how we can help your team move faster on the communications side. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Jeff,<br><br>One more thought on the platform evaluation piece I mentioned.<br><br>Guardian Life and Allstate both run policyholder communications on MHC. The pattern we see across insurers like them: once the business side can manage templates directly, the wait for developer availability stops being a bottleneck on every document change.<br><br>For a team doing journey mapping and VoC work, that matters. When a policy notice or renewal communication needs to change based on what customers are telling you, the people closest to that insight should be able to act on it. Not file a ticket and wait.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Jeff,<br><br>Sent you a couple of notes about document platform evaluation at Physicians Mutual. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction, feel free to reach out.

Hey Jeff, appreciate the connection. Sent you a few emails recently about the platform end-of-life question I raised. Figured LinkedIn might be a better place to continue it. At MHC we help insurers move template ownership off IT queues and onto the business side. Guardian and Allstate have both made that shift, and for both of them the EOL deadline was actually the forcing function that made the change worth doing properly rather than just migrating the same problems to a new platform. Happy to reconnect here if the timing ever works. Chris

Hi Amy,<br><br>Chris here from MHC Automation.<br><br>Given your role running the Word Processing Center at Physicians Mutual, I wanted to ask about something we see come up a lot at insurance organizations your size. With Ricoh WFA on a sunset path, has your team started evaluating what comes next, or is that still in early stages?<br><br>The reason I ask: when a document platform reaches end of life, most teams default to whatever the vendor recommends as an upgrade path. That's not always the wrong call, but it usually means inheriting the same constraints in a newer package. With your member base and the Medicare supplement focus, the volume and compliance demands on your documents are real.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help your team evaluate the options before anything gets locked in. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Amy,<br><br>Following up on what I sent about the platform transition piece.<br><br>One thing I should have mentioned: we see a lot of insurance organizations go through this exact moment, where the vendor announces a sunset, the team gets a short window, and the default path is the vendor's own upgrade. The problem is the upgrade usually keeps the same developer dependency baked in. Every template change, every regulatory notice, every renewal or cancellation letter still requires someone with system access to touch it.<br><br>Guardian Life, Allstate, Intact Financial, and Acuity Insurance run their policyholder communications on MHC. I won't pretend I have a single metric I can hand you. What I can tell you is the pattern: the insurer moves to MHC NorthStar CCM, the compliance and ops teams start handling template changes directly, and IT stops being the bottleneck for document updates.<br><br>For a Medicare supplement carrier with your member base, that matters when a regulatory notice or rate change has to go out fast and accurately across a large policyholder population.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Amy,<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction, feel free to reach out.

Hey Amy, glad we're connected. I sent a few emails recently about the platform end-of-life question I raised, and figured LinkedIn might be a better place to continue the conversation. At MHC we help insurers move template ownership off IT and to the business side before those deadlines force a rushed decision. Guardian and Allstate have both gone through this kind of transition, and MHC holds the top mid-market ranking for insurance CCM, so there's some relevant ground to cover if the timing at Physicians Mutual is getting closer. Worth a quick conversation to see if any of this is relevant? Chris

Hi Staci,<br><br>Chris here from MHC Automation.<br><br>Given your role in Marketing Operations at Physicians Mutual, I wanted to ask about something that keeps coming up with insurers your size. With PlanetPress heading toward end of life, is your team already in migration planning, or is that still being figured out?<br><br>The reason I ask: for companies with a large Medicare supplement and senior product base, the document layer touches a lot of critical communications. Policyholder notices, enrollment confirmations, premium correspondence, renewal documents. When the platform those run on goes EOL, it creates a forced decision. And if that decision defaults to whatever the vendor recommends, you can end up trading one constraint for another.<br><br>We work with 60+ insurance organizations on their document infrastructure, including Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a quick chat and see if there's a better path forward for your team before the migration timeline gets locked in. If you're not the right person on this, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Staci,<br><br>Following up on what I sent about the PlanetPress EOL.<br><br>One thing I should have included: we see this situation a lot with insurers in the Medicare and senior products space. The migration conversation starts as a platform swap. Then someone asks whether the new setup will let the Marketing or DocOps team update templates directly, without going through a developer every time. The answer is usually no, and that's where the frustration kicks in.<br><br>For what it's worth, Guardian Life, Allstate, Intact Financial, and Acuity all run their policyholder communications on MHC NorthStar CCM now. The honest pattern across all of them: once the business side can manage templates directly, the wait on IT for document changes disappears. That matters especially when a regulatory notice or enrollment communication has to reach a large policyholder base on a deadline.<br><br>If any of this resonates with where Physicians Mutual is headed, happy to chat in the days or weeks to come. I can share some docs first if that's the easier starting point.

Hi Staci,<br><br>Sent you a couple of notes about the PlanetPress EOL and what it means for Physicians Mutual's document layer. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If the timing is off or this isn't a priority right now, no problem. Happy to reconnect whenever it makes sense.

Staci, appreciate you connecting. I sent a few emails over the past couple weeks about the PlanetPress end-of-life situation and what a forced migration could mean for the 2026 roadmap at Physicians Mutual. Didn't want that to just disappear into the inbox. At MHC we help insurers move template ownership to the business side without the IT dependency. Guardian and Allstate are both in that camp, and Aspire ranks us number one for mid-market CCM, so we've done this migration a few times. Happy to reconnect here if the timing ever works. Chris

Hi Kathy,<br><br>Chris here from MHC Automation.<br><br>Given your role overseeing marketing administration and strategy at Physicians Mutual, I wanted to ask about something that's coming up a lot right now across the insurance space. With Ricoh winding down PlanetPress support, has your team started evaluating what comes next for your customer-facing document production?<br><br>For a company like Physicians Mutual with a large policyholder base, that transition touches a lot: policyholder notices, renewal correspondence, Medicare supplement communications, that kind of thing. The question most marketing ops and doc teams are working through right now is whether to follow the vendor's upgrade path or take the opportunity to look at alternatives.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help your team evaluate options before the timeline gets tight. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Kathy,<br><br>Following up on the platform evaluation piece I mentioned.<br><br>One thing I should have included: we've seen this play out a lot with insurers who default to the vendor's own upgrade path simply because it feels like the path of least resistance. The companies that paused and evaluated alternatives first tended to end up somewhere better, specifically around business users being able to manage template changes without going back to IT or a developer.<br><br>We work with Guardian Life, Allstate, Intact Financial, and Acuity Insurance on their policyholder communications, alongside 60+ other insurers. The pattern is consistent: once the business side can update compliance language, renewal notices, or policy correspondence directly, the wait on IT for every document change disappears.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls.<br><br>Given what you're building around digital engagement and AI-powered marketing at Physicians Mutual, having that kind of agility on the document side seems like it would matter. Happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Kathy,<br><br>Sent you a couple of notes about the document platform timing at Physicians Mutual. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction, feel free to reach out.

Hey Kathy, appreciate the connection. I sent a few emails about the PlanetPress end-of-life question and figured LinkedIn might be a better spot to actually have a conversation. At MHC we help insurers move template ownership to the business side so changes don't sit in an IT queue. Guardian and Allstate have both made that move, and we're ranked the top mid-market CCM platform by Aspire, so it's not a small sample. If the sunset timeline is something Physicians Mutual is actively working through, happy to reconnect here if the timing ever works. Chris

Hi Dave,<br><br>Chris here from MHC Automation.<br><br>Given your role running IT operations at Physicians Mutual, I wanted to ask about something that's come up a lot in our conversations with insurance teams lately. With the PlanetPress sunset now on the table, has your team started evaluating where to go next, or is it still in the planning stage?<br><br>The reason I ask is that a lot of IT leaders we talk to are getting pressure from their vendor to move to OL Connect as the natural upgrade path. Sometimes that's the right call. But sometimes it just trades one set of constraints for another, and it's worth at least knowing what else is out there before committing.<br><br>Physicians Mutual serves a large senior-oriented member base, so the volume of policyholder communications, renewal notices, and Medicare supplement correspondence going out the door is significant. A platform decision made now affects how fast your team can respond when CMS changes a disclosure requirement or a product update needs to hit thousands of policyholders.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help you evaluate your options before the sunset deadline closes in. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Dave,<br><br>One more thought on the platform evaluation piece I mentioned.<br><br>I'll be upfront with you: I don't have a single insurance case study with a specific before-and-after metric to share. What I can tell you is the pattern we see. An insurer moves off a legacy composition platform, business users start managing templates directly, and IT stops being the bottleneck for every document change.<br><br>For a carrier like Physicians Mutual, that matters most when a regulatory update hits and your team needs to push changes to Medicare supplement notices, renewal correspondence, or policyholder communications fast. On legacy systems, that's a developer project. On MHC NorthStar CCM, the compliance or ops team makes the change directly, with controls in place.<br><br>Guardian Life, Allstate, Intact Financial, and Acuity all run their policyholder communications on MHC. The common thread is that they wanted the document layer to move at the speed of the business, not at the speed of an IT queue.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Dave,<br><br>Sent you a couple of notes about the platform sunset situation at Physicians Mutual. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction, feel free to reach out.

Hey Dave, appreciate the connection. I sent a few emails recently about the platform end-of-life question I raised. No response needed there, but figured LinkedIn might be a better spot to actually have a conversation if the timing ever makes sense. At MHC we help insurers move template ownership off IT queues and to the business side. Guardian, Allstate, and Intact all run policyholder communications on MHC now, across 60+ insurance organisations. If any of this lands, feel free to reach out whenever. Chris

Hi Kumar,<br><br>Chris here from MHC Automation.<br><br>Given your role leading IT Transformation at QBE, I wanted to ask about something that comes up a lot at insurers your size. Is document template management still sitting on your developer team, and is that creating a bottleneck when the business side needs to make changes to policyholder communications?<br><br>What we usually see at large commercial and specialty insurers is that the people who know what a document should say, compliance, ops, underwriting, can't touch the templates without filing a ticket. So changes to things like policy notices, endorsements, renewal documents, or certificates pile up in a queue that depends on developers who have more critical work to do.<br><br>With a modernization program underway at QBE, I'd imagine that kind of drag on the team is worth looking at.<br><br>We work with 60+ insurance organizations on their document infrastructure, including Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. Happy to chat and see if any of this is relevant to where you're headed. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Kumar,<br><br>One more thought on the developer bottleneck piece I mentioned.<br><br>We work with Allstate, Intact Financial, and Acuity on their policyholder communications. The pattern across all of them was the same: business users needed to update documents, but every change went through a developer who knew the legacy platform. When a regulatory update came through, it became a project instead of a task.<br><br>With MHC NorthStar CCM, the compliance or ops team makes the change directly, within the controls IT sets. The developer stops being the bottleneck for day-to-day template updates, which frees up your engineering team for the higher-priority modernization work.<br><br>For an insurer with QBE's footprint across commercial, personal, and specialty lines, that's a meaningful amount of engineering capacity to reclaim.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Kumar,<br><br>Sent you a couple of notes about document infrastructure at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If document composition becomes a friction point in the broader transformation work, feel free to reach out.

Hey Kumar, saw you connected and figured LinkedIn was worth a shot after those emails went quiet. The developer scarcity piece I raised is something we see across a lot of mid-market and large carriers. At MHC we help insurers move template ownership off IT queues to the business side, which tends to free up dev capacity for the work that actually needs it. Allstate and Intact have both gone that route with us, and it's come up at 25-plus insurers we work with now. Worth a quick conversation to see if any of this is relevant? Chris

Hi Gautam,<br><br>Chris here from MHC Automation.<br><br>Given your role overseeing data, integration, and AI at QBE, I wanted to ask about something that comes up a lot with tech leaders at insurers your size. Does managing document template changes still pull developer time away from higher-priority integration and platform work?<br><br>What we typically see: the document layer sits on a legacy composition system, and every change to a policy notice or renewal runs through an IT queue. When your team is trying to push forward on AI and data infrastructure, that kind of overhead quietly blocks progress.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. Happy to chat and see if we can help free up your tech talent for the higher-order work. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Gautam,<br><br>Following up on what I sent about the document layer pulling developer time.<br><br>One example worth sharing: Natera cut document turnaround from 2.5 weeks to 2 days after moving off a legacy composition system. The main change was getting developers out of the day-to-day template path so the business side could handle updates directly.<br><br>For an insurer running at QBE's scale, that matters most when a regulatory change hits and policy notices or renewal documents have to go out fast across a large policyholder base. On most legacy systems, that is still a developer project.<br><br>That is what MHC NorthStar CCM does differently: it removes the developer from the routine change path without removing the controls IT needs.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that is the preferred initial step.

Hi Gautam,<br><br>Sent you a couple of notes about the document layer at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If document composition becomes a friction point in your modernization work, feel free to reach out.

Gautam, good to have you here. Sent you a few emails recently about the developer dependency piece with Documaker and how that kind of technical debt tends to quietly stall modernisation roadmaps. At MHC we help insurers shift template ownership off IT queues and onto the business side. Allstate and Guardian have gone that route, and at Natera it moved turnaround on policy documents from two and a half weeks to two days. Happy to reconnect here if the timing ever works. Chris

Hi David,<br><br>Chris here from MHC Automation.<br><br>Given your role as COO at QBE, I wanted to ask about something that comes up a lot at insurers going through operational modernization. Does updating policyholder-facing documents still require going through IT and waiting on a developer who knows the system?<br><br>At large insurers, that dependency tends to become a real drag. A regulatory change hits, or a product line gets restructured, and the document layer is suddenly the bottleneck. The business team knows exactly what needs to change, but they can't touch it without filing a ticket and waiting.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>I'd be happy to have a chat and see how we can help reduce that IT dependency on the document side. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi David,<br><br>One more thought on the IT dependency piece I mentioned.<br><br>Guardian Life, Allstate, Intact Financial, and Acuity Insurance all run their policyholder communications on MHC. Alongside 60+ other insurance organizations. The pattern we see consistently: once the insurer moves over, the compliance and ops team starts managing templates directly, and the wait for IT stops being part of the process.<br><br>With a modernization program underway at QBE, that kind of flexibility matters. When a regulatory change hits or a product line shifts, the people who actually know what the document should say can make the change the same day. No ticket, no queue, no developer context-switch.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi David,<br><br>Sent you a couple of notes about the document ops piece at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become too much of a friction point in the broader modernization work, feel free to reach out.

Appreciate you connecting, David. I sent a few emails over the past couple of weeks, so you probably have some context on what we do at MHC, helping insurers move template ownership off IT queues and to the business side. The IT dependency piece I mentioned tends to resonate differently depending on where QBE sits with it. Guardian and Allstate are both running on MHC now, along with 25 or so other carriers who had the same friction point. Happy to reconnect here if the timing ever works. Chris

Hi Jim,<br><br>Chris here from MHC Automation.<br><br>Given your role overseeing digital security and resilience at QBE, I wanted to ask about something that comes up a lot with large insurers running a modernization program. Does updating policyholder-facing documents still require going through a developer who knows the underlying system?<br><br>It's a surprisingly common friction point. The document layer gets left out of the modernization roadmap because it's tangled up in a platform that only a small group of people can actually touch. When that team is stretched or turns over, every change, whether it's a regulatory update, a product change, or a brand refresh, becomes a project.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see if any of this is relevant to what your team is navigating. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Jim,<br><br>One more thought on the developer dependency piece I mentioned.<br><br>Acuity and Guardian Life are two good examples. Along with 25+ other insurers, they've moved to MHC to decouple their document logic from their core systems. The business side handles template changes directly, with approval workflows built in. IT stops being the bottleneck for every compliance or product update.<br><br>For a company running global operations across commercial, personal, and specialty lines, that kind of resilience matters. When a regulatory change hits one market or a product gets restructured, the team responsible for the communication is the one who updates it. Changes happen the same day, not at the end of a ticket queue.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Jim,<br><br>Sent you a couple of notes about the document infrastructure piece at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction, feel free to reach out.

Appreciate you connecting, Jim. Sent you a few emails about getting document changes off the developer queue at QBE. Didn't want to just leave it at the inbox. At MHC we help insurers move template ownership to the business side so IT isn't the bottleneck on every change. Acuity and Guardian are among 25+ carriers that have used that model to decouple document logic from core systems without needing specialised developer pools to keep things compliant and resilient. Given your role, that architecture angle might actually be more relevant than the ops side. Worth a quick conversation to see if any of this is relevant? Chris

Hi Andrea,<br><br>Chris here from MHC Automation.<br><br>Given your role leading A&H underwriting at QBE, I wanted to ask about something we see come up constantly at insurers running modernization programs. When your team needs to update a customer-facing document, does that change have to go through IT first?<br><br>For A&H specifically, that friction tends to show up in the policy documents, renewal notices, and correspondence that your underwriting and ops teams rely on most. When only a developer can touch the templates, a regulatory update or a product change becomes a project instead of a task.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>I'd be happy to have a chat and see how we can help your team get more control over document changes without adding risk. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Andrea,<br><br>Following up on what I sent about the IT dependency piece.<br><br>One example worth sharing: <a href="https://www.mhcautomation.com/customer-stories/healthcare-organization-modernizes-billing-from-document-generation-to-payment-processing/?utm_campaign=227748570-CM_CDA_Customer%20Stories&utm_source=Chameleon&utm_content=Customer%20Story%20-%20Allied%20%28Anon%29">Allied Benefits</a> now processes over 1 million annual communications across 250+ templates and 80+ plan variations. They eliminated $4 per document in vendor fees. The shift happened when their business users stopped waiting on developers for every template change.<br><br>For an insurer like QBE with your member base and a transformation program already in motion, that kind of change cycle matters. When a product update hits the A&H line, the team managing the underwriting ops should be able to push it through the same day, not wait on a queue.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path with controls still in place.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Andrea,<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction, feel free to reach out.

Hey Andrea, good to be connected. Sent you a few emails recently about the IT dependency piece I mentioned on template changes. At MHC we help insurers move that ownership to the business side, off the developer queue. One thing that tends to resonate, Allied Benefits was processing over a million communications at around $4 per document before they made the switch. That number tends to land differently when you see it written out. If any of this lands, feel free to reach out whenever. Chris

Hi Eugene,<br><br>Chris here from MHC Automation.<br><br>Given your role as an enterprise architect at QBE, I wanted to ask about something we run into constantly at insurance organizations your size. Is your team still dependent on a shrinking pool of specialists to make template changes, or have you found a way to move that work closer to the business side?<br><br>At large carriers, this usually shows up the same way: a compliance or underwriting team needs to update a policy document, it becomes an IT ticket, and it sits in a queue behind everything else on the roadmap. When the person who knows the system is busy or gone, the wait gets longer.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>I'd be happy to have a chat and see how we can help reduce that dependency on specialized developer resources. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Eugene,<br><br>Following up on what I sent about the developer dependency piece.<br><br>One thing I should have mentioned: Guardian Life and Allstate both run their policyholder communications on MHC now. And separately, we helped a large healthcare payer cut their document change cycles from 2.5 weeks down to 2 days by moving template ownership away from IT and to the business teams who actually know what the documents need to say.<br><br>The mechanism is straightforward. Compliance or ops makes the change directly, within guardrails IT has already set. The ticket never gets written.<br><br>For a carrier with your member base, that matters most when a regulatory change hits and a document that goes to thousands of policyholders needs to be updated fast. On most legacy platforms, that's a developer project. It doesn't have to be.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Eugene,<br><br>Sent you a couple of notes about document infrastructure at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction, feel free to reach out.

Hey Eugene, good to be connected. I sent a few emails about the Documaker specialist shortage and what that does to a roadmap when manuscript endorsements and surplus lines filings are stuck waiting on a shrinking expert pool. Figured LinkedIn might be a better place to pick this up. At MHC we help insurers move template ownership off developer queues to the business side. At one large payer we cut template change cycles from two and a half weeks to two days. If any of this lands, feel free to reach out whenever. Chris

Hi Eric,<br><br>Chris here from MHC Automation.<br><br>Given your role managing production print and document management at QBE, I wanted to ask about something that comes up a lot at carriers your size. Does every template change still require going through a developer who knows the system, or has your team found a way around that?<br><br>From what we see, the issue usually isn't the volume of documents. It's that any time a form needs updating, whether it's a policy endorsement, a renewal notice, or a claims letter, someone has to write a ticket and wait. At a company running QBE's breadth of commercial and specialty lines, that queue adds up fast.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help reduce the dependency on specialist developer time for day-to-day document changes. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Eric,<br><br>Following up on what I sent about the developer dependency piece.<br><br>One thing I should have included: we help carriers like Guardian Life and Allstate manage complex document operations without the $150K+ specialist developer requirement. The pattern we see is that once business users can handle template changes directly, the ticket never gets written in the first place.<br><br>That matters especially when you're running a modernization program and the document layer is still moving at the pace of a change request queue. Endorsements, renewal notices, claims correspondence — those updates shouldn't be waiting on a developer backlog while the rest of the platform moves forward.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls IT needs.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Eric,<br><br>Sent you a couple of notes about document management at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become too much of a friction in the modernization work, feel free to reach out.

Hey Eric, appreciate the connection. Sent you a few emails recently about the developer dependency piece on Documaker, specifically around manuscript endorsements and surplus lines filings piling up in the IT queue. Didn't want to let the connection sit without saying something directly. At MHC we help carriers move that template ownership to the business side. Guardian and Allstate both got there without the $150K+ developer overhead that makes those queues so hard to clear. If any of this lands, feel free to reach out whenever. Chris

Hi Lauren,<br><br>Chris here from MHC Automation.<br><br>Given your role leading distribution at QBE, I wanted to ask about something that comes up a lot at insurers your size. When your broker-facing or policyholder documents need updating, does that still run through IT and wait on a developer to touch the template?<br><br>At carriers focused on distribution excellence, that wait time becomes a real problem. A change to a renewal notice or certificate of insurance takes days or weeks instead of hours because only a few people know the underlying system. With QBE's modernization push around digital platforms and customer experience, that kind of bottleneck tends to show up as friction in places leadership doesn't always expect it.<br><br>We work with 60+ insurance organizations on their document infrastructure, including Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help your team move faster on document changes without pulling developer resources away from higher-priority work. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Lauren,<br><br>One more thought on the document ops piece I mentioned.<br><br>Guardian Life, Allstate, Intact Financial, and Acuity run their policyholder communications on MHC. Across those accounts, the pattern is consistent: the carrier moves to MHC NorthStar CCM, the compliance or ops team starts managing templates directly, and the IT queue for document changes stops being a thing.<br><br>For a carrier focused on AI-driven modernization, that matters in a specific way. If your data and analytics investments are generating faster broker insights and better customer signals, but the document layer still requires a developer ticket to reflect those changes, you have a bottleneck that sits right in the distribution path.<br><br>Declarations pages, renewal notices, endorsements, certificates. When a product or regulatory change hits, your team needs to update those fast. The way most legacy systems are built, that's a developer project. With QBE's current focus on operational efficiency, that's worth a conversation.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Lauren,<br><br>Sent you a couple of notes about document operations at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction in QBE's modernization program, feel free to reach out.

Appreciate you connecting, Lauren. Sent you a few emails about the Documaker bottleneck, specifically the IT ticket wait on template changes and what that costs when your distribution teams need to move fast. At MHC we help insurers move that template ownership off the developer queue and onto the business side. Guardian and Allstate are two names that come up a lot in those conversations, and both made that shift while mid-market growth was the priority. If any of this lands, feel free to reach out whenever. Chris

Hi Ellie,<br><br>Chris here from MHC Automation.<br><br>Given your role leading data and strategic initiatives at QBE, I wanted to ask about something that comes up a lot at insurers your size. When your team needs to update policyholder documents like declarations pages, renewal notices, or endorsements, does that still require tracking down a developer to make the change?<br><br>At carriers running older document platforms, that's usually the case. The templates live in a system that only a specialist can touch, so every change becomes an IT project. With your modernization work underway, that kind of dependency tends to be one of the quieter friction points that slows everything else down.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help reduce that dependency on your end. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Ellie,<br><br>Following up on what I sent about the document change bottleneck piece.<br><br>One thing I should have included: the pattern we see most often at large carriers is that the developer who knows the document platform is either shared across teams or hard to backfill when they leave. That wait, whether it's days or weeks, gets absorbed into the process until someone upstream starts asking why renewals or endorsements are taking so long to turn around.<br><br>Allstate and Guardian Life both run their policyholder communications on MHC NorthStar CCM now. The short version is that their compliance and ops teams handle template updates directly, without writing a ticket. Changes that used to sit in a queue happen the same day.<br><br>That matters especially when a regulatory change has to propagate across declarations pages, renewal notices, and cancellation notices at your member base scale.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Ellie,<br><br>Sent you a couple of notes about document infrastructure at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction on the modernization side, feel free to reach out.

Ellie, good to have you in the network. Sent you a few emails about the Documaker developer scarcity piece at QBE, so you have some context on where I was going with that. At MHC we help carriers move template ownership to the business side so changes stop sitting in a developer queue. Allstate and Guardian have both gone through that shift without the IT dependency that tends to slow things down. Happy to reconnect here if the timing ever works. Chris

&mdash;

&mdash;

&mdash;

&mdash;

Hi Judy,<br><br>Chris here from MHC Automation.<br><br>Given your role in business transformation at QBE, I wanted to ask about something we see come up a lot at large insurers going through portfolio changes. When your teams are restructuring around divestitures or modernization programs, does the document layer end up as a bottleneck? Things like policy forms, renewal notices, endorsements, certificates of insurance, that kind of output.<br><br>The pattern we see: a business transformation initiative moves fast, but every template change still requires a developer ticket. The business side knows what needs to change, but they're waiting on someone with deep platform knowledge to actually make it happen. During an M&A integration or divestiture, that wait can take weeks.<br><br>We work with 60+ insurance organizations on their document infrastructure, including Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to chat and see if any of this is relevant to what your team is working through. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Judy,<br><br>One more thought on the template bottleneck piece I mentioned.<br><br>I'll be honest with you: I don't have a single insurance case study with a specific before-and-after metric to share. What I can tell you is the pattern across the 60+ insurers we work with, including Guardian Life, Allstate, Intact Financial, and Acuity. The insurer moves to MHC NorthStar CCM, the business side starts managing templates directly, and the IT ticket queue for document changes stops being the bottleneck.<br><br>For a team running a modernization program, that matters. When a regulatory change hits or a divestiture creates new policy form requirements, the people who know what the document should say are the ones making the update. Not waiting on a developer who also has ten other priorities.<br><br>With your member base and the scope of what QBE manages across commercial, personal, and specialty lines, that kind of flexibility compounds fast.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Judy,<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction point during your transformation work, feel free to reach out.

Hey Judy, appreciate you connecting. Sent you a couple of emails about the document infrastructure gap in the modernisation work, specifically the developer scarcity and IT ticket bottleneck that tends to slow policy changes during integration work. Didn't want to leave it at that. At MHC we help insurers move template ownership off IT queues to the business side. Guardian and Allstate have used it to remove that friction entirely, and MHC is ranked #1 for mid-market insurers by Aspire. Happy to reconnect here if the timing ever works. Chris

Hi Hemavathy,<br><br>Chris here from MHC Automation.<br><br>Given your role leading Application Delivery at QBE, I wanted to ask about something that comes up a lot with data and engineering leaders at insurers your size. Does updating policyholder-facing documents still require a developer to touch the template every time a change comes in?<br><br>With your member base and the scope of QBE's portfolio, that kind of dependency adds up fast. Compliance needs a change to a renewal notice or claims correspondence, and it turns into an IT ticket that sits in a queue behind higher-priority work. The business waits. The developer gets pulled from something else.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help reduce the IT lift on document template changes at QBE. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Hemavathy,<br><br>Following up on what I sent about the IT dependency piece.<br><br>Guardian Life, Allstate, Intact Financial, and Acuity Insurance run their policyholder communications on MHC. I'll be honest, I don't have a single insurance case study with a specific metric to share. What I can tell you is the pattern: the insurer moves to MHC, business users start managing templates directly, and IT stops being the bottleneck for document changes.<br><br>For a team focused on modernization and data infrastructure like yours, that matters. When a regulatory change hits or a product update needs to go out to your policyholder base, the compliance or ops team makes the change directly. The ticket never gets written. That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls in place.<br><br>I'm also aware QBE is in the middle of a broader modernization push. Document infrastructure is usually one of the last things to get updated, and it ends up slowing down the rest of the program.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Hemavathy,<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction, feel free to reach out.

Hemavathy, appreciate you connecting. I sent a few emails about the IT dependency piece I mentioned, so you've likely seen the gist of what we do at MHC, helping insurers get template changes off the developer queue and into business users' hands. Guardian and Allstate have both made that shift and seen real downstream benefits from it. Given your role across application delivery at QBE, figured there might be some overlap worth talking through. Worth a quick conversation to see if any of this is relevant? Chris

Hi Jason,<br><br>Chris here from MHC Automation.<br><br>Given your role in operations at QBE North America, I wanted to ask about something we see come up constantly at insurers your size. When a policy document needs to change, does that still require going through a developer to get it done?<br><br>At a lot of insurance organizations, renewal notices, declarations pages, endorsements, and certificates of insurance are all locked inside a composition system only IT can touch. So when a regulatory update hits or a product team needs a change, the ops side puts in a ticket and waits. That wait adds up fast when you're pushing documents across a large commercial and specialty book.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help reduce that dependency on IT for day-to-day document changes. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Jason,<br><br>One more thought on the bottleneck piece I mentioned.<br><br>I'll be honest, I don't have a single insurance case study with a specific metric to share. What I can tell you is the pattern we see at organizations running legacy composition platforms: the insurer moves to MHC NorthStar CCM, business users start managing templates directly, and the wait for IT to make document changes disappears. That's true across renewal notices, declarations, endorsements, certificates, and cancellation notices.<br><br>The reason it matters for a company your size is what happens when a state regulatory change comes in. If the only path to updating a disclosure or a policy form runs through a developer queue, compliance is working against the clock on something that should take hours, not weeks.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Jason,<br><br>Sent you a couple of notes about the document change bottleneck at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become too much of a friction, feel free to reach out.

Hey Jason, appreciate you connecting. Sent you a few emails recently about the developer dependency on template changes for renewals and declarations. Didn't want to just let that sit unanswered. At MHC we help insurers move that kind of work off the IT queue and back to the business side. Allstate and Guardian both run high-volume insurance comms through us now, which is roughly the scale QBE operates at. Happy to reconnect here if the timing ever works. Chris

Hi Ibrahim,<br><br>Chris here from MHC Automation.<br><br>Given your role in IT delivery at QBE, I wanted to ask about something we see come up a lot at insurers your size. Is document template maintenance still a developer-dependent process on your end, where every change to policyholder communications has to go through someone who knows the underlying system?<br><br>The pattern we hear most often: the business side knows exactly what needs to change in a declaration page or renewal notice, but the ticket sits in a queue waiting on a developer with platform-specific knowledge. With your modernization program in motion, I'd imagine that kind of friction shows up pretty clearly.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help reduce that IT delivery overhead on the document side. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Ibrahim,<br><br>Following up on what I sent about the developer dependency piece.<br><br>Acuity Insurance and Allstate both run their policyholder communications through MHC, alongside 60+ other carriers. The common thread across those implementations: the business team handles template changes directly, so the IT ticket for a document update never gets written in the first place.<br><br>That matters most when something time-sensitive hits, like a regulatory change that has to go out across your policyholder base in a defined window. Declaration pages, endorsements, cancellation notices, those kinds of updates usually live in a system only a developer can touch on older Oracle-era platforms. MHC NorthStar CCM changes that by letting the people who know what the document should say make the update, within controls IT still sets.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Ibrahim,<br><br>Sent you a couple of notes about document infrastructure at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become too much of a friction point in your IT delivery work, feel free to reach out.

Hey Ibrahim, appreciate the connection. Sent you a couple of emails about the Documaker developer scarcity piece and what that does to the template change queue over time. At MHC we help insurers move that ownership off IT and onto the business side. Acuity and Allstate are both running on MHC now, along with 25 or so other carriers who made the same shift. Given your role at QBE, figured this channel might be a better fit for a quick back and forth. If any of this lands, feel free to reach out whenever. Chris

Hi Dimple,<br><br>Chris here from MHC Automation.<br><br>Given your role leading data and integration at QBE, I wanted to ask about something that comes up a lot with VP-level integration leaders at large insurers. When your teams are pushing modernization work forward, is the document production layer keeping up, or does every template change still require a developer to touch the underlying system?<br><br>What I usually hear is that the integration side is moving fast, data pipelines are getting cleaner, platforms are consolidating, but policy documents, renewal notices, and claims correspondence are still sitting on an older composition system that only a few people know how to modify. When a regulatory change hits or a product line updates, it turns into a development project instead of a business-side update.<br><br>We work with 60+ insurance organizations on their document infrastructure, including Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help reduce the developer dependency on your document change cycles. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Dimple,<br><br>Following up on what I sent about the document layer bottleneck.<br><br>We work with Guardian Life, Allstate, Intact Financial, and Acuity on their policyholder communications, alongside 60+ other insurance organizations. The pattern is consistent: the insurer moves to MHC NorthStar CCM, the compliance and ops teams start managing templates directly, and the wait for a developer disappears.<br><br>That matters at QBE's scale. With your member base across commercial, personal, and specialty lines, policy documents, endorsements, and renewal notices are pulling from multiple systems. When a product or regulatory change comes through, someone has to track down the right template in a system only a small group can touch. That's a development queue problem sitting inside what should be a business operations workflow.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls IT needs.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Dimple,<br><br>Sent you a couple of notes about the document infrastructure piece at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction, feel free to reach out.

Dimple, good to be connected. Sent you a few emails recently around the IT dependency piece I mentioned, getting template changes off the developer queue and back to the business side. Didn't want that to be the only channel. At MHC we help insurers move document ownership away from IT backlogs so ops and business teams can work without waiting on a ticket. Guardian and Allstate are among the 25+ carriers that have gone that route with us. Happy to reconnect here if the timing ever works. Chris

Hi Hari,<br><br>Chris here from MHC Automation.<br><br>Given your role leading IT transformation at QBE North America, I wanted to ask about something that comes up a lot at insurers your size. Is the document layer one of those things that keeps showing up as a blocker in your modernization roadmap?<br><br>What I usually hear is that policy templates, endorsements, renewal notices, declarations pages, that kind of thing, can only be touched by a developer who knows the system. So when a regulatory change hits or a product team needs a template update, it becomes an IT ticket before it becomes anything else. At your member base, that queue adds up.<br><br>We work with 60+ insurance organizations on their document infrastructure, including Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to chat and see how we can help reduce the IT dependency around document changes as part of your broader digitization push. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Hari,<br><br>Following up on what I sent about the document layer and your modernization roadmap.<br><br>One thing I should have included: we work with 25+ insurers who've gone through similar transitions. The pattern we see most often is that the insurer moves to MHC NorthStar CCM, the business side starts managing templates directly, and IT stops being the bottleneck for every policy document change. Declarations pages, endorsements, renewal notices, cancellation letters, the compliance or ops team handles updates the same day instead of waiting on a developer ticket.<br><br>That matters especially when a state regulatory change has to propagate across your policyholder base quickly. With your member base, a two-week developer cycle on a template change is real exposure.<br><br>The broader point: document composition doesn't have to live on IT's plate. The controls stay in place, but the day-to-day change path shifts to the people who actually know what the document should say.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Hari,<br><br>Sent you a couple of notes about the document layer at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If document composition comes up as a friction point in the modernization program, feel free to reach out. Happy to reconnect whenever the timing makes sense.

Hari, appreciated the connect. I sent a few emails recently about the Documaker dependency piece, specifically how Oracle specialist scarcity tends to put IT in the middle of every template change request. At MHC we help insurers move that ownership to the business side, off the developer queue. Guardian and Allstate both made that shift with us, and Aspire ranked MHC first for mid-market and mega-carrier CCM transitions. Happy to reconnect here if the timing ever works. Chris

Hi Kelly,<br><br>Chris here from MHC Automation.<br><br>Given your role overseeing digital engineering at QBE, I wanted to ask about something that comes up a lot at insurers your size. When a policy notice or endorsement needs an update, does that still require an IT ticket and a developer before it goes out?<br><br>With your member base and the breadth of commercial, personal, and specialty lines QBE manages, that dependency adds up fast. A regulatory change hits one state, a brand update rolls across product lines, and suddenly the queue is backed up with document requests that feel routine but require specialist time to execute.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help reduce that engineering overhead on the document side. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Kelly,<br><br>Following up on what I sent about IT dependency on document changes.<br><br>I'll be straight with you: I don't have a single insurance case study with a hard metric I can drop here. What I can tell you is the pattern we see consistently across the 60+ insurers we work with. The insurer moves to MHC NorthStar CCM, the compliance or ops team starts managing templates directly, and the IT ticket never gets written in the first place.<br><br>Guardian Life, Allstate, Intact Financial, and Acuity all run their policyholder communications on MHC. The common thread is the same: declarations pages, endorsements, renewal notices, premium notices, all of those change cycles used to sit in a developer queue. After the move, the people who know what the document should say are the ones making the update, with approval workflows built in.<br><br>Given QBE's modernization focus on digital platforms and operational efficiency, that kind of shift on the document layer seems like it fits the direction you're already heading.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Kelly,<br><br>Sent you a couple of notes about document template dependencies at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become too much of a friction point as QBE's modernization program moves forward, feel free to reach out.

Hey Kelly, glad you connected. Sent you a few emails recently around the document infrastructure gap in modernisation work, so figured this was a better place to continue the conversation. At MHC we help insurers move template ownership off IT queues and onto the business side. Guardian and Allstate are both running on MHC now, and we're ranked number one in mid-market CCM by Aspire, so the model has been validated at scale. Happy to reconnect here if the timing ever works. Chris

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

Hi Shakeel,<br><br>Chris here from MHC Automation.<br><br>Given your role as a Senior Business Analyst at QBE, I wanted to ask about something that comes up a lot at insurers your size. When a policy document or customer notice needs updating, does that still require an IT ticket and a wait on a developer to make the change?<br><br>At carriers running legacy document platforms, that's usually the answer. Business analysts know exactly what the document should say, but the change has to go through someone who can edit the underlying template. When QBE is running modernization programs and trying to move faster, that kind of friction adds up.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help reduce that dependency on IT for day-to-day document changes. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Shakeel,<br><br>Following up on what I sent about the document change bottleneck.<br><br>One example worth sharing: Intact Financial runs their policyholder communications on MHC NorthStar CCM. The pattern we see there and at other carriers is consistent. Once the business side can manage templates directly, the wait disappears. Compliance or ops makes the change the same day instead of waiting on a developer queue.<br><br>That matters especially at an insurer like QBE, where you're optimizing the portfolio and pushing toward faster digital delivery. Declarations pages, endorsements, renewal notices, cancellation letters. When regulatory language has to update across your policyholder base, that's a project on most legacy systems. It doesn't have to be.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path with controls still in place, so IT isn't the bottleneck for every template edit.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Shakeel,<br><br>Sent you a couple of notes about document infrastructure at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become too much of a friction point in QBE's modernization work, feel free to reach out.

Hey Shakeel, good to be connected. Sent you a few emails recently around the document infrastructure gap in the modernisation work. Figured LinkedIn might be a better place to continue the conversation if any of it landed. At MHC we help insurers move template ownership off IT queues to the business side. We've done that for Intact, Allstate, Acuity, and around 25 other carriers, so the pattern of legacy document layers slowing down transformation programmes is something we've seen play out a lot. Worth a quick conversation to see if any of this is relevant? Chris

Hi Fred,<br><br>Chris here from MHC Automation.<br><br>Given your role overseeing residential lines at QBE, I wanted to ask about something that comes up a lot at insurers your size. Is updating policyholder documents like declarations pages, renewal notices, or endorsements still a process that requires a developer who knows the underlying system?<br><br>At a lot of carriers, even small template changes go through a specialist queue. When you're running a modernization program and trying to move faster, that bottleneck can quietly slow everything down. Hiring for those specialized roles is also genuinely competitive right now, which makes the dependency worse.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>I'd be happy to chat and see if there's a fit for what you're building at QBE. If you're not the right person for this conversation, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Fred,<br><br>Following up on what I sent about the document template bottleneck at residential lines.<br><br>Guardian Life and Allstate both run their policyholder communications on MHC NorthStar CCM. The pattern we see again and again: the carrier moves over, and the compliance or product team starts managing template changes directly. The wait for a developer who knows the legacy system disappears.<br><br>With your member base and the modernization work QBE has underway, that kind of speed matters. A regulatory change hitting declarations pages or renewal notices across residential lines shouldn't have to be a developer project.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Fred,<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction, feel free to reach out.

Hey Fred, glad we're connected here. Sent you a few emails about the developer scarcity piece on Documaker, specifically how that slows down template changes in residential lines when the hiring market for Document Analysts is this tight. Wanted to see if the channel switch was worth it. At MHC we help insurers get template ownership off the IT queue and onto the business side. Guardian and Allstate both run thousands of insurance templates through it without a dev-heavy cycle to manage changes. If any of this lands, feel free to reach out whenever. Chris

Hi Ben,<br><br>Chris here from MHC Automation.<br><br>Given your role overseeing infrastructure architecture at QBE, I wanted to ask about something that comes up a lot with infrastructure leaders at carriers your size. Does managing document template changes still route through developers, even when the change is on the business side?<br><br>With your member base and the complexity of commercial and specialty lines, that dependency tends to create a real queue problem. Every endorsement, renewal notice, or claims letter that needs a tweak becomes an IT ticket. The people who know what the document should say are waiting on the people who know how the system works.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to chat and see how we can help reduce that developer dependency on the document side. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Ben,<br><br>Following up on what I sent about the developer bottleneck on document changes.<br><br>One thing worth mentioning: Guardian Life, Allstate, Intact Financial, and Acuity all run their policyholder communications on MHC now. I'll be straight with you, I don't have a single insurance case study with a headline metric I can drop here. What I can tell you is the pattern that plays out every time. The insurer moves to MHC NorthStar CCM, the compliance or operations team starts managing templates directly, and the wait disappears. IT stops being the bottleneck on every declarations page update or cancellation notice.<br><br>For a team with a DevOps orientation and an active modernization program, that matters. The document layer should behave like the rest of your modern infrastructure: business logic owned by the people closest to the requirement, with controls in place that IT sets.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Ben,<br><br>Sent you a couple of notes about the document infrastructure piece at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction on the modernization side, feel free to reach out.

Appreciated the connection, Ben. Sent you a few emails about the IT dependency piece, so you may already have some context on what we do. At MHC we help insurers get template changes off the developer queue and into the hands of business users directly. Guardian and Allstate are among 25+ carriers that moved away from legacy Documaker bottlenecks that way, which is what made me think of QBE. Worth a quick conversation to see if any of this is relevant? Chris

Hi Michael,<br><br>Chris here from MHC Automation.<br><br>Given your role overseeing application development at QBE, I wanted to ask about something that comes up a lot at insurers your size. Does updating customer-facing documents like policy notices, endorsements, or renewal correspondence still require a developer to touch the template every time?<br><br>At large carriers, that dependency tends to create a real backlog. A compliance change hits, a state filing comes in, a brand update rolls out, and suddenly the queue is full of document tickets that could have been handled by the business side if the tooling allowed it.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>I'd be happy to have a quick chat and see if there's a fit. If you're not the right person for this, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Michael,<br><br>One more thought on the developer dependency piece I mentioned.<br><br>Guardian Life, Allstate, Intact Financial, and Acuity Insurance run their policyholder communications on MHC, alongside 60+ other insurers. The pattern is pretty consistent: once the business side can manage templates directly, the IT ticket queue for document changes stops growing. Compliance handles their own updates. Ops handles theirs. Changes happen the same day instead of waiting on a sprint cycle.<br><br>That matters especially when a state regulatory change has to propagate across policy documents for a large policyholder base fast. On most legacy document platforms, that's a developer project. On MHC NorthStar CCM, your compliance team makes the change directly, with approval workflows built in.<br><br>With QBE's modernization focus on digital platforms and operational efficiency, I'd imagine anything that removes developer time from low-value work is worth a look.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Michael,<br><br>Sent you a couple of notes about document infrastructure at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become a friction point as QBE's modernization program moves forward, feel free to reach out.

Hey Michael, appreciate you connecting. Sent you a couple of emails about the IT dependency piece I mentioned, so you've got the context. At MHC we help insurers move template ownership to the business side so document changes stop landing in developer queues. Guardian and Allstate are two of the 25+ carriers that have shifted that workload off their engineering teams entirely. Given your role at QBE, figured LinkedIn might be a better place to have this conversation than an inbox. If any of this lands, feel free to reach out whenever. Chris

Hi Ashley,<br><br>Chris here from MHC Automation.<br><br>Given your role in underwriting operations at QBE, I wanted to ask about something we see come up a lot at large commercial and specialty insurers. Does every change to a customer-facing document, like a stop loss certificate or an A&H policy form, still require going through IT and waiting on a developer to touch the template?<br><br>At organizations running legacy document platforms, that wait can stretch from days to weeks. The business side knows exactly what the document needs to say, but the change doesn't happen until a developer with platform-specific knowledge has bandwidth. For a team managing something as document-heavy as stop loss and A&H operations, that adds up fast.<br><br>We work with 60+ insurance organizations on their document infrastructure, including Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help your team get document changes out of the IT queue. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Ashley,<br><br>Following up on what I sent about the template bottleneck piece.<br><br>One example that might be relevant: <a href="https://www.mhcautomation.com/customer-stories/healthcare-organization-modernizes-billing-from-document-generation-to-payment-processing/?utm_campaign=227748570-CM_CDA_Customer%20Stories&utm_source=Chameleon&utm_content=Customer%20Story%20-%20Allied%20%28Anon%29">Allied Benefits</a> processes over 1M annual communications across 250+ templates and 80+ plan variations. They eliminated $4 per document in vendor fees and got template turnaround down from weeks to days.<br><br>The way they got there was by moving template ownership to the business side, with controls still in place for compliance review. The people who knew what the documents needed to say were the ones making the changes. IT stopped being the bottleneck for every update.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the guardrails.<br><br>For a team running stop loss and A&H documents, where plan-level language and state-specific forms have to stay accurate, that kind of turnaround matters. A regulatory update or a mid-term endorsement change doesn't have to sit in a queue.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Ashley,<br><br>Sent you a couple of notes about document ops at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become too much of a friction, feel free to reach out.

Hey Ashley, glad we're connected. Saw you're deep in the digital transformation work at QBE and thought the document infrastructure gap I mentioned in my emails might be worth a second look. At MHC we help insurers move template ownership off the IT queue and onto the business side. Allied Benefits saw that shift pay off at scale, cutting $4 per document across over a million communications and pulling template turnaround from weeks down to days. Happy to reconnect here if the timing ever works. Chris

Hi Sushma,<br><br>Chris here from MHC Automation.<br><br>Given your role leading transformation at QBE, I wanted to ask about something that comes up a lot with global insurers running modernization programs. When your teams need to update policyholder documents like declarations pages, endorsements, or renewal notices, does that still require a developer to make the change in the system?<br><br>At the scale QBE operates, that dependency adds up fast. A regulatory change in one market, a brand update, a product revision — and the business side is waiting on IT to touch a system only a few people know how to use. It slows down the local execution piece that usually matters most in a global-to-local transformation.<br><br>We work with 60+ insurance organizations on their document infrastructure, including Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help reduce that developer dependency across your document production layer. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Sushma,<br><br>Following up on what I sent about the developer dependency piece.<br><br>One example that might be relevant: Allstate, Acuity, and Guardian Life run their policyholder communications on MHC NorthStar CCM. The pattern we see consistently is that once the business side can manage templates directly, the IT ticket queue for document changes stops being a bottleneck. Changes happen the same day instead of waiting on a sprint cycle.<br><br>With your member base and the number of markets QBE operates in, that matters. A regulatory change in one region shouldn't require a developer project. Your compliance or operations teams should be able to make that update directly, with the right controls in place.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the guardrails.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Sushma,<br><br>Sent you a couple of notes about document infrastructure at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become a friction point in QBE's transformation roadmap, feel free to reach out.

Sushma, good to have you connected here. Sent you a few emails recently about the IT dependency piece I mentioned, getting template changes off the developer queue. At MHC we help insurers move that ownership to the business side. Optum shifted 200-plus templates across their BCBS and Humana lines that way, and Natera cut a two-and-a-half week turnaround to two days on similar work. Given what's typically on the plate of a transformation office at QBE, that kind of friction is worth knowing you can remove. If any of this lands, feel free to reach out whenever. Chris

Hi Beckie,<br><br>Chris here from MHC Automation.<br><br>Given your role in underwriting operations at QBE, I wanted to ask about something that comes up a lot at insurers your size. When a policy form or endorsement needs to change, does that still require going through IT and waiting on a developer to touch the template?<br><br>At a lot of carriers running older document platforms, that wait is measured in weeks. The business team knows what needs to change, but they can't get to the template without going through someone in IT who knows the system. With QBE's modernization push, I'd imagine that kind of friction is starting to get attention.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>I'd be happy to have a chat and see how we can help your ops team move faster on document changes without adding to IT's plate. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Beckie,<br><br>Following up on what I sent about the document change bottleneck.<br><br>One thing I should have included: the pattern we see most at insurers running legacy document platforms is that the developer pool keeping those systems alive is shrinking. When one of those folks leaves or moves to a different project, template changes stop. That becomes a real problem when a regulatory update hits or a product change needs to go out to your policyholder base.<br><br>Guardian Life, Allstate, Intact Financial, and Acuity run their policyholder communications on MHC NorthStar CCM. The common thread: once they made the switch, the compliance and ops teams started handling template changes directly. IT stops being the bottleneck for every endorsement, renewal notice, or policy form update.<br><br>Given where QBE is with its modernization program, taking the document layer off the IT dependency list seems like a natural fit.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Beckie,<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become too much of a friction point in QBE's modernization work, feel free to reach out.

Beckie, good to have you in the network. Sent you a few emails about the document infrastructure gap sitting in the middle of modernisation roadmaps, so you probably have some context on where we play. At MHC we help insurers move template ownership off IT queues and onto the business side, which tends to clear some of the bottleneck that slows everything else down. Carriers like Guardian, Allstate, and Intact have gone through this with us, so there's a reasonable proof of concept for what that shift looks like in practice. Happy to reconnect here if the timing ever works. Chris

Hi Nick,<br><br>Chris here from MHC Automation.<br><br>Given your role in operations at QBE, I wanted to ask about something that comes up a lot at insurers your size. When a policy change needs to go out or a renewal notice has to be updated, does that still require going through IT and waiting on a developer to touch the template?<br><br>At large carriers, that wait can stretch for weeks. Especially when the people who know the system are stretched thin or the work requires a specialist who understands the underlying platform. With your member base, that kind of lag on policyholder documents can become a real problem fast.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help reduce that dependency on IT for day-to-day document changes. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Nick,<br><br>One more thought on the document bottleneck piece I mentioned.<br><br>We worked with <a href="https://www.mhcautomation.com/customer-stories/healthcare-organization-modernizes-billing-from-document-generation-to-payment-processing/?utm_campaign=227748570-CM_CDA_Customer%20Stories&utm_source=Chameleon&utm_content=Customer%20Story%20-%20Allied%20%28Anon%29">Allied Benefits</a> on a similar challenge. They were processing over 1 million annual communications across 250+ templates and 80+ plan variations. By giving their business team direct control over templates, they eliminated $4 per document in vendor fees and removed the back-and-forth with IT entirely.<br><br>The pattern we see at insurers is consistent. Policyholder data sits across several systems. Declarations, endorsements, renewal notices all pulling from different sources. When a regulatory change hits or a product line gets updated, someone has to find the right template in a system only a developer can touch. That wait time doesn't have to exist.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path with approval workflows still built in.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Nick,<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction, feel free to reach out.

Hey Nick, good to be connected. Sent you a couple of emails recently about the developer scarcity piece on Documaker and how that kind of dependency tends to slow down the broader modernisation work. Didn't want to let this connection sit without saying something here too. At MHC we help insurers get template ownership off the developer queue and onto the business side. Allied Benefits cut $4 per document in manual costs running that way, and Natera brought cycle times from 2.5 weeks down to 2 days. Happy to reconnect here if the timing ever works. Chris

Hi Greg,<br><br>Chris here from MHC Automation.<br><br>Given your role leading digital transformation at QBE, I wanted to ask about something we see come up a lot at insurers your size. When modernization programs push into underwriting and data platforms, does the document layer end up being the thing that slows everything else down?<br><br>What we usually hear: policy communications, endorsements, renewal notices, claims correspondence all still live in a system only a developer can touch. So every template change goes into an IT queue, and the business side waits. At your scale, that wait compounds fast.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help get the document layer off the critical path for your transformation work. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>Chris<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Greg,<br><br>Following up on what I sent about the document layer piece.<br><br>One thing I should have included: the pattern we see at insurers who move to MHC NorthStar CCM is that compliance and ops teams start owning template changes directly. The IT ticket for a disclosure update or a renewal notice revision never gets written. Changes happen the same day.<br><br>I know QBE is pushing hard on digitalization across underwriting and operations. The document production side tends to be the last thing that catches up, especially when policyholder communications are pulling from multiple systems and every change is a developer project.<br><br>Guardian Life, Allstate, Intact Financial, and Acuity Insurance run their policyholder communications on MHC alongside 60+ other insurers. The consistent result is that business users stop waiting on IT for document changes, and IT gets that time back for the work that actually requires them.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Greg,<br><br>Sent you a couple of notes about the document infrastructure piece at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become too much of a friction point in your modernization program, feel free to reach out.

Greg, good to have you in the network. Sent you a few emails about the IT dependency piece on template changes. At MHC we help insurers move that ownership to the business side so document updates stop sitting in developer queues. Intact and Acuity have both made that shift, which tends to free up meaningful IT capacity for the roadmap work that actually needs engineering attention. Given what you're driving at QBE on the transformation side, there may be some overlap there. If any of this lands, feel free to reach out whenever. Chris

Hi Srikanth,<br><br>Chris here from MHC Automation.<br><br>Given your role leading infrastructure services at QBE, I wanted to ask about something that comes up a lot with insurance organizations running legacy document platforms. Does managing template changes for policyholder communications still require developer involvement every time something needs to update?<br><br>From what we see, that dependency tends to become a real problem when modernization programs are in motion. The document layer gets left behind because touching it requires someone who knows the system deeply, and those cycles are already stretched.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>I'd be happy to chat and see if there's a fit given what QBE has underway. If you're not the right person for this, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Srikanth,<br><br>Following up on what I sent about the document infrastructure piece.<br><br>We recently helped Guardian Life and Allstate modernize how their teams manage policyholder communications. The pattern was consistent: both moved away from a developer-dependent document layer and got their compliance and ops teams making template changes directly. IT stopped being the bottleneck for every update.<br><br>That matters especially when a regulatory change hits across multiple states and the update has to reach millions of policyholders fast. Declarations pages, renewal notices, endorsements, cancellation notices, all of it. On a legacy system, that's a developer project. On MHC NorthStar CCM, the business side handles it with controls in place.<br><br>Given QBE's modernization program, I'd think the document layer is one of those things worth getting off the critical path sooner rather than later.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Srikanth,<br><br>Sent you a couple of notes about document infrastructure at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If the current document composition setup becomes a friction point in QBE's infrastructure work, feel free to reach out.

Srikanth, appreciate you connecting. I sent a few emails over the past weeks about the IT dependency piece I mentioned, getting template changes off the developer queue so the business side can move without a ticket. At MHC we help insurers do exactly that. Guardian and Allstate both made that shift and cut the back-and-forth with IT significantly on document updates. Not sure if that maps to anything on your side at QBE, but happy to reconnect here if the timing ever works. Chris

Hi Todd,<br><br>Chris here from MHC Automation.<br><br>Given your role leading claims at QBE, I wanted to ask about something that comes up a lot with insurers your size. When your claims team needs to update customer-facing correspondence, like denial letters, coverage confirmations, or settlement notices, does that still require going through IT and waiting on a developer to make the change?<br><br>At a lot of general insurers, the claims documents are technically owned by the business but practically controlled by whoever knows the legacy document system. A compliance update or a new state disclosure requirement turns into a developer ticket, and the timeline slips.<br><br>We work with 60+ insurance organizations on their document infrastructure, including Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>I'd be happy to have a chat and see how we can help your claims team move faster on document changes without waiting on IT. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Todd,<br><br>One more thought on the IT dependency piece I mentioned.<br><br>Natera cut their document turnaround from 2.5 weeks to 2 days after moving off their legacy platform. Different industry, but the underlying problem was the same: every change had to go through a developer, and the queue never got shorter.<br><br>For a claims operation at QBE's scale, that kind of delay hits hardest when a regulatory notice or a coverage letter needs to go out fast and accurately to a large group of policyholders. With your member base across commercial, personal, and specialty lines, a single template change can touch a lot of documents.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path with approval workflows still in place, so your compliance or claims ops team handles it directly.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Todd,<br><br>Sent you a couple of notes about document infrastructure at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become too much of a friction for your claims team, feel free to reach out.

Hey Todd, glad you connected. Sent you a few emails about the template change bottleneck on Documaker, specifically the IT ticket wait every time DocOps needs an update. At MHC we help insurers move that ownership to the business side, off the developer queue entirely. One company doing high-volume template work across BCBS and Humana got to 200+ templates under management, and another cut cycle times from 2.5 weeks to 2 days once the IT dependency was removed. Worth a quick conversation to see if any of this is relevant? Chris

Hi Alissa,<br><br>Chris here from MHC Automation.<br><br>Given your role in North America Communications at QBE, I wanted to ask about something that comes up a lot at carriers your size. When a policy renewal notice or endorsement needs to change, is that still a developer project, or has your team found a way to handle it without going through IT?<br><br>We see this constantly with large commercial insurers. The people who know what the document should say can't touch the template. Someone has to write a ticket, find a developer with the right system knowledge, and wait. With your member base and the volume shifts coming out of the US commercial book, that bottleneck tends to get expensive fast.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help your communications team move faster on document changes without pulling in IT every time. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Alissa,<br><br>Following up on what I sent about the document change bottleneck.<br><br>We recently helped <a href="https://www.mhcautomation.com/customer-stories/healthcare-organization-modernizes-billing-from-document-generation-to-payment-processing/?utm_campaign=227748570-CM_CDA_Customer%20Stories&utm_source=Chameleon&utm_content=Customer%20Story%20-%20Allied%20%28Anon%29">Allied Benefits</a> process over 1 million annual communications across 250+ templates and 80+ plan variations. They also eliminated $4 per document in vendor fees by moving away from their legacy platform.<br><br>The bigger shift was that their ops team stopped waiting on developers for every template update. When a regulatory change came through, the business side handled it directly. Changes happened the same day instead of sitting in a queue.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls IT needs.<br><br>With QBE's US commercial liability transfer and the document volume that comes with it, that kind of flexibility seems worth at least a conversation. If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Alissa,<br><br>Sent you a couple of notes about document infrastructure at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction, feel free to reach out.

Alissa, appreciate you connecting. I sent a few emails recently about the Documaker developer dependency piece, so you may have some context already on what we do at MHC. The short version is we help carriers move template ownership off specialist developer queues and back to the business side. Allstate and Guardian have both gone through that shift with us, which is partly why I reached out to QBE specifically. If any of this lands, feel free to reach out whenever. Chris

Hi Jennifer,<br><br>Chris here from MHC Automation.<br><br>Given your role overseeing Claims and Risk Solutions at QBE, I wanted to ask about something that comes up a lot at insurers your size. When a claims letter or policy notice needs to change, does that still require an IT ticket and a developer to touch the template before anything goes out?<br><br>At large carriers, that dependency is usually invisible until it isn't. A regulatory change drops, or a new claims workflow gets rolled out, and suddenly the bottleneck is the document layer. Business teams know what needs to change but can't touch the template without going through IT.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>I'd be happy to have a quick chat and see how we can help reduce that IT dependency on the documents side. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Jennifer,<br><br>Following up on what I sent about the IT dependency piece.<br><br>I want to be straightforward with you: I don't have a single insurance case study with a specific metric I can point to. What I can tell you is the pattern we see across the 60+ insurers we work with. The carrier moves to MHC NorthStar CCM, the compliance or ops team starts managing templates directly, and IT stops being the bottleneck for every document change. Changes happen the same day instead of waiting in a queue.<br><br>For claims teams specifically, that matters when a state changes its required language on an adverse action notice or a new coverage disclosure has to go out with your member base in mind. Right now that's probably a developer project. It doesn't have to be.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Jennifer,<br><br>Sent you a couple of notes about the document infrastructure piece at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become too much of a friction as QBE continues its modernization push, feel free to reach out.

Hey Jennifer, appreciate you connecting. Sent you a few notes recently about the template change bottleneck on IT queues. At MHC we help insurers move that ownership to the business side, away from developer dependencies entirely. That's why carriers like Guardian, Allstate, and Intact have moved to us, and we're working with 25 or so insurers globally at this point. With claims governance touching as much document throughput as it does at QBE, figured it was worth a direct note. Worth a quick conversation to see if any of this is relevant? Chris

Hi Ketan,<br><br>Chris here from MHC Automation.<br><br>Given your role overseeing technology and AI at QBE, I wanted to ask about something that comes up a lot with insurers running a modernization program. Does the document production layer keep pace with the rest of the stack, or does it end up being the thing that slows everything else down?<br><br>The pattern we see: the modern data and AI infrastructure gets built out, but policy documents, renewal notices, claims correspondence still depend on a developer to touch the template every time something changes. The business team knows what needs to change. They just can't make the change themselves.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>Happy to have a chat and see if any of this is relevant to what your team is working through. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Ketan,<br><br>One more thought on the document infrastructure piece I mentioned.<br><br>HSBC runs 100 to 200 trade document templates on MHC NorthStar CCM, covering letters of credit, guarantees, and SWIFT messages. What made it work was that their operations team stopped depending on developers for routine template updates. Changes that used to require a ticket and a wait now happen the same day, with approval workflows still in place.<br><br>For an insurer with your member base, that matters when a regulatory change hits and policyholder notices, endorsements, or cancellation letters need to go out fast and accurately across multiple lines of business.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Ketan,<br><br>Sent you a couple of notes about document infrastructure at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes ever become a friction point in your modernization program, feel free to reach out.

Ketan, appreciated the connection. Sent you a few emails recently about the IT dependency piece I mentioned, so figured LinkedIn made more sense to continue the conversation. At MHC we help insurers move template ownership off the developer queue and onto the business side. HSBC went through a similar shift when they consolidated over a hundred templates onto the platform, including work tied to their SWIFT infrastructure. Given where QBE is on the modernisation side, that document infrastructure gap tends to show up in unexpected places. If any of this lands, feel free to reach out whenever. Chris

Hi Ian,<br><br>Chris here from MHC Automation.<br><br>Given your role overseeing technology and operations at QBE, I wanted to ask about something we see come up a lot at insurers your size. When a regulatory change hits or a product line shifts, does updating the policy documents and customer notices still require pulling a developer in to touch the templates?<br><br>At carriers running older document platforms, that dependency tends to become a real drag. The compliance team knows what needs to change, the ops team is waiting, but the change sits in a queue until someone technical gets to it. With QBE's focus on modernizing digital platforms and moving faster operationally, I'd imagine that kind of friction is worth looking at.<br><br>We work with 60+ insurance organizations on their document infrastructure, including Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help reduce that dependency for your document operations teams. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Ian,<br><br>Following up on what I sent about document template dependencies at QBE.<br><br>Something I should have included in my last note: the pattern we see most often at insurers your size is that the compliance or product team knows exactly what a document needs to say, but they're waiting on a developer to make it happen. Declarations pages, endorsements, renewal notices, cancellation letters. One regulatory update can touch dozens of templates across multiple lines of business.<br><br>The insurers we work with on MHC NorthStar CCM have largely moved the day-to-day change work off the IT queue entirely. The people who need to update the document are the ones who update it, with approval workflows and controls built in so IT isn't a bottleneck but still isn't out of the picture.<br><br>With QBE's member base and the breadth of your commercial and specialty lines, the volume of documents affected by any given change is significant. That's where having the business side handle template changes directly starts to matter a lot.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Ian,<br><br>Sent you a couple of notes about document infrastructure at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become too much of a friction as QBE continues its modernization program, feel free to reach out.

Hey Ian, appreciate you connecting. Sent you a few emails recently about the Documaker side of things, specifically the IT ticket wait on every template change. At MHC we help insurers move that ownership to the business side so changes don't queue behind developer availability. Guardian, Allstate, and Intact have gone that route, and we work with 25 or so insurers at a similar scale to QBE. Given you're across technology and operations both, figured this channel might be a better fit than the inbox. Worth a quick conversation to see if any of this is relevant? Chris

Hi Nelson,<br><br>Chris here from MHC Automation.<br><br>Given your role running hosting and operations at QBE, I wanted to ask about something that comes up constantly with infrastructure teams at insurers your size. Does updating policyholder-facing documents still run through developers, or has your team found a way to get the business side handling those changes directly?<br><br>The pattern we see a lot: every template change, no matter how small, turns into an IT ticket. A developer has to touch it. That queue adds days or weeks to something that should take hours. With QBE's modernization push around digital platforms and operational efficiency, I'd imagine the document layer is either already on the roadmap or quietly blocking progress on it.<br><br>We work with 60+ insurance organizations on their document infrastructure, including Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a quick chat and see if what we do is relevant to where QBE is headed. If you're not the right person for this, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Nelson,<br><br>One more thought on the IT dependency piece I mentioned.<br><br>I'll be straight with you on proof: we don't have a single insurance case study with a hard metric I can point to. What I can tell you is the pattern across the 60+ insurers we work with, including Intact Financial, Acuity, and Allstate. The insurer moves to MHC NorthStar CCM, the compliance and operations teams start managing templates directly, and the wait for IT stops being part of the process.<br><br>For a team like yours, the value is less about document output volume and more about who owns the change path. When a regulatory update hits, or QBE needs to push a policy communication across your commercial and personal lines book, the question is whether that requires a developer or not.<br><br>That's the problem we're built to solve: removing IT from the day-to-day document change path without removing the controls that IT needs to keep in place.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Nelson,<br><br>Sent you a couple of notes about document infrastructure at QBE. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become too much of a friction point on the modernization side, feel free to reach out.

Hey Nelson, appreciated you connecting. Sent you a few notes over email about the developer scarcity piece and the document layer sitting in the way of broader roadmap work. At MHC we help insurers move template ownership off IT queues so engineering capacity goes somewhere more strategic. A few names you might recognise on that side: Guardian, Allstate, Intact, Acuity. Twenty-five plus insurers have made the shift, and MHC ranks as the top mid-market platform in the Aspire leaderboard. If any of this lands, feel free to reach out whenever. Chris

&mdash;

&mdash;

&mdash;

&mdash;

Hi Meghann,<br><br>Chris here from MHC Automation.<br><br>Given your role in operations at AIG, I wanted to ask about something that comes up a lot at insurers your size. When a regulatory change or a brand update hits, does your team have to route document template changes through IT and wait on a developer to get it done?<br><br>At companies running older document platforms, that wait can stretch into weeks. Business and compliance teams know exactly what the document should say, but they can't touch it without going through a developer. At AIG's volume, across millions of policyholders, that's a real operational drag.<br><br>We work with 60+ insurance organizations on their document infrastructure, including Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help your ops team reduce that dependency. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Meghann,<br><br>Following up on what I sent about the document change bottleneck.<br><br>One example that might be relevant: HSBC runs 100 to 200 trade document templates on MHC for letters of credit, guarantees, and SWIFT messages. Their IT team stopped being the bottleneck for every template update. The people who know what the documents should say handle changes directly, with controls in place.<br><br>I think about that in the context of AIG Next. Modernization goals tend to stall when the document layer isn't keeping pace. If compliance or ops still needs a developer ticket to update policyholder notices, renewal communications, or endorsement language, that's friction the rest of the modernization work can't route around.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the guardrails.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Meghann,<br><br>Sent you a couple of notes about document operations at AIG. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become a friction point in the AIG Next rollout, feel free to reach out.

Meghann, good to be connected. I sent a few emails recently about the Documaker developer dependency piece, specifically the cost and capacity squeeze when a small number of specialists own every template change for things like portfolio reports and 1099s. Figured LinkedIn might be a better place to continue that conversation. At MHC we help insurers move that template ownership to the business side. HSBC used the same approach to manage 100-200 complex templates and SWIFT communications while pulling IT out of the day-to-day. Happy to reconnect here if the timing ever works. Chris

&mdash;

&mdash;

&mdash;

&mdash;

Hi Daune,<br><br>Chris here from MHC Automation.<br><br>Given your role leading IT technology delivery at AIG, I wanted to ask about something that comes up a lot at global insurers your size. With AIG Next pushing hard on operational efficiency, is the document layer keeping up, or is every template change still a developer ticket?<br><br>At your volume, that adds up fast. Policyholder communications, endorsements, renewal notices, claims correspondence across Global Specialty and beyond. When a regulatory change hits or a business team needs a document updated, if that still requires someone who knows the underlying system to do it, the backlog gets real.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help free up your dev capacity for higher-priority AIG Next work. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Daune,<br><br>Following up on what I sent about the document layer and AIG Next.<br><br>One example worth sharing: HSBC runs 100 to 200 trade document templates on MHC for letters of credit, guarantees, and SWIFT messages. The compliance and ops teams handle template changes directly now. IT stops being the bottleneck, and changes happen the same day instead of waiting in a queue.<br><br>ING Bank in Poland manages around 600 templates for accessibility and regulatory compliance on the same platform. When a regulatory change comes through, the people who need to act on it are the ones making the update.<br><br>For a global operation like AIG, where Specialty Aerospace alone touches multiple jurisdictions and document types, that kind of flexibility matters. That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Daune,<br><br>Sent you a couple of notes about AIG's document infrastructure. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become too much of a friction point inside AIG Next, feel free to reach out.

Daune, appreciate you connecting. Sent you a few emails about the document infrastructure gap in the modernisation work, so you probably have some context already. At MHC we help insurers get template ownership off IT queues and onto the business side. ING Poland moved around 600 templates that way and freed up their developers for higher-priority work. Given your role sitting across both IT delivery and doc operations at AIG, figured LinkedIn might be a better place to have this conversation anyway. If any of this lands, feel free to reach out whenever. Chris

Hi Bonnie,<br><br>Chris here from MHC Automation.<br><br>Given your role in operations at AIG, I wanted to ask about something that comes up a lot at global insurers your size. When a policy form, renewal notice, or compliance disclosure needs to change, does that still go through IT and wait on a developer to touch the template?<br><br>At AIG's volume, that bottleneck gets expensive fast. A regulatory update that affects millions of policyholders shouldn't take weeks to move from approval to production. But on most legacy document platforms, that's exactly what happens.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help reduce the time between a document change decision and the moment it reaches policyholders. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Bonnie,<br><br>One more thought on the document ops piece I mentioned.<br><br>I'll be upfront: I don't have a single insurance case study with one clean metric to point to. What I can share is the pattern we see across the 60+ insurers we work with. Once the business side, your compliance team, your ops coordinators, can make template changes directly without writing an IT ticket, the wait disappears. Changes that used to take two to three weeks happen the same day.<br><br>At AIG's scale, with millions of policyholders across property-casualty, life, and retirement lines, that kind of speed matters. A state regulatory change hits, and your team needs to push updated policy forms, endorsements, and renewal notices across all affected lines fast. On most legacy document platforms, that's a developer project. It doesn't have to be.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path with approval workflows and controls still in place.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Bonnie,<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction, feel free to reach out.

Bonnie, appreciate you connecting. Sent you a few emails a while back about the document infrastructure piece, so figured LinkedIn was a better spot to continue the conversation. At MHC we help insurers move template ownership to the business side so doc ops teams aren't waiting on IT for every change. Guardian, Allstate, and Intact all run their policyholder communications on MHC across 60+ insurance organisations, so AIG is a space we know well. If any of this lands, feel free to reach out whenever. Chris

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

&mdash;

Hi Andrea,<br><br>Chris here from MHC Automation.<br><br>Given your role managing forms and document production at AIG, I wanted to ask about something we see come up constantly at insurers your size. When a change needs to happen on a policy contract, beneficiary notice, or premium notice, does that still mean an IT ticket and a wait before anything moves?<br><br>At companies with millions of policyholders, that wait adds up fast. Especially when a regulatory update or product change has to hit welcome kits, annual statements, and surrender letters all at once. We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>Happy to chat and see if there's a fit. If you're not the right person for this conversation, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Andrea,<br><br>Following up on what I sent about the template change bottleneck.<br><br>One thing I should have included: Natera was running a similar situation where document changes were stuck in a long queue before anything got out the door. They cut their turnaround from 2.5 weeks to 2 days by letting the people who know what the documents should say handle the updates directly, with controls in place so IT wasn't removed from the picture entirely.<br><br>With something like the Corebridge transition underway and leadership pushing on GenAI and digital modernization, the document layer tends to be one of the first things that either accelerates that work or quietly holds it up. Policy contracts, beneficiary notices, annual statements, those don't get simpler during a merger. That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the guardrails.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Andrea,<br><br>Sent you a couple of notes about document template workflows at AIG. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team put together a resource on how insurers replace legacy document platforms when the old setup starts slowing everything else down.</a><br><br>If current document composition processes become too much of a friction point, feel free to reach out. Happy to reconnect whenever the timing makes sense.

Hey Andrea, appreciate you connecting. Sent you a few emails recently about the IT ticket bottleneck on template changes, so you have some context on what we do at MHC. Short version: we help insurers move template ownership to the business side so changes don't have to route through a developer queue. Natera ran into the same thing and got cycle times down from two and a half weeks to two days after making the switch. Happy to reconnect here if the timing ever works. Chris

Hi Jason,<br><br>Chris here from MHC Automation.<br><br>Given your role leading the Duck Creek Center of Excellence at AIG, I wanted to ask about something that comes up a lot with large carriers running Duck Creek environments. When a policy document or endorsement needs to change, does your team still have to route that through a developer, or has AIG found a way to put that in the hands of the business side?<br><br>At AIG's scale, that dependency adds up fast. Millions of policyholder communications, declarations pages, endorsements, renewal notices, cancellation letters, each one potentially blocked behind a developer who knows the composition layer. When a regulatory change hits or an underwriting requirement shifts, the wait can stretch across weeks just to get a template updated.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to chat and see if there's a way to reduce that dependency within your Duck Creek ecosystem. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Jason,<br><br>Following up on what I sent about the document change bottleneck.<br><br>One example that might be relevant: <a href="https://www.mhcautomation.com/customer-stories/optum-home-community-streamlines-patient-communications/?utm_campaign=227748570-CM_CDA_Customer%20Stories&utm_source=Chameleon&utm_content=Customer%20Story%20-%20Optum">Optum</a> consolidated 200+ templates across multiple plan types, authorization letters, approval notices, denial correspondence, all running through one compliant workflow. They cut turnaround from 2.5 weeks to 2 days by getting developers out of the day-to-day change path.<br><br>The pattern we see at large carriers is similar. Policyholder data sits across policy admin, claims, and rating systems. Every document pulls from a different source. When a regulatory change hits or Duck Creek pushes an update, someone has to chase down the right template in a system only a developer can touch. At AIG's volume, that's not a one-off delay, it stacks.<br><br>That's what MHC NorthStar CCM does differently: your compliance or operations team makes the change directly, with approval workflows built in, and IT stops being the bottleneck.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Jason,<br><br>Sent you a couple of notes about document workflows at AIG. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction, feel free to reach out.

Hey Jason, good to be connected. Sent you a few emails about the IT dependency piece on template changes, specifically the developer cost every time a manuscript endorsement or broker communication needs updating. At MHC we help insurers move that ownership to the business side so changes don't sit in a queue. Optum got 200+ templates down from a 2.5-week turnaround to 2 days. Allied Benefits cut $4-per-doc costs across more than a million communications. Worth a quick conversation to see if any of this is relevant? Chris

Hi David,<br><br>Chris here from MHC Automation.<br><br>Given your role overseeing global platforms and shared technology at AIG, I wanted to ask about something we see come up a lot at carriers your size. With everything moving under AIG Next, is the document production layer keeping up, or is it still dependent on developers to get anything changed?<br><br>At mega-scale, that dependency compounds fast. Policy documents, endorsements, renewal notices, claims correspondence going out to millions of policyholders globally. Every template change requiring someone who knows the underlying system before anything moves. That kind of bottleneck tends to surface as a real friction point when you're trying to move faster on the operational side.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help reduce that dependency without disrupting what's already running. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi David,<br><br>One more thought on the document infrastructure piece I mentioned.<br><br>HSBC runs 100 to 200 complex trade document templates on MHC, covering letters of credit, guarantees, and SWIFT messages. High compliance requirements, multiple jurisdictions, tight turnaround windows. Their team manages template changes without routing every update through a developer.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path while keeping the approval workflows and controls in place.<br><br>For a platform like AIG's, where you're running policyholder communications across multiple lines of business globally, that matters especially when a regulatory change has to propagate across millions of policies fast. The compliance team makes the change the same day instead of waiting on an IT queue.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi David,<br><br>Sent you a couple of notes about the document infrastructure piece at AIG. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become too much of a friction as AIG Next moves forward, feel free to reach out.

Hey David, appreciate you connecting. Sent you a few emails recently about the IT dependency piece I mentioned, getting template changes off the developer queue. At MHC we help insurers move that ownership to the business side so IT isn't the bottleneck on every document update. One thing that resonated with a similar team was HSBC managing 100-200 complex SWIFT templates with strong compliance controls, without the constant developer lift. Given AIG's scale across global platforms, figured it was worth a note here. Worth a quick conversation to see if any of this is relevant? Chris

Hi Roshan,<br><br>Chris here from MHC Automation.<br><br>Given your role as CIO at AIG, I wanted to ask about something we see come up a lot at global carriers your size. With millions of policyholders across property-casualty, life, and retirement lines, does updating customer-facing documents still require going through a developer every time a change needs to happen?<br><br>At that scale, even a small delay in the change cycle creates real exposure. A regulatory update hits one state, and the team has to queue it up with IT, wait on someone who knows the composition system, and hope nothing else is blocking the sprint. Multiply that across AIG's global footprint and it becomes a structural problem.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help reduce the developer dependency in your document change path. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Roshan,<br><br>Following up on what I sent about document bottlenecks at AIG's scale.<br><br>One thing I should have included: Guardian Life, Allstate, Intact Financial, and Acuity Insurance run their policyholder communications on MHC. That's alongside 60+ other insurance organizations. The pattern we see is consistent. The insurer moves to MHC, the compliance or ops team starts managing templates directly, and IT stops being the bottleneck for every document change.<br><br>That matters at AIG's volume. Your policyholder data probably sits across multiple systems. Every document pulls from a different source. When a regulatory change hits, someone has to update the template in a system only a developer can touch. With millions of policyholders across your P&C, life, and retirement lines, that wait is not a minor inconvenience.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path with controls in place so the guardrails IT cares about stay intact.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Roshan,<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become too much of a friction point as AIG Next moves forward, feel free to reach out.

Roshan, good to have you in the network. Sent you a few emails recently about the IT dependency piece on document template changes. Didn't want to assume you'd seen them, so figured LinkedIn was worth a shot. At MHC we help insurers move template ownership off developer queues and to the business side. Guardian and Allstate both use us to cut out that bottleneck in document composition, which at AIG's scale tends to compound fast. Worth a quick conversation to see if any of this is relevant? Chris

Hi Michelle,<br><br>Chris here from MHC Automation.<br><br>Given your role running Financial Lines Operations at AIG, I wanted to ask about something that comes up constantly at carriers your size. Does every change to a policyholder-facing document still require an IT ticket and a developer to touch the template before it goes out?<br><br>At mega carriers, that queue can be brutal. A regulatory update hits, or a product change rolls through underwriting, and the ops team is stuck waiting on IT to update declarations pages, endorsements, renewal notices, cancellation letters. The document layer becomes the slowest thing in an otherwise fast operation.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to chat and see if there's a fit. If you're not the right person at AIG for this, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Michelle,<br><br>Following up on what I sent about the document change bottleneck.<br><br>We recently helped Guardian Life and 25+ other insurers modernize their document infrastructure. The pattern is consistent: once the compliance or ops team can update templates directly, the wait disappears. A regulatory change to an endorsement or renewal notice gets handled the same day instead of sitting in an IT backlog.<br><br>With AIG's scale and the AIG Next push around operational efficiency, that kind of friction in the document layer tends to show up in the expense ratio before anyone fully connects the dots. Declarations pages, endorsements, cancellation notices, certificates of insurance across millions of policyholders. That's a lot of tickets that never needed to be written.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Michelle,<br><br>Sent you a couple of notes about document ops at AIG. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become too much of a friction on the AIG Next roadmap, feel free to reach out.

Hey Michelle, good to be connected. Sent you a few emails about the IT ticket bottleneck on template changes, so you have some context on where we're coming from. At MHC we help insurers get document changes off the developer queue and into the hands of the business side directly. Guardian moved that direction and we've since worked through similar migrations with 25 or more insurers running into the same Documaker constraints. No pressure on timing. Happy to reconnect here if the timing ever works. Chris

Hi Alpa,<br><br>Chris here from MHC Automation.<br><br>Given your role leading transformation at AIG, I wanted to ask about something that comes up a lot when global insurers are deep in an operational overhaul. Does the document production layer keep pace with the rest of the modernization work, or does it end up being the thing that slows everything else down?<br><br>At AIG's scale, with millions of policyholders across property-casualty, life, and retirement, every policy document, renewal notice, declarations page, endorsement, and claims letter is tied to a system that probably requires a developer to touch. When your modernization roadmap moves fast, that dependency can become a real friction point.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help reduce that kind of bottleneck as part of the AIG Next work. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Alpa,<br><br>One more thought on the document infrastructure piece I mentioned.<br><br>Guardian Life, Allstate, Intact Financial, and Acuity Insurance run their policyholder communications on MHC, alongside 60+ other insurance organizations. The pattern is consistent: the insurer moves to MHC, the compliance and ops teams start managing templates directly, and IT stops being the bottleneck every time a document needs to change.<br><br>At AIG's volume, that matters. Your policyholder data sits across property-casualty, life, and retirement systems. When a regulatory change hits or the AIG Next roadmap requires a document update, the change has to propagate across all of them. On most legacy platforms, that's a developer project. On MHC NorthStar CCM, the business side makes the change with controls in place.<br><br>That kind of flexibility matters especially when a regulatory update has to reach millions of policyholders fast across declarations pages, endorsements, renewal notices, and claims correspondence.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Alpa,<br><br>Sent you a couple of notes about the document layer at AIG. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become too much of a friction point in the AIG Next work, feel free to reach out.

Alpa, good to have you in the network. I sent a few emails over the past weeks about the document infrastructure gap in modernisation work, so you may have seen those. At MHC we help insurers move template ownership off IT queues so the business side can make changes directly. Guardian and Allstate are both running on it now, along with 25 or so other carriers who had the same document layer sitting in the way of broader roadmap progress. Worth a quick conversation to see if any of this is relevant? Chris

Hi Claude,<br><br>Chris here from MHC Automation.<br><br>Given your role guiding AIG Next and the GenAI expansion, I wanted to ask about something that comes up often at insurers your size. As you modernize operations and push toward a unified structure, is the document production layer keeping pace with the rest of the transformation, or is it still a bottleneck that requires developer involvement for every change?<br><br>At the volume AIG operates, policyholder communications, endorsements, renewal notices, declarations pages, that kind of output, even small template updates can sit in a queue waiting on a developer who knows the legacy system. When your AI and modernization investments are moving fast, that gap tends to show up at the worst moments.<br><br>We work with 60+ insurance organizations on their document infrastructure, including Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>I'd be happy to have a chat and see how we can help reduce that dependency as AIG Next continues to roll out. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Claude,<br><br>Following up on what I sent about the document layer piece.<br><br>I want to be straightforward with you: I don't have a single insurance case study with a headline metric I can point to. What I can tell you is the pattern across the 60+ insurers we work with. The insurer moves to MHC, compliance and operations teams start managing templates directly, and the wait for developer availability stops being a factor in how fast a document change goes out.<br><br>That matters especially when a regulatory change hits a state market, or when AIG Next's unified structure means a single update has to propagate across multiple lines and geographies fast. With millions of policyholders, the delay between a required change and the document reflecting it is real exposure.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls in place.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Claude,<br><br>Sent you a couple of notes about the document infrastructure piece at AIG. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction as AIG Next moves forward, feel free to reach out.

Good to connect, Claude. Sent you a couple of emails about the Documaker piece, specifically the IT ticket wait on every template change and what that costs when developers are already stretched. Figured I'd try a different channel since you accepted. At MHC we help insurers move that ownership off the developer queue to the business side. Allstate and Intact have made that shift, and we're running document infrastructure for 25+ carriers at this point. Given your background at AIG, you've probably seen that bottleneck up close. Happy to reconnect here if the timing ever works. Chris

Hi Angie,<br><br>Chris here from MHC Automation.<br><br>Given your role in business transformation and technology at AIG, I wanted to ask about something that comes up a lot at global insurers your size. When your teams are pushing AI into underwriting and claims workflows, does the document layer keep pace, or does every template change still require a developer to touch it?<br><br>At AIG's volume, that bottleneck shows up fast. Policy correspondence, claims letters, regulatory notices, all of it pulling from multiple systems. When a regulatory change hits or a workflow gets redesigned, someone has to update templates in a platform only IT can touch. That slows down everything the business side is trying to move.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help your transformation team close the gap between your AI investments and the document layer underneath them. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Angie,<br><br>One more thought on the document infrastructure piece I mentioned.<br><br>Guardian Life and 25+ other insurers have moved their policy and claims correspondence onto MHC. The pattern I keep seeing: once the business side can update templates directly, the IT ticket for every document change just stops getting written. Compliance handles the language, ops handles the layout, and changes happen the same day instead of sitting in a queue.<br><br>At AIG's scale, with millions of policyholders across property-casualty, life, and retirement lines, that kind of speed matters especially when a state regulatory update or a claims workflow change has to propagate across your full document output. That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls IT needs.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Angie,<br><br>Sent you a couple of notes about the document layer at AIG. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction, feel free to reach out.

Appreciate you connecting, Angie. Sent you a few emails recently about the IT dependency piece I mentioned, so figured I'd reach out here too since you're deep in transformation work at AIG. At MHC we help insurers get template changes off the developer queue and into the hands of the business side. Guardian and 25-plus insurers have moved their policy and claims correspondence over to us for that reason. Happy to reconnect here if the timing ever works. Chris

Hi Brad,<br><br>Chris here from MHC Automation.<br><br>Given your role overseeing engineering at a company like AIG, I wanted to ask about something we see come up a lot at global carriers your size. With everything moving under AIG Next, is the document template layer keeping pace, or is every change still routing through developers who know the legacy system?<br><br>At your volume, that bottleneck gets expensive fast. Policyholder communications, endorsements, renewal notices, certificates of insurance, any of those document types tied to a platform that requires a developer to touch every update becomes a real drag on the modernization timeline.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help reduce that dependency so your team stays focused on higher-priority work. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Brad,<br><br>Following up on what I sent about the document template bottleneck.<br><br>One example worth sharing: <a href="https://www.mhcautomation.com/customer-stories/optum-home-community-streamlines-patient-communications/?utm_campaign=227748570-CM_CDA_Customer%20Stories&utm_source=Chameleon&utm_content=Customer%20Story%20-%20Optum">Optum</a> consolidated 200+ templates across BCBS and Humana plan types. Authorization letters, approval notices, denial correspondence, all running through one compliant workflow. The compliance team makes changes directly now. IT stops being the bottleneck.<br><br>That matters at AIG's scale because when a regulatory change hits across multiple states, someone has to update the right templates in the right system fast. With millions of policyholders, that's not a small ask. If the change still requires a developer queue, the timeline slips.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Brad,<br><br>Sent you a couple of notes about the document layer at AIG. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction, feel free to reach out.

Hey Brad, appreciated the connection. Sent you a few emails about the IT dependency piece on template changes, so you've probably got the gist of what we do at MHC. Short version: we help insurers move document ownership off the developer queue and to the business side. Allied Benefits was spending roughly $4 per document in IT overhead before they moved off their legacy platform. That number tends to add up fast at AIG's scale. Happy to reconnect here if the timing ever works. Chris

Hi Daisy,<br><br>Chris here from MHC Automation.<br><br>Given your role running client and policy servicing operations at AIG, I wanted to ask about something that comes up constantly at insurers your size. When a document needs to change, whether that's a policy notice, a renewal, a certificate, or claims correspondence, does that still require tracking down a developer and waiting on an IT ticket?<br><br>At organizations with millions of policyholders, that wait adds up fast. And the developers who know the document system well are genuinely hard to find and keep. When one leaves, the institutional knowledge goes with them.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>I'd be happy to chat and see if there's a fit with what your team is working through on the AIG Next side. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Daisy,<br><br>Following up on what I sent about the document change bottleneck piece.<br><br>We've worked with Guardian Life and Allstate, along with 25+ other insurers, on exactly this. The pattern is consistent: once business users can manage policy and claims document templates directly, the wait disappears. Changes that took days or weeks start happening the same day.<br><br>That matters a lot when a regulatory update has to go out to millions of policyholders and the only person who can touch the template is unavailable or no longer with the company.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls IT needs.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi Daisy,<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current document composition processes become too much of a friction with everything happening under AIG Next, feel free to reach out.

Daisy, good to connect. I sent a few emails about the Documaker dependency piece, specifically the IT ticket wait on template changes and what that costs when your developer pool is shrinking. Figured LinkedIn was worth a try since the emails didn't land. At MHC we help insurers move template ownership off the IT queue and to the business side. Guardian and Allstate both went through that shift, and we've done it with 25 or so other carriers at this point. If any of this lands, feel free to reach out whenever. Chris

Hi Christopher,<br><br>Chris here from MHC Automation.<br><br>Given your role overseeing operations at AIG, I wanted to ask about something that comes up a lot during large-scale modernization efforts. As you're working through AIG Next and the operational separation from Corebridge, is the document production layer keeping pace, or is it still dependent on developers for every template change?<br><br>At your volume, that dependency compounds fast. Policyholder communications, endorsements, renewal notices, declarations pages, all of it sitting behind an IT queue. When a regulatory change hits across multiple lines and geographies, someone has to find the developer who knows the system before anything moves.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire.<br><br>I'd be happy to have a chat and see how we can help reduce that IT dependency on the document side as AIG Next moves forward. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi Christopher,<br><br>Following up on what I sent about the document dependency piece.<br><br>One example worth sharing: <a href="https://www.mhcautomation.com/customer-stories/optum-home-community-streamlines-patient-communications/?utm_campaign=227748570-CM_CDA_Customer%20Stories&utm_source=Chameleon&utm_content=Customer%20Story%20-%20Optum">Optum</a> consolidated 200+ templates across multiple plan types and pulled their compliance and ops teams out of the IT queue entirely. Authorization letters, approval notices, denial correspondence, all running through one compliant workflow. The people who knew what the documents needed to say were the ones making the changes.<br><br>That matters especially at AIG's scale. With millions of policyholders across property-casualty, life, and retirement lines, a single regulatory update can mean hundreds of template variants across states and product types. On most legacy document systems, that is a developer project before it is a compliance project.<br><br>That is what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that is the preferred initial step.

Hi Christopher,<br><br>Sent you a couple of notes about the document infrastructure piece at AIG. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If the document layer becomes a friction point as AIG Next moves forward, feel free to reach out.

Hey Christopher, appreciate you connecting. Sent you a few notes over email about getting document changes off the developer queue. At MHC we help insurers move template ownership to the business side so IT tickets stop being the bottleneck on customer communications. Optum got there with 200+ templates now managed without routing every change through an IT queue, which gives you a sense of what that shift looks like at scale. Happy to reconnect here if the timing ever works. Chris

Hi David,<br><br>Chris here from MHC Automation.<br><br>Given your role overseeing technology at AIG, I wanted to ask about something that comes up a lot as insurers push through modernization programs. With AIG Next in motion and the AI strategy accelerating, is the document production layer keeping up, or is it still bottlenecked by developers who know the legacy system?<br><br>At your scale, that bottleneck compounds fast. Millions of policyholder communications, each tied to templates that need a specialist to touch. When underwriting or claims workflows modernize but the documents feeding out of them don't, the gap shows up in cycle times and compliance exposure.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a quick chat and see if there's a fit. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar

Hi David,<br><br>Following up on what I sent about the document layer piece.<br><br>One example worth sharing: <a href="https://www.mhcautomation.com/customer-stories/optum-home-community-streamlines-patient-communications/?utm_campaign=227748570-CM_CDA_Customer%20Stories&utm_source=Chameleon&utm_content=Customer%20Story%20-%20Optum">Optum</a> consolidated 200+ templates across BCBS and Humana plan types. Authorization letters, approval notices, denial correspondence, all running through one compliant workflow. They cut document cycle times from 2.5 weeks to 2 days by letting the business side handle template changes directly.<br><br>The reason that matters for a program like AIG Next is that most document platforms require a developer in the loop for every template change. When a regulatory update hits, or a product change needs to reflect in policyholder communications at scale, that becomes an IT project, not a business operations task.<br><br>That's what MHC NorthStar CCM does differently: it removes the developer from the day-to-day change path without removing the controls in place.<br><br>If this resonates, happy to chat in the days or weeks to come. I can share some docs if that's the preferred initial step.

Hi David,<br><br>Sent you a couple of notes about the document infrastructure piece at AIG. Wanted to share one last thing before I get too persistent.<br><br><a href="https://www.mhcautomation.com/your-document-platform-shouldnt-be-your-biggest-liability/">Our team has put together a resource on how we replace legacy document platforms</a><br><br>If current CCM or document composition processes become too much of a friction as AIG Next moves forward, feel free to reach out.

Hey David, appreciate you connecting. Sent you a few emails about the IT dependency piece I mentioned, figured LinkedIn might be a better place to pick up the thread. At MHC we help insurers move template ownership to the business side so changes stop sitting in developer queues. Optum got there with 200+ templates, cutting cycle times from two and a half weeks to two days. No agenda here, just thought it was worth a different channel given what's happening with developer capacity at carriers right now. Happy to reconnect here if the timing ever works. Chris

Hi David,<br><br>Chris here from MHC Automation.<br><br>Given your role as CIO at AIG, I wanted to ask about something that comes up a lot at global carriers your size. As you're pushing through AIG Next and the broader modernization effort, is the document production layer keeping pace with everything else on the roadmap?<br><br>At organizations running policy admin and claims platforms at your volume, the document layer is often the last thing to get modernized. Template changes still route through a small group of developers, and as teams thin out post-restructuring, that bottleneck gets harder to work around. With millions of policyholders across commercial, personal, and life lines, the downstream risk on delayed or noncompliant communications adds up fast.<br><br>We work with 60+ insurance organizations on their document infrastructure, including companies like Guardian Life, Allstate, and Acuity. Ranked #1 mid-market CCM by Aspire. I'd be happy to have a chat and see how we can help reduce that dependency without disrupting what's already in production. If you're not the right person, I'd appreciate being pointed in the right direction.<br><br>PS: here is my calendar link for convenience: https://meetings-na2.hubspot.com/chris-raffield/mhcnorthstar