Write an Email Platform Brief Before Comparing Plans: List the Emails You Actually Send, Then Judge Every Tool Against That

A feature list describes software; your brief describes your business

Comparing features is how people get stuck for weeks. This one has more automations. That one has better templates. Another has a scoring tool.

A feature list tells you what software can do in general. It doesn't tell you whether you can do your real jobs in it, and keep doing them on a busy evening.

What most small brands need is modest: a few emails that go out at the right moment, to the right people, with the right facts.

So start with your own work, not with platforms.

List the emails that genuinely matter right now

On a fresh page, list every email the business sends or should send. For Bramble & Bee:

• A welcome email, with the promised "guide to choosing a honey"
• A harvest email, when new honey is ready, twice a year
• A care note after purchase: crystallised honey is normal, and how to soften it
• An occasional update about the bees, three or four times a year

For each one, write:

• What triggers it: a signup, a purchase, a harvest
• What must be in it: the guide, the honey varieties and prices, the care instructions
• What should stop it: an unsubscribe, a purchase, an open problem

Add one more column: what goes wrong if this email fails?

If the harvest email goes out with the wrong price, people are annoyed. If it goes out to people who unsubscribed, that's a much bigger problem. If the care note doesn't send, people email worried that their honey has "gone off".

Writing the failure down tells you which emails really matter, and what you must test before trusting any platform with them.

Some emails aren't this platform's job

Order confirmations and dispatch updates often come from your shop software, not your email tool. Write them down anyway, so you don't compare email platforms against a job they'll never do.

The signup promise is your first real requirement

Bramble & Bee's signup form says: "Get our short guide to choosing a honey, and be first to hear when each harvest is ready."

That's two requirements, straight away:

• An email that sends automatically the moment someone signs up, with the guide
• A way to send the harvest email to everyone, quickly, when the jars are ready

Write the form's promise word for word in your brief. If the form and the current welcome email disagree, fix that first. No new platform can fix a mismatch you carry into it.

Keep the subscriber record small, because data you don't use is work you don't need

Many platforms can store a great deal about each subscriber.

You only need what your emails depend on. For Bramble & Bee:

• Email address
• Where they signed up: website, market stall or farm shop
• Whether they've bought before
• Whether they want harvest emails only, or the bee updates too

That's it. Extra data is extra work and extra responsibility. Keep the record honest, and remember that buying a jar isn't automatic permission to send marketing emails.

Give each email one source of truth for its facts

Each email should take its facts from one clear place:

• The harvest email takes honey names, prices and jar sizes from the shop's product records
• The welcome email takes its promise from the signup form
• The care note takes its instructions from the label on the jar

If the same fact lives in two places, and someone updates one, an old price ends up in an email nobody remembered.

Write the source beside each email in the brief. Then whoever changes a price knows exactly which emails to check.

Test one complete route before you trust any platform with your list

This is the step most people skip.

Before committing, run a real test on the platform, using an address you control:

• Sign up through the real form
• Check the welcome email arrives, and the guide link works
• Change the guide link as if you'd updated it
• Pause the welcome email, then switch it back on
• Change the test subscriber's preferences to "harvest emails only"
• Unsubscribe

Help pages tell you what a platform says it does. A test shows what it actually does.

Test the things that should not happen

The quiet tests often matter most:

• Sign up twice. Does the welcome email arrive twice?
• Choose "harvest emails only". Does a bee update still arrive?
• Unsubscribe. Do emails really stop?

When Fionn tested their current tool, the second check failed. The preference page existed, but the bee updates were going to everyone regardless. That's a real requirement the brief now names.

Price your real quiet month and your real busy month

Only now are you ready for pricing tables.

Write down your real pattern first:

• Contacts now, and a sensible estimate for a year's time
• How often you send, and when the bursts come
• What you need included: automations, signup forms, a shop connection
• Your currency, and whether tax is added to the shown price

Bramble & Bee sends very little most months, then two or three emails in a harvest week. Some plans charge by contacts, others by emails sent. Either can catch you out, so price each shortlisted platform against two scenarios, a quiet month and a harvest month, using identical numbers.

Keep introductory prices separate from regular ones. A cheap first year and an expensive second year are very different things.

Count the costs that never appear on a pricing table

The monthly price is only part of the cost. Note these, in rough hours:

• Rebuilding signup forms on the website
• Importing the list and checking permissions came across correctly
• Setting up your sending domain so emails don't land in spam
• Rebuilding templates, which usually don't transfer
• Learning your way around

A platform that's slightly cheaper per month can cost more overall if it takes a weekend to set up and an hour every time you change something.

Deliverability belongs in the brief, even if the word puts you off

"Deliverability" means whether your emails actually reach the inbox. For a small brand, it mostly comes down to basics, which your brief can check:

• Can you send from your own domain, with clear instructions for setting it up?
• Does it handle bounces and unsubscribes automatically?
• Does it warn you about signs of trouble, like a rise in spam complaints?

The cheapest plan isn't a bargain if your harvest email lands in spam the week the honey is ready.

Choose for the person who'll maintain it on a busy evening

For Bramble & Bee, that's Gráinne, after a day with the hives, trying to send the harvest email before the jars sell out at the farm shop.

So the brief has a maintainer column. Who writes the emails? Who tests the links? Who untangles a duplicate send? Who answers replies?

If you only send a few kinds of email, a simple tool you fully understand beats a powerful one you're nervous to touch.

