Most agencies my size run on @company.com email addresses. We do not. After more than a decade of running MageCloud as a 30-person ecommerce team, every client conversation I have still goes through my personal Gmail, and so does every email my team sends.
I made that call back in 2014, and I have only become more convinced of it as we have grown. The short version is this: ecommerce founders do not hire agencies. They hire people. Putting a corporate domain in front of those people gets in the way of that relationship, and most of the time it adds nothing the client actually values.
Personal Gmail vs. Corporate Email at a 30-Person Agency
The Switch From Corporate Email to Personal Gmail
When I started out, I did what every other consultant did. I set up an @magecloud address, signed every email with my title, and tried to look bigger than I was. The problem was that nothing about that signal matched how the work actually got done.
Clients did not write to MageCloud. They wrote to me. They had questions about a Magento upgrade, or a launch deadline, or a checkout bug we shipped Friday at 11pm. The corporate address sat in front of those questions like a velvet rope. It made the relationship feel further away than it actually was.
So I dropped it. By 2014 I was using my personal Gmail for every day-to-day client conversation, and that has not changed since. Today, with the team scaled up, every member still uses their own Gmail with clients. The corporate domain only shows up on contracts and the website.
Why Clients Care About People, Not Domains
The argument for corporate email is usually framed as a trust signal. A branded sender line tells the recipient that the person on the other end has been entrusted by the company to represent the brand. That argument has real weight in regulated industries or when a stranger is reaching out cold.
It does not have much weight inside an existing client relationship. The clients who pay our invoices already know who is on the project. They have met the team, sat in calls, watched releases ship. The trust signal that matters is the one we earned by delivering. The email domain is wallpaper next to that.
What I have noticed is that personal email actually strengthens the relationship in three ways. It makes the client feel like they have a direct line to the person doing the work, not an inbox shared with five other accounts. It makes our developers and project managers more accountable, because their name is on the message rather than a generic department. And it removes any ambiguity about who is responsible when something goes wrong.
What Personal Gmail Costs Us, and What It Does Not
The honest tradeoffs are smaller than people assume. We lose the ability to centrally manage a team mailbox the way Google Workspace allows on a corporate domain. We lose some elegance in our outbound prospecting, where a personal Gmail looks less polished than a branded sender line. And we lose the option of formal compliance setups that some enterprise procurement teams expect.
What we do not lose is professionalism. The signature line on every team member’s Gmail still says MageCloud, links to our site, and identifies their role. The contracts are still on company letterhead. The invoices still come from Xero with our company details. The only thing we are choosing not to do is dress up the daily messaging.
For a 30-person team running roughly two million in annual revenue, that has been the right call. We are not trying to win procurement battles at Fortune 500 companies. We are trying to do excellent work for ambitious ecommerce founders, and those founders care that the person who promised them something is the same person typing the email back.
When a Corporate Email Actually Starts to Matter
I am not against corporate email on principle. There are real moments where it earns its place.
Cold outbound to enterprise buyers. If you are pitching a £10m+ retailer where procurement runs the relationship, a personal Gmail will hit the spam folder more often and lose status points before you say a word. A branded address is table stakes there.
Regulated or sensitive sectors. Healthcare, finance, and legal often have a written policy that vendor communication must come from a corporate domain with proper SPF, DKIM, and DMARC. There is no working around that and I would not try.
Acquisitions and large team handoffs. Once you cross 50 people, the cost of recovering an inbox when someone leaves becomes meaningful. Centralised mail with an admin who can lock and forward an account is worth the trade.
For everyone else, especially the small and mid-sized ecommerce agencies I talk to most weeks, I would tell them the same thing I told myself in 2014. Pick the channel that mirrors how the work actually gets done. If it is one named human talking to another named human, do not put a corporate sender line between them.
The Question I Keep Asking Myself
I do still ask myself, every couple of years, whether it is time to switch back. The team is bigger now than it was. Some of our newer enterprise clients would probably prefer a branded sender. We have the budget to set it up properly, with retention policies and shared mailboxes and the rest of it.
I keep coming back to the same answer. The clients who matter most to us are the ones who hired us because we are operators, not because we are a brand. Switching to corporate email would not lose us those clients. But it would change the texture of the relationship in a small way that adds up. The handful of conversations we might gain at the procurement door are not worth what we would soften at the working level.
If you are running a team that lives or dies on the strength of one-to-one relationships with founders, I would push you toward keeping the daily comms human. Save the corporate sender line for the contract.
And if you want to talk through how we structure client communication at MageCloud, or how we keep the team coordinated without a shared inbox, come find me at the next Ecommerce Camp UK. The room is full of operators who have made their own version of this same call.
Related reading: How I Spotted a Fake Shopify Takedown Email — the same ‘second pair of eyes’ habit applied to fake takedown emails impersonating Shopify.
Related reading: Why One Project Board Beats Three Agency Meetings — the cross-vendor coordination layer that sits above personal-email comms.