Newsletter Service vs. Substack Pro Writers: Which Should B2B Firms Pick?

Substack Pro was never for B2B firms

Substack Pro was an invitation-only program that paid selected individual writers cash advances — publicly reported figures ranged from $25,000 to over $100,000 — in exchange for an 85/15 revenue split in year one, stepping down to the standard 90/10 split. It was not an advertising program. It was not a business newsletter service. It was a talent retention play for individual creators who already had audiences.

The program was scaled back significantly after 2022. Substack had announced early Substack Pro deals for writers including Glenn Greenwald, Heather Cox Richardson, and Matt Taibbi — individual journalists and commentators with established audiences who could be persuaded to move to the platform. The economic logic was creator economics, not B2B client retention.

B2B firm owners sometimes cite “Substack Pro” when what they actually mean is “hiring a freelance writer who runs or has run a Substack.” That is a legitimate arrangement but has nothing to do with the Substack Pro program. It is independent contractor hiring, priced at independent contractor rates. The distinction matters because it changes what you are actually buying: a person’s labor, billed monthly, with all of the continuity risk that implies.

The third thing B2B owners sometimes mean is “publishing our firm newsletter on Substack as a platform” rather than on a firm-owned ESP. That is a platform choice, not a talent-hiring choice, and it has its own set of tradeoffs around list ownership and compliance that the rest of this page addresses. For the broader production landscape, see Newsletter Content.

Who actually owns the audience

When a writer runs a newsletter on Substack under their own account, subscribers follow that writer’s Substack publication — not the firm that paid for the content. If the writer leaves, the subscriber relationship stays with the writer. If the firm wants to migrate those subscribers to a firm-owned ESP, it needs the writer’s cooperation to export and transfer the list. If the writer declines or the contract ended badly, the firm has no claim.

This is not a hypothetical risk. It is the structural reality of how Substack accounts work. Consider the concrete scenarios:

• Writer runs the Substack under their own account, byline, and brand. The audience is the writer’s. If your firm’s name appears in the publication, it appears as a sponsor or employer — the subscriber is following the writer. This is the norm for journalism-style Substacks. For a law firm trying to build client retention through a newsletter, this is the opposite of what the newsletter is for.
• Writer runs the Substack under the firm’s account name. Better: the firm created the Substack account, so the subscriber CSV is accessible to the firm. But Substack is still the platform, sending from a Substack subdomain or custom domain — which affects deliverability trust differently than a firm-owned domain and ESP. The writer can still leave and the firm has to find a replacement who can maintain continuity.
• Firm owns the ESP, writer provides copy only. Best structure for list ownership. The firm sends from its own domain, the list lives in its own account, and the writer’s departure is a content continuity problem, not a list-loss problem. This is the same structure a done-for-you newsletter service uses.

A done-for-you newsletter service like NaaS operates exclusively in the third structure: the list lives in the firm’s ESP (Mailchimp, Kit, ActiveCampaign, or the firm’s existing CRM email tool), the email sends from the firm’s domain, and the firm owns the subscriber asset from day one. The service provides editorial labor; the firm owns the infrastructure.

On Substack specifically: Substack does allow list export. The practical issue is not technical; it is relational. If a writer built 2,000 subscribers over two years writing under their name on Substack, those subscribers signed up for that writer, not for the firm. Export the CSV and you have a list of people who may not recognize the firm’s name in their inbox. That is a deliverability and re-engagement problem on top of the cost of migrating platforms.

What it actually costs over 12 months

The cost comparison between a done-for-you newsletter service and a Substack-style independent writer is not close. A solo Substack writer with relevant B2B and industry knowledge costs $3,000 to $8,000 per month for ongoing newsletter production. Mid-tier freelancers with niche expertise run $4,000 to $6,000/mo. Known names or writers with proven B2B newsletter track records charge $10,000/mo or more. NaaS is $297/mo, flat, with the first four editions free.

The 12-month totals: a solo writer at $3k/mo runs $36,000/yr. At $5k/mo, $60,000/yr. At $10k/mo, $120,000/yr. NaaS at $297/mo is $3,564/yr.

The gap reflects what is being priced. An independent freelance writer is pricing their time, their expertise, their client management overhead, and their market rate as a solo operator. They are not a service; they are a contractor. The rate reflects that they could be billing someone else for those hours. There is nothing wrong with that structure — it is just expensive, and the cost does not include what the firm still has to provide: ESP infrastructure, deliverability monitoring, compliance review for regulated content, and a backup plan if the writer goes on leave or takes a competing client.

A done-for-you newsletter service prices differently because it provides the infrastructure, the workflow, and the editorial labor as a single product. The economics of a service business are not the economics of a solo contractor. That is why the number looks so different.

The compliance gap regulated industries miss

Law firms, financial advisory practices, and insurance agencies operate under marketing communication rules that require archive access, pre-publication review capability, and in some states explicit recordkeeping of client-facing communications. Substack provides none of these controls. An individual Substack writer, unless specifically contracted and equipped to support them, provides none of these controls either.

