What does a done-for-you newsletter service include?
Seven deliverables, who owns each one, and what stays yours.
What are the seven deliverables?
"Done for you" is a loose phrase. Some services mean "we write the words." Others mean "we run the whole thing." Before you compare quotes, check which of these seven the service actually does. Use this as a checklist in the sales call.
- Strategy. Who the newsletter is for, what it promises, what it should lead to (replies, meetings, renewals), and how often it goes out. This is written down once and revisited every quarter.
- Editorial calendar. A rolling plan of issues, usually four to eight weeks ahead, with a working title and an angle for each one.
- Writing. Interviewing the people inside your company who know the subject, drafting, editing, and the subject line and preview text.
- Design. A reusable email template, image and chart handling, and a check of how each issue renders on phones and in dark mode.
- Sending. Building the issue in your email platform, test sends, scheduling, and the technical setup that keeps mail out of spam.
- List management. Signup forms, welcome emails, segments, handling unsubscribes and bounces, and cleaning subscribers who have gone quiet.
- Reporting. A short monthly read-out: what went out, what readers did, what the team will change next month.
A writing-only service covers items two and three. A full service covers all seven. Neither is wrong, but the price and the amount of your own time involved are very different. If you are weighing those prices, see how much a B2B email marketing agency costs.
Who does what?
The cleanest way to read a proposal is to ask, for each task, who holds the pen and who gives the final yes. The table below is Sawa's split. Other services draw the line in different places, which is exactly the thing to ask about.
| Task | The service | You |
|---|---|---|
| Define the reader and the promise | Proposes, writes it down | Decides |
| Choose the sending cadence | Recommends from your content supply | Approves |
| Plan the next six issues | Drafts the calendar | Adds what the company is seeing |
| Interview subject matter experts | Runs the interview, 20 to 30 minutes | Names the right people, shows up |
| Write and edit each issue | Drafts and edits | Reviews, in one or two rounds |
| Subject line and preview text | Writes options | Picks one, or trusts the service |
| Build the email in your platform | Builds, tests, schedules | Keeps the platform account in your name |
| Domain authentication (SPF, DKIM, DMARC) | Specifies the DNS records | Adds them, or gives IT access |
| Welcome email and signup forms | Writes and sets up | Approves the copy |
| Unsubscribes, bounces, complaints | Monitors and handles | Nothing, unless a pattern appears |
| Clean quiet subscribers | Proposes a rule, runs it | Agrees to the rule |
| Monthly report | Writes it | Reads it, decides what changes |
| The list itself | Works inside it | Owns it |
Two rows deserve a closer look. Domain authentication needs changes to your DNS records, which only someone with access to your domain can make. Mailchimp notes that most records update within a few minutes but can take up to 48 hours, so this is a week-one job, not a launch-day job. And the last row is the one that matters most: the list is yours, in your account, from day one.
What does a month of work look like?
Once the setup is done, a done-for-you newsletter runs on a repeating monthly rhythm. Here is what that looks like for a newsletter that goes out every two weeks. A weekly send doubles the writing steps but keeps the same shape.
- Week 1: plan and interview. A short planning call. The service confirms the next two issues, books one or two interviews with your experts, and sends the questions ahead of time.
- Week 2: draft, review, send issue one. The draft arrives with the subject line options. You review within two working days. The service builds the issue, sends a test to you, and schedules it.
- Week 3: draft issue two, check the list. Second draft goes out for review. The service checks bounces, complaints and unsubscribes from issue one, and flags anything unusual.
- Week 4: send issue two, report, adjust the calendar. Issue two goes out. The monthly report lands, with one or two proposed changes. The calendar rolls forward another month.
The first month is different, because the setup has to happen before the rhythm starts. Sawa aims to be fully running within four weeks. On Sawa's most recent project (a survey, a five-email welcome sequence and a lead magnet for a fractional CFO firm's weekly newsletter for founders) the first weeks ran like this. Day 1: kickoff call, ten questions on voice, audience and the first action a subscriber should take. Day 4: first drafts of every email and the lead magnet in one shared folder, with a visual map of how the emails route. Day 7: the client's review back, in one email thread. Day 11: second version applied. Day 12: everything built in the client's Beehiiv account. Day 15: a 15-minute walkthrough call. Day 17: automations switched on and the old welcome email retired. For comparison, Storyarb's public process page says a first draft typically arrives within four to five weeks of kickoff and that each piece gets two rounds of feedback. Timelines like that are normal. If a service promises a first issue in week one, ask what they skipped.
What do you still own?
"Done for you" does not mean "decided for you." Three things stay with the client no matter how much is handed over.
Voice and position
The service can learn how you talk and match it, but what the company believes, which topics it will take a side on, and which it will stay out of, are your calls. Expect to be asked about this in the first weeks, and expect the answers to be written into a short voice guide you can read.
Approvals
Every issue should pass through someone at your company before it goes out. One round of review is enough once the voice is settled. Agree on a turnaround up front, because a draft that waits a week for sign-off is the most common reason a cadence slips.
The list and the platform
The subscribers, the signup forms, the sending domain and the platform account should all be in your name. Sawa works inside the client's existing email platform for this reason. If a service moves your list into their own account, you have rented a newsletter, not built an audience you own. That is the point of the engage stage: the content keeps readers, and the readers stay yours.
What does "sending" actually involve?
Sending sounds like pressing a button. It is the part most likely to go wrong, because mailbox providers now set rules for anyone who sends in volume. Google's sender guidelines say that senders of more than 5,000 messages a day to Gmail accounts must authenticate with SPF, DKIM and DMARC, must support one-click unsubscribe, and should keep the spam rate reported in Postmaster Tools below 0.10% and never let it reach 0.30%. Google also recommends fulfilling unsubscribe requests within 48 hours.
In plain words: SPF, DKIM and DMARC are three DNS records that prove your emails really come from your domain. One-click unsubscribe is a header in the email that lets Gmail show an unsubscribe button at the top of the message. A spam rate is the share of recipients who mark a message as spam. A done-for-you service should set all of this up, check it monthly, and tell you if a number moves. If a service cannot explain these in a sentence each, that is a red flag worth adding to your list of questions to ask before hiring.
What does list management include?
A list is not a static file. People change jobs, mailboxes close, and some readers simply stop opening. List management is the routine of keeping the list honest. Kit, for example, marks a subscriber as cold after 90 days without an open or click, or after 30 days for people who joined recently, and notes that cold subscribers still count toward your bill. Every platform has its own version of this. The service should propose a rule for re-engaging and then removing quiet subscribers, get your agreement, and run it on a schedule.
The tradeoff is real. Removing quiet subscribers shrinks the number on the dashboard, which can feel like a loss. Keeping them raises your cost and, if they start marking you as spam, hurts delivery to the readers who do want you. Agree the rule once, in writing, so nobody has to re-argue it every quarter.
What is usually not included?
Scope lines vary by provider, so ask. Common gaps:
- Paid ads to grow the list. Sawa, for example, does not run paid ads. Some services do; it is usually a separate line.
- Distribution beyond email. Storyarb's page says plainly that it does not yet handle distribution. Repurposing issues into LinkedIn posts is sometimes included, sometimes not.
- Website and landing page builds for signup, beyond the form itself.
- Platform fees. The email tool's own subscription is almost always billed to you directly.
- Ad hoc requests. Several services, Storyarb among them, state that one-off requests outside the plan are not accepted.
If you need list growth as well as the newsletter, you may be looking for a different kind of partner. Our comparison of a newsletter agency and a growth agency covers that choice.
What should the monthly report show?
Ask for the report before you sign. A good one fits on a page: which issues went out, how many people received them, what readers did (clicks, replies, meetings booked or forwarded), list growth and list losses, delivery health (bounces, complaints, authentication still passing), and one or two proposed changes. Open rates belong in the appendix, not the headline, because mail apps load images and inflate them. The report is where the service earns the next month, so a vague one is a sign to ask harder questions.
About this guide and its sources
This is Sawa's description of what a done-for-you newsletter service should cover, based on how Sawa runs its own engagements. The responsibility table and the monthly rhythm are Sawa's framework, not an industry standard. The sending and list-management figures come from Google's and Kit's own documentation; the agency process facts come from Storyarb's public how-it-works page.
- Google Workspace Admin Help: Email sender guidelines
Supports the 5,000 messages a day threshold, the SPF, DKIM and DMARC requirement, one-click unsubscribe, and the 0.10% and 0.30% spam rate figures.
- Google Workspace Admin Help: Email sender guidelines FAQ
Supports the recommendation to fulfil unsubscribe requests within 48 hours.
- Kit Help Center: The subscriber profile page and status
Supports the 90-day and 30-day cold subscriber definitions and the note that cold subscribers count toward billing.
- Mailchimp: Set up email domain authentication
Supports the statement that DNS records usually update within minutes but can take up to 48 hours, and that authentication requires a domain you own.
- Storyarb: How it works
Supports the two rounds of feedback per piece, the first draft within four to five weeks of kickoff, and the statements on ad hoc requests and distribution. Used as an example of one agency's public process, not as a benchmark.
Frequently asked questions
How often should the newsletter go out?
Cadence is the first thing a service will ask you about. Answer three questions and get a starting schedule.
Need help with this? See how Sawa handles newsletters and ongoing content, or book an intro call.