beehiiv

View saved version →

---
name: automation-dropoff
description: Find where subscribers disengage or leave in a beehiiv automation such as a welcome series, and explain why. Use when someone asks how their welcome sequence or an automation is performing, where readers drop off, or why an automation email underperforms.
---

# Automation drop-off

These are instructions for you to carry out now, in this conversation, using the beehiiv tools. Nothing runs in the background.

Walk the automation step by step and find where readers stop engaging or leave.

1. **Find the automation.** If they don't name it, pick the live one that fits (a welcome series usually triggers on signup), and ask when several do.
2. **Walk the funnel.** Get its stats with per-step counts and go through the steps in order: how many reached each email, its open and click rate, and how many unsubscribed there. Compare each email with the one before it. The drop-off point is where opens fall sharply or unsubscribes jump. It is not simply the last email, which always has the fewest readers.
3. **Read the email at the drop-off.** Read it, and the one before it for contrast. Look for what changed: a vaguer subject line, a bigger ask, a shift in tone, or a pitch that comes too early.
4. **Report back.**
   - The drop-off point in one line, with its numbers beside the previous email's.
   - A funnel table in step order: email, reached, open rate, click rate, unsubscribes.
   - The likely cause, quoted from the email.
   - Two or three fixes, such as a rewritten subject line or moving the ask later.

Offer to draft the fixes, and change the automation only if they ask.

View saved version →

---
name: build-segment
description: Turn a plain-language description of an audience into a beehiiv subscriber segment and report how many readers it matches. Use when someone wants to find, group, target, or count subscribers by engagement, tier, signup source, location, custom fields, or behaviour.
---

# Build a segment

These are instructions for you to carry out now, in this conversation, using the beehiiv tools. Nothing runs in the background.

Give the publisher a segment that matches what they meant, and proof that it does.

1. **Check what exists.** List the publication's segments. If one already matches, offer it instead of making a duplicate.
2. **Map each criterion.** Read the segment reference. When the request mentions something only the publisher would track, such as an interest, plan type, or company size, list the custom fields, because conditions on them need the field's ID. If a criterion has no matching field, say so and leave it out rather than approximating it silently.
3. **Resolve vague words.** Terms like "engaged" or "recent" need a number. Pick a sensible default and say which one you chose.
4. **Save and check the size.** Save a dynamic segment with a name that says who is in it, then recalculate it and read the member count. A count of zero, or close to the whole list, usually means a condition is wrong, so re-check the rule before reporting.
5. **Report back.** Give the segment's name, the rule in plain language with one line per condition, and the member count. Mention what they can use it for, such as targeting a post or starting an automation. Creating a segment emails no one.

View saved version →

---
name: edit-post
description: Edit, tighten, or rewrite a beehiiv post in the publication's own voice, or turn notes, a transcript, or an outline into a new draft. Use when someone wants a post shortened, restructured, proofread, rewritten, repurposed, or drafted from source material.
---

# Edit a post

These are instructions for you to carry out now, in this conversation, using the beehiiv tools. Nothing runs in the background.

Leave the publisher with a better draft that still sounds like them, and a clear account of what changed.

1. **Find the post.** If they don't name it, check recent drafts, and ask when more than one fits.
2. **Learn the voice.** Skim two or three recent published posts: how they open, how they sign off, how sections are labelled, and how long paragraphs run. Keep their recurring openers, sign-offs, and section labels word for word, because readers recognise them.
3. **Edit.** Change only what the request needs and leave strong blocks alone, so the publisher's own sentences survive. Read the post again right before you change it, so the edit uses the current version; stale content causes errors. When a draft feels long, the usual culprits are throat-clearing intros, hedges, and asides, so cut those before cutting substance.
4. **Drafting from source material:** use the structure their posts already follow and take facts only from the source. Mark anything you would have to invent as `[TK: what's needed]` for them to fill in.
5. **Report back.** List what you changed and why, give the old and new word counts, and link the draft in the editor. Say plainly that it is still a draft and that they publish it from beehiiv.

View saved version →

---
name: media-kit
description: Build a sponsor-ready media kit for a beehiiv newsletter from its real audience, engagement, and growth numbers. Use when someone wants a media kit, a sponsor one-pager, a rate card, or audience stats to pitch advertisers.
---

# Media kit

These are instructions for you to carry out now, in this conversation, using the beehiiv tools. Nothing runs in the background.

Give the publisher a one-page kit they can send to a sponsor today, where every number can be checked.

Gather audience size and engagement for the last four weeks, growth over recent months, where web readers are and what they read, acquisition sources, and past advertisers from ad network reports.

Sponsors weigh reach, engagement, fit, and trust, so lead with those:

- **Headline:** subscribers, open rate, click rate.
- **Audience:** who reads it, drawn from the publication's description and top content, and where readers are.
- **Growth:** the change over the period, as a number and a percentage.
- **Content that performs:** two or three top posts.
- **Past sponsors:** if there are any.
- **Placements and rates:** `[TK]` unless the publisher gives them.

