WordPress security maintenance with AI: A safer routine for small business sites

A digital graphic illustrating AI-powered WordPress security and maintenance against a blue gradient background. On the right, a smiling man in an olive green sweater works on a laptop. In the background, a dark WordPress dashboard features a green badge reading "Website secured" with a shield check icon. In the foreground, a floating translucent UI card displays the user prompt "Review my plugins and users..." next to his avatar, followed by an AI status reading "Reviewing..." alongside a SiteGround logo, with a white sparkle symbol floating nearby.

WordPress security maintenance is the recurring work of keeping your site’s exposure small: updating WordPress itself along with your plugins and themes, checking what’s installed, reviewing who has access to the dashboard, removing what you no longer use, and confirming your backups ran. It’s basic housekeeping, and it’s separate from the tools that guard your site, but it’s just as important.

And for small business owners who manage their own WordPress websites, it’s another nuisance to think about. Our 2026 report on AI in WordPress for small businesses found that 67% of small business owners run their site entirely themselves, with no agency or freelancer behind them, and 28.9% named security and updates among the things they find hardest. What many don’t know is that an AI assistant can now help with WordPress security maintenance by connecting to their site and carrying out recurring tasks through a simple chat.

Key takeaways:

  • Protection and WordPress security maintenance are two different jobs. Protection is your firewall, malware scanner, and host, running around the clock. Maintenance is updates, audits, and access reviews, and it basically depends on you.
  • Most small business owners handle WordPress security maintenance alone. 67% of small business owners manage their site entirely themselves, and 28.9% find security and updates among the hardest parts, as per SiteGround’s report.
  • A specialized AI assistant like SiteGround’s AI Agent for WordPress can help you complete WordPress security maintenance faster and more consistently. It can do things like update plugins and themes, check what’s installed, and review users and roles.
  • You shouldn’t postpone your WordPress security maintenance work for too long. It takes five hours between a flaw being made public and the first attack on it.

What WordPress security maintenance actually covers

Most writing on this subject blurs two things that need to stay apart: the tools that watch your site continuously, and the housekeeping that keeps its exposure minimal. They work at different levels (and can fail in different ways):

LayerWhat it coversWho or what does it
Security protectionFirewall, malware scanning, watching for newly announced weaknesses, login protection, server hardening, cleanup after a break-in, and the backup system itselfDedicated security plugins, your host, or a managed service.
Security maintenanceUpdates to WordPress, plugins, and themes; checking what is installed; reviewing who has access; removing what you do not use; checking settings; and doing it again next monthYou. An AI Agent can help you complete much of this faster and more consistently.
The overlapBackups. The system that takes them is protection, but confirming they ran and knowing how to restore is maintenanceYour host or backup tool provides it. You confirm it, with or without AI help.

Security protection: what your tools and host do

Protection runs whether or not you are paying attention:

  • A firewall sits in front of your site and checks incoming visitors before they reach it, turning away requests that match known attack patterns. You may see it called a WAF, short for web application firewall.
  • A malware scanner reads through your site’s files looking for malicious code, which is code an attacker has added to make your site do something you did not intend, such as redirecting your visitors to another site.
  • Vulnerability monitoring watches for public announcements that something you have installed has a newly discovered weakness. A vulnerability is a flaw in a piece of software that someone can misuse to get in.
  • Login protection blocks repeated password guessing, known as a brute-force attack, where software tries thousands of passwords until one works.
  • Server hardening is your hosting company tightening the settings on the machine your site runs on, so that even a successful attack has less room to move.

None of this is a daily task for you. It runs continuously and automatically, which is why it belongs to dedicated security plugins and your hosting provider.

Security maintenance: what stays your job

While security protection runs automatically, security maintenance is something that gets done, over and over, and it involves judgments about your particular site: which plugins you actually still need, who should be able to log in, what is safe to remove. That is why it stays with you even when you have good security tools running.

Four things can help explain why these tasks matter more than they look:

  • An update is a fix you have to install. When a plugin developer finds a security flaw, they fix it and release a new version. Until you install that version, your site is still running the flawed code, and by then the flaw is public knowledge. The fix existing does nothing for you. Installing it does.
  • Access only ever accumulates. Everyone who has ever needed to log in still can, unless somebody removes them. Most people get given the administrator role, the highest level of access in WordPress, because it is the fastest way to unblock someone. A WordPress user access audit is going through that list and asking who still needs to be on it.
  • An abandoned plugin looks exactly like a maintained one. Nothing in your dashboard turns red when a developer stops working on a plugin. It stops receiving updates and carries on running as before. The only way to find out is to look.
  • A backup you have never restored is unproven. Backups fail without announcing it. A setting changes, a disk fills up, a plugin interrupts the process, and the report still says the job completed. You find out whether the backup is any good at the moment you need it most.

None of these tasks is difficult, which is what makes them easy to put off. There’s no deadline, nothing visibly breaks, and skipping them appears to cost nothing. Except when it does.

Why postponing WordPress security maintenance is riskier than it used to be

Two things changed recently, and neither is about WordPress itself getting worse. The first is volume: Patchstack’s annual security report recorded 11,334 new weaknesses across WordPress plugins, themes, and WordPress itself in 2025, 42% more than the year before and roughly 200 a week. The second matters more: the dangerous share grew faster than the total. Highly exploitable flaws rose 113% in a single year, and more high-severity ones were found in 2025 than in the previous two years combined. The same monthly check now covers more ground, and more of what it covers is worth attacking.

Where those weaknesses live has not changed. 91% were in plugins, and siix were in WordPress itself, all low priority. This basically means WordPress plugin security is a big part of the problem.

About half of high-impact weaknesses are attacked within 24 hours of becoming public, and weighted by how heavily each one was targeted, the median gap between a flaw being announced and the first attack on it was five hours.

No maintenance routine closes a five-hour gap. Nobody checks their site every five hours, and 46% of flaws had no fix available from the developer when they were disclosed, so updating sooner would not have helped in almost half of cases either. That’s the argument for dedicated protection running underneath your routine.

What a routine does fix is the backlog. Every skipped week adds unpatched plugins, unreviewed accounts, and code you have forgotten is still there. Plugins are sometimes pulled from the WordPress directory over security problems that never get fixed, and if one of yours has been pulled, updating will never help.

The recurring WordPress security maintenance checklist

Six tasks make up a WordPress security checklist within any broader WordPress maintenance checklist. None is complicated on its own. The value comes from doing them regularly instead of when something goes wrong.

TaskWhat it preventsHow often
Update WordPress, plugins, and themesPublished weaknesses being used against you when a fix already existsWeekly, and straight away for anything under active attack
Check what is installedAbandoned or withdrawn plugins sitting on your site unnoticedMonthly
Run a WordPress user access auditOld accounts and contractors who still have full administrator accessMonthly
Delete plugins and themes you don’t useInactive code that can still be attacked and still needs patchingQuarterly
Confirm backups ranFinding out during an emergency that the backup you counted on was never being takenWeekly
Check your settingsOptions that were changed for a one-off reason and never changed backQuarterly

Deleting unused WordPress plugins and themes is the task many people skip, because switching a plugin off feels like enough. However, deactivated code still sits on your server, can still be reachable, and still needs patches that nobody is applying because you stopped thinking about it. Switching off is a pause, while deleting is the fix.

Where an AI Agent helps with WordPress security maintenance

A specialized AI assistant like SiteGround’s AI Agent for WordPress is connected directly to your site, so that instead of only answering questions, it can make actual changes in your dashboard when you ask. For instance, if you ask a chatbot like ChatGPT in another browser tab how to update your plugins, it will explain the steps. But if you ask an AI connected agent, it can actually update them for you.

What an AI Agent can help you complete

Every task in the checklist above is something you would otherwise do by clicking through the dashboard, which means it is something the AI Agent for WordPress can do on request:

  • Updating WordPress core, plugins, and themes, individually or in bulk, with approval for higher-risk changes.
  • Managing plugins and themes across their lifecycle: listing what is installed, explaining what each item appears to do, activating, deactivating, updating, or removing unwanted items after approval.
  • Pointing out plugins or themes that look inactive, redundant, outdated, abandoned, or suspicious, so the quarterly clear-out becomes a short list to review rather than a full investigation.
  • Reviewing and managing users and roles, from listing administrator accounts to creating users, updating profiles, changing roles, downgrading access, or removing accounts after approval and content reassignment.
  • Helping configure WordPress-level or compatible plugin-level security settings, such as login protection or hardening options, when those controls are available inside the site.
  • Repeating the same routine across multiple connected sites, instead of opening one dashboard after another.

Here’s an example prompt you can give to the AI Agent for WordPress:

“Run a WordPress security maintenance review: core, plugins, themes, users, roles, comments, and supported security settings; identify updates, risky or inactive items, admin accounts, and cleanup tasks; group everything by risk; then ask for approval before making changes.”

The AI Agent sorts what it finds into high, medium, and low risk, lists the plugins, themes, users, and settings it checked, then proposes a specific plan: deactivate this, delete those two, switch on these three settings, leave the rest alone.

A screenshot of the AI Agent by SiteGround interface displaying a Recommended cleanup plan for a WordPress website. The outlined plan categorizes tasks including deactivating the WordPress Beta Tester plugin, deleting inactive themes (Twenty Twenty-Four and Twenty Twenty-Three) while retaining Twenty Twenty-Five, enabling security settings like two-factor authentication, and noting an optional decision for inactive Akismet. At the bottom sits a text input box with the placeholder "Ask me anything WordPress related and I'll help."

Approve the plan and it works through it, then reports back on what it changed. Anything it was not sure about it leaves alone and asks about separately, so any genuine judgment calls come back to you.

A screenshot of the AI Agent by SiteGround chat interface following up on site cleanup tasks. At the top right, a user prompt reads "Proceed with the recommended changes." In response, the "WordPress Expert" assistant confirms that the approved recommendations have been completed—listing the deactivation of the WordPress Beta Tester plugin, deletion of Twenty Twenty-Four and Twenty Twenty-Three themes, enablement of two-factor authentication and readme file removal, and disabling of default pingbacks. The assistant then asks whether to delete Akismet or keep it installed for future anti-spam configuration. At the bottom, an input box sits with the placeholder "Ask me anything WordPress related and I'll help."

For more prompts you can reuse and adapt, read our guide on how to turn WordPress admin work into simple conversations.

What an AI Agent cannot do for WordPress security

An AI Agent doesn’t run a firewall, and it doesn’t scan your files for malware. It doesn’t watch vulnerability announcements overnight and wake up when something you have installed comes under attack. It doesn’t itself block password-guessing attempts in real time, although it may help configure a security tool that does. It doesn’t harden the server itself, although it may help adjust WordPress-level hardening settings.

The reason is structural rather than a gap somebody will close in the next version. An agent acts when you ask it to, working through the same WordPress controls you would use yourself.

A firewall works somewhere else entirely: it inspects every request arriving at your site, thousands of times a day, before WordPress even starts loading. A malware scanner reads every file on a fixed schedule. Vulnerability monitoring watches disclosure feeds around the clock and does not wait to be asked. Those jobs are continuous, automatic, and positioned underneath or in front of the layer an assistant works in.

How to run AI-assisted WordPress security updates without breaking your site

Applying WordPress security updates quickly matters, especially when an update fixes a security issue. But updating carelessly creates its own problems. An AI Agent can reduce the manual work, organize the process, and add approval steps before high-impact changes, but it cannot make live updates risk-free. A plugin, theme, or WordPress core update can still introduce a bug, conflict with another extension, break checkout, alter layouts, or trigger a compatibility issue.

The safest way to use AI is not to let it push every update blindly. It’s to use it as an operator with guardrails: inventory first, plan the work, update in controlled batches, and keep a rollback path ready.

  • Back up before you update, and know how to restore. A backup you have never tested is a hope rather than a plan. The AI Agent can help coordinate the update routine, but it is not the backup or restore system, so the restore point needs to exist before changes begin.
  • Test complicated or business-critical updates on a staging copy first. WooCommerce, payment plugins, page builders, membership plugins, booking systems, multilingual plugins, caching tools, and major theme updates can break important parts of a site. The AI Agent can help identify which updates belong in the staging-first group before anything touches the live site.
  • Use AI to plan and batch the work, not to remove judgment. Instead of updating everything at once, ask the agent to list available updates, group them by risk, and run smaller batches. If something breaks after one giant update batch, it is much harder to know what caused it.
  • Keep approval over anything with a large blast radius. Deleting plugins, removing themes, changing user roles, modifying security settings, and running bulk operations should pause for confirmation. A good AI-assisted workflow keeps the agent as an operator, not an unchecked autopilot.
  • Check the site after meaningful update batches. Visit key pages, test forms, confirm the dashboard is not showing new errors, and run through checkout if you sell online. The AI Agent can report which updates completed successfully, but it cannot replace checking the real user journeys your site depends on.
  • Know how to undo an update before you need to. For posts and pages, WordPress revisions may help. For plugin, theme, core, or database-impacting changes, your real rollback plan is usually a backup, restore point, staging copy, or dedicated rollback tool.

A recurring WordPress security routine you can actually keep

For a busy small business owner, the difference is not just how long each WordPress security maintenance task takes, but how much of the security maintenance routine can be organized, explained, and safely prepared before you have to make a decision.

CadenceWhat you doRoughly how long manuallyRoughly how long with AI
WeeklyReview WordPress core, plugin, and theme updates. Apply low-risk updates, test complicated or business-critical plugins on staging first, confirm your latest backup exists, and check key pages or flows after updating.30 to 60 minutes5 to 15 minutes, plus any staging or manual checks
MonthlyCheck installed plugins and themes against what you actually use. Review users and roles, especially administrator accounts, and remove or downgrade access that is no longer needed.45 to 90 minutes10 to 20 minutes, depending on how many items need approval
QuarterlyIdentify inactive, redundant, abandoned, or confirmed-unused plugins and themes, then delete what you no longer need. Review WordPress security settings, backup settings, and connected services. Restore a backup somewhere safe to prove it works.2 to 4 hours30 to 60 minutes, plus the time needed to test the backup restore
Continuously, not by youFirewall, malware scanning, vulnerability monitoring, login protection, and automated backups run underneath all of the above.Handled by your tools and hostStill handled by your tools and host


These estimates assume someone who doesn’t already know every plugin, setting, and maintenance screen by heart. The AI Agent shortens the dashboard work by inventorying, explaining, grouping, and carrying out approved changes, but it doesn’t remove the time needed for staging, backup restores, or checking the parts of the site your visitors actually use.

Close the follow-through gap

WordPress security maintenance rarely fails because someone decides it doesn’t matter. It fails because it’s never the most urgent thing on any given day, and because a neglected site can look perfectly fine for months. That is the follow-through gap: the space between knowing what should be done and actually doing it regularly.

AI does not replace the security layers that run all the time. Your firewall, malware scanner, vulnerability monitoring, backups, and host still handle the continuous work. But an AI Agent can make the recurring WordPress-side work much easier to keep: checking updates, reviewing plugins and themes, auditing users, spotting old admin accounts, cleaning up clutter, and preparing changes for approval.

FAQs

Can AI keep a WordPress site secure?

No. AI cannot keep a WordPress site secure on its own. It can help with WordPress security maintenance that reduces risk, such as updates, audits, and access reviews, but firewall, malware scanning, vulnerability monitoring, and login protection still require dedicated security tools and your host.

What is included in WordPress security maintenance?

WordPress security maintenance includes updating WordPress, plugins, and themes, checking which extensions are installed, completing a WordPress user access audit, deleting unused plugins and themes, confirming backups ran, and checking your settings on a recurring schedule.

Does an AI Agent replace a firewall or WordPress security plugin?

No. An AI Agent does not replace a firewall or security plugin. They do different jobs. A firewall and scanner watch your site continuously, while an AI Agent helps you complete the maintenance work that would otherwise be postponed.

Why should unused WordPress plugins and themes be removed?

Unused WordPress plugins and themes should be removed because inactive code can still be attacked and still needs patching. Plugins accounted for 91% of WordPress vulnerabilities recorded in 2025, and switching a plugin off does not remove its code from your server.

