Designers

Email Templates for Designers

Email templates built to keep a visual standard from the first draft to the final send, with the tools that fit design work, what each one lists as its price, and copyable text for the emails designers send most.

Beefree Professional, listed at $30 per month, is the best starting point for a designer who reuses layouts across client work. Its unlimited project folders and unlimited reusable content blocks let you save a header, footer or call-to-action button once and place it in every new campaign, so each client gets the same structure without a rebuild. The free Starter plan allows 10 designs and 6 exports per month. That is enough to learn the editor, but it usually runs short once client work becomes regular.

This page compares the four tools that fit design production: Beefree and Stripo for visual building, MJML for template code, and Make for sending an email when a form is submitted or an order is placed. It sets out the listed prices at several output levels, gives copyable text for four common designer emails, and ends with a checklist for shipping a template that someone else can send.

What a Designer Needs From a Template Tool

Designers judge an email tool on fidelity first. A marketer may care most about how fast a send can go out. A designer wants the layout to still look like the design once it reaches a phone, a dark-mode inbox or a webmail client that strips part of the stylesheet. Speed still counts, but it counts after the design holds up.

Four questions separate a useful tool from a pleasant editor. Is the exported HTML readable enough to open and inspect? Can a header, footer or button be saved once and reused? Can brand rules such as typefaces, colors and button shapes hold steady when a second person edits the template? And do the export limits or credit allowances match how often you actually ship?

Pricing pages describe what a plan includes. They do not show how a template renders in a given inbox, so a render check belongs in every project plan, whichever tool you choose.

Tool Comparison for Designers

The table shows the four options with their listed starting prices. Each price names the plan and the billing view shown on the vendor's pricing page.

ToolBest forStarting price (plan and billing)Key limitation
BeefreeDesigners who reuse blocks across many client projectsStarter, $0; Professional, $30 per monthStarter caps you at 10 designs and 6 exports per month
StripoDesigners who want a free start and a clear upgrade pathFree editor plan with no time limit; Basic, $20 per monthThe step from Medium ($45 per month) to Pro ($125 per month) is large
MJMLTemplates kept in code and under version controlSelf-hosted; pricing on requestNo visual canvas, so people without code need a build step
MakeSending emails when a form, order or event happensFree plan with 1,000 credits per month; Core, $9 per month billed annuallyIt is not a template editor and needs a builder alongside it

Beefree: The Default for Reusable Design

Beefree is a visual editor, and its main value for designers is reuse. On the Professional plan, listed at $30 per month, unlimited project folders let you keep one folder per client, campaign or product line. Unlimited reusable content blocks let you save a header, a footer or a product module once and drop it into any project. For a studio that sends similar layouts to many clients, the time saving comes from carrying those modules forward instead of rebuilding them each time.

The Business plan, listed at $160 per month, adds advanced brand controls. These matter when several people produce templates and typefaces, colors and spacing must stay consistent across all of them. A solo designer will usually find Professional enough. A team that hands campaigns to marketers is where the brand controls justify the higher price.

The limits are real. Six exports per month is tight for regular client work, so the Starter plan suits evaluation better than production. The second limit is conceptual: a visual canvas makes it easy to build a layout that looks right while you edit and still needs checking in real clients. The vendor lists a 15-day free trial, which is enough to build one complete template, export it and run it through the render checks later in this guide. What each plan includes is listed on the Beefree pricing page.

Stripo: A Free Start and a Plugin Route

Stripo has a free editor plan with no time limit, which makes it a reasonable place for a designer to learn the medium before paying for it. The editor plans step up as output grows: Basic at $20 per month, Medium at $45 per month and Pro at $125 per month. Stripo also lists plugin tiers: Plugin Free at $0, Plugin Startup at $100 per month, Plugin Business at $550 per month, and Plugin Enterprise on request.

The strength is the ladder itself. You can start free, learn on real work and move up when the output justifies the cost. If you already work inside a design environment where a plugin fits better than a separate editor, read the plugin tiers alongside the editor plans before deciding.

The main limit is the jump between tiers. Going from Medium at $45 to Pro at $125 is a large step for a freelancer, so estimate your monthly output before you commit. The pricing page lists what each plan includes, and plan names alone do not show which controls you pay for. Details are on the Stripo pricing page and the Stripo plugin page.

