Vendor guide · Creator sequences · verified pricing
Kit Pricing Guide
The audience flywheel perfected — for creators, educators, and newsletter businesses.
Kit (formerly ConvertKit) optimizes the grow-nurture-launch loop with commerce hooks near the editor. Verify tiers on the official Kit pricing page.
Who this guide is for
This guide is for creators, educators, and newsletter operators who found Kit through the recommendation circuit — and for founder-led SaaS teams who keep being told to run their newsletter in Kit while wondering what to do about trials, seats, and dunning. You will find the verified tier structure, an honest map of the creator flywheel's strengths, and the specific boundary where a creator tool should stay a creator tool.
The free Newsletter plan deserves careful reading before any paid decision: 10,000 subscribers with broadcasts included sounds like permanent shelter, but automations are locked on it. Teams that build an entire growth motion on broadcast cadence discover the lock exactly when a sequence would have been the right instrument — usually during a launch.
If lifecycle automation is already revenue-critical — trial nurture, failed-payment recovery, expansion messaging — the SaaS boundary section below will save you a quarter of tag spaghetti. If your business is courses, paid newsletters, and audience products, most of those warnings will never apply, and Kit's economics will look as good as its reputation suggests.
Holding a twelve-month list projection against every guide's tier table remains the only honest way to compare — especially here, where the free plan's subscriber ceiling and the paid plans' entry band sit far apart.
The creator flywheel
Lead magnet to nurture sequence to launch to evergreen pitch — visual sequences, landing pages, tagging rules, and a cross-promotion network keep creator businesses fast and understandable. Commerce features handle ebooks, cohorts, and paid newsletters without extra plugins.
What makes the flywheel work is editorial focus: the product is built around people who publish on a schedule and sell to their own audience, so the common paths — magnet, sequence, pitch, launch — are first-class citizens rather than configurations. A creator shipping a course four times a year should feel at home on day one.
Visual sequences
Tag-triggered email sequences with delays and conditions cover the classic lead-magnet-to-pitch arc without requiring a canvas full of engineering concepts.
Landing pages and magnets
Signup pages and incentive emails ship inside the platform, so list growth experiments do not wait on a developer or a second tool.
Creator commerce hooks
Digital products, paid newsletters, and cohort sales attach near the editor — monetizing the list without exporting it into a separate store first.
Cross-promotion network
Creator-to-creator recommendations add a growth channel that media buyers rarely model and newsletters rarely document — worth tracking like any other source.
For the audience this product targets, those four cards compound. The rest of this guide asks a narrower question: what happens when the product being launched is software with trials and invoices rather than a cohort with a cart.
One more strength worth naming for evaluators comparing tools on paper: the tagging model stays legible to whoever writes the emails. When the person building the sequence is also the person shipping the issue, a system that respects editorial attention — rather than demanding schema design — wins on velocity for years, not weeks.
The SaaS boundary
No subscription objects, no dunning playbooks, limited event branching — trial and billing workflows become tag spaghetti at scale. Founder-led SaaS companies sometimes run Kit for the newsletter while lifecycle lives in a SaaS-native tool: a legitimate split, not a single-platform story. And because every subscriber counts including cold ones, list cleaning is a cost discipline here. Compare creator-versus-lifecycle axes in our verified pricing snapshot.
The failure mode is specific and common: trial-started becomes a tag, trial-expiring becomes another tag, payment-failed becomes a third, and every branch reads combinations of tags that only one person on the team understands. It works at fifty subscribers per cohort and ossifies at five hundred, precisely when dunning starts mattering to the numbers.
Kit is genuinely excellent at what it was built for. The boundary is not a criticism of the product — it is a category distinction. Creator newsletters and SaaS lifecycles share the inbox and almost none of the event vocabulary, which is why splitting the stack across the two is a normal architecture rather than an admission of defeat.
Counting rule to internalize early: every subscriber counts toward limits, including cold ones. On a free plan that reaches 10,000, growth feels free until paid bands scale with list size — then two years of unengaged signups show up as a line item. Cleaning is budgeting here.
Pricing tiers and the billing axis
| Plan | Entry price | Subscriber basis | Reality check |
|---|---|---|---|
| Newsletter | $0 — free to 10,000 subscribers | Broadcasts included; automations locked | A large broadcast runway with no sequence capability — the lock arrives when launches need it |
| Creator | From $39 per month | Up to 1,000 subscribers at entry, scaling with list size | Automations unlock here; the real entry cost for anyone running sequences |
| Creator Pro | From $79 per month | Up to 1,000 subscribers at entry, scaling with list size | The upper tier on the same band — for teams outgrowing Creator's feature set, not its size |
| Counting rule | Applies to every plan | Every subscriber counts, including cold | Growth pushes the band whether or not the new cohort has opened anything |
The axis is subscribers, uniformly, with a twist worth stating plainly: the free plan's generous 10,000-subscriber ceiling applies to broadcasts only, while paid plans enter at the 1,000-subscriber band and scale upward from there. Free optimizes for list size without automation; paid optimizes for sequence capability with list size as the meter. Reading either number without the other produces bad decisions in both directions — "free covers 10k, so paid must too" is the most expensive misreading on this page.
Because every subscriber counts, including cold ones, list hygiene functions as a cost control rather than a nice-to-have. A creator importing aggressively from launches and podcasts will hit band steps built entirely of people who never intended to hear from the weekly edition again. Sunset policy — with genuine removal, not just a suppression tag — keeps the band aligned with the actual audience.
The paid jump itself is honest: $39 to unlock automations at the 1,000-subscriber band is cheap against the revenue a working launch sequence returns, and $79 for Creator Pro targets feature depth rather than a ransom for the same list. The bill only surprises teams who treat the free tier's 10,000 ceiling as a permanent pricing promise. Verify current bands on the official pricing page before any list-growth sprint, since scaling with list size means today's comfortable band is a snapshot, not a contract.
Model it this way: project subscribers at twelve months, discount for the cleanup you should be running anyway, then read both Creator and Creator Pro at that band. If the Pro premium is smaller than the launch revenue of one course sale, the tier decision is already made; if neither fits the unit economics, the free broadcast plan plus a sequence-capable migration target deserves a look instead.
Where it fits in the five-stage lifecycle
For an audience business, the five stages line up with how creator revenue actually arrives: welcome converts a magnet, nurture builds the relationship between launches, convert runs the launch itself, retain keeps the paid cohort or subscriber, win back resurrects the lapsed — and because every subscriber counts, win back doubles as a billing decision, not just an engagement one.
For SaaS, welcome and nurture translate if you accept tag-based modeling; convert breaks first, because a trial is not an offer with a cart; retain breaks second, because seats and usage are not cohort memberships. Win back remains doable but should be re-read as churn recovery with your own decay logic rather than Kit's audience instincts.
The workable split for founder-led software: keep stages one, two, and five — the editorial relationship — wherever the newsletter lives, and put convert-and-retain billing stages on a platform whose native events are invoices and subscriptions.
Draw that boundary before the first launch on the new arrangement, not after the first double-send. One system of record per stage — the rule that keeps a split stack from becoming two stacks arguing over the same subscriber.
Automation depth: what you can and cannot build
Kit's sequences are visual, tag-driven, and quick to ship — deep enough for editorial and launch automation, deliberately shallow on event-driven subscription logic. The honest limits below are about object models, not node counts.
Build freely on paid plans
Lead-magnet welcome sequences, tag-triggered nurture, launch countdowns, link and tag conditions, form and landing-page automations, and broadcast-to-sequence hybrids.
Build with external plumbing
Trial and billing events pushed in as tags from your product or billing system — with you owning mapping, retries, and the documentation nobody writes until something breaks.
Out of reach natively
Invoice retrial branches, seat-expansion triggers, plan-change messaging tied to real subscription objects, and dunning that distinguishes a soft decline from a dead card.
Locked on the free tier
Every sequence capability above sits behind the paid gate. The Newsletter plan's 10,000-subscriber runway is real — for broadcasts — and automation absence is the trade.
- Automations are unavailable on the free Newsletter plan regardless of list size.
- Every subscriber counts, including cold ones — bands scale with cruft if cleanup slips.
- Tag-based branches grow unreadable past a few conditions; there is no subscription state to branch on instead.
- Paid bands start at the 1,000-subscriber entry and scale with list size — project past launch spikes, not to them.
- Creator commerce covers creator offers; SaaS upgrade attribution needs properties and discipline you bring yourself.
Honest framing: for creator launches and editorial nurture, these limits rarely bite — the object model matches the business. They bite when a SaaS team tries to make invoices behave like course purchases.
There is also a sequencing discipline worth adopting on paid plans: because sequences and broadcasts share one subscriber base, a heavy launch calendar plus weekly editorial cadence is a fatigue question before it is a pricing one. Preference tags and quiet periods cost nothing to configure and protect the list that the band prices.
Where Kit fits for SaaS teams
Kit is a creator and newsletter platform at heart: visual sequences, landing pages, tags, and commerce hooks tuned to the grow-nurture-launch loop, with a free Newsletter plan that carries broadcasts to 10,000 subscribers. Subscription teams should treat trial and billing workflows as an integration project rather than assume newsletter tags can stand in for product state.
For teams that want one decision instead of a split: choose by where the revenue event lives. Course sales and paid newsletters point at Kit; trial expiries and failed cards point at the billing-native platform. Businesses that genuinely have both usually run both — with the boundary documented before the first flow crosses it.
Common mistakes when adopting Kit
- Building the whole growth motion on the free Newsletter plan and discovering mid-launch that automations are locked. Broadcasts to 10,000 are real; sequences are not available at any list size on that tier.
- Reading "free to 10,000" as a pricing promise. Paid plans enter at the 1,000-subscriber band and scale with list size — the two numbers describe different tiers, not a discount cliff.
- Letting cold subscribers accumulate because growth felt free. Every subscriber counts including cold ones; run sunset with genuine removal before the band steps.
- Straightening SaaS trial and dunning logic into tag combinations only one person can debug. If invoices drive the flow, invoices should be the object — not a tag approximating one.
- Skipping cleanup before a band upgrade. Paying a scaled band for a list padded with launch-window lurkers is a self-inflicted invoice; clean first, then upgrade.
- Confusing broadcast fluency with lifecycle coverage. Editorial cadence and event-driven branching are different skills — teams that excel at the first often underestimate the second.
- Waiting for the tag spaghetti to hurt revenue before splitting the stack. The newsletter can stay; move the billing stages while they are still a design choice.
Kit pricing FAQ
What does the free Newsletter plan actually include?
Broadcasts to up to 10,000 subscribers as of the September 2026 snapshot, with automations locked. You can grow and send an editorial newsletter at no cost — you cannot build the welcome, nurture, or launch sequences that the rest of this guide describes. Treat the lock as a scheduling decision: plan the Creator upgrade for the first campaign that genuinely needs a sequence, not for the day the list passes some arbitrary size.
Why does free allow 10,000 subscribers when paid plans start at 1,000?
Because the tiers meter different capabilities. The free plan optimizes for broadcast list size without automation; Creator and Creator Pro unlock automations and enter at the 1,000-subscriber band, scaling with list size from there. There is no contradiction to arbitrage — only a decision about whether sequences are part of your product yet. Verify current band pricing on the official page whenever a growth sprint lands.
Do cold or unengaged subscribers count toward my plan?
Yes — every subscriber counts, including cold ones, on every tier. Unlike rivals that stop billing for the unsubscribed, Kit's axis keeps charging for anyone still subscribed who simply never opens. That makes sunset policy a cost discipline: remove lapsed subscribers genuinely, not just via a suppression tag, and the band reflects your real audience rather than your historical import.
Can Kit handle failed-payment dunning for a SaaS product?
Not natively. There are no subscription or invoice objects to branch on, so payment events must arrive as tags pushed from your billing system — and every branch then reads combinations of those tags. It works briefly at small scale and becomes unmaintainable exactly when dunning starts affecting churn numbers. If dunning is a revenue line item, weight platforms with native Stripe, Paddle, or Lemon Squeezy triggers.
Creator or Creator Pro — which tier makes sense?
Both enter at the 1,000-subscriber band: Creator from $39, Creator Pro from $79, each scaling with list size. Creator covers the full sequence-and-broadcast workflow most solo operators need; Pro targets teams that want the deeper subscriber scoring and reporting tier as their audience operations mature. Run both numbers at your projected band — if the delta is smaller than one launch's margin, the decision is comfort, not cost.
We run a SaaS product but love Kit for the newsletter. Is splitting the stack reasonable?
Yes — it is the standard arrangement for founder-led software with an editorial audience. Keep welcome, nurture, and win-back relationship mail in Kit where the writing and tagging are fast; run trial, billing, and dunning stages on a platform whose native events are subscriptions, so those branches read invoice state instead of approximations. Draw the boundary explicitly — one system of record per stage — so the two halves never both send the same message.