How often should WordPress plugins and themes be updated?

WordPress plugins and themes should be updated at least weekly, and WordPress security updates for anything under active attack should be applied as soon as you can safely test them. Patchstack measured a weighted median of five hours between a flaw becoming public and the first attack on it.

Can an AI Agent update WordPress plugins safely?

Yes, with conditions. An AI Agent can update WordPress plugins safely when you back up first, test complicated plugins such as WooCommerce or page builders on a staging copy, and keep approval over high-impact changes rather than letting anything run unattended.

What is a safe recurring WordPress security routine?

A safe recurring WordPress security routine follows a WordPress security checklist: check updates and backups weekly, review users and installed extensions monthly, and check settings and remove unused plugins and themes quarterly, with dedicated security tools running continuously underneath.

Teaser еmail еxamples: How to build anticipation without giving away the reveal

Teaser email on a phone screen with bold "This. Is. Big." text over a colorful sneaker graphic and a "Shop Now" button, next to a woman reacting with excitement while holding her phone.

A teaser email withholds one thing on purpose: the specific offer, product, or date. It names the category (a launch, a sale, an event) and stops there. The teaser email examples below show that same gap at work, and it’s what gets the next email in the sequence opened. Cliffhanger time.

Key takeaways:

  • A teaser email never reveals the product, date, or price. If any of those three appear, it has become the reveal, not the teaser.
  • Question-format subject lines average a 20% open rate compared to 12% for non-questions, based on a Klenty analysis of over 200,000 emails.
  • The reveal email’s open rate, not the teaser’s, is the real measure of whether a sequence worked.
  • Most teaser sequences run two emails before the reveal: an initial teaser and, optionally, a second one that narrows the gap slightly.
  • A teaser email creates a kind of debt with the reader. The reveal is where that debt gets paid off, and a reveal that underdelivers on the buildup costs more trust than a teaser that was never sent.

How the information gap makes a teaser email work

A teaser email works because it creates a small, specific gap between what a reader knows and what they want to know, and people act to close that gap. This is the same mechanic behind a film trailer or a locked door: enough is shown to signal what’s coming, but nothing that lets the audience guess the ending.

The gap has to be specific to work. “Something’s coming” alone is vague and easy to ignore. “Something’s coming for the ones who’ve been asking about faster shipping” names a category without naming the fix, and that specificity is what pulls the click. This is also why email copywriting for a teaser reads differently from copy for a standard promotional send. A promo email answers questions. A teaser email is built to raise exactly one.

Teaser email vs. pitch email vs. coming-soon email

These three get confused because they often arrive back to back in the same sequence. The distinction is what each one reveals and what it asks the reader to do.

Teaser emailPitch emailComing-soon email
GoalBuild curiosity about something unnamedConvert on a named offerAnnounce a fixed date or launch
What’s revealedCategory only: a launch, a sale, an eventFull offer: product, price, call to actionWhat’s coming and when
Typical CTANone, or a soft one like “Check back Thursday”Buy now, sign upGet notified, join the waitlist
Where it sits in the sequenceEarlyMid to late (the reveal itself)Can replace or precede the teaser stage

A coming-soon page often works alongside the coming-soon email, since both name the date without opening sales yet, while a teaser deliberately withholds the date too.

The three stages of a teaser email sequence

Most teaser sequences follow the same three-part shape, whether the brand is announcing a product, a sale, or an event. Understanding the job each stage does makes it easier to know when to add a second teaser and when one is enough.

  1. The setup email

The first email in the sequence. It names the category and nothing else. No product name, no date, no discount. Its only job is to plant a question in the reader’s head.

  1. The build (optional second teaser)

A second teaser, sent a few days after the first, narrows the gap slightly without closing it. This step is optional. Smaller launches and single-product announcements often skip straight from setup to reveal, while bigger campaigns use the build to sustain interest over a longer run-up.

  1. The reveal

The email where the product, date, or offer finally appears. This is where the earlier restraint pays off, or doesn’t. If the reveal underdelivers against what the teaser implied, the gap the sequence built up becomes a debt that goes unpaid, and the reader remembers that the next time a teaser lands in their inbox.

A teaser sequence is one form this can take, sitting alongside other structures covered in what email marketing is and how to get started.

Teaser email examples by use case

What differs between a product launch, a seasonal sale, and an event isn’t the mechanic, it’s what the audience already expects and how much urgency belongs in the mix.

Product launch teaser emails

Product launch teasers work by naming the category (a new release) without showing the product itself. Here’s what that looks like for a small brand adding a new item to its lineup:

Subject line: Get ready: we’re working on something big
Preheader: You’ll want to be the first to know
Body: Something new is on the way. We’re not ready to show you what it is, but we didn’t want you to hear about it anywhere else first.
Closing: Keep an eye on your inbox.

Why it works: a plain layout and a few lines of copy do the job, no product name, no image of the item itself. Readers are told a category (something new is coming from a brand they already know) and given nothing else to go on.

A brand with a more visual product can lean on imagery instead of copy to hold the same restraint:

Subject line: Shhh… coming soon
Preheader: We can’t say much, but we can show you a little
Body: [Short animated preview showing motion and color, no product visible]
Closing: More to come.

Why it works: a short animated preview shows motion and color without revealing the actual product. Both examples name the category (a new release) while keeping the specifics of what, and when, out of the email entirely. The information-gap mechanic in both cases is identical: signal scale or excitement, withhold identity. A coming-soon page is a natural next step once the teaser has done its job of gathering attention.

Seasonal campaign teaser emails

Seasonal teasers carry the extra challenge of naming an occasion without naming a price. Here’s how that plays out for Black Friday:

Subject line: Coming soon: our Black Friday sale
Preheader: Something’s about to get very good
Body: [Short animated graphic repeating “coming soon,” no discount or product shown]
Closing: Stay tuned.

Why it works: the email names the occasion (Black Friday) without naming a single price or product, which is the harder version of restraint for a seasonal sale, since sale emails almost always lead with the number.

The same restraint works just as well outside the Black Friday window, for any seasonal sale:

Subject line: Coming soon: our biggest sale of the season
Preheader: A preview, just for our subscribers
Body: [Preview of the sale catalog, no discounts listed yet]
Closing: Full details coming soon.

Why it works: a preview of the sale catalog without revealing specific discounts lets shoppers get a sense of what’s coming without giving them enough to decide whether to buy before the sale actually opens.

Seasonal teasers carry one extra pressure that product launches don’t: the calendar. A generic teaser works for a product launch whenever it’s ready. A Black Friday teaser has one shot, sent roughly a week ahead of the sale itself, since sending it too early lets the anticipation fade and sending it too late doesn’t leave enough runway to build it. This is also where seasonal campaigns benefit from a companion piece like a Black Friday ecommerce plan that maps the teaser against the rest of the sale calendar.

Event announcement teaser emails

Event teasers work a little differently, since the audience already expects a fixed date rather than a surprise. Here’s how a small business announcing a workshop or webinar could approach it:

Subject line: We’re planning something for the people who’ve been asking about [topic]
Preheader: Mark the date, details coming soon
Body: You’ve been asking about [topic] for a while, so we’re putting something together. No agenda or sign-up yet, just save the date: [date].
Closing: The full details land in your inbox next week.

Why it works: it holds a date without naming the speaker, agenda, or registration link. The reveal email that follows is where the agenda and signup link actually appear.

The gap here is narrower by design, since an event teaser can’t withhold the date the way a product teaser withholds the product, but it can withhold everything else: who’s speaking, what’s covered, and what the reader walks away with. That’s enough to justify a second email before the full event reminder email goes out closer to the date.

How to write a teaser email subject line that doesn’t give everything away

The subject line carries almost the entire weight of a teaser email, since the body rarely has more than a line or two of copy to work with. A few patterns show up across the examples above:

  • Name the category, not the contents. “Something big” or “get ready” signal scale without specifying what.
  • Ask a question instead of making a statement. Questions create the same gap in the subject line that the email body creates as a whole. Question-format subject lines average a 20% open rate against 12% for non-questions, according to a Klenty study of over 200,000 emails. The study looked at cold outreach rather than teaser campaigns specifically, but the same curiosity mechanism applies: a question creates a gap the reader wants closed.
  • Use lowercase, conversational phrasing over ALL CAPS urgency. “SHHH… COMING SOON” works because it’s an exception, not the norm. Overusing all-caps urgency in every teaser trains readers to skim past it. Urgency language does lift open rates by roughly 22% on average, according to Zippia’s subject-line research, but that effect is strongest on the reveal email, not the teaser, since urgency and curiosity pull a reader in different directions. 

Preview text (the line that shows next to the subject line in most inboxes) should extend the gap, not close it. A one-line continuation like “you’ll want to see this before Friday” adds a soft deadline without naming anything. 

Teaser email subject line templates you can copy

These fill-in-the-blank templates apply the patterns above:

  • Product launch: “Get ready: we’re working on [category]”
  • Product launch, question format: “Guess what’s coming to [brand or shop name]?”
  • Seasonal sale: “Coming soon: our [occasion] sale”
  • Seasonal sale, second teaser: “Not [current category], but you’ll still want it”
  • Event announcement: “We’re planning something for the people who’ve been asking about [topic]”

Each template names a category (a launch, a sale, an event, a topic) and stops there, which is the one rule every subject line above shares.

How many teaser emails to send (and how to space them)

How many teaser emails a sequence needs, and how far apart to send them, depends on the size of the campaign:

Campaign typeTeasers before the revealSpacing
Single-product launch1 (just the setup email)Reveal follows a few days to a week later
Bigger campaign (multi-category sale, multi-day event)2 (setup, then a second teaser)Second teaser 2–3 days after the first; reveal a few days to a week after that
Black Friday1 teaser, plus the sale’s own 3-email cadenceTeaser about a week before the sale; main promotion on sale day; last-chance reminder before it closes

SiteGround Email Marketing lets you schedule each campaign in the sequence for its specific send date in advance, so the setup email, the optional second teaser, and the reveal all go out on the days you plan for without needing to trigger each one manually on the day.

Diagram of an automated email flow, showing a trigger event followed by a sequence of timed emails sent automatically to new subscribers.

Mapping the right cadence in advance also matters for seasonal marketing campaigns, where the send dates are fixed by the calendar rather than flexible.

Common teaser email mistakes that break the payoff

Most teaser emails fail in one of three ways, all variations on the same problem: the gap and the payoff stop matching.

  • Revealing too much, too soon. If a reader can screenshot the teaser and correctly guess the product, the date, or the price, the email has already done the reveal’s job for free, and the actual reveal email has nothing left to deliver.
  • Sending too many teasers. A third or fourth teaser before the reveal usually reads as stalling rather than building anticipation, and open rates on later teasers in an overlong sequence tend to drop as readers lose patience.
  • The reveal underdelivers on the buildup. This is the costliest mistake, since it isn’t just one weak email, it changes how the reader treats every future teaser from the same sender. A teaser creates a kind of debt with the reader: it promises something worth the wait, and the reveal is where that debt gets paid. A modest reveal after a big buildup reads as a letdown even if the offer itself is reasonable on its own terms.

These same principles show up across other campaign types too, not just teasers; see 15 successful email marketing campaign examples for how buildup and payoff play out in welcome sequences, cross-sells, and other campaign formats.

A full teaser sequence, step by step

Here’s how a small ecommerce shop expanding into a new product category, say, a candle brand adding a home fragrance line, could map the same information-gap mechanic into a complete sequence, from first email to reveal:

  1. Send the first teaser 5 to 7 days out. Name the category only, a new product line, nothing about what it is or does. This is the “get ready” stage.
  2. Send a second teaser 2 to 3 days later (optional). Narrow the gap slightly, perhaps a hint at the category the new product belongs in (for the shop, something like “not candles, but you’ll still want to light it”), still nothing specific enough for a reader to guess it.
  3. Send the reveal 2 to 3 days after the last teaser. This is where the product, price, and purchase link appear for the first time. Waiting much longer than this risks losing the momentum the teasers built.
  4. Compare the reveal’s open rate against the teaser’s. If the teaser opened well but the reveal didn’t lift above a normal send to the same list, the gap was either too vague to build real curiosity or held open for too long.
SiteGround graphic showing a four-step teaser email timeline: setup teaser on day 1, optional second teaser on days 5-7, reveal on days 8-10, and a comparison of open rates between reveal and teaser emails.

The same four-step shape applies just as well to a seasonal sale or an event announcement, since the only thing that changes between categories is what gets revealed at the end, not the structure that gets you there. A holiday email marketing guide can help map this same sequence onto a specific date on the calendar, like Black Friday or a year-end sale.

Build your teaser email sequence with SiteGround Email Marketing

Every example above depends on timing: the teaser has to go out early enough to build curiosity and the reveal has to land while that curiosity is still fresh. Getting that right by hand, across a launch, a sale, or an event, means remembering exact send dates and manually triggering each email in the right order.

SiteGround Email Marketing lets you build the full sequence, from the first teaser through the reveal, and schedule every email in advance, so the cadence you plan is the cadence that actually goes out. The Generate with AI feature can draft each stage for you: describe the setup teaser in your own words to get a subject line, preheader, and body with the specifics deliberately left out, then use the Announcement or Promotional preset for the reveal once you’re ready to name the actual offer.

[58]

Frequently asked questions about teaser email campaigns

What is the purpose of a teaser?

The purpose of a teaser is to create curiosity by revealing just enough to signal that something is coming without naming what it is. A teaser’s job is to earn an open on the email that follows it, not to sell anything on its own.

What is a teaser email vs pitch email?

A teaser email withholds the offer to build curiosity, while a pitch email states the offer directly and asks for a purchase or signup. See the comparison table above for how the two differ in goal, reveal timing, and typical call to action.

What’s the difference between a teaser email and a coming-soon email?

A teaser email withholds the date along with the product or offer, while a coming-soon email typically states the date but not the specifics of what’s launching. The comparison table above breaks down where each fits in a sequence.

When should you send a teaser email before a launch?

A teaser email typically goes out five to seven days before the reveal for a single product launch, with longer campaigns sometimes adding a second teaser two to three days after the first. Waiting much longer than a week risks losing the momentum the teaser built.

How short should a teaser email be?

A teaser email should be as short as the subject line and one or two lines of body copy, since the goal is to raise a question, not answer one. Adding more copy than that risks revealing details the sequence is designed to withhold.

What are some teaser marketing campaign examples?

A product launch teaser might read “Get ready: we’re working on something big,” naming the category without the product. A seasonal teaser might say “Coming soon: our Black Friday sale,” naming the occasion without a price. An event teaser might say “We’re planning something for the people who’ve been asking about [topic],” holding back the agenda and speaker until a follow-up email. Each one names a category and stops there.

How much does it cost to build a website or web app for your business in 2026?

A digital graphic illustrating website building and development costs against a dark green grid background. In the center, a website editor preview showcases a culinary site featuring a steaming bowl of risotto garnished with herbs, where a selected white button reading "GET STARTED" sits beneath a floating text-formatting toolbar. Floating on the right are three translucent price badges with indicator arrows displaying "$6,173" with a red upward arrow, "$2,646" with a green downward arrow, and "$1,376" with a green downward arrow, anchored by a white price tag icon badge in the bottom right corner.

Search for what a website costs, and you’ll get answers ranging from nothing to $250,000, which can hardly help you. The number is that wide because the question should really be what your project costs based on the path you take to build it.

The cost to build a website in 2026 is about $200 a year on a DIY builder, $1,500 to $8,000 with a freelancer, and $6,000 to $35,000 or more at an agency. Web apps and MVPs start higher, from a few hundred dollars on no-code tools to $18,000 and up for custom development.

Key takeaways:

  • Most small businesses spend under $10,000. 61% of small business buyers spent less than $10,000 on their most recent website and 84% spent under $20,000. Professional small business website costs cluster between $3,000 and $15,000.
  • The cost to build a website or web app is set by the path, not just the project. The same brochure site can cost $200 a year on a builder or $12,000 at an agency. What changes is who does the work.
  • A web app costs more than a website because it does something. Custom web app development starts around $18,000 for an MVP, against $3,000 to $15,000 for a typical small business site.
  • AI and no-code builders are the cheapest entry. AI app builders start free, and no-code platforms now run roughly $36 to $69 per month at entry level.
  • Ongoing costs are the line most quotes leave out. Budget roughly $600 to $6,000 a year for a small business site, and 15% to 25% of the build cost annually for a web app.

