Which pricing and packaging changes would lift Workflows' growth ceilings? #217

Activity

1. Silthus

   added

   wayfinder:research

   on Oct 3, 2026
2. Silthus

   added a parent issue on Oct 3, 2026

   • Map: grow Workflows activation, from first visit to first delivered message #210
3. Silthus

   marked this as blocking on Oct 3, 2026

   • Rank the growth bets and choose which get their own map #219
4. Silthus

   self-assigned this

   on Oct 3, 2026
5. Silthus commented on Oct 3, 2026

   

   Silthus

   on Oct 3, 2026

   OwnerAuthor

   More actions

   Claimed by a Claude Code research worker (Opus 5.5)
6. Silthus

   removed their assignment

   on Oct 3, 2026
7. Silthus commented on Oct 3, 2026

   

   Silthus

   on Oct 3, 2026

   OwnerAuthor

   More actions

   Lane orphaned: the worker's temporary worktree was removed while its sub-agents ran. Unassigned; the conductor redispatches it in a persistent worktree.
8. Silthus

   self-assigned this

   on Oct 3, 2026
9. Silthus commented on Oct 3, 2026

   

   Silthus

   on Oct 3, 2026

   OwnerAuthor

   More actions

   Claimed by a Claude Code research worker (Opus 5.5), redispatch
10. Silthus commented on Oct 3, 2026

    

    Silthus

    on Oct 3, 2026

    OwnerAuthor

    More actions

    Resolution

    Evidence: the code on master and the public pricing pages of PostHog, Customer.io, Loops and Resend. Guesses are marked as guesses. Full findings with sources: https://github.com/Silthus/posthog/blob/research/pricing-packaging/research-pricing-packaging.md

    What the code shows

    • One email is counted three ways: billing counts one per send step, the sending cap counts each to, cc and bcc recipient, and the Reputation tab meter counts one per send.
    • Only email and destinations have a public price. SMS has a usage key but no price, quota or billing view. Push bills and is limited as a destination.
    • A spent email quota blocks every run of a flow that has an email step, even runs that only reach a webhook.
    • The sending tier ignores the plan. Every new team starts at 100 emails a day, below its own 10,000 free emails a month. The tier shows on the Reputation tab only.
    • Reading the code, a send that ends in a provider error, such as an unverified domain, seems to bill. Not yet confirmed by a test.

    Recommendations for billing and leadership

    1. Let a paying team start above the lowest sending tier (guess: tier 1 or 2). Tier 0 caps a team below its free allowance, and Customer.io switchers arrive with a real list. Resend lifts its daily quota on any paid plan. Reputation-driven demotion stays as it is.
    2. Show the sending allowance where it limits someone, for example when picking a batch audience or when a workflow slows down, with the way to raise it.
    3. When a quota runs out, block only the channel that ran out, and show the upgrade path. Today the whole workflow stops without a visible reason.
    4. Count one email the same way everywhere, per delivered recipient, so the cap, the meter and the bill agree. Resend and SES count each recipient.
    5. Charge only for sends the provider accepted. Confirm the failed-send billing with a test first.
    6. Decide a price and a quota for SMS and push, and make the quota check match the bill. A simple option (guess): price both as destination dispatches, since the carrier cost sits with the customer.
    7. Review the entry price per email, and lead with "no per-contact pricing". The first paid tier is $3 per 1,000 emails, against $20 for 50k at Resend Pro. PostHog is the only one of the four that does not charge for contacts.
    8. Consider a larger free allowance paid for by a "Sent with PostHog" footer, as Loops does. Removable on paid plans.
    9. Consider bring-your-own sending as a paid lever for Customer.io switchers. A team on its own sending provider carries its own reputation and could skip the shared-pool ramp. This is a separate bet, not a pricing change alone.

    Re-check every guess against real usage data after 2026-11-02, in the private note.

    Security note, ask Michael.
11. Silthus

    closed this as completedon Oct 3, 2026