Quote numbers exactly, with their time period. Label website figures as website visitors, because they are not the same people as email subscribers. beehiiv doesn't hold age, income, gender, or job title unless a custom field does, so leave those out or add a `[TK]` line for the publisher to fill. Invented demographics are the fastest way to lose a sponsor's trust.

Write it so it pastes cleanly into a doc or a pitch email.

View saved version →

---
name: onboarding
description: Audit a new beehiiv publication, show what is set up and what is missing, and finish the setup the publisher picks. Use when someone has just signed up, has a new publication, or asks how to get started or set up their newsletter.
---

# Onboard a new publication

These are instructions for you to carry out now, in this conversation, using the beehiiv tools. Nothing runs in the background.

Take a new publication from sign-up to ready for its first send, doing only what the publisher chooses.

1. **Audit first, change nothing.** Find the publication, and ask which one if there are several. Check the workspace's plan before anything else, because several write tools need a paid plan and knowing that up front beats finding out from a failed call. Then check what is set up and what is missing: name, description, tags, sender and email settings; a first post, drafted or published; logo, brand colours and site theme; welcome email automation; subscribe form; website pages; subscriber count; the author profile; the referral program and recommendations; paid tiers. If they already publish elsewhere, moving their existing posts in is an item too. A custom domain, a custom sending domain, and a subscriber import cannot be done through the tools, so mark them "do it in beehiiv" and link the step-by-step help article for each, found with the documentation search, with `?utm_source=mcp&utm_medium=skill` added to the link. Never pretend to do them.
2. **Show one checklist.** Give a single table grouped into "Should do now" (what a newsletter needs before its first send, in this order: settings, subscriber import if they are moving from another platform, logo, subscribe form, website, welcome email, first post) and "Can do later". The subscribe form and website come before the first post because they bring in the first readers. Columns: item, status (done, missing or partly), and who does it (I can do it here, needs a paid plan, or do it in beehiiv). Keep it short enough to scan.
3. **Let them choose.** Stop and ask which items they want done. Change nothing in the account until they pick.
4. **Do only what they picked.** Ask only for facts the account cannot supply, such as their niche, audience, send cadence, or a site URL to take branding from. Anything that emails readers stays a draft: automations stay inactive and posts stay as drafts. Report what changed, with a link to where they can review each item. If you drafted a welcome email, state plainly that it stays off and sends nothing until they turn it on in the beehiiv automation editor.

Some failures are expected:

- A plan gate is correct behaviour. Mark that item "needs a paid plan" once and move on. Never retry it.
- Before you edit a post's content, read it again so the edit uses the current version. Stale content causes errors.
- On a website built with the simple builder, some site tools are not available yet. Say so, and leave the website items for beehiiv.

View saved version →

---
name: performance-report
description: Analyse how a beehiiv newsletter's recent posts performed and explain what drove the difference, especially subject lines. Use when someone asks how their newsletter or posts are doing, which subject lines or topics worked best, wants a performance report for a period, or asks what to write next or for a content calendar.
---

# Newsletter performance report

These are instructions for you to carry out now, in this conversation, using the beehiiv tools. Nothing runs in the background.

Tell the publisher which posts worked, why, and what to do next, using only their own numbers.

Find the publication first. If the account has several and the request doesn't say which, ask. List the published posts in the period (default: the last 30 days, or the last ten sends if that is sparse), fetch their stats, and get publication-level stats as the baseline.

Judge subject lines by open rate and content by click rate. Compare each post with the publication's own average rather than industry benchmarks, because audiences differ too much for outside numbers to mean anything. With fewer than five sends, say the sample is too small to call a pattern.

Look across the strongest and weakest posts for what separates them: subject line shape (numbers, questions, specificity, length), topic, and format. Name a pattern only when at least two posts support it.

Shape the answer like this:

- A one-line headline with the single most useful finding.
- A table of posts sorted best first: subject, send date, open rate, click rate.
- Two to four patterns, each naming the posts that show it.
- Two or three concrete next steps, such as a weak subject line rewritten in the winning style.

When they ask what to write next, or for a content calendar, turn the next steps into a dated plan at their usual cadence, inferred from recent send dates. Check scheduled and draft posts first so the plan doesn't duplicate work already under way. Give each issue a date, a working title, a subject line in the style of their best performers, and the past post or pattern it builds on. Include one clearly labelled experiment so they keep learning.

Quote every figure exactly as the tools return it.

View saved version →

---
name: revenue-report
description: Report what a beehiiv publication earned over a period and where the money came from, across the ad network, paid subscriptions, boosts, recommendations and digital products. Use when someone asks about revenue, earnings, income, ad earnings or monetisation.
---

# Revenue report

These are instructions for you to carry out now, in this conversation, using the beehiiv tools. Nothing runs in the background.

Give an accurate earnings breakdown with the detail a finance check needs.

Get the publication's earnings for the requested period, defaulting to the last four weeks, or the exact dates if they give them. For ad network revenue, also list the individual ad reports in the same window, so each advertiser, post and amount is visible along with whether it has been paid.

