Email Marketing for Small Business: Complete Guide
What to do when there is no team: the minimum viable programme, and the four things that are worth paying for anyway.
On this page
The short version
- Four flows cover most of the value available to a small list, and three of them are written once and then run unattended.
- The constraint is production time, not budget. Design the programme around what one person can sustain in an hour a week.
- Pay for deliverability and templates. Do not pay for automation complexity you have no volume to justify.
Advice written for teams assumes a division of labour that does not exist when the person writing the email is also the person answering the phone. The result is programmes designed to be impressive rather than survivable, abandoned within a quarter.
A one-person email programme has one real constraint: sustained attention. Everything below is chosen for how little of that it consumes after setup.
The four flows, in build order
Build them in this order because each one earns its place before the next is worth the effort. Three of the four run without you once written, which is the whole point.
What to build
The welcome sequence — three emails
Delivers whatever was promised, says who you are, and sets the expectation for what comes next. This is the highest-read email you will ever send and it runs forever once written.
Three emails over about a week is enough. Longer sequences are for programmes with a long sales cycle and someone to maintain them.
One regular send you can actually hold
Monthly is a real cadence. Weekly is a real cadence if you have material. Fortnightly is usually the honest answer for a business run by one person, and a fortnightly send kept for two years beats a weekly send abandoned after eight.
A post-purchase or post-enquiry sequence
Two or three messages that confirm, set expectations and ask for the thing you want — a review, a referral, a repeat visit. Triggered, so it never needs your attention again.
A win-back, running quarterly
One message to people who have gone quiet, sent on a schedule, with removal at the end. It protects deliverability and takes an hour to build.
Where to spend and where not to
With limited budget the split is unusually clear-cut.
Worth paying for
- A template that renders correctly everywhere, built once
- Email verification at the point of capture
- A provider with genuinely good deliverability
- An hour of someone competent setting up authentication
Not yet
- Branching automation you have no volume to test
- Dynamic content platforms above your ESP's built-in merge
- Separate analytics tooling before you have a revenue line
- A second sending domain
The hour a week
Assume one hour, once a week, and design backwards from that. In practice: three weeks of the month are writing and scheduling the regular send in stages, and the fourth is a short review — what went out, what happened, what needs fixing.
The reason to formalise this is that email is the first thing that gets dropped when the week goes wrong, and a programme with no fixed slot has no defence. A calendar entry is a weak protection but it is much better than intention.
What to measure when you have no analyst
Two numbers, checked monthly, are enough. The first is replies — actual human responses to your sends. For a small business this is a better health signal than any rate, because it is uncontaminated by machine opens and it correlates with the thing you want, which is people who consider you worth talking to.
The second is whatever your commercial outcome is: bookings, orders, enquiries, walk-ins with a mention. You will not be able to attribute it cleanly, and that is acceptable at this size. A rough monthly figure that everyone agrees is roughly right beats a precise figure nobody has time to produce.
Ignore open rate beyond noticing if it falls off a cliff, which usually means a delivery problem rather than a content one. Chasing a two-point movement in a number that is partly machine-generated is exactly the kind of work a one-person programme cannot afford.
Setup, once
- SPF, DKIM and DMARC published on your sending domain
- One template built and tested on a phone and in dark mode
- Opt-in form live with the promise written on it
- Welcome sequence written and switched on
- Reply-to goes to an address someone reads
- A recurring calendar slot for the regular send
Frequently asked questions
How many subscribers before this is worth the effort?
The welcome sequence is worth building at any size, because it is written once. The regular send starts justifying the hour somewhere in the low hundreds, though that depends far more on what a customer is worth than on the count.
Is a free plan good enough?
Usually yes at small volumes, with two things to check: whether the free tier forces branding into the footer, and whether it lets you authenticate your own domain. The second matters much more than the first.
Should I write in a personal voice or a company one?
Personal, if the business is small enough that customers know who you are. It is an advantage larger competitors cannot copy, and it makes replies far more likely — which is itself a deliverability benefit.