A marketing and sales team runs a single event on Resonue: one brief on a calendar in January, a room full of booked demos in March, and a pipeline number that traces back to where it started. Between those points, two people make five decisions. Everything else on this page happened on a schedule while they were doing something else.
Priya, the CMO, is bringing her team to a conference in San Francisco on March 12. Six weeks out, she opens the briefs calendar and lays down a High priority brief, "Conference countdown," running February 1 to February 18, with a short window: everyone talks about the event and who's speaking, then goes quiet until the follow-up.
0 */6 * * * UTC, four times a day
The company page, employees, and external voices all see the same brief and the same window. Each one generates their own draft from their own top posts, not a shared template, and Rosa scores it before it goes out. Nobody publishes on their behalf: the draft waits for the person whose name is on it.
What Priya does not do is chase people for confirmations. Four times a day the sweep re-reads the roster, captures whatever went out, and matches it against the brief, so the coverage row on that brief is a count of real posts rather than a list of promises. Twice during the window she looks at it and sends two nudges. That is the whole of her involvement for eighteen days.
0 3 * * * UTC, every night of the window
This is the beat nobody sees and the one that makes the rest work. Every night at 03:00 UTC, the heat on every person who touched a conference post is decayed and recomputed. Someone who reacted in week one and went quiet drifts down. Someone who came back three times in week two climbs. Nobody marks anybody warm and nobody marks anybody cold.
On the eleventh night, a fourth person from Northwind Co. crosses the threshold, and the same run flags the account as a forming buying committee with the four names and their roles on it. It is on the board the next morning. The alternative version of this event is a rep scrolling notifications hoping to spot the pattern.
Theo, an AE, opens the list of people who reacted to the conference posts, already ranked, with the Northwind cluster already flagged. He did not build this list and he did not maintain it. He reaches out to each person individually with Rosa's drafted opener, pulled from the exact post they engaged with, and books a demo slot for every warm reply.
Rosa writes and stops. Theo reads every draft, changes a line in most of them, and sends them himself, one at a time. Nothing left the workspace under his name that he had not read.
Every meeting on the calendar traces back to a name from the conference brief's engager list, not a walk-up booth conversation. Working the room cold would have been worth maybe five demos. Theo walks in with forty already booked.
The deals opened at the event roll onto the pipeline board as influenced pipeline, still tagged to the Northwind committee and the conference brief that started it. By the end of the month, the team can point to a single number and a single brief it came from, not a vague sense that the event "went well."
The briefs calendar, priority levels, engager tracking and the two schedules running underneath this walkthrough are shipped today. Marketing, Revenue Ops, and Sales each use the same data differently.
Resonue is in early access. We're working with our first design partners now.