Client campaigns without owning the infrastructure risk.
An independent consultant is judged on results they can show and problems they can explain. The awkward part of the job is that the sending infrastructure is usually the client's, the deliverability problems are usually inherited, and neither is something you were hired to rebuild.
What goes wrong, and what handles it.
You inherit a domain reputation you did not damage
Run the client's domain through the authentication checker before your first send, and you have a documented starting position. If SPF, DKIM or DMARC were already broken, that is a finding you report rather than a problem you silently absorb.
Clients ask why results dropped, and you have no evidence
Open and click data with device and approximate location, exportable as a PDF, gives you something to show at a review that you did not have to assemble by hand.
One client's list quality affects another client's sending
Each client gets its own authenticated sending domain and mailboxes, so reputation is built per domain. A poor list on one engagement has no path to affect the others.
You are billed per contact on platforms your clients outgrow
Pricing here is fixed by domains and mailboxes rather than by list size or messages sent, so a client with a large list does not change what the tooling costs you.
How a campaign runs.
- 01
Audit the client's domain with the free SPF, DKIM and DMARC checker and record the starting position.
- 02
Authenticate their sending domain and connect the mailboxes they provide.
- 03
Import and validate the list, reporting invalid and duplicate rows back to the client before sending.
- 04
Build the campaign with mail merge and Spintax so messages are personalised and non-identical.
- 05
Send with volume rotating across their mailboxes at a safe per-account rate.
- 06
Export the PDF report at completion and use it as the basis of the review.
Where this is not the right tool
This is a sending platform, not a consultancy toolkit. There is no client portal, no per-client login, no time tracking and no proposal tooling. Each account is a single workspace, so several clients means either sharing one workspace or running separate accounts. If you need genuine multi-tenancy, an agency-specific platform will serve you better.
Questions from consultants teams.
Setup, limits and the things worth knowing before you commit.
Can I use this for multiple clients as a freelancer?
Yes, within one workspace — you can authenticate several client domains and connect mailboxes on each. What you do not get is separate client logins or a client-facing portal. For a consultant running a handful of engagements that is usually fine; for an agency managing dozens it is not.
Should the client own the sending domain, or should I?
The client, almost always. Domain reputation is an asset that should stay with the business it belongs to, and a client who later moves on should not lose the sending reputation they paid you to build. It also keeps you out of an awkward position if the engagement ends.
Can I white-label the reports?
Reports export as PDF for you to send on, but there is no branding customisation applied across the dashboard or the export. If white-labelled reporting is central to how you present work, this will not cover it.
What do I do if a client's domain is already damaged?
Diagnose before you send. Run the authentication checker, look at their bounce and complaint history, and check whether they have been mailing an unengaged list for years. Sending a campaign into an existing reputation problem makes it your problem — establishing the starting position first makes it a finding you were hired to fix.
Send a real campaign first.
Connect a mailbox, run your domain through the authentication checker, and see the results before you commit to a plan.
Start Free Trial