Why I Built LeadRobin

Insurance agencies have a lead problem. Leads come in from everywhere - website forms, comparison sites, referral networks - but distributing them to brokers is still manual in most shops. Someone checks the inbox, picks a broker, forwards the email, and hopes they remember to follow up.

I saw this at agencies I worked with. Leads were getting lost. Brokers were getting uneven workloads. And there was no way to track what happened after a lead was assigned.

The old system was a C# desktop application running on a Windows server. It worked, but it was only available on the local network and it needed to be exposed to the internet for connectivity. It needed a new authentication system and to be hosted on a Linux container, easier and less expensive to deploy.

But there was another piece of the puzzle: the agencies already use Microsoft 365 for business. They have shared mailboxes set up specifically for leads - leads@agency.com, info@agency.com, etc. Brokers check these mailboxes manually throughout the day. The infrastructure is already there, it's just not being leveraged.

When I founded Magnum Software Services, I decided to rebuild it from the ground up - and this time, integrate directly with the Microsoft 365 ecosystem they're already using. The result is LeadRobin.

The goal was simple: an automated system that monitors those shared mailboxes via Microsoft Graph API, parses incoming lead data, assigns it to the next available broker using round-robin logic, forwards the email, and pushes via an API integration the lead to an agency management system. No manual intervention. No lost leads. Complete visibility.

What followed was building, debugging, and iterating. And I used AI coding tools and agents as my staff and developers. This series documents the journey.