From a merged change to a conversation.

Cheerblast reads what your product team changes, decides who each change matters to, writes one message per person, and waits for your approval before anything goes out.

Request access

Five steps, every time.

Follow one change, an Excel export, from the merge to the message logged on the account.

  1. It reads what changed

    Merged code, release notes and tickets, turned into plain words: what changed, and what someone can do now that they couldn't before.

    GitHubGitLabLinearJiraRelease notes
    In plain wordsReady to review

    You can now export any table to Excel in one click.

    What changed
    An Export to Excel option on every table.
    What someone can do now
    Send a report to finance without copying rows by hand.
    Who can get it
    Pro and Team plans, once the Excel export switch is on.
    PR #4821LIN-882Release note 2.41
  2. It decides who it matters to

    Who has it: the plan, integration or switch. Who uses that part of your product. Who asked for it. Which open, lost or stalled deals it answers. For a fix, whether that account's own data actually changed after the deploy.

    StripeFeature flagsPostHogMixpanelZendeskIntercomHubSpotSalesforce
    Export any table to ExcelMatched against 435 accounts
    yes no
    Example: how one change is matched to five accounts
    AccountHas itUses itAskedDealOutcome
    Acme LogisticsPro plan Yes.Switch on Yes.Exports weekly Yes.Ticket #2231 No.None open Message
    NorthwindLost in March Yes.In the trial No.Not a customer Yes.Lost reason Yes.Lost deal Message
    HalcyonTeam plan Yes.Switch on Yes.Copies tables by hand No.No request Yes.Stalled upsell Message
    BrightlinePro plan No.Switch off Yes.Exports weekly Yes.Feature request No.None open WaitNot live for them yet
    KestrelTeam plan Yes.Switch on No.Never opens tables No.No request No.None open Left alone
    And 430 more accounts with nothing new from this change. They hear nothing.
    FixDuplicate invoice lines

    Did this account's own data change after the deploy?

    VandermeerHad the bug, now cleanMessage to Lena
  3. It writes one message per person

    For the right role in each account, in their language and in the rep's voice, on the channel they read.

    The right roleTheir languageThe rep's voiceTheir channel
    Export any table to Excelat Acme Logistics, in Lisa's voice
    AdminENEmail

    Hi Marc, the Excel export you asked for in ticket #2231 is live for all 40 of your seats. Nothing to set up.

    MTo Marc, IT adminfrom Lisa
    FinanceFREmail

    Bonjour Claire, vous pouvez maintenant exporter n'importe quel tableau vers Excel en un clic, y compris le rapport mensuel des coûts.

    CTo Claire, financefrom Lisa
    Floor teamENIn-app

    Omar, the shift list now goes to Excel in one click. Look for Export at the top right of any table.

    OTo Omar, warehouse leadfrom Lisa
  4. A person approves it

    You pick which updates are worth telling. The rep or account owner approves each message. Nothing goes out unseen.

    You pick the updatesThe rep approves each message
    S
    Sara, NorthwindLost in March: no Excel export
    Waiting for Tom

    Hi Sara, you went with someone else in March because you couldn't export to Excel. As of today, any table goes to Excel in one click. Worth 15 minutes to see it?

    Email from Tom

    Try it: edit the draft, then approve it.

  5. It lands, and is logged

    Email, in-app, Slack Connect, Teams, a personal branded video or a product tour. Every message is logged on the account in your CRM.

    HubSpotSalesforce
    Email In-app Slack Connect Teams Personal video Product tour
    Acme LogisticsActivity
    1. Cheerblast: product update sent to Marc, Acme LogisticsEmail, Excel export, approved by Lisa
      9:02
    2. Cheerblast: product update sent to Claire, Acme LogisticsEmail in French, approved by Lisa
      9:02
    3. Cheerblast: in-app note shown to Omar, Acme LogisticsIn-app, approved by Lisa
      10:15
    4. Ticket #2231 from Marc: export tables to ExcelRequested 12 Aug
      Aug
    A personal video in Halcyon's branding, for Jonas. 0:40

What it reads, and where it lands.

It connects to the places your changes and your customers are already recorded.

What it reads
What changed
GitHubGitLabLinearJira
Who has it
Your plansStripeLaunchDarklyStatsigPostHog
How they use your product
PostHogMixpanelAmplitude
Who asked for it
ProductboardCannyIntercomZendesk
Your deals and accounts
HubSpotSalesforce
cheerblast
Where it lands
To your customers
EmailIn-appProduct toursPersonal videoSlack ConnectTeams
To your reps
CRM tasksSales sequencesAccount review slides
In public
Your websiteDocsSocial clips

An example week.

Illustrative numbers for one team with 435 accounts, not a customer result. Most changes aren't worth telling. The few that are fan out to the accounts and people they matter to.

Example numbers
23

accounts heard about something that changed for them, from their own rep.

412

accounts were left alone, because nothing that week changed anything for them.

Guardrails, built in.

Rules that hold on every message, without anyone having to remember them.

Two a week, at most

No person gets more than two messages a week. A fix to their own ticket is the one exception, and goes out right away.

Excel exportFor Brightline

Not live for them yet. The message is held.

Waits until it's live

If an account doesn't have the plan, integration or switch yet, Cheerblast holds the message until it does.

Read-only on your code

Cheerblast reads your sources. It never changes your code or your product.

412accounts left alone in the example week

Left alone if nothing changed

Accounts a change doesn't affect get nothing at all. No newsletter, no blast, no “in case you missed it”.

Make your next update pay.

For B2B software sales and customer success teams. Your first pilot is free.