We built the tool
we couldn't find.

After more than 20 years running an MSP in the Mid-Atlantic, we had accumulated a stack of tools that technically did everything we needed — just never in the same place. Domains were spread across a couple of registrars, DNS management was handled separately, hosting was in its own control panel, and DMARC reporting had become its own silo once it graduated from "nice to have" to something clients actually asked about.

None of those tools were bad at their individual job. The problem was that none of them were built with an MSP's workflow in mind. They were built for the person who owns one domain or manages one server. The MSP use case — dozens of clients, hundreds of domains, team members with different access levels — was an afterthought, if it was considered at all.

DMARC was the last straw. Email authentication had become a real part of client deliverables, not a checkbox on a security audit. But every DMARC reporting tool we looked at was designed for the end organisation, not for an MSP managing email security across twenty clients simultaneously. You'd set up reporting, start getting aggregate data, and then have nowhere sensible to put it in the context of that client's broader DNS and domain configuration.

We kept working around it. Spreadsheets, notes, custom scripts to pull data together. At some point that workaround started costing more time than building something better would have.