It might seem simpler, from a product design standpoint, to bundle the newsletter into a platform tier and call it a feature. Signal Intelligence deliberately does the opposite: newsletter subscriptions are completely independent from platform access, in both directions, with no exceptions baked into the billing or entitlement logic.
What independence actually means here
- A newsletter-only subscriber never gains platform dashboard access, signals, or HPI analysis
- A platform subscriber on Starter, Professional, or Enterprise never automatically receives newsletter content unless they separately subscribe
- Detection of which product a customer purchased is handled exclusively through distinct Lemon Squeezy variant IDs — never through string matching or inferred behaviour
Why this matters for trust, not just architecture
Billing logic that conflates separate products is a common source of customer-facing errors — accidental access grants, accidental access removals, confusing invoices. Keeping these systems genuinely independent, down to the database schema, is part of the same discipline that governs every other part of this platform: precision in naming, precision in what's measured, and precision in what any given subscription actually entitles someone to.
What this looks like for future domain-specific newsletters
As new domains launch — Watches, Property, Insurance Intelligence — any future domain-specific newsletter will follow this exact same independence pattern, with its own dedicated variant ID and its own entirely separate entitlement logic.