We send about four hundred thousand a month, so Google and Microsoft's requirements applied directly, and our SPF was over ten lookups and returning permerror. Alignment was failing on our own mail. One hosted include fixed it inside a week. I still verify the record with an outside tool before I attest to anything.

We are a consumer brand, so the inbox is part of the buying experience. Our logo getting shown beside our mail is not a vanity project; it gives people a quick way to recognise a message they should open. Before this, BIMI felt like a collection of technical hurdles: get the domain to enforcement, prepare the logo in the required SVG Tiny PS format, sort out the certificate, publish the record, and make sure the sending mail is still aligned. Palisade gave us one place to work through the authentication and hosted BIMI record instead of juggling a design export, a DNS ticket, and an email security project separately. Our designer's first export was not usable, so the conversion support mattered. We still had to do the certificate work, and that takes longer than anyone wants, but now the mark appears where we expect it to on our authenticated mail. It is a visible result from a project that would otherwise be completely invisible to the commercial team.

Palisade has an MCP server, so I connect it and ask which of my clients is failing DKIM this week without opening anything. The answer comes back with the actual ticket behind it. Approvals still happen in Palisade with me clicking, which is right. Nobody expects a DMARC tool to meet you where you already work.