What determines website and web app development cost

Many cost guides start with features: how many pages, whether you need e-commerce, how complex the design is. Those are important details, but they’re actually second-order. The variable that moves the number most is who builds it and on what.

A five-page brochure site is a five-page brochure site whether you assemble it on a template, hand it to a freelancer, or commission an agency. The work is broadly the same. But that site is about $200 a year built yourself, around $4,000 from a freelancer, and $12,000 or more from an agency. You are not buying more website at the top of that range. You are buying more of three things.

  • Time is the one people underestimate. What you don’t pay in money you pay in hours: learning the tool, writing the copy, resizing images, fixing what breaks. A DIY site isn’t free, it’s unpaid. If your hours are worth anything to the business, price them before calling the builder path cheap.
  • Judgment is knowing which decisions matter and where projects like yours usually go wrong. Someone who has built dozens of these will skip the arguments you would have had. On the DIY path, that judgment is yours to supply, which is fine when the stakes are low and expensive when they aren’t.
  • Accountability is the least visible line on any quote. It answers who fixes it when the contact form stops sending on a Tuesday. On a builder, that’s you. With a freelancer, it depends what you agreed and whether they’re free that week. With an agency on a retainer, it’s contractual.

That’s also why quotes from different paths aren’t directly comparable. A $3,000 freelancer and a $12,000 agency are often quoting different work, because content, photography, revisions, and post-launch support may be inside one number and billed separately in the other. Write down what you need first, then check each quote against the same list.

So the useful question isn’t what a website costs. It’s which path fits what your site or app has to do, and what that path costs in 2026.

How much does it cost to build a website in 2026?

It costs between roughly $16 per month and $35,000 or more to build a website in 2026, depending on the path. Most professional small business website costs land between $3,000 and $15,000. In the Clutch 2026 survey, 61% of small businesses spent under $10,000 on their most recent website. GoodFirms’ 2026 software development cost survey found 51.6% of web development agencies quoting $3,000 to $15,000 for small-scale sites.

Build pathTypical 2026 costBest forWatch for
DIY website builder (Wix, Squarespace)$16 to $50 per monthSimple brochure sites, tight budgets, fast launchLimited customization, and you build and maintain it yourself
AI website builderFree to about $50 per monthNon-technical owners who want a fast first versionOutput quality varies, and publishing or a custom domain usually needs a paid plan
Self-hosted WordPress (DIY)$100 to $500 per yearOwners comfortable with a small learning curveMore technical than a hosted builder
Freelancer$1,500 to $8,000 one-timeCustom branding without agency overheadTurnaround times and limited post-launch support
Boutique or full agency$6,000 to $35,000 and upStrategy, custom design, and ongoing supportHighest upfront cost, and scope creep adds to it

The builder prices are entry plans billed annually: Wix starts at $17 per month and Squarespace at $16 to $19, but the plan most small businesses actually need sits closer to $29 to $39 once you add selling or remove transaction fees. And the agency range is wide because it covers everything from a boutique studio’s $6,000 template build to a $35,000 custom project with strategy and content included.

AI website builders sit alongside the DIY tier rather than replacing it, and the sticker price is rarely the whole bill. Our guide to AI website builder pricing covers plans, renewals, limits, and the fees that appear when you try to publish.

How much does it cost to build a web app or MVP in 2026?

Web app development cost starts where website cost tops out. An MVP built with no-code tools can cost a few hundred dollars a year, while custom development for the same idea starts around $18,000. The cost to build a web app depends on the same build path question, with an extra tier at the top that websites do not have.

Build pathTypical 2026 costBest forWatch for
AI app builderFree to about $300 per year to startValidating an idea fast, cheapest entryA complexity ceiling you may eventually outgrow
No-code platform (Bubble, Adalo, FlutterFlow)About $430 to $2,400 per yearFounders needing more logic than a builder allowsYou rent it, expect 100 to 300 hours to learn it, and per-seat costs climb
Hybrid no-code plus custom work$1,000 to $5,000MVPs expected to scale to real usersNeeds some technical help at the edges
Agency-built MVP$5,000 to $25,000 with a productized or offshore teamFunded teams wanting a polished first versionUS agencies commonly quote $25,000 and up for the same scope
Custom development (agency or team)$18,000 to $60,000 for an MVP; $45,000 to $150,000+ for a full appGenuinely complex or large-scale softwareMost expensive by far, and typically three to six months

No-code platforms are the tier most often misquoted in older guides. Entry plans currently run roughly $36 to $69 a month, with Adalo at the lower end and Bubble at the upper, and FlutterFlow’s Basic plan at $39. FlutterFlow raised that from $30 during 2026, so check current pricing rather than trusting a figure from last year’s roundup.

Note also how wide the agency MVP band is. Productized offers and offshore teams genuinely deliver at $5,000 to $25,000, while US agency quotes for a lean MVP commonly start at $25,000 and run past $100,000. If you are scoping an MVP, our guide to building an MVP with vibe coding covers what to include and what to cut.

“MVP” has no agreed meaning, which is why the quotes vary so much. One agency’s MVP is a landing page with a signup form. Another’s is a working product with accounts, payments, and an admin panel. When quotes for the same idea come back at $8,000 and $60,000, they are usually pricing different products, not the same product at different rates. Write the feature list yourself first, in plain language, and send the identical list to everyone. The spread shrinks immediately.

Why a web app costs more than a website

A web app costs more than a website because it does something, while a website mostly shows something. That single distinction explains most of the gap between the two tables.

A website presents information: pages, images, a contact form, maybe a shop. The work is largely design and content, and once built it mostly sits there. A web app has users who log in, data belonging to each of them, rules about who can see and change what, and logic that has to be right every time. All of that needs designing, building, and testing, and testing is where the hours go. Custom web app costs also carry a longer tail than custom website costs, because logic touching real customer data has to keep working as payment providers and integrations change around it.

What increases the cost

Within any path, five things move you from the bottom of the range to the top.

  • Design originality. A template build and a custom design are different products. This is the single biggest gap between a $3,500 site and a $14,000 one.
  • Page count and feature complexity. Bookings, e-commerce, and third-party integrations push toward the top of every range, because each one is a system that has to be configured and tested.
  • Who writes the content. Writing it yourself is free and slow. Done-for-you copy and photography are often quoted separately, and they are a common reason a quote comes in higher than expected.
  • User roles, data, and logic. This is the dividing line between website pricing and web app pricing. The moment people log in and the site remembers things about them, you have crossed into the second table.
  • Ongoing costs. Hosting, security, backups, maintenance, and tool subscriptions are rarely in the headline quote, and they run for as long as the site does.

On the AI and DIY paths there is a sixth cost that does not appear on any invoice, which is your own time. AI builders produce a first version quickly, then you iterate, and the number of rounds is where the hours accumulate. Describing what you want precisely cuts that down, and our guide to writing better prompts for building is the practical version of that skill.

Which path is right for your budget

One question routes you faster than any feature checklist: how much of your revenue depends on this site or app? Not how much you like it, or how much you want it to impress people. How much money moves through it or because of it.

If the site is a low-cost small business site or an early test

Stay in the DIY and AI builder tier, free to about $50 per month. This covers a local service business that needs to be findable and credible, a portfolio, a landing page for something you are still validating, or a first version of an app idea. Paying $8,000 for a site that supports a business but does not drive it is a poor trade.

This is also where an all-in-one AI builder earns its keep on cost. For instance, SiteGround’s Coderick AI sits on this line: you describe what you want, and building, hosting, SSL, version control, and publishing come in the same plan rather than as five separate subscriptions you assemble and pay for individually.

If the site is one of several lead sources

Look at freelancers and small agencies, roughly $1,500 to $10,000. This is the tier where custom design starts paying for itself, because the site is doing real work in a real sales process and looking like everyone else’s template costs you something measurable. A freelancer at $1,500 to $8,000 gets you custom branding without agency overhead. A boutique agency from around $6,000 adds strategy and a process, which matters more as the site gets more complicated.

If the site or app is revenue-critical

Budget for an agency or custom website or web app development: $6,000 to $35,000 and up for websites, $18,000 and up for web apps. If the site is the storefront, if downtime costs money by the hour, or if the app is the product itself, the cost of getting it wrong is larger than the cost of building it properly. This is also the tier where the ongoing budget stops being optional, because software that carries revenue needs someone responsible for it.

Pro tip: Count the weeks, not just the money. A site built with an AI builder can be live in a few days. An agency project commonly runs eight to sixteen weeks, and a custom web app three to six months. If the site or app brings in customers, every month of delay is revenue you didn’t earn, and that rarely appears in any comparison. It can flip the maths entirely: a cheaper build that starts working in March may beat a better one that starts in July.

Ongoing website and web app costs to budget for

Ongoing website costs, including website maintenance costs, are the line most quotes leave out, and they are why a build that looked affordable becomes a problem in year two. Website maintenance cost covers:

  • Hosting. The largest recurring line for most sites, and the one that scales as traffic grows.
  • Domain renewal. Small and annual, and easy to forget until the site goes down.
  • SSL certificate. Usually included with hosting now, but worth confirming rather than assuming.
  • Software and plugin updates. Free if you do them yourself, billed if somebody else does.
  • Security and backups. Sometimes bundled with hosting, sometimes a separate subscription.
  • Content edits. The line that grows fastest if you cannot make changes yourself.

For a small business site, expect roughly $600 to $6,000 a year in total, with full-service maintenance plans commonly landing at $95 to $195 per month. If the site is simple and you handle updates yourself, you can run it for well under $100 a year in domain and hosting alone, but you are paying in hours instead.

Ongoing web app costs work differently and are higher. Web app maintenance costs are usually estimated as a percentage of the build rather than a flat fee, at roughly 15% to 25% of the original cost every year, because the code has to keep working as the services around it change. On a $40,000 MVP that is $6,000 to $10,000 a year, indefinitely. Add hosting, monitoring, and any AI or third-party services the app depends on. If you want to see how those separate subscriptions add up in practice, our breakdown of AI coding and hosting costs prices a full stack line by line.

Match the path to the job, not to the lowest price

The cost to build a website or web app in 2026 spans four orders of magnitude, and every number in that range is correct for somebody. What makes it useful is the question underneath it, which is what this thing has to do for your business. A site that has to be findable and credible does not need the budget of a site that has to sell. An idea you are testing does not need the budget of a product people will pay for.

Pick the cheapest path that can genuinely do the job, then add the ongoing costs before you compare quotes. The expensive mistake is rarely overspending at the start. It’s choosing a path that cannot do what you needed, and paying to build the thing twice.

If you are not sure which tier you are in, the cheapest way to find out is to build the simple version and see where it runs out. A month with a real site teaches you more about what you need than another week of comparing quotes, and it makes the next quote a better one.

[96]

FAQs

How much does it cost to build a website in 2026?

It costs anywhere from about $16 per month on a DIY builder to $35,000 or more at a full agency to build a website in 2026. Most professional small business sites land between $3,000 and $15,000, and 61% of small businesses spent under $10,000 on their last site.

Why does a web app cost more than a website?

Web app development cost is usually higher than website development cost because a web app does something rather than just shows something. Websites mostly present information, while web apps handle users, data, logic, and roles, which means more design, engineering, and testing. Custom web app MVPs typically start around $18,000.

What is the cheapest way to build a business website?

The cheapest way to build a business website is a DIY or AI builder, starting free to around $50 per month. You trade customization and hands-off support for a low price, which suits simple brochure sites and early-stage testing.

Should I use an AI builder, freelancer, agency, or developer?

You should choose based on how much of your revenue depends on the site, how much customization you need, and your website development cost ceiling. An AI or DIY builder fits simple needs and tight budgets, a freelancer suits custom branding at $1,500 to $8,000, and an agency fits complex, revenue-critical projects starting around $6,000.

How much does it cost to build an MVP before hiring developers?

MVP development cost can range from nothing to a few thousand dollars before hiring developers, depending on the build path. AI app builder costs start free to about $300 per year, no-code app builder costs run roughly $430 to $2,400 per year, and hybrid builds land around $1,000 to $5,000.

How much does custom website or web app development cost?

Custom website cost is usually lower than custom web app cost, because a web app requires more logic, data handling, user interaction, and testing. Custom websites run from around $6,000 to $35,000 and up, while custom web apps start near $18,000 for an MVP and reach $150,000 or more for a full product.

What are the ongoing costs after building a website or web app?

Ongoing website costs and ongoing web app costs include hosting, domain renewal, security, backups, updates, subscriptions, and support. Budget roughly $600 to $6,000 a year for a small business site, and 15% to 25% of the build cost annually for a web app.

Can Coderick AI reduce the cost of building a website or web app?

Yes. Coderick AI can reduce the cost of building a website or web app by combining AI building, hosting, SSL, version control, and publishing in one plan, which removes several separate setup and subscription costs that a pieced-together stack would carry.

Stripe for small business: What to know before going live, from setup to testing

Abstract of Stripe for small business

Going live with Stripe for small business means real money starts moving the moment you flip one switch, and there’s no finance team or QA department standing between you and that switch. One short list catches the problems that matter: test mode, checkout, confirmation, refunds, disputes, and tax, checked once before launch.

Key takeaways:

  • Stripe for small business comes down to one go-live checklist: test mode, checkout, confirmation, refunds, disputes, and tax.
  • Your first Stripe payout typically takes 7 to 14 days after your first live payment, so plan cash flow around the delay.
  • Test and live mode run on separate keys, so nothing touches real money until you deliberately switch.
  • Refunds don’t return Stripe’s processing fee, and disputes add their own fee, around $15 in the US, on top.
  • Stripe Tax calculates the right rate automatically at checkout and can flag when you cross a threshold, but it doesn’t handle registration or filing for you.
  • Coderick AI handles checkout and confirmation for you, but live keys, payouts, receipts, and tax are still yours to set up.

Stripe for small business: what “going live” actually means

For a small business, going live with Stripe means one person wearing hats across finance, engineering, and QA. There’s no separate team to catch a misconfigured price or a forgotten test key before a customer sees it. That’s the real risk behind Stripe for small business: the checks a bigger company spreads across three departments land on you alone, with nobody double-checking your work before the switch flips.

The same short list of things to confirm applies whether you’re selling through a payment link sent in a DM, a checkout embedded on a page you built, or a full ecommerce website, even though where you go to check some of them differs. This article walks through that list once, in the order it matters, and closes with a checklist you can work through section by section. Let’s get started.

How Stripe payment processing works

The path a payment takes from checkout to your bank account

When your customer pays, Stripe allows you to accept payments online by sitting between three parties: the customer’s bank, the card network, and your bank. Stripe authorizes the charge in real time, holds the funds in your balance, and later batches them into a payout.

Diagram of the path a payment takes to your bank account

When the money actually lands: payout timing

Important to note though: new Stripe accounts don’t get paid out immediately. According to Stripe’s payout documentation, the first payout typically arrives 7 to 14 days after your first live payment, and it can be even longer depending on industry and country. After that, most US accounts settle onto a rolling two-day schedule. But that delay matters more without a cash reserve to smooth it over, so be sure to plan around it rather than the payment date.

Stripe Checkout: for a page you control

Stripe Checkout is a hosted payment page you generate through the Stripe API: you, or an AI builder like Coderick AI generating it on your behalf, create a Checkout Session with the product, price, and currency baked in, and Stripe renders a payment page that matches your branding. 

Coderick AI, in this case, is SiteGround’s AI website and app builder: you describe what you’re selling, and it builds the site around that, including this Stripe connection. Either way, it’s genuinely Stripe’s own checkout, so Stripe’s own dashboard settings, like the receipt toggle, are the ones that apply.

Worth knowing: a full ecommerce website builder like SiteGround Ecommerce works differently. It typically runs its own checkout, with Stripe plugged in as the processor underneath, so things like order confirmations and receipts usually come from the platform’s own system instead.