MJML: When the Template Should Live in Code

MJML is code-first. You write the template in its own markup, compile it to HTML and send the built output. It is self-hosted, so you run the build yourself. Pricing is on request, which means the real cost is setup time: getting the build running, keeping it working and maintaining the markup skills it needs.

For designers the appeal is control and history. A template in code sits in a repository beside the rest of your work, gets reviewed like any other file and builds the same way every time. That suits a designer who already works with developers, or a studio that wants every campaign to come from one source.

The limit is that there is no canvas for people who do not write code. If marketers will send campaigns, give them a build step they can run, or agree that the designer owns the structure while others fill in content. The MJML pricing page sets out the terms, which are worth reading before you plan a rollout.

Make: Sending Emails When Something Happens

Make does not design templates. It connects apps and can trigger an email when something happens, such as a portfolio inquiry arriving through a form or a client approving a proposal. For a designer, it is the piece that turns a finished template into a message that goes out on its own.

The free plan includes 1,000 credits per month with no time limit. It allows 2 active scenarios, runs a scenario no more often than every 15 minutes, caps each run at 5 minutes and keeps execution logs for 7 days. Core, listed at $10.59 per month or $9 per month billed annually, covers 10,000 credits and removes the active-scenario cap. Pro, listed at $18.82 per month or $16 billed annually, adds priority execution, custom variables and full-text log search. Teams, listed at $34.12 per month or $29 billed annually, adds team roles and shared scenario templates. Enterprise is priced on request.

Credits are the detail people miss. Each module action in a scenario uses one credit, so a scenario with three steps uses three credits every time it runs. Count the steps before you estimate cost. The Make pricing page lets you choose a credit allowance on a slider, and the card prices shown are for 10,000 credits per month.

What It Costs at Three Output Levels

Design tools are priced by plan or workspace rather than by subscriber, so the useful comparison is against output. Builders are measured in designs and exports; automation is measured in runs and credits. The table uses those units. Each figure is the price listed for that plan, and annual totals are the monthly figure multiplied by twelve.

Output levelPlanListed priceWhat the plan covers
Learning, fewer than 10 designsBeefree Starter$0Up to 10 designs and 6 exports per month
Learning, no budgetStripo Free$0Free editor plan with no time limit
Regular client work, one designerBeefree Professional$30 per monthUnlimited project folders and reusable content blocks
Growing output on a visual builderStripo Basic$20 per monthBasic editor plan on the Stripo ladder
Weekly templates with heavier editingStripo Medium$45 per monthMedium editor plan on the Stripo ladder
Team that needs shared brand rulesBeefree Business$160 per monthAdvanced brand controls
100 form submissions a month, 3-step scenario (300 credits)Make Free$0Within 1,000 credits; up to 2 active scenarios
1,000 form submissions a month, 3-step scenario (3,000 credits)Make Core, billed annually$9 per month ($108 a year: 12 × $9)Within the 10,000 credits per month allowance
3,000 form submissions a month, 3-step scenario (9,000 credits)Make Core, billed annually$9 per month ($108 a year: 12 × $9)Close to the 10,000 credit limit, so little headroom remains
4,000 form submissions a month, 3-step scenario (12,000 credits)Make above 10,000 creditsPricing on requestThe allowance is chosen on the Make pricing page

A common pairing is a builder with an automation service. A designer on Beefree Professional who also wants portfolio inquiries to trigger a confirmation email pays $30 a month for the builder. Adding Make Core on annual billing brings the total to $39 a month, or $468 a year (12 × $39). Because a scenario with more steps uses more credits, recalculate with your own step count before you commit to a plan.

Copyable Templates for Four Common Designer Emails

Each template below is plain text you can paste into a text block in a builder or into an HTML module. Square brackets mark fields to replace. Keep the subject line short, let the first line give the reason for the email, and keep everything in a single column so it reads well on a phone.

Portfolio inquiry reply

Send this within a day of a new inquiry. It sets expectations and avoids a second round of questions.

Subject: Thanks for reaching out about [project type]

Hi [First name],

