Resonue
a feature launch scenario / two weeks, one brief

One new feature, two weeks, every voice announcing it at once.

The announcement stops depending on the all-hands. Every voice gets the brief, a window, and a draft in their own words. Then something that runs on Monday morning tells the team which of the accounts they already know quietly came back to look. Here is what that does to the quarter's pipeline.

priya briefs-> watch.agent-> scoring.agent-> brief.agent-> Halt-> the AM writes back
Learned at the all-hands
  • Voices hear the feature shipped at the weekly all-hands, the one moment nobody is about to write a post
  • A few mention it eventually, scattered over the following weeks, each with a different story
  • Most never post about it at all
  • A churned account looks at three of the posts and nobody in the company ever knows it happened
$0Pipeline attributed to the launch. Not zero impact, zero measurable: nothing connects a post to a deal.
Briefed, drafted, synchronized
  • One brief with what shipped, who it helps, and a two-week window
  • Every voice, sales reps included, posting the same beat at the same time
  • Churned and current accounts re-engaging surface in Monday's email without anyone hunting for them
  • New logos, returning churns, and upsells, all traced back to the brief
$300kInfluenced pipeline, attributed to one brief on the board
Monday morning dana and priyathe decision, made once

Dana ships it, Priya briefs it

Dana, Head of Product, walks over to Priya's desk: the feature the roadmap promised is live. Instead of waiting for Friday's all-hands, Priya opens the briefs calendar and writes it down once, properly: what the feature is, the problem it kills, who feels that problem. High priority, a two-week window starting tomorrow. That one brief is now the single source for everything the company will say about the launch.

Same day each voicewrites and publishes their own

Every voice finds the brief waiting, sales included

No launch thread to scroll back through, no "wait, that shipped?" three weeks later. The brief sits on the shared calendar, and it's right there in Compose when each voice on the roster comes in to write, sales reps included. Full context, benefits included, and a window that says: now, not whenever.

The two-week window watch.agent0 */6 * * * UTC, counting coverage

Fifteen days of the same beat, in twelve different voices

Each voice generates their own Rosa draft anchored to the brief: written in their own register, built from their own best-performing posts and the themes they already own, and aimed at the ICP the workspace defined. Not twelve copies of a press release, twelve people saying the same true thing their own way. Nobody publishes for them: Rosa writes the starting point and the person whose name is on the post decides what goes out.

Priya does not chase anyone for a confirmation. Every six hours the sweep re-reads the roster and matches what went out against the brief, so the coverage row is a count of real posts. She reads it twice in fifteen days and nudges the two people who have not moved.

Effect one scoring.agent0 3 * * * UTC, then Theo decides

New logos: the feature is the reason to say yes

The synchronized wave puts the feature in front of accounts that stalled after a demo months ago. Engagers on the launch posts heat up, and on the night a fourth Northwind name crosses the threshold, the 03:00 run flags the account as a forming buying committee, with the names and the roles. Theo, an AE, works the brief's engager list by heat with Rosa's drafted openers. For some prospects the feature is the missing piece. For others it's simpler: proof the product is alive and moving.

Effect two, the following Monday brief.agent0 8 * * 1 UTC, in the inbox

Churned accounts see the reason they left is gone, and the email says so

Bellwood Group churned a year ago, and the board still remembers: the account sits in the Churned column. During the window, two Bellwood names engage with the launch posts. Nobody is watching the Churned column, and nobody needs to be: assembling the week, the brief agent looks specifically for accounts already marked Customer or Churned that have started engaging again over the last seven days, and Bellwood is in Monday's email under that heading.

The account manager does not cold-call a lost customer. She reads a line in an email she did not ask for, and replies to a door that reopened on its own. What she does next is entirely hers: there is no automated churn alert firing at the account, no sequence starting, no message going out in anyone's name.

Effect three, the same email brief.agentsame run, same section

Upsells: current customers discover what they're not paying for yet

The quietest segment on the engager list turns out to be the most profitable: existing customers. Accounts sitting in the Customer column start engaging with the launch posts, and they surface in the same weekly section for the same reason, because a known account went from silent to active inside seven days. That is how their account managers learn they didn't know the feature existed.

Interest shown in public becomes the easiest expansion conversation of the quarter. One honest note on this beat: the signal lives in the weekly brief today. Seeing it as a flag on the pipeline board itself is on the roadmap, not in the product.

End of the window the teamthe number, and what to do with it

Three streams, one board, one brief

New logos, reopened churns, and expansions all land on the pipeline board as influenced pipeline, tagged to the same launch brief. The team closes the window with a number, not a feeling. And one effect never shows up on the board: Dana's product team watched their feature turn into pipeline in real time. The next launch brief writes itself.

1New feature, announced once, properly
2 wksOf coordinated posting, not months of trickle
$300kInfluenced pipeline, tagged to one brief
1 teamProduct, watching their work become revenue

Your next feature deserves better than the all-hands.

The briefs, brief-anchored drafts, engager tracking, account stages, and the Monday email that surfaces re-engaging customer and churned accounts are all shipped today. See the launch event walkthrough, or how Marketing, Revenue Ops, and Sales each run the same data.

coverage countedevery 6 hours committees flaggednightly, 03:00 UTC the re-engagement emailMondays 08:00 UTC

Resonue is in early access. We're working with our first design partners now.