Enabling Stripe via the SiteGround Ecommerce platform

Stripe Payment Links skip the website entirely. That is, you can set up a product once in the Stripe dashboard, get a reusable URL, and paste it in all the places you’re already talking to customers. Think: a DM, an invoice, an email signature, or a QR code at an event. 

There’s no code and no page to build for this, which makes Payment Links the faster option for selling one thing to people you’re already in conversation with. 

Stripe test mode vs. Stripe live mode: what actually changes when you flip the switch

Abstract image of topping on Stripe integration on an ecommerce site

How does Stripe test mode work?

Test mode is a full copy of your Stripe setup that never touches real money. Here’s what that gives you:

  • Separate test keys, clearly labeled “Test” in your dashboard, so you can’t accidentally mix them up with your live ones.
  • Test card numbers, such as 4242 4242 4242 4242, that simulate successful payments, declines, and refunds.
  • A safe place to run a full purchase, a canceled checkout, and a failed payment before you launch.

Nothing you do here shows up in your live dashboard, and nothing costs you money.

What changes the moment you switch to Stripe live mode

Switching to live mode swaps your test keys for live ones, and every charge now processes against a real card and moves real money into your balance. It also requires details test mode never asked for:

  • Your legal business name and address.
  • Your tax information.
  • A bank account for payouts.

This toggle is worth checking twice, wherever it lives in your setup, before you tell anyone the store is open.

The most common go-live mistake: forgetting to swap the key

The most common go-live mistake is leaving test keys in place after flipping the switch elsewhere. Test mode and live mode both produce a checkout that looks successful, so a customer can complete a purchase and never know no real money moved. Nobody catches it because there’s no second person checking, which is exactly the risk of building without a developer: fewer people to notice the mismatch before it costs you a launch day. Reconciling your bank account is the only way you’d find out, and by then, you’ve likely already told people you’re open.

What should happen after a customer pays through Stripe

Confirmation: what the customer should see immediately

Right after payment, the customer needs a clear thank-you page or next step, not a blank redirect to your homepage. Two things make the difference:

  • Say what happened next. “Your order is confirmed, we’ll email details shortly” is a lot more confidence-inspiring than a generic “thanks.”
  • Match the reassurance to the trust gap. A stranger clicking a Payment Link needs more of it than someone checking out on an established brand’s site.

Receipts: what the customer should receive by email

Stripe can email a receipt automatically, but it isn’t switched on by default in every setup. A few things worth knowing before launch:

  • Turn it on under Customer emails in your Stripe dashboard settings, by toggling “Successful payments” on.
  • Receipts only go out for completed payments. A failed charge never generates one.
  • With no support team to catch the gap, a missing receipt becomes a support email, so confirm the toggle before a customer asks where theirs went.

What you should see on your end

A successful payment should show up in your Stripe dashboard with the customer’s details, the amount, and the payment method attached, filed under your live data, not test data. Glance at that after your first few sales: if a payment you just took shows up in test mode instead of live mode, that’s the swapped-key mistake showing up here first, before you’d otherwise catch it reconciling your bank account.

How Stripe refunds and disputes work

How refunds work and what happens to your fees

A refund returns the customer’s money in full — but important caveat: Stripe doesn’t return its processing fee from the original charge. So on a $100 sale processed at Stripe’s standard US rate of 2.9% + $0.30, you’d keep $96.80 after the sale and still lose that $3.20 if you refund it. For a large retailer, that’s a rounding error. Alone, a handful of big refunds in a launch week can start to put a dent in the numbers you expected.

How disputes are different from refunds

A dispute isn’t a refund. It’s the customer going to their card issuer instead of you, and the issuer reversing the payment immediately, before you’ve had a chance to respond. Stripe adds a separate dispute fee, around $15 in the US, on top of the disputed amount the moment a dispute is filed, and the back-and-forth can take two to three months to resolve.

Where disputes show up, and who should respond

Disputes show up in your Stripe dashboard under Disputes, with an email notification the moment one is filed. Responding means submitting evidence: proof of delivery, a signed agreement, or a support thread showing the customer got what they paid for. Someone has to gather and submit that before Stripe’s deadline, and if you’re running a service business online solo, that someone is you.

Stripe Tax as a pre-launch setting, not an afterthought

Sales tax depends on where you have “nexus,” which is the legal term for a strong enough connection to a state that it can require you to collect its sales tax. If your business is based in a state and what you sell is taxable there, that’s enough on its own, so you likely owe tax on sales into that state from day one, regardless of revenue. 

Selling into other states is a different story: there, the connection is triggered by a sales threshold instead, commonly $100,000 over 12 months, though it varies by state, and few new businesses clear it right away.

Turning on Stripe Tax handles the mechanical part of this:

  • It calculates the right rate automatically at checkout, for any state or country where you’ve told it you’re registered.
  • It monitors your Stripe-processed sales by state and can notify you once you’ve crossed a threshold in a given location, though it’s still worth checking in yourself rather than relying on it as your only signal.
  • It applies once you’re registered; it doesn’t decide where you need to register, or handle the registration and filing itself.

Registration, filing, and the full state-by-state picture are a bigger topic than this checklist covers. SiteGround’s ecommerce sales tax guide walks through all of it. For go-live purposes, the short version holds: confirm what your home state requires before your first sale, then turn on Stripe Tax so it calculates the right amount automatically at checkout, and keep an eye on other states as your sales grow.

A Stripe go-live checklist for small business

This is the payments half of a broader website launch checklist. Work through both before you tell anyone you’re open. Each row below maps to a section above, so if anything doesn’t check out yet, you’ll find the details a few paragraphs up.

Go-live itemWhat to check
CheckoutMake sure the customer sees the right product, price, currency, and payment method.
Test modeRun test purchases, cancellations, failed payments, and refunds.
Live modeConfirm the correct live key is saved in the correct place.
ConfirmationShow a clear thank-you page or next step after payment.
ReceiptsConfirm the customer receives the right email or receipt.
RefundsKnow how refunds are issued and what happens to fees.
DisputesKnow where disputes appear and who responds.
TaxConfirm what your home state requires, and keep an eye on other states as your sales grow.
SupportDecide who answers payment questions after customers pay. If it’s just you, plan for that.

Coderick AI Stripe setup: why to use it and what to check before launch

No developer? Don’t want to spend a week picking a platform and wrestling with setup? Coderick AI just builds the site for you from a description of what you’re selling, checkout and confirmation included. It won’t set up your live keys, payout account, receipt emails, or tax registration for you, though, so check those before you launch:

  • The Coderick AI Stripe connection shows live mode, not test.
  • Your payout bank account is added and verified.
  • Your confirmation page says what happens next.
  • Receipt emails are switched on in your Stripe settings.
Example of connecting Stripe payments to a client's AI built website

Skip one, and a launch day can go by without a single real payment landing in your account, and you won’t know until you reconcile your bank. Gulp.

Flip the switch with confidence

Going live with Stripe for small business isn’t complicated once you’ve checked it off in the right order: pick how customers pay, run it in test mode, swap in live keys, sort confirmation and receipts before you tell anyone you’re open, and have a plan for refunds, disputes, and tax before the first one shows up. None of that requires a finance team. It requires going through the list once.

If you’re building the site itself rather than just connecting payments to one, start your Coderick AI payment project and get checkout, confirmation, and hosting handled together from the first prompt.

[96]

Frequently asked questions

What should a small business know before going live with Stripe?

Before going live with Stripe, confirm test mode, checkout, live-mode keys, confirmation, receipts, refunds, disputes, and tax, in that order, as one connected checklist rather than separate tasks.

What should a Stripe go-live checklist include?

A Stripe go-live checklist should cover checkout accuracy, a completed test run, the live-mode key swap, a confirmation page, working receipts, a refund process, a dispute plan, and a tax decision. The table above works as a starting point.

What is the difference between Stripe test mode and live mode?

The difference comes down to the keys: test mode uses a separate set of test keys and never touches real money, while Stripe live mode uses your live keys and processes real charges.

Do I need to test Stripe before accepting real payments?

Yes. Test mode is the only way to confirm your checkout, confirmation page, and refund flow work correctly without risking a customer’s card or your own money.

What should happen after a customer pays through Stripe?

They should see an immediate confirmation, receive a receipt by email if that setting is on, and the payment should appear in your Stripe dashboard with the amount and payment method attached.

How do Stripe refunds and disputes work?

Stripe refunds return the customer’s money but not the processing fee Stripe already charged you. Disputes work differently: the card issuer reverses the payment directly, and Stripe adds its own dispute fee on top.

Do small businesses need to think about tax before taking Stripe payments?

Yes. Sales tax in your home state can apply from your first sale, while a threshold-based obligation in other states usually doesn’t kick in until much higher revenue. Stripe Tax calculates the right rate once you’re registered and can flag when you cross a threshold elsewhere.

Is Stripe for small business a good fit before going live?

Stripe for small business is a strong fit before going live, provided you complete the pre-launch checks. Skipping the checklist, not the platform itself, is where problems tend to start.

Can Coderick AI help with Stripe setup for a small business?

Yes. Coderick AI Stripe setup wires up checkout and confirmation automatically inside your project. You still confirm your live keys, payout account, receipt emails, and tax settings yourself before launch.

What should I understand before connecting Stripe to an AI-built website or app?

The AI builder typically handles checkout and confirmation, while you’re still responsible for switching to live mode, verifying your payout account, turning on receipt emails, and deciding whether tax collection applies to your sales.

Choosing a bakery website builder that’s easy now and ready to grow

Abstract of bakery website builder

Pick a bakery website builder the way you’d pick a mixer: focus on the batches you’re actually making, and less so on the wedding-cake empire you might run someday. That means an easy-to-use platform that can actually take a payment, priced in a way that matches how much you’re really selling. What does that mean? Let’s unpack.

Key takeaways:

  • A bakery website builder needs things a generic site builder doesn’t: real online ordering, pickup as its own checkout option, and space for cottage food or allergen disclosures.
  • Entry-level builders get you online in a day, but cap out fast: no real ordering system, no inventory tracking, no order notifications.
  • Some platforms give you built-in ordering without a steep learning curve or a pile of add-on costs.
  • Plan price isn’t the full story: some platforms charge a per-order fee on top of a lower monthly price, others charge more upfront with none. Run the math against your own volume before assuming the cheaper plan is cheaper.
  • A slow-loading order page costs real sales during pickup rushes and pre-order windows, not just search rankings.

What actually matters in a bakery website builder

Two things matter most when you’re narrowing down a bakery website builder: how easy it is to run day to day, and whether the pricing still makes sense once real orders start coming in. Everything else on the list that follows still matters, but these two are the foundation the rest builds on.

A home baker testing recipes on weekends mostly needs the first: something live this weekend, with nothing to configure or maintain. A bakery already taking orders every week needs both, a platform that doesn’t get in the way, at a price that doesn’t quietly cost more than it looks like once volume climbs.

Start there, then use the list that follows to cover what’s specific to selling food, like allergen disclosures and cottage food rules, on top of that foundation.

What to look for in a bakery website builder

Here are the eight checkpoints to run any platform through, covering the foundation above and what’s specific to selling food, allergen disclosures, cottage food rules, and everything else that comes with running a bakery online.

1. Ease of setup

Setup time is the first filter, since most bakery owners are running the kitchen and the website at the same time. But the real test isn’t how few features a platform has, it’s whether a platform that does a lot still feels simple to run.

  • Look for a guided setup that walks you through adding products, connecting payments, and publishing.
  • The best platforms hide the complexity: real infrastructure and a real payment processor running underneath, with a dashboard that reads like a checklist, not a settings menu.
  • Test this before you commit. Try going from creating an account to actually taking a payment, and notice whether the platform explains each step as you go, or leaves you guessing.
SiteGround Ecommerce checklist to get started step by step

2. Bakery website templates

Templates matter more for food than almost any other product category, because photos do the selling. You won’t always find a template labeled specifically for bakeries, and that’s fine. What matters is whether any given template handles design and high quality images well. Before you commit to one, check for:

  • Large image grids that can showcase a cake gallery, not just generic text blocks.
  • A clean, scannable layout that works for a daily-changing menu.
  • A homepage hero built to show one great photo, not a stock banner that could belong to any business.
Large image grid on a bakery website builder

3. Online ordering or order forms

A real ecommerce cart lets a customer pick a product variation, like size or flavor, and pay online, all without a phone call. Building an ecommerce website the right way means checking, before you commit, what a platform actually handles out of the box:

  • Product variations for size, flavor, or filling, selectable right on the product page.
  • A dedicated field for allergy or dietary notes, so customers can flag what to avoid.
  • The ability to add notes during checkout, whether that relates to customization, allergies, or otherwise.

4. Local pickup

For many bakeries, pickup is essential, so there are few features you’ll want to look for when picking a website builder that is right for you.

  • Pickup listed as its own option at checkout, separate from shipping, so customers aren’t charged a shipping fee they’ll never use.
  • A clear description of the pickup process.
Adding local pickup as a shipping option in a bakery website builder

5. Mobile-friendly menu and photo display

More than half of local searches happen on mobile devices, according to Semrush’s local search data, often while someone is deciding what to order in the next five minutes. Here’s what to keep in mind when it comes to mobile:

  • Test the mobile website design with your own bakery photos, not the demo content.
  • Remember that mobile speed is a web hosting question, not just a design one. A perfectly responsive template can still be painfully slow if the hosting behind it can’t handle a spike, and spikes hit exactly when you need the site most. SiteGround’s infrastructure, for example, is built to absorb exactly those moments, so a good week doesn’t accidentally take the site down.
A mobile version of a bakery website

6. Local SEO basics

Most bakeries’ customers are almost entirely local, so local SEO matters more than broad keyword rankings. Check whether the builder:

  • Links out to and reinforces your Google Business Profile, since that’s often the first thing a local searcher sees, before they ever click through to your site.
  • Makes it easy to optimize your product page SEO with elements like the page name and meta description
  • Generates and automatically updates an XML sitemap as you add products or pages, so search engines can find new content without you doing anything by hand
  • Has solid hosting and performance, which translates to faster pages, something search favors

One easy win either way: make sure your city or neighborhood name shows up naturally in your homepage title and “about” section, not just your address. Someone searching “bakery near me” is looking for that context before they click. As your menu grows past a handful of items, the same logic applies to product page SEO: each one needs to be structured to be found, not just listed.

7. Compliance: cottage food laws, allergen labeling, health permits

Cottage food laws let bakers sell certain low-risk foods, like selling baked goods, out of a home kitchen without a commercial license or routine health inspection, in exchange for limits on what and how much you can sell. Most states require a specific disclosure statement on any product sold under cottage food law, something like “this product was produced in a home kitchen not subject to state food safety inspection.” The exact wording, and whether it belongs on your website or just the packaging, is set by each state’s health department, so check the current requirement before publishing. 

Beyond the legal disclosure, make sure your platform lets you cover:

  • Allergen labeling for the nine major allergens under U.S. law, including milk, eggs, wheat, soy, peanuts, and tree nuts
  • A custom text field on every product page, not a description box shoppers scroll past
  • A visible health permit number, if you have a storefront and your jurisdiction requires it posted online
A bakery website builder product vpage where you can add descriptions

8. Pricing and transaction fees vs. your order volume

The plan price is rarely the whole story, and “free” isn’t realistic. What actually varies across platforms is whether the price you pay comes as a flat monthly fee, a percentage cut of every order, or some mix of both. This shapes which platform makes sense at your order volume. Before ruling a platform in or out on price alone:

  • Check whether its ordering plan charges a percentage-based fee per order, a flat monthly cost with no added fee, or both.
  • Estimate your average monthly order revenue, then calculate what a percentage fee would actually cost you at that volume.
  • Compare that dollar figure to the flat monthly cost of a platform or plan that skips the percentage fee entirely.

Say you’re doing 15 orders a week at $35 average, that’s about $2,100 a month. A 3% per-order fee costs roughly $63 a month. SiteGround Ecommerce’s Sell plan charges that 3% fee at $18/month, while its Grow plan removes the fee entirely for $24/month, just $6 more. At this volume, the fee alone ($63) is already ten times the $6 price gap, so the plan without the fee is the clear win. Run this same math against your own numbers, and not just a platform’s advertised starting price: starting an online store on a budget means doing it before you pick a platform, not after a busy holiday season does it for you.