The specific requirements vary by profession and jurisdiction, but the pattern is consistent:

• Law firms. The ABA Model Rules and most state bars treat client newsletters as attorney advertising. Rule 7.2 and its state equivalents require that advertising be retained for a specified period (two years in most states; longer in others). A newsletter sent via Substack and not archived in the firm’s document management system is a compliance gap. If a client later claims the newsletter contained a specific representation, the firm needs the archived version to defend it.
• Financial advisors. FINRA Rule 2210 classifies client newsletters as retail communications and requires pre-use filing with FINRA for certain content, plus recordkeeping for three years. An RIA under SEC jurisdiction is subject to the Books and Records Rule (Rule 204-2), which requires retention of all written client communications. Substack is not an SEC-recognized archival system. The firm’s compliance officer cannot audit a Substack publication the way they can audit an ESP with export and search capabilities.
• Insurance agencies. State insurance departments regulate agent advertising. Most state DOI regulations require that advertisements be filed or retained for examination. An email newsletter from a Substack account, sent from a Substack subdomain, is still an advertisement subject to those rules. The agent is responsible for compliance regardless of what platform the advertisement moved through.

A done-for-you newsletter service that sends from the firm’s own ESP solves this structurally: every edition is archived in the firm’s account, searchable, exportable, and available for compliance review. Substack provides none of that. An individual freelance writer using the firm’s ESP can satisfy the technical requirement, but the compliance review layer — checking that the copy does not cross into advice, contains required disclosures, and uses the correct qualifying language — still falls back on the firm unless the service explicitly covers it.

When a Substack writer is the right call

The case for hiring a Substack writer is real, but it applies to a specific context: a solo practitioner or individual founder who wants to build a personal brand audience on Substack’s network, has no regulatory archive obligations, and is prepared to pay independent-contractor rates for ongoing production.

Substack’s built-in network has genuine value for individual creators. The “Recommendations” feature, cross-publication subscriber exchanges, and Substack’s email-deliverability infrastructure all serve the use case of an individual growing a public audience. If you are a solo financial coach (not a registered advisor), an independent management consultant building a thought-leadership platform, or a solo attorney experimenting with a public audience before starting a firm — and you want to grow subscribers beyond your existing network — Substack’s discovery layer actually helps.

The cases where a Substack writer is a defensible choice:

• Solo founders building personal brand. One person, one byline, audience growth through Substack’s network. The “brand” is the person, not a firm.
• Creators with existing micro-audiences to monetize. If a solo practitioner already has 500 to 1,000 engaged subscribers on Substack and wants to monetize via paid tiers, hiring a writer to help produce content makes sense at the right volume.
• No enterprise compliance constraints. Unregulated industries, solopreneurs, and creators outside the legal / financial / insurance / healthcare compliance stack can use Substack freely without the recordkeeping exposure.

What these cases share: they are individual-creator economics, not B2B firm economics. The moment you have multiple partners, an existing client list in a CRM, regulatory obligations for communication archiving, or a brand that is the firm rather than a person — the Substack writer path stops making structural sense.

When a service like NaaS is the right call

A done-for-you newsletter service is the right structure for multi-partner firms, firms with existing client and prospect lists in a CRM or ESP, firms in regulated industries, and any firm that needs predictable cost rather than independent-contractor variability.

The structural advantages compound quickly when you map them to a typical professional services firm:

• Multi-stakeholder firms. A three-partner law firm or five-advisor RIA cannot credibly publish a newsletter under one writer’s personal Substack brand. The newsletter needs to represent the firm. That means firm-owned infrastructure, firm-reviewed copy, and firm-branded delivery — all of which a newsletter service provides and a personal Substack writer cannot without structural compromise.
• Existing client lists. Most professional services firms already have a CRM with hundreds or thousands of client and prospect contacts. The goal of a newsletter is nurturing those relationships, not discovering new subscribers through Substack’s network. Firm-owned ESP delivery to a warm existing list outperforms Substack discovery for this use case by a wide margin.
• Regulated industries. As covered in Section 4: legal, financial advisory, insurance, and healthcare firms have archive and disclosure obligations that Substack does not satisfy. A service that sends through a firm-owned ESP with full archive access does.
• Predictable cost. A freelance writer’s rate is a negotiated contract that can change at renewal. Key-person dependency is real: if your writer takes a better-paying client or goes on extended leave, your newsletter stops. A service has built-in redundancy and a fixed monthly rate.

NaaS at $297/mo includes research, drafting, editorial review, and delivery coordination. First four editions are free. For details, see pricing.

The question this comparison is really answering is a content production question: what is the right workflow for a professional services firm to produce a client newsletter, sustainably, at a cost that makes sense, with the right compliance architecture? For the full treatment of all six production paths — including where independent writers fit among the options — see Newsletter Content.