Thanks for getting in touch. I have read your note about [project brief in a few words], and it sounds like a good fit for how I work on [type of work].

Here is what happens next:
1. I reply within [two working days] with a few questions about scope, timing and budget.
2. If the project is a fit, I send a short proposal with a fixed fee for the first stage.
3. We agree a start date once the proposal is signed.

The work closest to your brief is here: [portfolio link].

Best,
[Your name]
[Studio name]

Proposal cover email

Use this when the proposal is attached. The two checkpoints at the bottom prevent most disputes about scope and payment before they start.

Subject: Proposal for [project name], [stage] stage

Hi [First name],

The proposal for [project name] is attached. It covers [deliverables in one line], with a fixed fee of [amount] for this stage and an estimated delivery window of [date range].

Two points to check before you sign:
- One round of consolidated feedback is included. Further rounds are billed at [rate].
- Final files are released once the invoice for this stage is paid.

Reply with any changes and I will update the proposal within one working day.

[Your name]

Deliverable review request

Send this with the link to a template or design that is ready for feedback. Asking for a single consolidated list keeps revisions manageable.

Subject: Ready for review: [deliverable name]

Hi [First name],

The [deliverable] is ready for review. Please open the link below on a desktop and on a phone, and look at the layout with images turned off.

[Review link]

Send one consolidated list of changes by [date], marked by priority: must change, should change, or optional. Once the list is in, I will issue the next version within [number] working days.

Thanks,
[Your name]

Studio update to existing clients

A short, single-column update keeps a client list warm between projects. The closing line asks a question, which gives the reader a reason to reply.

Subject: What we shipped this quarter

Hi [First name],

Three projects went live this quarter. The most useful one for your team is [project name], a [short description] that [result in plain words].

Next quarter we are opening two slots for [type of work]. If your roadmap has anything in that area, reply to this email and I will send availability.

[Your name]
[Studio name]

Build the Template in a Builder

Start with a one-page token sheet. List your type scale, your spacing values, your color palette with a dark-mode variant for each color, and the rule for when each button style is used. Keep it short enough to read in a minute, because a sheet nobody opens does nothing for consistency.

Next, build a single-column base template that reads well at 320 pixels wide. Then add the modules you reuse most: a header with the logo, a footer with the legal and unsubscribe lines, a text call-to-action button and a content block. Name each module the way you would name a component in a design file, so that anyone on the team can find it.

Finally, write down what must not change. Typefaces, logo clearance, button shape and minimum text size are the usual candidates. A visible list of these limits answers most questions before they come up, and it gives a marketer clear room to work inside the brand.

Rendering Constraints That Shape the Design

Email does not render like a web page, and most of its constraints follow from that. Many clients ignore parts of the stylesheet, so layouts are usually built with tables and inline styles. Web fonts load in some clients and fail silently in others, so every typeface needs a fallback stack that still looks deliberate in system fonts. Images are often blocked by default, which means the message has to survive without them: the headline should be live text, and the main call to action should be a text button rather than a graphic.

Dark mode adds another layer. Some clients invert colors automatically, which can turn a transparent logo into a dark shape on a dark background or make pale text disappear. The defence is to declare colors deliberately and to check the logo and key text in both modes before the layout is final. The dark mode email templates guide covers the patterns in more depth, and the HTML email coding tips explain the markup choices behind them.

Render Checks Before Anything Goes Live

Build the checks into the project plan. Start with a phone-first pass: read the email on a phone, note what sits above the fold, and confirm the call to action is reachable and the layout stacks in a sensible order. Then run an images-off pass and a dark-mode pass. Finally, open the template in a webmail client and look for spacing that collapses or styles that were stripped.

Keep a short written record of what you checked and what you changed. Across several projects it becomes a personal QA log, and it shows a client or colleague how the template was checked before it was sent. Each check takes minutes. Skipping them is the most common reason a well-designed template looks broken once it reaches a real inbox.

Accessibility Decisions to Make Early

Accessibility is mostly a set of decisions made at the start. Give every meaningful image descriptive alt text. Keep body text dark enough to hold contrast on both light and dark backgrounds. Use a live-text button for the main action so the label is always readable. Do not rely on color alone to signal status: add an icon or a word beside any colored cue. Set the reading order to follow the layout, so a screen reader reaches the headline first.