Bakery website builders compared

Not every option here deserves equal weight. Most of the market splits into a few predictable buckets, so here’s the general breakdown.

OptionStarting priceReal online orderingBest for
Carrd, SITE123Free, paid from about $19/yearNo (contact form only)Testing an idea before investing more time
Wix, SquarespacePaid plans from about $16 to $29/month, real ecommerce needs a higher tierYes, on a higher-tier planDesign flexibility, if that matters more than selling costs
Square OnlineFree, but at a higher processing rate than paid tiersYes, built for food and pickupBakeries already using Square in person
ShopifyPaid plans from about $39/monthYes, full ecommerce suiteHigh volume, multi-channel, or shipping nationally
SiteGround Ecommerce$18/month (Sell plan)Yes, from the Sell plan upA real store today, with room to grow and no fee surprises later

Not every option here escapes a growth ceiling or a pricing catch. The difference is where the catch shows up and how much it costs to clear it.

Best for getting online fast with minimal setup (Carrd, SITE123)

Carrd and SITE123 solve one problem: getting something live today. No real ecommerce, so orders travel through a contact form, email, or a linked Instagram DM. Fine for testing an idea, a dead end once daily orders start.

Best for built-in ordering without a big learning curve (Square Online, SiteGround Ecommerce)

Square Online gives you a real cart and food-friendly ordering, tied to Square’s point-of-sale ecosystem. Strong if your in-person payments already run through Square, less useful if they don’t.

SiteGround Ecommerce follows the same pattern: the entry-level Build plan is a general website with no selling built in, and moving up to Sell is what turns on a real cart. What’s different is what that climb actually costs. The Sell plan ($18/month) turns on a real cart and payments, at a 3% fee per order. The Grow plan ($24/month), just $6 more, drops that fee to 0% and adds customer accounts, promo scheduling, and a wishlist. Every tier is backed by SiteGround’s hosting infrastructure and 24/7 expert support.

Best for design-forward storefronts (Wix, Squarespace)

Wix and Squarespace are general-purpose website builders with an online store added on. Real ecommerce usually means a separate, pricier commerce-tier plan on top of the advertised entry price, and what that extra cost buys is design range, not more ability to sell.

Best for scaling and high order volume (Shopify)

Shopify is built for volume across sales channels and shipping. Real setup overhead and ongoing app costs that outweigh what most bakeries need before they’re shipping nationally or running a subscription box.

A quick decision framework

Match your current stage to the row that fits, not the one you hope to be in next year.

Your stageOrder volumeWhat to prioritizeFits best
Testing an idea, home-basedUnder 10 orders/weekGetting live fast, minimal costCarrd, SITE123
Established home bakery10 to 50 orders/weekReal ordering, pickup scheduling, local SEOSquare Online, SiteGround Ecommerce
First storefront, growing50+ orders/week, some wholesaleOrdering plus room to add features, product page SEO as your catalog growsSiteGround Ecommerce, Wix, Squarespace
Shipping nationally or multi-locationHigh volume across channelsInventory, shipping, app ecosystemShopify

The middle two rows cover most bakery owners reading this. If you’re already taking real orders every week, the deciding factor usually isn’t design, but rather whether the ordering system was actually built to sell effectively.

Choosing the right bakery website builder for where you are now

Keep two things in mind as you compare platforms: how easy one actually is to run day to day, and whether its pricing still makes sense at your real order volume, not the volume you’re hoping for. Get those right first. Everything else mentioned above still matters, but these two are where the wrong choice costs you the most.

For most bakeries past the testing phase, that means a builder with real ecommerce built in from the start. SiteGround Ecommerce bundles a full online ordering system with hosting built for the traffic spikes that come with holiday pre-orders and weekend rushes, so the setup you do today doesn’t need a rebuild the day your order volume doubles.

[103]

Frequently asked questions

What’s the best website builder for a bakery?

There’s no single best bakery website builder; it depends on order volume and stage. Home bakery businesses testing an idea do fine with Carrd or SITE123. Bakeries taking regular orders need real ecommerce, which is where SiteGround Ecommerce fits in.

How much does a bakery website cost?

A basic bakery website can cost nothing beyond a domain name if you use a free plan, but free ecommerce plans usually charge a per-transaction fee that adds up with volume. Paid ecommerce plans typically run from around $15 to $40 a month, plus standard card-processing fees on every order.

What pages should a bakery website have?

A bakery website needs a home page with a clear hero photo and call to action, a menu or product pages with prices and allergen information, an ordering or contact page, a pickup or delivery details page, and an about page that builds trust in a home-based or small operation. Cottage food or health permit disclosures belong on the ordering page, not buried in a footer link. A short FAQ page covering lead times, custom order minimums, and payment methods also cuts down on repetitive customer questions sent by email or DM, which frees up time better spent decorating cakes.

Can I build a bakery website without any coding experience?

Yes. Every builder covered here, including SiteGround Ecommerce, is designed for setup without writing code. The difference between them is how much time the drag-and-drop setup takes and how deep the customization options go once you’re past the basics.

Do I need a website if I already sell through social media?

Social media marketing reaches new customers, but a website is what lets you take an order without depending on a platform you don’t control. Instagram and Facebook can disable accounts, change algorithms, or bury your posts, and neither is built for real order management the way a proper bakery website is. Think of social media as the storefront window and your website as the actual cash register.

How to build a 12-month email marketing calendar (with free template)

An email planner calendar showing scheduled campaigns next to a "one day offer" email preview and a bar chart tracking results

Your email marketing calendar is tied to real send dates, your list, and your own cadence, and not just vibes. By the end of this guide, you’ll have one built for your business, plus a free template to run it from.

Key takeaways:

  • An email marketing calendar tracks send dates, campaign type, ownership, and subject lines, not just topics.
  • Most small businesses send 2 to 4 marketing emails a month; ecommerce brands often go weekly or more.
  • Cadence should follow your list’s tolerance and your content supply, not a fixed rule applied to every month equally.
  • Mapping seasonal moments before regular content prevents your busiest sales periods from being an afterthought.
  • A free email marketing calendar template, ready for you to copy and paste, is included further down this page.

What is an email marketing calendar?

An email marketing calendar is a schedule of your planned sends: the date, campaign type, owner, and status, all in one place. Unlike a general content calendar, it exists for one job: keeping each send tied to a clear email marketing goal.

The tool doesn’t matter, a spreadsheet, a project board, or your email platform’s own scheduling view all work. What matters is whether the four fields covered below (send date, campaign type, owner, subject line) are filled in before the month starts, not backfilled the day of the send.

Why you need an email marketing calendar (even with a small list)

An email marketing calendar matters at any list size. Without one, most small lists run into the same handful of problems, all preventable once you can see the whole month at once.

  • Going quiet, then bursting. Weeks with no send, then three emails in five days because someone remembered a launch was coming up.
  • Clustered, unrelated sends. A promotion, a newsletter, and a product update all land in the same week, competing for the same inbox slot.
  • Slipping deliverability. Clustered, low-engagement sends read as unwanted to mailbox providers, chipping away at your sender reputation. A rising unsubscribe rate is the visible symptom; shrinking deliverability is the real cost.
  • Uneven segment coverage. One group gets three campaigns in a week, another hears nothing, simply because there’s no full-month view to catch the imbalance.

Each of these is a sequencing problem, not a volume one, and a calendar is what puts the whole month in view so you catch them before they ship.

What to include in your calendar

Four fields turn a list of dates into a working calendar. Skip any one of them and the calendar stops doing its job.

Send dates and cadence

Cadence means how often you send, logged as a specific field, not a vague plan. Weekly, biweekly, and event-triggered are the three practical options: weekly and biweekly are fixed slots on the calendar, while event-triggered sends (cart abandonment, post-purchase follow-up) run on their own schedule, driven by email automation rather than a calendar date.

Match cadence to what your list will tolerate and what you actually have to say. Not confident you have enough to say every week? Biweekly with more substance beats weekly with filler.

WeekTypeCadenceSend time
Week 2, MarchNewsletterBiweeklyTuesday, 10 a.m.
Week 3, MarchPromotionalMonthlyThursday, 9 a.m.
N/ACart abandonmentEvent-triggered2 hours after cart is left

If your platform supports scheduling, like SiteGround Email Marketing does, this field doubles as your real send schedule. Set the date once, and the send is queued.

Email campaign type and goal

Four core types cover most calendars: newsletter, promotional, transactional, and seasonal, each mapped to a specific goal.

TypeGoal
NewsletterRetention, keep the list warm
PromotionalConversion, drive a specific sale or offer
TransactionalOrder confirmation, delivery updates
SeasonalTimely relevance around a key date

The right mix isn’t universal. It shifts by industry: 

  • Ecommerce: promotional and transactional-heavy.
  • Service businesses: newsletter and seasonal-heavy.
  • Restaurants and fitness studios: seasonal-heavy with occasional promotional pushes.
  • Real estate and education: newsletter and nurture-heavy.

Weight your calendar toward whichever two or three types actually match how your business makes money.

Owner and status

Two fields, both simple: who’s responsible for drafting and reviewing each send, and a status marker.

SendOwnerStatus
Week 2, March newsletterAnaDrafted
Week 3, March promotionMarcoReviewed
Spring sale seasonal sendAnaNot started

Without an owner attached, “send a spring newsletter” is an idea. With one, it’s a task with a deadline.

Subject line/preheader notes

A field to draft subject lines ahead of time, so send day isn’t also writing day.

SendSubject linePreheader
Week 2, March newsletter“What’s new this March”A quick roundup before the month gets busy
Week 3, March promotion“Spring sale starts today”20% off through Sunday

You’ve seen the individual pieces, cadence, campaign type, ownership, subject lines. Now it’s time to put them together into an actual calendar.

How to build your yearly email marketing campaign calendar

Four steps, done once and then repeated each quarter.

Step 1: Audit your current sends

Look back at your last 3 to 6 months of sends: what went out, what got skipped, and what actually performed.

  • Pull three numbers for each send: open rate, click rate, and unsubscribe rate.
  • Look for a pattern, not a single winning email, like a day of the week that consistently underperforms, or a campaign type that quietly drives more unsubscribes than the rest.
  • If you skipped sends, note why. No content is a supply issue Step 3 should account for. No owner is a gap Step 4 exists to close.

Step 2: Map key dates and seasonal moments

Plot major seasonal moments before you fill in regular content: Black Friday, back-to-school, and whatever else is relevant to your business.

  • Not every date is worth a campaign. A seasonal marketing framework helps you filter which moments earn a full send versus a single line in your regular newsletter.
  • Once you know which moments matter, this step is about scheduling around them: lead time needed, and how many emails to build around each one.

Step 3: Set your cadence by month

Decide send frequency per month based on your audit and seasonal load, not a flat rule for the whole year.

Heavier months (seasonal peaks, launches) earn more sends. Quieter months pull back.

How SiteGround Email Marketing’s scheduling makes this easier

Sends can be scheduled in advance, so the monthly cadence you just planned becomes a real, locked-in schedule instead of a to-do list someone has to remember to act on each week.

Step 4: Assign ownership and review steps

Lock in who drafts, who reviews, and when.

A calendar with dates but no named owner tends to slip the first time someone gets busy.

Free email marketing calendar template

The template below covers all four fields: date and cadence, campaign type and goal, owner and status, and subject line notes, as a month-by-month grid you can duplicate each month. Copy it straight into Google Sheets or an email marketing calendar template for Excel, whichever you already have open ten times a day.