Shape the answer like this:

- The total for the period, with the exact dates it covers.
- A table by source with the amount and its share of the total. Show sources at $0 rather than dropping them, so the reader knows they were checked.
- Ad network detail by advertiser, split into settled and pending.
- One or two observations, only where the data supports them, such as a single advertiser making up most of ad revenue.

Use the figures exactly as returned, and do not forecast or estimate.

View saved version →

---
name: start-here
description: Work out where a beehiiv publisher is up to and suggest the one task to do first. Use when someone asks what you can do, what the beehiiv tools can do, where to start, or what to do next, without asking for a specific task.
---

# Start here

These are instructions for you to carry out now, in this conversation, using the beehiiv tools. Nothing runs in the background.

Give the publisher one recommended next task, why it suits them, and an offer to start it.

1. **Check the account, change nothing.** Find the publication, and ask which one if there are several. Check the subscriber count, published posts, paid tiers, earnings, and live automations.
2. **Work out where they are.** Pick the stage that fits best: starting from zero (no posts sent, few subscribers), moving from another platform, publishing but not growing (posts going out, subscriber count flat), or earning (paid tiers, ad network, or sponsors). If the account has no posts and no subscribers, ask whether they already have a newsletter or list somewhere else.
3. **Recommend one task.** Give one line on why, using their own numbers.
   - **Starting from zero or moving from another platform:** get the newsletter ready for its first send (onboarding).
   - **Publishing but not growing:** see which posts worked and what to write next (performance-report).
   - **Earning:** see where the money comes from (revenue-report).
4. **Offer the rest.** List at most three other things you can help with later, one line each, and ask what they would like to do. Run nothing until they choose. Mention a paid plan only if the recommended task needs one.

View saved version →

---
name: unsubscribe-spikes
description: Find when a beehiiv newsletter lost unusual numbers of subscribers and trace each loss to the post that likely caused it. Use when someone asks why they are losing subscribers, what caused an unsubscribe spike, or which emails made people leave.
---

# Unsubscribe spikes

These are instructions for you to carry out now, in this conversation, using the beehiiv tools. Nothing runs in the background.

Show the publisher when they lost readers and the likely reason, so they don't repeat it.

1. **Find the spikes.** Get the daily subscriber count for the period (default: the last three months). A typical day's change is the baseline; look for days where the count fell, or grew far less than usual.
2. **Match them to posts.** Get stats for the posts sent in the period and compare each post's unsubscribe rate with the typical rate. A spike usually lands on the send day or the day after.
3. **Read the culprit.** Read each post that lines up with a spike. The cause is often in the body, such as a price change, a paywall move, a sponsor-heavy issue, or an off-topic piece, rather than in the subject line.
4. **Report back.**
   - A headline naming the worst spike: the date, the post, and how many readers left.
   - A dated table of posts with unsubscribes and unsubscribe rate, spikes marked.
   - For each spike, the likely cause, quoted from the post. Present it as the most likely explanation, not proof, because unsubscribes don't record a reason.
   - One or two concrete changes, such as how to announce the same news with less loss.

If nothing stands out, say so. A steady list is a finding too.

View saved version →

---
name: upgrade-campaign
description: Build a campaign that turns engaged free readers into paid subscribers on beehiiv, as a segment of likely upgraders plus a draft email sequence. Use when someone wants to grow paid subscriptions, upsell free readers, or reach engaged readers who haven't upgraded.
---

# Upgrade campaign

These are instructions for you to carry out now, in this conversation, using the beehiiv tools. Nothing runs in the background.

Create a segment of engaged free readers and a short draft automation that invites them to upgrade. Everything stays a draft for the publisher to review, because turning an automation on emails real readers and they should approve the copy and timing first.

1. **Check there is something to sell.** List the active tiers and their prices. If no active tier has an enabled price, stop and say so: there is nothing to upgrade to yet.
2. **Build the segment.** Target free, active subscribers with strong recent engagement. A sensible default is the free tier, active status, and an open rate of 50% or more over the last 90 days. Use the user's criteria instead if they give any. Give it a name that says what it is for, such as "Engaged free readers (upgrade campaign)".
3. **Build the sequence.** Create an automation that starts when a subscriber enters that segment, with three emails a few days apart:
   - **Value:** what paid readers get, tied to the topics these readers already open.
   - **Proof:** why it is worth it, answering the price objection directly.
   - **Offer:** a clear ask naming the tier and its price.

   Write each email in the publication's own voice, so skim one or two recent posts first. Keep each one short, with a single call to action linking to the publication's `/upgrade` page.
4. **Report back.** Give the segment's name and rule, the automation's name, and each email's subject line. State plainly that the automation is a draft and that nothing sends until they review it and turn it on in the beehiiv automation editor. The segment trigger only enrols readers who join the segment after the automation goes live, so tell them to add the readers already in the segment once it is on, and link https://www.beehiiv.com/support/article/21526057683991?utm_source=mcp&utm_medium=skill.