None of these decisions is expensive at the start. They are expensive to retrofit, because a finished layout often has to be rebuilt around a headline that was never live text.

Which Tool to Pick: A Decision Guide

The table matches common needs to a starting point and the reason for it. Treat it as a shortlist. Your own clients and output volume should make the final decision.

If you needPickBecause
Reusable blocks across many client projectsBeefree ProfessionalUnlimited project folders and reusable content blocks, listed at $30 per month
No budget while you learn the mediumBeefree Starter or Stripo FreeBoth have free tiers; Starter is limited to 10 designs and 6 exports per month
Templates kept in version controlMJMLIt is self-hosted, so the template source can live in your own repository
Brand rules enforced across a teamBeefree BusinessAdvanced brand controls, listed at $160 per month
Sends triggered by a form or an orderMake, alongside a builderIt connects apps and sends on events, with 1,000 free credits per month to start
A free start that can grow with outputStripoA free editor plan with no time limit, then Basic, Medium and Pro as volume rises

Setup Checklist for Your First Template Project

The checklist covers the steps most often skipped when a finished design becomes a template someone else can send. Work through it in order on the first project, and it will become routine by the second.

StepDone whenCommon miss
Export the template to HTML and open the fileThe HTML is readable and the styles are inlineTreating the builder canvas as the final output
Confirm the fallback typeface stackHeadings and body still read well in system fontsDesigning only for the web font you chose
Check the images-off viewThe headline, offer and button all survive without imagesPutting the call to action inside an image
Check the dark-mode viewLogo, text and buttons keep their contrastLeaving a logo on a transparent background
Save header, footer and button as reusable modulesA new campaign can be built from modules aloneCopying the same block by hand into each project

How to Choose

Start with your output. If you produce a few designs a month for different clients, Beefree Professional at $30 per month gives you the folder structure and reusable blocks you need. If you are still learning the medium, the free tiers of Beefree Starter or Stripo are enough to build and check your first templates. If you already work in code and want templates under version control, MJML is the natural choice, provided someone on the team can maintain the build.

Then decide whether automation matters. A template that goes out only when you press send does not need Make. A template that should go out when a form is submitted or an order is placed does. Make's free plan is enough to test one scenario before you pay for more credits.

Finally, pick the tool your marketers can actually use. A strong template that only you can send becomes a bottleneck within a few campaigns. Choose the option that lets the people who send the emails work inside the system you built.

Related reading: the email template design guide, the mobile-first email design article and the responsive email templates guide. For developers building the same templates in code, see email templates for developers. To browse ready-made layouts, visit the template library, or return to the use cases overview.

Frequently Asked Questions

Which tool should a freelance designer start with?

Beefree is the most direct starting point. Its Professional plan, listed at $30 per month, adds unlimited project folders and reusable content blocks. Begin on the free Starter plan to learn the editor, and move up once you regularly need more than 6 exports a month.

Is there a free option that works for client work?

Free options suit learning and small volumes. Beefree Starter is capped at 10 designs and 6 exports per month. Stripo's free editor plan has no time limit but is a starting tier. For regular client work, plan on a paid plan from the start so that export limits do not interrupt a project.

Can a designer keep email templates in version control?

Yes, with MJML. It is self-hosted, so the template source can live in a repository and be built the same way each time. The trade-off is that people without code need a build step to send campaigns, so agree that handover before you start.

How much does automation add to the cost?

On Make's Core plan billed annually, the listed price is $9 per month for 10,000 credits, which is $108 a year. Each module action in a scenario uses one credit, so count your steps to estimate how many credits a scenario needs. The free plan includes 1,000 credits per month and allows 2 active scenarios.

Do I need to write HTML to use these tools?

Not for the visual builders. Beefree and Stripo are used through an editor. Reading the exported HTML is still worth learning, because it shows what the tool produced and helps you spot problems. MJML is the option that requires writing markup.

What should I check before a designed template goes live?

Check the phone view, the images-off view, the dark-mode view and a webmail view. Confirm that the headline and main button still work without images, that the logo keeps its contrast in dark mode, and that every typeface has a fallback that looks intentional. Keep a short written record of these checks for each project.