DateCampaign typeGoalOwnerStatusSubject line
[DateNewsletter/ Promotional/ Seasonal[Goal][Name]Not started/ Drafted. Reviewed[Subject line]

Fill in seasonal moments from Step 2 first, then work backward with your regular cadence. Once you’re sending consistently, tracking your email open rate tells you whether the plan is working.

What can vary in each field

  • Campaign type: Newsletter, promotional, transactional, seasonal, or event-triggered (cart abandonment, post-purchase).
  • Goal: Retention, conversion, order confirmation, timely relevance, whatever matches the campaign type in that row.
  • Owner: Whoever is drafting that specific send, can rotate by month or stay fixed depending on your team size.
  • Status: Not started, drafted, reviewed, or sent, a simple four-stage progression rather than a custom workflow.
  • Subject line: Draft version is fine here. It just needs to exist before send day, not be final.

Keep your calendar sustainable long-term

Review it monthly, quarterly at a deeper level. Adjust cadence and campaign mix based on what performed, not what you guessed would.

That review is where the calendar earns its keep. Line performance up against your email marketing ROI to see whether the planning time is actually paying off, or just making your spreadsheets look tidier.

A calendar is only as good as whatever’s executing it. SiteGround Email Marketing handles the scheduling and contact management, so your carefully planned Tuesday send doesn’t depend on someone’s memory. Set it up alongside the calendar from day one, and the plan and the actual sends live in the same place instead of you syncing two systems by hand like it’s 2010.

[58]

Frequently asked questions about email marketing calendar

How far in advance should I plan my email marketing calendar?

Plan a full quarter at a time, with seasonal moments locked in about a month ahead of when they need lead time. Trying to plan too many subject lines up front usually means the details go stale before you get there.

What’s the difference between an email marketing calendar and a content calendar?

An email marketing calendar tracks scheduled sends specifically: dates, cadence, and ownership tied to your email platform. A content calendar is broader and often includes blog posts or social captions that don’t carry the same fixed-date pressure an email send does.

How many emails is too many in one month?

There’s no fixed number, but clustering multiple unrelated campaigns into the same week is the more common problem than raw volume. If a promotion, a newsletter, and a product update all land within days of each other, that’s a clustering problem worth fixing before it shows up as a rising unsubscribe rate.

Should seasonal campaigns replace my regular newsletter, or run alongside it?

Run them alongside it for most businesses. A seasonal campaign is a spike on top of your baseline cadence, not a replacement for it. Pausing your regular newsletter to make room for a seasonal push usually costs you more consistency than it gains you in relevance.

Can I schedule a full month of emails in advance?

Yes, if your platform supports advance scheduling. Set each send’s date and time once, and they go out automatically, which is what turns a calendar from a planning document into an actual production schedule.

What’s a realistic cadence for a service business vs. an ecommerce store?

A service business (an agency or consultancy, for example) can often sustain a solid calendar on 2 to 4 sends a month. An ecommerce store, with more to promote and a shorter buying cycle, often sends weekly or more without overwhelming subscribers, provided each send has a distinct purpose.

7 AI mistakes small businesses make with WordPress AI tools and how to avoid them

A digital graphic depicting AI tool management and cost tracking around a website, set against a light blue gradient background. In the center, a browser mockup displays a waterfront luxury real estate website titled "THE ATELIER." Floating UI cards surround the website, detailing various software costs and system statuses: a "Generic AI Writer" card at "$8/mo," an "Enterprise Bot" card noting "Idle for 14 days • $120 spent," an active "WP Core" card showing "$15 spent," an inactive "Image Optimizer" card showing "$45 spent," a "Cohesive Agent" card at "$78," and a "Legacy Translator" card at "$12" displaying a "Memory limit exceeded" error.

Small business owners managing their WordPress sites are increasingly relying on AI, as our 2026 report on AI in WordPress for small businesses found by surveying more than 7,000 of them. However, we also saw the same handful of issues come up again and again.

The most common AI mistakes small businesses make on WordPress usually happen around the tools they choose and how they’re set up: generic chatbots that can’t reach their site, AI plugins that reach too far into it, API keys left exposed, token bills nobody capped, and changes published without review. Luckily, each one is easily avoidable, and the fix is usually smaller than the problem.

Key takeaways:

  • The AI mistakes small businesses make on WordPress start with the tool, not the task. Two-thirds use ChatGPT as their main AI tool, but that usage clusters in research (66.5%) and content (65.7%), not the site admin that eats the most time.
  • Plugin sprawl is the fastest-growing risk. WordPress AI plugins are growing about three times faster than the wider plugin economy, and most reported WordPress vulnerabilities come from plugins.
  • Your AI API key is a billing credential. Keys saved through the WordPress Connectors screen sit in your database as readable text, and WordPress sets no spending limit by default.
  • Unreviewed output costs more than it saves. 41% of small business owners say usable results take multiple attempts, and 22% don’t trust AI accuracy.
  • Some AI setups create more admin than they remove. Getting AI running in WordPress by hand means a provider account, an API key, two plugins, and a separate billing dashboard to watch.

Mistake 1. Relying on a generic chatbot for WordPress work

Two-thirds of small business owners use ChatGPT as their primary AI tool for WordPress work, but our 2026 report on AI in WordPress also found that usage concentrated in research and content creation. Site management, which is where most of the hours actually go, barely registers.

There’s a simple reason for that gap. A chatbot in a browser tab has no connection to your WordPress installation. It can write you a product description for your WooCommerce store, explain where a setting lives, and draft a policy page. But you’re still the one who publishes the page, updates 40 product descriptions, and clicks through to the setting three menus deep. The time you saved with the chatbot comes back as implementation time, which is why you’re still spending hours in the WordPress admin.

The fix: Go beyond generic chatbots to an AI agent that can reach your site. For example, a site-connected AI assistant like SiteGround’s AI Agent for WordPress can not only draft your product descriptions, but it can update them in bulk, use your store data to create and update the products themselves, adjust pricing, generate discount coupons, manage customer orders, and even pull a sales report for you. Our guide to using AI in WordPress beyond content creation covers what that looks like.

SiteGround AI Agent for WordPress chat interface with a prompt to update sale prices for all products in the Tennis category, with a WooCommerce product grid showing discounted tennis equipment in the background

Mistake 2. Installing AI plugins reactively, one problem at a time

WordPress AI plugins are growing roughly three times faster than the wider plugin economy, and installing them on impulse is one of the most common WordPress AI mistakes. It happens because of how these plugins are built: most do one job. For example, a translation plugin turns your pages into other languages, and an SEO plugin writes your page titles and meta descriptions.

Each is good at its own job, so when you need three of those things, you install three plugins, each with its own settings screen, its own subscription, and often its own AI account to create. Also, many AI plugins don’t include the AI itself: they connect to a service like ChatGPT or Gemini through an account you set up and pay for separately. Each install makes sense on the day you make it. Six months later, you’re paying for four tools and maintaining four interfaces, when one chosen with all four tasks in mind might have done.

The fix: Start from the job, not the plugin. Write down the two or three tasks that actually take up your week, then look at what you already have installed, because something on your site may already do part of it. Overlap is the check most people skip, and two plugins doing the same job compete rather than add up. If your list spans several different jobs, one tool that covers all of them costs you less time than four that each cover one. Our comparison of AI plugins and AI agents covers that choice.

Mistake 3. Stacking narrow plugins until the site is a patchwork

While we’re on the plugins topic, most WordPress security problems actually come from them. That isn’t because plugin developers are careless. It’s arithmetic: every plugin is code written by someone else, running inside your site, with permission to read and change what’s there. The more you install, the more chances one of them has a flaw.

WordPress AI plugins raise the stakes because of what they hold. Many store a key that lets them use an outside AI service and bills you for the usage, which makes them worth stealing in a way an ordinary plugin isn’t. Once a flaw becomes public, attackers typically start using it within five hours. And if you’re using WordPress 7.0 or above, your AI plugins share one set of AI credentials, which means a single compromised plugin can reach all of them, not just its own.

The fix: Fewer plugins is the fix for AI plugin fragmentation, and an audit is the fastest way there. Hand it to an AI assistant like SiteGround’s AI Agent for WordPress: it can list what’s installed, say what each one actually does rather than what its name suggests, flag anything that overlaps or hasn’t been updated in a long time, and remove the ones you agree to drop. Deleting a plugin you no longer use does more for your security than installing another that promises to protect you. Our guide to choosing AI plugins for WordPress covers what to look at.

Mistake 4. Leaving your AI API keys unprotected in WordPress

An API key is how one piece of software proves to another that it’s allowed to be there. Think of it as a password with your credit card attached: it identifies you to the AI service, and everything done with it gets billed to your account.

WordPress 7.0 added a Connectors screen where you paste that key in once, so any AI plugin on your site can use it. What isn’t obvious is where it goes: into your site’s database, as ordinary readable text. The screen hides it behind dots so nobody reads it over your shoulder, but that’s a curtain rather than a lock: the stored value is unchanged, and anything that can read your database can read the key. WordPress documented this when the feature shipped. It has since tightened how the key is displayed, but the encryption work is still open, so what’s in the database hasn’t changed.

Your database gets copied more often than you’d think: every backup, every staging copy, every time someone pulls the site down to work on it. The key travels with all of them. And unlike a stolen password, a stolen AI key locks nobody out and changes nothing you can see. Someone else simply starts spending on your account until the bill tells you.

The fix: Choose a setup where your host makes the connection for you, because a key you never paste in is a key nobody can copy out. If you do paste one in, treat it like a house key you’ve lent out: replace it whenever a copy of your site goes somewhere new, and delete any connection you’ve stopped using. And if you have someone technical to hand, ask them to keep the key in your site’s configuration file rather than the database, which is the route WordPress itself recommends. Our explainer on how AI works in WordPress 7.0 shows where these settings live.

Mistake 5. Not setting a limit on what AI can spend

AI billing costs in WordPress aren’t always a flat monthly fee. They bill by the amount of text going in and out, counted in units called tokens, where one token is roughly three-quarters of a word. So the cost moves with how much you ask for, and there’s no fixed number you can put in a budget.

If you’ve connected to an AI provider on WordPress 7.0 or above, WordPress itself doesn’t cap that for you. There’s no spending limit built in and no usage tracking either, so unless you set a limit yourself in your AI account, nothing stops the meter and nothing shows you it running. Two things push it up: a busy month of content can double or triple the bill, and some plugins send AI requests in the background while you work, checking your text or generating suggestions you never asked for.

The fix: Set the limit before you paste the key, and check it’s a limit that actually stops something. Providers differ here: OpenAI and Anthropic let you set a hard monthly cap that refuses requests once you reach it, while Google’s billing runs through Google Cloud, where the default budget is an alert that emails you and lets the spending carry on. Our comparison of ChatGPT, Claude, and Gemini covers how else the three differ.

Mistake 6. Publishing AI output on WordPress without review

Most people already know AI output on WordPress needs human review. In our 2026 report on AI in WordPress for small businesses, 41% of small business owners said they need several attempts before AI gives them something usable, and 22% said they don’t trust its accuracy. So the mistake isn’t that anyone believes AI is always right. It’s that knowing output is unreliable and actually checking it are two different things, and a page that looks finished tends to get published.

That’s what makes AI output hard to check: it rarely looks wrong. A made-up statistic reads exactly like a real one, and a product description can be fluent while describing a feature your product doesn’t have. There’s no equivalent of a spelling mistake to catch your eye, so anything published without a proper read has gone out on trust.

The fix: Make the AI check its own work. Paste the text back into the chat and ask it to separate what it knows from what it filled in, with a prompt like this one: “List every factual claim in the text above: numbers, dates, prices, product features, and names. For each one, tell me whether you are certain, unsure, or made it up. Do not rewrite anything.” What comes back is a short list to verify rather than a whole page to reread, and invented details tend to surface in the unsure column. It isn’t a guarantee, since a model can be wrong about its own confidence, so use it to narrow what you check rather than to replace checking. Our guide to writing ChatGPT prompts covers more habits that cut rework.

Mistake 7. Adding AI that creates more admin, not less

Some AI tools for WordPress take more admin to run than they save, and the setup is usually where that happens. For example, here’s what it currently takes to get AI working if you’re on WordPress 7.0 or above: open the Connectors screen, pick an AI provider, install that provider’s plugin, create an account on the provider’s website, find your way into its developer dashboard, generate an API key, come back to WordPress and paste it into the right field, then install a second plugin before you see any AI features you can actually use.

After that, you track spending in the provider’s billing dashboard, a third place to keep an eye on. That’s one job spread across WordPress, an AI company’s developer platform, and a separate billing system, creating more admin instead of removing it. And what many people get at the end of that setup is AI that writes text inside the editor, which is the part they were already doing in a chatbot.

The fix: Before setting anything up, count the accounts, screens, and bills involved. If a tool needs three systems to do one job, that’s admin you’ve taken on, not admin you’ve removed. The alternative is a tool that arrives already connected. For example, SiteGround’s AI Agent for WordPress is active on SiteGround-hosted sites from the start, with no provider account to create, no key to generate, and no separate bill to follow.

MistakeThe fix
Relying on a generic chatbot for WordPress workUse AI that connects to your site, so it makes the change instead of describing it
Installing AI plugins reactively, one problem at a timeWrite down the two or three tasks that eat your week, check what you already have, then pick one tool against the whole list
Stacking narrow plugins until the site is a patchworkAudit what’s installed and delete what you don’t use. A site-connected agent can list, flag overlaps, and remove
Leaving your AI API keys unprotectedAvoid handling a key at all where you can. Otherwise replace it whenever your site gets copied, and keep it in the config file rather than the database
Not setting a limit on what AI can spendSet a hard cap, or prepay credit so it can’t be exceeded. Use one key per plugin to see what each is spending
Publishing AI output without reviewHave the AI list its own factual claims, then check that short list instead of rereading the page
Adding AI that creates more admin, not lessCount the accounts, screens, and bills before you set anything up. Prefer tools that arrive connected

What these mistakes have in common

The AI mistakes small businesses make on WordPress look like seven unrelated problems, but they share a shape. In each one, the AI does exactly what it was built to do, and what’s missing sits around it: a tool that can reach the thing you want changed, a plan before the first plugin goes in, an audit before the fourth, a limit on the key, a ceiling on the bill, and a second look before anything reaches a customer. None of that arrives with the tools, so it lands on whoever adopted them, which on most small business sites is one person who already has a business to run.

That’s also why none of it takes technical skill to fix. Work out what you want AI to do before you go looking at WordPress AI tools, keep the stack small enough to hold in your head, and put a limit and a check on anything that can spend your money or change what your customers see. How much of that you’re left doing depends on what you choose. For instance, a tool that connects to your site on its own, with no key to guard and no separate bill to watch, means most of this list never becomes your problem.

FAQs

What are the most common AI mistakes small businesses make on WordPress?

The most common AI mistakes small businesses make on WordPress are treating a generic chatbot as a site management tool, installing AI plugins reactively, stacking too many, leaving API keys unprotected, skipping spend limits, publishing without review, and adding AI that creates more admin than it removes.

Why is relying on a generic chatbot a WordPress AI mistake?

Relying on a generic chatbot is a WordPress AI mistake when the tool isn’t connected to your site. It can draft and advise, but it can’t publish, update products, or change settings, so you still do the implementation by hand.

What are the risks of stacking WordPress AI plugins?

The risks of stacking WordPress AI plugins are a larger security surface, conflicting code, and multiple subscriptions and keys to manage. Most reported WordPress vulnerabilities come from plugins rather than from WordPress itself, and every AI plugin you add increases the exposure.

Why can AI billing surprise WordPress site owners?

AI billing costs in WordPress can surprise site owners because providers charge by the amount of text processed and WordPress sets no spending limit by default. A plugin making frequent background requests, or a busy content month, can double or triple the bill before anyone notices.

Why should you review AI output before publishing on WordPress?

You should review AI output before publishing on WordPress because AI rarely looks wrong when it is wrong. In our survey, 41% said usable results take multiple attempts and 22% don’t trust AI accuracy, so anything published without a proper read has gone out on trust.

How can a small business use AI safely on a WordPress site?

A small business can improve WordPress AI safely by mapping its real workflow before installing anything, keeping the plugin stack small, avoiding or protecting API keys, setting spend limits, checking output before it goes live, and preferring site-connected tools that ask for confirmation.

How agencies can add payments to client websites without custom code

Abstract of adding payment functionality to a client website

You quote a website build. Partway through, the client asks if people can actually pay through it: a checkout, a deposit, a subscription, whatever the case. Treat that like a custom-dev request, and your fixed-scope build turns into open-ended work.

That’s not where the real cost is, though. It’s custom payment code, unclear scope, a broken checkout handoff, and the post-launch fixes that eat your margin after delivery. Doing it right means delivering a payment-ready client site before launch: the checkout works, the confirmation fires, the record gets kept. This piece walks through how to add payments to client websites the right way: matching the setup to each client, building it with Coderick AI and Stripe instead of custom code, and handing it off clean.

Key takeaways:

  • You can add payments to client websites without custom payment code. Stripe handles the transaction layer; you handle the configuration.
  • The agency margin risk isn’t the website build. It’s custom payment code, unclear scope, and the post-launch fixes that follow a broken checkout handoff.
  • Payment-ready client sites need an end-to-end payment flow that runs itself: an automatic confirmation, a business notification, a status update, and a record you can actually search. Miss one, and you’re the tech support line now.
  • Client payment flows differ by project. A booking deposit, a one-time invoice, and a recurring membership charge each need a different setup, not a different codebase.
  • Standardizing agency payment workflows is what actually lets you ship client websites faster. Skipping the testing step just moves the slowdown to launch week.

What it means to add payments to client websites

Adding payments to a client website means connecting two separate things, and most of the confusion comes from treating them as one:

  • Payment access: having a Stripe account and API keys. Takes about five minutes. 
  • Payment integration: the working path from “client clicks pay” to “client’s business records the sale.”
Example of connecting Stripe payments to a client's AI built website

When agencies stop at access, they end up shipping a checkout button that looks finished and does about half the job.

To be clear on the scope here: this isn’t about an agency invoicing its own clients, and it isn’t about a business owner setting up payments on their own site themselves. It’s about building that payment flow into a site for someone else’s customers to use.

The gap between access and integration shows up in what a client actually means when they ask to “add payments to my website.” Usually it’s “let people pay me and tell me when it happens,” and that second half, the notification and the record, is the part nobody truly scopes and everybody just assumes is included. Closing that gap once, by matching the client’s situation to the right setup, means you’re not re-solving it on the next project. That match-up is exactly what the next three flow types cover.

Types of payment-ready client sites: bookings, stores, and memberships

Alas, “client website” covers a wide range of projects, and each one maps to a different Stripe object (Stripe’s term for a pre-built checkout, billing, or customer resource that already handles the logic for you) as part of the client payment setup. Match a format to a setup once, and that pairing holds for every future project of the same type. Here’s what each looks like.

What you can sell online with Stripe integration

Booking and service pages

A salon, a consultant, or an event venue usually needs a deposit or a full payment collected at the time of booking, tied to a specific date and service. But this payment has to be linked to the booking record, not just logged as a generic transaction, or the client ends up cross-referencing two systems…by hand…every week. No thanks.

So nail down the deposit amount, the cancellation policy, and the calendar sync before setting up client booking pages, because those decisions decide the Stripe setup, not the other way around.

Simple stores

A small catalog (say, ten to 20 products) doesn’t need a full ecommerce platform to take payments. Indeed, a Checkout Session with a short product list can handle it just fine. The right store setup depends on catalog size and how often it changes, not on defaulting to the heaviest tool on the shelf.

Membership and subscription sites

Recurring billing is a different beast entirely from a one-time charge. Stripe’s Billing product already handles proration, failed payments, and cancellations, so none of that needs custom code. What it doesn’t handle is whether the site checks a member’s status before letting them in, and that’s the part client membership sites actually break on.

Where agency payment workflows break down

Matching a flow to the right object solves the technical half. It doesn’t solve the payment setup cost side. The website build isn’t what blows the budget on a payment project. That said, four finicky things reliably do:

  • Custom payment code. Writing a bespoke checkout form and backend handler for a single client site takes days and creates a one-off system nobody else on the team can maintain.
  • Unclear scope. “Add payments” without a defined flow (one-time, deposit, subscription) invites scope creep the moment the client sees what’s possible.
  • Broken checkout handoff. The payment succeeds, but the confirmation email, the CRM entry, or the fulfillment step downstream doesn’t fire.
  • Post-launch fixes. Refund requests, failed webhook deliveries, and currency mismatches surface after launch, right when the project’s margin has already left the building.

None of these actually require more code. What they do require is a workflow that treats payments as configuration with a testing step, and not as a feature to be built from scratch every time. That’s the difference between agency payment workflows that scale and ones that end up eating their own margin. It’s the same repeatable pairing from the last section, just applied to the whole process instead of one flow: build it once, and it holds for the next client project instead of getting rebuilt from scratch.

How to build client websites with payments without custom code

Stripe already provides the hosted objects agencies need:

  • Payment Links
  • Checkout Sessions
  • Customer Portal
  • Billing for subscriptions

Each one handles the card form, the fraud checks, and the receipt. Building a payment-ready flow without custom code comes down to five steps:

  1. Connect the client’s Stripe account. This is the payment access piece from earlier: a real account, live API keys, nothing generated yet.
  2. Pick the Stripe object for this client’s flow. This is the same matching from the last section, just applied to an actual client instead of a category: a booking gets a Checkout Session, a subscription gets Billing, and so on.
  3. Describe the flow in plain language. Something like “when this Stripe Checkout Session completes, mark this booking as paid and send this confirmation” is enough for an AI-built app to skip payment code entirely.
  4. Let the app generate the plumbing. The success page, the webhook listener (the bit of code that catches Stripe’s automatic “this just happened” notification and reacts to it), and the record that ties a payment to a specific client all get built from that one description. The agency still makes every decision; it just isn’t hand-coding the webhook handler and the database write for every client separately.
  5. Review the result before it goes live. This step doesn’t get to skip a turn. A generated webhook handler can fail on a declined card the same way a hand-coded one can, and the failure stays invisible until a customer emails asking where their confirmation went.

Steps 3 and 4 are the ones that repeat: describe the flow once, and the same description applies to every future client who needs that same setup.

How Coderick AI builds client payment flows

Coderick AI payment flows turn a described payment flow into working code, connected to a real Stripe account, without a developer starting from a blank file each time. So you, as a noncoder, describe the flow (deposit, one-time charge, or subscription), and it generates the checkout, the webhook listener, and the confirmation logic to match. Note, of course, that the output still needs testing in Stripe’s test mode before it touches a live client account.

AI website prompt example for creating a booking page

Think of it as generating the plumbing, not the plumbing decisions (and, oh, you don’t need to be a proper “plumber”). The agency still decides:

  • Which Stripe object fits this client’s flow
  • Whether a client needs a deposit or a full charge
  • Whether a booking cancels the payment or just the slot
  • The deposit amount, cancellation policy, or calendar sync, if it’s a booking flow
  • What the confirmation should actually say

Coderick AI turns those decisions into working code connected to the client’s own Stripe account, so the same webhook-and-confirmation pattern doesn’t get rebuilt by hand on every new client site. 

This is also where agencies protect project margins: once a booking flow, a simple checkout, and a subscription flow each have a known pattern, quoting a new client project takes minutes instead of a scoping call about what’s technically possible. Working this way with an AI builder for client projects means the variable becomes the client’s business rules, not the underlying plumbing.

Pre-launch checks that prevent post-launch fixes

Before handing a payment-ready site to a client, run through a short list:

  1. Complete a test transaction with a Stripe test card and confirm the webhook fires.
  2. Confirm the confirmation email or notification reaches the right inbox, not a developer’s testing address.
  3. Test the refund path once, even if the client hasn’t asked for it yet (they will).
  4. Check the mobile checkout flow specifically; card entry on mobile is where most abandoned payments happen.
  5. Confirm the site’s currency and language match the client’s actual market.

These client launch checks take under an hour and remove most of the support tickets that would otherwise show up in the first week after launch. Most agencies that run this checklist once end up reusing it as a fixed step in every project. That’s the actual efficiency gain: not skipping verification, but never having to reinvent it per client.

What a clean payment-ready client handoff looks like at launch

Before calling a site ready to hand off, confirm it clears all of this:

  • These three things happen automatically after a payment. A confirmation to the customer, a notification to the client’s business, and an update to whatever system tracks status (booking calendar, membership list, order queue).
  • The checkout is tested, not just connected. A checkout button only proves Stripe is connected. A payment-ready app handoff proves the business can operate on the payments it receives without a person in the loop, which is exactly what the pre-launch checks above were for.
  • Every payment lands somewhere searchable. Who paid, how much, what for, one-time or recurring, stored as paid client records, not left as receipts buried in Gmail.

If any of these depend on someone checking an inbox, or the client manually checking Stripe’s dashboard, the site isn’t ready to hand off yet, no matter how finished it looks.

Once all three actually hold, the handoff itself comes down to three things: who owns the account, what gets documented, and what access changes hands.

Who should own the payment account and payout details?

The client should normally own the live payment account, payout details, tax settings, and customer payment records. The agency should keep only the access needed for agreed maintenance or support, and should document all retained permissions during handoff.

What the agency should document and hand off

Handoff documentation should cover:

  • Which Stripe object handles which flow
  • How to check whether a payment’s confirmation fired, using the Events log in the Stripe dashboard
  • What confirmation each flow sends, and to whom

Skip this, and the client ends up calling the agency for things they could’ve handled themselves, which defeats the point of handing it off in the first place.

What access the agency should remove or retain after launch

Once launch is confirmed, remove any development or test-mode API keys from production and transfer account ownership to the client’s own Stripe login. If there’s an ongoing maintenance contract, keep only the specific access that contract requires, spelled out by name, not a blanket admin role left over from the build.

Making payments part of the build, not a detour

Every format in this piece, from bookings to stores and memberships, comes down to the same three questions: which Stripe object fits, what has to happen after the charge, and where the record lives. Answer those once, reuse the answer, and you can add payments to client websites the same way you handle fonts or hosting: as a standard part of the build and not a separate quote with its own risks attached. That’s what keeps client website delivery predictable, project after project.

Build client sites with Coderick AI, and connecting Stripe is simple. The site runs on SiteGround’s own hosting the moment it’s published, so there’s no server to configure or database to set up on the side, and every version along the way gets saved automatically, so testing a payment flow doesn’t put a live project at risk. The booking, store, and membership setups from this piece already exist as a starting point. The only real variable left is the client’s own business rules, not whether the checkout works.

[96]

Frequently asked questions

How do you add payments to client websites without custom code?

You can add payments to client websites without custom code by using a payment processor’s hosted objects, such as Stripe Checkout or Payment Links, and generating the surrounding confirmation logic instead of hand-coding a payment form and backend.

What is the difference between payment access and payment integration?

Payment access is having a processor account and API keys connected to a site. Payment integration is the complete working path from checkout to confirmation to a recorded transaction, which is what actually makes a site payment-ready.

Can Coderick AI build client websites that accept Stripe payments?

Yes, Coderick AI can generate a client website and payment flow connected to a Stripe account, including the checkout flow and the confirmation logic, though the resulting flow still needs testing in Stripe’s test mode before it goes anywhere near a live client.

What should agencies test before handing off a payment-enabled client website?

Before handing off a payment-enabled client website, test a full transaction in the processor’s test mode, confirm the webhook and confirmation notifications fire correctly, and check the refund path once, even before a client requests one.

Is a checkout button enough for a payment-ready client site?

No, a checkout button alone isn’t enough for a payment-ready client website. It proves the payment processor is connected, but the app also needs a confirmation step and a way to record the payment against the right customer or booking.

Announcement emails: How to write news your subscribers open and read

Woman working on a laptop next to an inbox preview showing a "New collaboration" email with subject line and preheader text highlighted

Announcement emails deliver one piece of news. A launch, a price change, a store opening, a rebrand. You send them on their own, either as a single email or a short sequence, separate from your regular newsletter. They get opened and read when you do three things: name the news in the subject line instead of teasing it, match the number of emails to whether there’s a deadline, judge each one by the metric that fits its goal, not just the open rate.

Key takeaways:

  • Announcement emails cover seven situations: launches, store openings, seasonal sales, rebrands, pricing or hours changes, events, and milestones.
  • Name the news in the subject line, don’t tease it. “New hours starting March 1” beats “Big changes are coming.”
  • Match sequence length to the deadline. A sale needs two to four emails with reminders; a rebrand needs one.
  • Match the metric to the type. Judge a sale on click-to-open rate; judge a rebrand on unsubscribes, not clicks.
  • If there’s no CTA, don’t grade the email on clicks.

What is an announcement email? (and when to send one)

An announcement email delivers one specific piece of news, either as a single send or a short sequence, rather than nurturing a relationship the way a recurring newsletter does. It earns a dedicated send when the news changes how, when, or why someone buys from you or deals with your business:

  • A product or feature launch
  • A store opening or new location
  • A seasonal sale or promotion
  • A rebrand or name change
  • A pricing, hours, or business policy change
  • An event or webinar
  • A company milestone or business update

If the news is small enough to mention in your next scheduled newsletter without anyone needing to act on it right away, it probably doesn’t need its own send. Announcement emails are one of the core types of marketing emails worth keeping a template ready for, precisely because the situations above show up on a schedule you don’t control.

Announcement emails by type, with templates

Each type below gets its own subject-line logic in the next section. Here’s the template and the one thing to get right for each. Treat these as structural skeletons, not scripts: the bracketed placeholders carry the logic (what changed, why, what it means for the reader), and your own brand voice, formal, playful, terse, warm, is what goes into the sentences you write to fill them in.

If your brand leans playful, each type below also gets a few optional lines to steal, more personality, same structure, drop them in wherever the brackets say so.

Product or feature launch

Use this when you’re introducing something genuinely new, not running a sale on something you already sell.

  • Open with the product name and what it does, in one sentence.
  • Add one sentence on who it’s for.
  • Include a single link or button to see it, sized as the one action you want.
  • Note availability: today, this week, or waitlist.

Your ready-to-copy template (just adapt it to your needs):

Subject: [Product name] is here 

Hi [First Name], [Product name] is live today. 
[What it does, one sentence]. 
We built it because [the actual reason: a problem customers raised, or a gap you saw]. 

[See it now] → [link]

Want more personality? Try:

  • P.S. with an early-access wink: “P.S. First 50 people to try it get [perk]. Yes, we’re bribing you. It’s working, isn’t it?”
  • An origin story with attitude: “Built this after the 47th person asked why we didn’t already have it.”
  • A confidence flex: “We’ve been sitting on this for weeks and it was physically hard not to tell you.”

What metric to watch: click-to-open rate. Healthy is around 6.4%. Below that, the subject line oversold the news, so fix that before the body.

A single launch email rarely carries the whole job. For a full sequence spanning the teaser, launch day, and follow-up, see SiteGround’s product launch email guide.

Store opening or new location

Use this for a physical opening, a new service area, or a reopening after closure.

  • Lead with the location and date, not company excitement.
  • Add one line on what’s different about this location.
  • Include a directions or map link, since that’s the real action you want.
  • Mention an opening-week detail if you have one, such as extended hours or a launch offer.
  • Update your Google Business Profile the same week you send this. If your email says “open Mon–Sat, 9–6” but Google still shows the old address or hours, that’s the first thing a curious reader checks, and now you look like you don’t know your own hours.

Subject: We’re open in [Location]

Hi [First Name],

Our [Location] location opens [Date]. [One sentence on what’s different about this spot].

Find us here: [Address]
[Get directions] → [map link]

[Opening-week detail, if there is one]

Want more personality? Try:

  • Overly specific and proud of it: “The corner unit. The one with the good light. We’ve wanted it since 2022.”
  • Opening-week bribery, said out loud: “Free coffee opening week, no strings, we just want you to see the place.”
  • A cheeky nudge: “Bring a friend. Bring the dog. Bring nothing, we don’t check.”

What to watch: click-to-open rate again. If it’s below the healthy benchmark (6.4%), the location or date wasn’t clear, put both higher in the email.

Seasonal sale or promotion

Use this for time-bound discounts or campaigns tied to a calendar date rather than company news.

  • Lead with the offer and the deadline in the first line.
  • Add one sentence on what qualifies.
  • Include a single call to action to shop or redeem.
  • Send a reminder 24 to 48 hours before the deadline, since urgency is the entire mechanism here.

Subject: [Discount]% off through [Date]

Hi [First Name],

[Discount]% off [category or product] through [Date]. [What qualifies, one sentence].

[Shop now] → [link]

And if you want to take it a step further, you can also send a reminder a day or two before the deadline, along the lines of:

Subject: [Discount]% off ends [Date] at [Time]

Hi [First Name],

Your [Discount]% off on [category or product] ends [Date] at [Time]. After that, prices go back to normal.

[Shop now] → [link]

Want more personality? Try:

  • Say the quiet part: “[Discount]% off. No riddles, no ‘mystery deal.’ Just the number.”
  • Deadline with teeth: “Ends tonight. Not ‘soon.’ Not ‘this week-ish.’ Tonight, at [time].”
  • A wink at the reader’s inbox habits: “We know you’ll open this at 11:58pm. We respect the hustle.”

A seasonal marketing calendar helps you plan these dates months ahead instead of scrambling the week before.

What to watch: click-to-open rate. Healthy is around 6.4%. Below that, the offer or deadline isn’t clear in the body, so lead with the discount and cutoff time instead of burying them.

Rebrand or name change

Use this for a new company name, logo, or positioning that changes how customers should refer to or find you.

  • State the change and the effective date in the first sentence.
  • Add one sentence explaining what doesn’t change, such as the product, the support team, or the pricing.
  • Note what the reader needs to update on their end, if anything, such as bookmarks, saved logins, or invoices.
  • Skip the CTA. Informing calmly is the goal here, not driving a click.

Subject: We’re now [New name]

Hi [First Name],

Starting [Date], [Old name] is now [New name]. [Why, one honest sentence].

What doesn’t change: [product/support/pricing — name what’s actually true].
What to update on your end: [bookmarks, saved logins, invoices — if anything].

Questions? Reply to this email.

Want more personality? Try:

  • Own the awkwardness: “Yes, we know, everyone’s going to call us the old name for six months. We’ll survive.”
  • A light self-aware close: “New name, same chaos behind the scenes, don’t worry, that part’s staying consistent.”
  • Reply bait: “Reply if it’s weird. We’ll agree with you.”

What to watch: unsubscribe rate. Healthy is under 0.5%. Above that, the change felt sudden, give more lead time next time.

Pricing, hours, or business policy change

Use this for anything that changes the terms someone signed up under, a price, your hours, a cancellation or return window.

Updating a privacy policy or terms of service instead? Those often carry specific legal notice requirements. This template isn’t a substitute for legal review, see our guide on legal requirements for email marketing for what applies to your situation.

  • State exactly what’s changing and the effective date in the first sentence.
  • Add one sentence on why, if you can share it honestly.
  • Note what the reader needs to do, if anything, before the effective date.
  • Include a support contact. This type generates more replies than any other announcement email.

Subject: Your [service] pricing changes on [Date]

Hi [First Name],

Starting [Date], [the exact change — e.g., your plan moves from $X to $Y per month]. [Why, one sentence, stated directly].

What this means for you: [the specific impact — nothing to do, or a specific action needed].

Questions? [Support email or link].

What to watch: unsubscribe rate. If it’s above 0.5%., it might be that too little notice was given, so try moving the effective date higher in the email.

Event or webinar

Use this for a scheduled, attendance-based event with a registration step.

  • Lead with the date, format (in person or online), and the single benefit of attending.
  • Include a registration link as the one CTA.
  • Add a short agenda or speaker line if it strengthens the case to attend.
  • Send a follow-up reminder 48 hours before, matching the timing table below.

Subject: [Event name]: [Date]

Hi [First Name],

Join us for [Event name] on [Date] ([format]). [The one thing you’ll walk away able to do].

[Register now] → [link]

And again, you can send a reminder:

Subject: [Event name] is in 2 days

Hi [First Name],

[Event name] starts [Date] at [Time] ([format]). [One-line reminder of the benefit, restated briefly].

[Register now] → [link], if you haven’t already.

What to watch: click-to-open rate. Below 6.4%, it’s a weak case for attending, sharpen the one-sentence benefit.

Company milestone or business update

Use this company announcement email template for a growth number, an anniversary, or a general update with no specific action attached.

  • Lead with the number or fact itself, not the buildup to it.
  • Add one sentence of context on what it means for the customer, not just the company.
  • Thank the list if that’s genuine to the news.
  • Skip the CTA. This type exists to build trust, not drive a click.

Subject: [The number or fact]

Hi [First Name],

[Lead with the fact itself — e.g., “We shipped our 10,000th order this week.”] [What this means for you specifically, not just for us].

Thanks for being part of it.

What to watch: open rate, directionally only. Healthy is around 36%. This type usually has no CTA, so there’s no click to measure, treat it as a trust signal, not a conversion metric.

How to write an announcement email subject line that people will open

The biggest subject line mistake in announcement emails is treating them like a promotional email that needs a hook. A promotional subject line teases because there’s often nothing to say until the reader opens it. An announcement usually has the actual news right there, so hiding it defeats the point.

  • Name the news, don’t tease it. “New hours starting March 1” beats “Big changes are coming.” “We’re now Meridian Studio” beats “Exciting news!”
  • Let it filter. A specific subject line lets someone who doesn’t care skip it without missing anything urgent.
  • Set accurate expectations. The reader should know what’s inside before opening, not just that something happened.
  • Exception: events can lean on urgency. “Save your seat” still names the exact action, so it doesn’t lose specificity the way a vague teaser does.

Getting this right doesn’t have to start from a blank page, either. SiteGround Email Marketing now offers AI-generated emails right inside the New Campaign flow: pick “Announcement” as your starting point, answer a few quick questions about your business and this specific update, and you land in the Campaign Builder with a subject line, preheader, and body already drafted.

Build with AI" screen showing selectable email types (Promotional, Newsletter, Announcement, Welcome, Event invitation) and a text field to describe a campaign

When and how often to send it

Two questions decide the send plan for any announcement: 

  1. How much of a deadline is attached
  2. How personally the news affects each subscriber. 

The first drives sequence length. The second drives who hears about it first.

For single-send announcements, there’s no deadline to build toward, so one email says everything that needs saying: a rebrand, a policy change, a milestone. For multi-email sequences, there’s a date the reader could miss, so the send builds toward it with a heads-up and a reminder: a launch, an opening, a sale, an event.

Single-send announcements

TypeWho hears it firstTiming
Rebrand or name changeFull list at once (partners get an early heads-up)Day the change goes live
Policy, pricing, or hours changeOnly the customers affected~30 days before it takes effect
Company milestone or updateFull listStandalone, low frequency

Multi-email sequences

TypeSequence lengthFirst sendLast reminder
Product or feature launch2–3 emailsActive users or beta listNon-openers, 3–5 days later
Store opening or new location2–3 emailsLocal or geo segment3–5 days before opening
Seasonal sale or promotion2–4 emailsVIP or loyalty segment (early access)Urgency reminder as deadline nears
Event or webinar3–4 emailsFull list or interest segment48 hours before

Once you’ve mapped out a sequence like the ones above, most of it comes down to scheduling, not automating. SiteGround Email Marketing’s segments let you group your VIP or loyalty list, your local or geo audience, or your active users, then schedule one campaign to that group now and a second campaign to the full list a few days later, covering the staggered releases in the table above. 

True automation in the product is trigger-based: it fires when someone joins a group, so it’s the better fit for an ongoing case, like a rebrand explainer that should reach every new subscriber from now on, rather than a one-time push to a list you already have. 

For a targeted reminder to people who didn’t open the first send, check the campaign’s Recipient Activity report, manually group the openers, and send the follow-up to everyone else.

What metrics to watch for each type of announcement emails

Which metric to check depends on what the email was for. A sale and a rebrand don’t succeed the same way, so grading both by open rate or click-through rate misses what actually happened in each case.

TypeWatch this metricWhyRed flag
Product or feature launchClick-through rate to the launch pageThe goal is driving traffic to a specific actionHigh opens, low clicks: the subject line oversold the news
Store opening or new locationClick-through rate to the directions or map linkThe goal is getting people to show upHigh opens, low clicks: unclear location or date
Seasonal sale or promotionClick-to-open rateYou already earned the open through urgency; the question is whether the offer converts once readBelow-average click-to-open rate: the offer or deadline isn’t clear in the body
Rebrand or name changeUnsubscribe and reply volume, not clicksThere’s often no CTA. Success means the change landed calmlyA spike in unsubscribes or replies: a timing or framing issue
Policy, pricing, or hours changeUnsubscribe rate and support inquiriesSame logic. The goal is informing without alarmingA spike in either: not enough lead time given
Event or webinarClick-through rate to the registration linkOne clear action, easy to isolateHigh opens, low registration clicks: a weak case for attending
Company milestone or business updateOpen rate or click-to-open rate, directionally onlyThere’s nothing to click. This is a trust signal, not a conversion metricNot applicable

If there’s no CTA, don’t grade the email on clicks.

Match the format, the deadline, and the metric: that’s your announcement email

Seven types, seven templates, one rule underneath all of them: match the format to the news, the sequence to the deadline, and the metric to the goal. Skip that last part and you’ll spend a week refreshing your open rate for an email that was never supposed to get clicks in the first place.

None of that requires a second tool bolted onto your inbox. SiteGround Email Marketing helps you draft the first version with or without AI, lets you group your list into segments, and lets you schedule each send in advance, so the only thing left to decide is what your news actually is.

[58]

Frequently asked questions about announcement emails

What’s the difference between an announcement email and a newsletter?

An announcement email covers one specific piece of news and often stands alone or in a short sequence, while a newsletter is a recurring update covering several smaller items at once. If the news needs its own subject line and its own send timing, it’s an announcement, not something to fold into your next scheduled newsletter.

Should you combine a product launch and a sale in the same email?

Combining them usually weakens both messages, since a launch email needs to build credibility for something new while a sale email needs to create urgency around price. If you want to launch with a discount, say so directly in the launch subject line, such as “[Product] launches today, 20% off through Friday,” rather than sending two competing calls to action in one email.

Does a store opening email need a special offer attached?

No, though it helps. If you’re building excitement without discounting, lead with the location, date, and what makes this opening different, and let the map link drive the first visit instead of a coupon.

How long should an announcement email be?

Short enough to read on one screen without scrolling, typically 50 to 150 words in the body. Announcement emails work because they deliver one piece of news clearly, not because they explain it exhaustively.

AI for email marketing campaigns: 6 steps from idea to launch

Marketer holding a laptop next to icons for content, ads, automation, and A/B testing, with a growth chart and progress ring representing AI-driven marketing results.

Using AI for email marketing comes down to six moves: pick a goal, research the message, generate the content, send it, test it, and read the results back into the next one. Follow them, and AI does real work at each stage instead of just window dressing the send.

Key takeaways:

  • Run AI for email marketing as six steps, in order: goal, research, content, execution, testing, measurement.
  • Set one measurable goal before you generate any content, not after.
  • Generate 10 to 15 subject line variants, then pick and edit rather than send the first draft.
  • Never send an AI copy without a human edit pass first.
  • Test two or three variants on a small segment before a full send.
  • Feed each campaign’s results into the next one’s goal and research step.

What is AI for email marketing?

AI for email marketing means AI tools handle specific tasks inside a campaign: research, drafts, send times, or performance data. 

A person still sets the goal, picks the audience, and checks that the copy sounds like the brand. AI handles what sits around those decisions: faster research, more draft variants than one person could write alone, and patterns in the past send data that would otherwise take hours to spot.

That distinction matters because AI works best as an assistant at each stage of a campaign, not a replacement for it. 

The 6 steps to run AI for email marketing

Here’s the order that actually works, start to finish.

Step 1. Set your goal and audience

Every campaign starts with one measurable email marketing goal, not “increase awareness,” but something like “get 50 newsletter sign-ups from a landing page by month’s end.” Vague goals produce vague AI output, since the model has nothing specific to write toward.

Use a structured prompt to lock in the goal and audience before you generate a single line of copy:

PromptWhat it’s for
“List the top 3 pain points for [audience description], specific to [product or offer].”Surfaces the pain point your content should lead with
“Write a one to two sentence positioning statement for [offer], aimed at [audience].”Gives every later prompt a consistent angle
“Based on [audience] and [pain point], what funnel stage is this campaign for: awareness, consideration, or decision?”Sets the tone and CTA strength for content generation

Run all three prompts before moving to Step 2. Skipping this step is the single most common reason later drafts read generically: the AI never learned who it was writing for.

Step 2. Research your audience and message with AI

With a goal in hand, use AI to widen the research, not start it. Ask for objections a skeptical reader would raise, competing messages they’ve already seen, and language patterns from your own past campaigns that worked. This produces raw material, not final copy.

Don’t skip the old-fashioned part either: picture an actual person on your list, how they talk, what they’d roll their eyes at, what would actually get them to click. AI can widen your research, but it still doesn’t know your audience the way you do.

Match the research to the funnel stage from Step 1. Awareness-stage needs objection handling and category education; decision-stage needs pricing objections and comparisons. 

For instance, a welcome email to a brand-new subscriber needs research on “why should I care about this brand at all,” while a follow-up email to someone who already asked about pricing needs research on “why buy now instead of waiting.” One generic prompt for every campaign is how AI output ends up sounding the same across all of them.

Step 3. Create content and creative assets with AI

This is where AI drafts the actual assets: subject lines, body copy, and first-pass visuals. Ask for more options than you need so you actually have a range to pick from, say 10 to 15 subject lines, rather than accepting the first one AI hands you. 

Not every part of an email needs AI, or editing, the same way. Working through a campaign in the order you’d actually build it:

Email partAI’s roleHuman’s role
Subject lineGenerate 10 to 15 variantsPick the best one, tighten the wording
PreheaderDraft a version that matches the chosen subject lineConfirm it doesn’t just repeat the subject
Body copyWrite the first full draftPass for brand voice and factual accuracy
VisualsGenerate or suggest a first optionCheck it fits the brand and the message
CTASkipWrite directly; this is where conversion nuance lives

Treating this table as a fixed rule, not a suggestion, is what keeps an AI-assisted campaign from reading like it wasn’t edited at all.

SiteGround Email Marketing’s new “Generate with AI” option makes working through this table even easier. An interviewer agent asks for a business name, industry, audience, a summary of the email, look and feel, and tone. It reflects those answers back to you in a short summary, and once you hit Generate, it hands you a draft with the subject line, preheader, and body already filled in, ready for the edit pass each row above calls for.

AI assistant email generator form filled out for a lemonade stand promotion, showing fields for business name, business type, email summary, language, style, and audience, with a Generate My Email button.

Step 4. Send the campaign

By this point you have your edited copy ready to send. Whether it came from the AI generation flow in Step 3 or a template you built by hand, the send itself works the same way: review the final draft, confirm it against your goal and audience, and send once a person has signed off. 

Most email platforms let you schedule that release for a specific date and time instead of sending immediately (including SiteGround Email Marketing with the Send later option in Campaign Builder), separate from anything an AI generation flow does. 

Send Campaign modal in SiteGround Email Marketing showing recipient selection, sender name and address fields, and a highlighted Send Later scheduling option with date and time pickers.

That review moment in Campaign Builder is the right point to catch what’s easy to miss under a deadline:

  • Every link in the email has been clicked and tested, not just visually checked
  • Sender name and reply-to address are set correctly
  • A test send to yourself looks right on both desktop and mobile
  • Unsubscribe link and compliance basics are in place

SiteGround Email Marketing handles unsubscribe links and email authentication automatically, so this checklist is about what’s still on you.

Step 5. Test before you launch

If you want to be even more data-driven about it, ask AI to generate two or three variants of your subject line or opening line, then send each to a small segment of your list before you commit to a full send. 

Take a summer sale email, for example. 

  • Variant A, “20% off everything this weekend,” leads with the discount. 
  • Variant B, “Only 6 hours left,” leads with urgency. 
  • Variant C, “Our summer picks are here,” leads with no framing at all. 

A small segment split, say 500 people out of a 10,000-person list, shows which one actually gets opened before the rest of the list gets whichever one wins.

AI’s job here stops at generating the options; which one wins gets decided by actual opens and clicks, not a prediction.

Step 6. Measure and optimize

Match the metric to the goal you set in Step 1:

  • Sign-up or download goal → track conversions on the landing page itself, not just clicks to it
  • Sales goal → track click-through to the product or checkout page, then check your store’s own sales data for that window, since email tools don’t always tie revenue directly to a specific send
  • Engagement or re-activation goal → track open rate and click rate, since that’s what re-activation actually looks like

Open rate and click rate are useful as diagnostics either way: a low open rate points back to the subject line from Step 3, a low click rate with a decent open rate points back to the body copy or the offer itself. But neither should be the goal unless the goal in Step 1 actually was engagement.

Feed the results back into the next campaign’s Step 1 and Step 2 prompts: which subject line pattern won, which pain point got the most clicks. This is what makes six steps a repeatable process instead of a one-off and it’s exactly what turns individual campaigns into an actual email marketing strategy rather than a series of unconnected sends.

Types of AI email marketing tools to know before you pick one

Most “best AI email marketing tools” lists are vendor roundups. The categories underneath them matter more than any single name, since tools inside each category are largely interchangeable for the job:

CategoryWhat it doesWhen you’d use it
Generative content toolsDrafts subject lines, body copy, and visualsStep 3, content creation
Predictive and analytics toolsScores likely engagement or churn, flags send-time patternsStep 2 research and Step 6 measurement
List segmentation toolsGroups subscribers by behavior or attributes for targeted sendsStep 1 audience definition and Step 5 testing
Email-specific automation toolsSubject-line testing, scheduling, send-time logic built into the sending platformStep 4 and Step 5, email specifically

What to consider before you start

AI output is only as good as the data behind it. If your past campaign data is incomplete or your audience research is stale, AI will confidently generate content based on the wrong assumptions rather than flag the gap itself.

Keep a person in the loop at these points specifically:

  • Does the draft actually reflect your brand voice, or just a generic version of it? (Step 3)
  • Would you send this exact subject line to your own inbox? (Step 5)
  • Does the pattern you’re feeding back into the next campaign hold up, or is it one good result being read as a rule? (Step 6)

AI ethics in marketing covers where automated decision-making needs a person in the loop in more depth, particularly around targeting and personalization choices.

Common mistakes to avoid

Three mistakes account for most underperforming AI email campaigns:

  • Publishing AI drafts unedited. The table in Step 3 exists specifically to prevent this: some tasks need a human finishing pass every time.
  • Skipping goal-setting and jumping straight to content generation. Without Step 1’s specific goal, AI has nothing concrete to write toward, and the output reads generically as a result.
  • Ignoring data quality. Feeding AI incomplete or outdated audience data produces confident, wrong output rather than a flagged gap.

Put these 6 AI marketing campaign steps to work

Whether you’re creating a single email or a full campaign, the process is the same: start with your goal, let AI do the heavy lifting, and keep a human reviewing the parts that matter. SiteGround Email Marketing hands you the segments and scheduling for Steps 4 and 5, so you’re not duct-taping three different tools together to send one campaign.

Now go write down that one measurable goal, before you let any AI near a subject line.

[58]

Frequently asked questions about AI for email marketing 

How do you use generative AI for email marketing campaigns?

Generative AI for email marketing campaigns works best for drafting, not deciding: subject line options, first-pass body copy, and creative variants that a person then edits and approves before anything goes out.

What are the best AI email marketing tools?

The best AI email marketing tools fall into four categories: generative content tools, predictive and analytics tools, list segmentation tools, and email-specific automation tools, with the right choice depending on which stage of the campaign you’re working on.

Will AI-generated emails hurt my deliverability?

AI-generated emails don’t hurt deliverability on their own; spammy patterns do, generic subject lines, no personalization, and unedited copy that reads like a template. The human edit pass in Step 3 and the checklist in Step 4 exist to catch exactly that before you send.

Is AI email marketing worth it for a small business?

AI email marketing is worth it for a small business specifically because it removes the time cost of research and first drafts, not because it replaces strategy or judgment, both of which still need a person setting the goal and reviewing the output.