If someone else ever helps, check that they can have their own login rather than sharing a password.

Check how you'd leave before agreeing to join

Ask, for each platform:

• Can you download your list, with signup sources and permission records?
• Does "export" include your templates and automation rules, or just addresses?
• What are the cancellation terms?
• What support exists if something goes wrong?

Whether a change of plan is easy or painful is part of what you're buying.

Send the platform's support team your brief's questions

Support pages answer common questions. Your brief raises specific ones. Asking before you sign up tells you two things: the answer, and how helpful the support actually is.

Bramble & Bee's questions:

• "Can subscribers choose harvest emails only, and is that respected for every campaign?"
• "When I export, do signup sources and consent records come with the contacts?"
• "How do you count contacts, including unsubscribed ones?"
• "Can my business partner have her own login?"

Keep the answers, dated, in the brief. A vague reply, or none, is useful information too.

Turn the must-have emails into a small test grid

The brief lists what you need. A test grid shows whether a platform actually does it.

Run the grid with test addresses on your current tool first, then on any platform you're considering. A platform that passes your grid is a real candidate. One that only passes its own demo isn't.

If the brief points to a move, count the moving work honestly

Moving platforms is rarely just "export, import, done". Typical work includes:

• Exporting contacts with signup sources and permission records
• Checking unsubscribed people stay unsubscribed after the import
• Rebuilding signup forms on the website and at the farm shop
• Rebuilding the welcome email and care note
• Setting up your sending domain on the new platform
• Reconnecting the shop, so purchases are recognised
• Sending a small, low-risk email before anything important

Plan it for a quiet period, never just before a harvest. Give it weeks, and keep the old account open until nothing depends on it.

Score your current platform against the brief before shopping

Go down the required column and ask whether your current tool already does it.

Bramble & Bee's current tool passed almost everything: signup automation, the harvest email, the care note, a working unsubscribe. It failed one requirement, preferences being respected, and that turned out to be a setting they hadn't switched on.

They didn't switch platforms. They fixed the setting, tested it again, and saved themselves weeks of moving.

If your current tool passes the required column, your problem probably isn't the platform. If it fails one or two requirements, you know exactly what any new platform must do better.

Check how your emails look on a phone in each platform

Most of your subscribers read on phones. A platform's templates can look beautiful in the editor and cramped on a small screen.

During any trial, send yourself the harvest email built in that platform, and open it on your phone. Check that the honey names and prices are readable without zooming, the buttons are easy to tap, and the email still makes sense with images turned off.

Bramble & Bee's harvest email depends on one photo of the jars. With images off, one trial platform showed nothing but a blank box and a button. That's a template to fix before choosing, not after.

Make sure the business owns the account, the list and the sending domain

It's easy to set up an email account in one person's name, on a personal email address. Years later, that becomes a problem if that person leaves, or forgets the password.

Put in your brief: the account belongs to the business email address, both owners can log in, and the sending domain is one the business controls. Check each platform lets you do that before signing up.

Don't choose a platform for an imagined future business

It's tempting to pick a platform for ten thousand subscribers and daily sends. You'll pay for that future every month, and maintain its complexity every week, long before it arrives.

Choose for the business you have now, with sensible room for the next year or so, and check your data can be moved later. If you outgrow it, moving becomes a planned step rather than a trap.

Sort everything into three columns, and let only the first decide

• Required: what your real emails depend on
• Useful later: things you might want one day
• Not needed now: everything else, however impressive

Bramble & Bee's brief:

Compare platforms against the first column only. A feature in "useful later" shouldn't win today's decision.

When the brief says stay, that's a result too

It can feel like an hour wasted if the brief ends with "keep what we have". It isn't.

Bramble & Bee now know exactly what their emails need, which setting was missing, and what they'd look for if they ever moved. When a cheaper platform's advert arrives next spring, they can check it against the brief in ten minutes instead of an evening.

Keep the brief and revisit it when the business changes

The brief isn't finished once you've decided. Keep it with the date, and look at it again when:

• You add a new kind of email, like a harvest waiting list
• Your list grows past a pricing tier
• You start selling somewhere new, like a second market
• A test from your grid starts failing

Each time, update the three columns and rerun the grid. The decision stays grounded in what you actually send.

Your next step this week

Write your own three-column list before opening a single pricing page.

List the emails you genuinely send, with what triggers each, what must be in it and what should stop it.

Then run one complete test on your current tool: sign up, change preferences and unsubscribe, and check what should and shouldn't arrive.

That test will tell you more than any pricing page. And if you do compare platforms, your brief will keep the comparison honest.

Keep going

Software / Practical guide

Page Builder or Clearer Plan? How to Tell Whether Your Product Page Needs New Software or a Better Brief

When a product page feels wrong, a page builder looks like the obvious fix. Often the real problem is a missing measurement, a weak photo or an unclear option, and no layout tool can supply those. Write the job down as a task, try it with what you already have, and test any builder on a real page, including the sixth small edit, before you pay.

Software / Practical guide

Email Software for Seasonal Senders: Choose for the Year You Actually Have, Not an Average Month That Never Happens

If your shop is quiet for months and then sends several emails a week in its busy season, an "average monthly" figure will mislead you about every pricing page you read. Describe your real sending year, total each tool's cost across twelve months, test a realistic burst, and you'll often find the best answer is to stay where you are.