Comparison
Niche and HeyNews both run editorial workflows for one person, but they serve different writers and ship different output. HeyNews is built for newsletter operators with an existing publishing rhythm; it learns the writer's voice from a five-to-ten-issue archive and publishes natively to Beehiiv or Kit. Niche is built for writers publishing across multiple formats (LinkedIn, X, Substack, Instagram, long-form, plus a newsletter) who need primary-source signal and an agent-callable workflow. Pick HeyNews if your output is one newsletter and you have an archive to learn from. Pick Niche if you publish across formats or need a multi-source signal scan.
The lanes diverge on three axes.
Output format. HeyNews produces newsletter issues, end to end, with the layout, section curation, and ad placement that newsletter operators expect. Niche produces platform-native pieces across LinkedIn, X, Substack, Instagram, long-form essay, image cards, and reels, with a newsletter section as one of several output formats. A writer whose entire stack is one newsletter is served well by HeyNews; a writer publishing across formats needs the multi-platform pipeline.
Signal source. HeyNews reads RSS feeds, social handles the writer subscribes to, and Chrome-save bookmarks. Niche reads multi-source primary signal: web search across the beat, Reddit and Hacker News for community signal, Wikipedia attention spikes for pre-news interest patterns, SEC EDGAR for primary corporate disclosures, Congress.gov for legislative activity, OpenFEC for campaign finance. A writer whose beat is well-covered by RSS gets what they need from HeyNews; a writer whose beat requires primary-source coverage (defense procurement, capital markets, policy, biotech) gets material from Niche that the RSS-only path misses.
Agent surface. HeyNews exposes one MCP skill (subscribe-newsletter). Niche exposes 21 workflow-grained MCP tools covering the full pipeline. A writer running an agent-driven workflow (Claude Desktop, Claude Code, Cursor) can drive Niche end to end without opening the dashboard; the HeyNews surface is currently shaped for the human-in-the-dashboard path.
A writer's ICP fit follows from these three. Newsletter operators with an established voice and a curated RSS-feed input fit HeyNews's strengths cleanly. Writers running a beat across formats, drawing from primary sources, who want their agent to handle the workflow, fit Niche's shape.
Three things, all newsletter-specific and well executed.
Voice training from a publisher archive. HeyNews ingests five to ten of the writer's previous newsletter issues and learns their tone, structure, transitions, and section conventions. The drafts that come back sound like the publisher on a good day, not like a generic AI. For a newsletter operator with a mature archive, this is a real edge; voice-from-archive is harder to get right than voice-from-prompt, and HeyNews ships it well.
Native publishing to Beehiiv and Kit/ConvertKit. HeyNews pushes finished issues straight into the publisher's existing send pipeline, with the formatting and delivery handled end to end. Importing from Substack, Ghost, Mailchimp, and LinkedIn Newsletter is also supported. For a newsletter operator on these platforms, the integration depth is real.
Smart Select and AdApt. Smart Select auto-picks stories per section against audience relevance (replacing the manual curation step). AdApt rewrites sponsor ad copy in the publisher's voice (replacing the manual ad-localization step). Both are useful workflow accelerators for newsletter operators with a section-shaped issue and sponsor relationships.
Niche does not ship native Beehiiv push (manual handoff today), does not auto-curate sections in the issue-shaped sense (Niche's pipeline is angle-per-piece, not section-per-issue), and does not rewrite sponsor ads. These are areas where HeyNews's product is more directly fitted to the newsletter-operator use case.
Three things, all driven by the multi-platform + multi-source + agent-surface shape.
Multi-platform output from one picked angle. When a Niche user picks a story and an angle, the system produces LinkedIn text posts, X threads, long-form essay sections, Instagram carousel slides, image cards, and reels in a single pass. The same editorial through-line stays consistent across surfaces. A writer publishing on LinkedIn + X + Substack + Instagram from one beat gets all four formats from one workflow.
Primary-source signal beyond RSS and social. Niche reads SEC EDGAR for corporate disclosures, Congress.gov for legislative activity, OpenFEC for campaign finance, Wikipedia attention spikes for pre-news interest patterns, in addition to web search, Reddit, and Hacker News. For beats where the most-cited story has not yet been picked up by mainstream RSS (defense procurement filings, capital-markets disclosures, congressional movements), the primary-source layer surfaces material the RSS-only path will miss.
21-tool agent surface. Niche's MCP server exposes workflow-grained tools across discovery, angle proposal, drafting, rendering, brand-profile management, and publish. Every tool returns a structured trust block (source attribution, faithfulness score, ungrounded-claim list, source-diversity check). Writers running agent-driven workflows can run Niche end to end from Claude Desktop, Claude Code, Cursor, or any MCP-compatible client. HeyNews's one-skill surface (subscribe-newsletter) covers a narrower job.
Pricing as of 2026-05-29 (HeyNews from heynews.co pricing page; Niche from the locked pricing model).
| Tier | Niche | HeyNews |
|---|---|---|
| Free trial | 3-day trial, 1,500 credits, no card | 14 days OR 5 issues |
| Entry | Creator $39/mo (8K credits, full editorial pipeline, all output formats) | Hobbyist $39/mo |
| Lower mid | Studio $99/mo (30K credits, all modules, 5 brand profiles, 1 PAT) | Starter $99/mo (10 issues / month) |
| Upper mid | (Studio covers this band) | Pro $299/mo (30 issues / month) |
| Top | Operator $299/mo (80K credits, unlimited PATs + brands, auto-top-up) | Team $499/mo (60 issues / month) |
| Failed runs | Free (auto-refund via reservation pattern) | Counted against issue cap |
| Output formats | LinkedIn + X + Substack + Instagram + long-form + image cards + reels | Newsletter issues |
| Signal sources | Web + Reddit + HN + Wikipedia + SEC EDGAR + Congress + OpenFEC | RSS + social handles + Chrome-save |
| Agent surface | 21 MCP tools (full pipeline) | 1 MCP skill |
Two model differences worth naming:
Unit shape. HeyNews's plans gate on issue count (10 / 30 / 60 issues per month). Niche's plans gate on credits (8K / 30K / 80K credits) with transparent per-action cost. For a newsletter operator who ships a predictable number of issues per month, HeyNews's unit model is clean. For a writer whose monthly mix of LinkedIn posts, X threads, long-form essays, image cards, and reels varies, Niche's credit unit fits the workload better.
Failed-runs-are-free. Niche's reservation pattern means a run that errors out costs nothing; credits are reserved at session start and refunded on failure. HeyNews counts attempts against the issue cap. For workflows that fail occasionally (any agent-driven workflow, any pipeline with external data fetching), the failed-runs-free guarantee meaningfully changes the unit economics.
HeyNews, in most cases. The product is purpose-built for the newsletter-operator workflow: voice from archive, section curation, native send to Beehiiv or Kit, sponsor ad rewriting, issue-shaped pricing. A writer publishing one newsletter weekly or biweekly, with an existing archive and sponsor relationships, fits HeyNews's strengths cleanly.
The exception runs through signal sources. A newsletter operator whose beat depends on primary-source signal (a defense-policy newsletter that needs Congressional Quarterly + SEC disclosures, a capital-markets newsletter that needs primary filings) may find that even with HeyNews's polished newsletter workflow, the RSS-only input doesn't reach the underlying signal. For that operator, Niche's signal layer plus a Substack export covers the same job at the cost of giving up HeyNews's section-curation polish.
Niche, by design. A writer publishing on LinkedIn + X + Substack + Instagram from the same beat needs an editorial pipeline that produces all four formats from one picked story. HeyNews's output is newsletter-shaped; a multi-format writer using HeyNews still needs separate tools for the social surfaces.
The pairing question (use HeyNews for the newsletter, use Niche for everything else) is technically possible but practically high-friction: two separate signal stacks, two separate angle workflows, two separate brand-voice surfaces. Most writers in the multi-format ICP will get more leverage from one editorial pipeline that handles every surface than from stitching two together.
Niche is the editorial-intelligence layer for writers publishing across formats. For writers whose primary surface is one newsletter, HeyNews's purpose-built newsletter-operator product is a strong fit and often the better choice for that specific use case. The competitive lanes are real but narrower than "either-or"; the right tool depends on the writer's output mix and signal needs.
To go deeper: read what we mean by editorial intelligence, why a content desk runs the whole loop, or the agent integration surface.
Keep reading