Build a campaign once, save it as a private template your whole team can reuse across clients, and export the compiled HTML to run through each client's own ESP and domain — instead of starting from a blank canvas every time.
An agency's real bottleneck isn't building one great interactive email — it's building the tenth one without redoing the same structural work, and handing delivery off cleanly to whichever ESP each client already trusts.
Save the structure, not just the copy
Open a finished build in the studio and click Save as template, kept Private — visible to you and anyone you've invited to your team, listed under "My team's templates" in the picker on every future project. A few one-time fields (real delivery codes, real meeting links, real dates) are cleared automatically, since they wouldn't make sense to reuse.
Invite your team with the right role
Editor teammates get full access to build and send from shared templates and projects; only the account owner can rotate credentials or manage billing and team membership itself — see Team collaboration for the full split.
Hand delivery to the client's own domain
Once a client's version is built, Export compiles it into a single static HTML file — all three fallback tiers included — ready to paste into that client's own ESP. Delivery, domain authentication, and sender reputation all stay on their side; MailInApp keeps hosting the interaction endpoints and live view afterward.
Private, not public
Publishing to the community gallery needs admin approval and blanks every merge-tag variable's default value — the opposite of what an agency wants when a template carries a specific client's own placeholder defaults. Private keeps those defaults intact for just your team.
Getting started
Build a client-agnostic shell, Save as template as Private, invite your team under Settings → Team, and Export each client's finished version to their own ESP.