A recurring job, every week

Keep every voice posting, and knowwhat each one produced.

Four people posted for three weeks in January and then it stopped. It always stops, and never because anyone refused. It stops because writing from a blank page is work, and because nobody ever showed those four people that it did anything. Resonue removes both reasons.

For whoever owns employee advocacy, and for teams paying content partners. The pillar the other three use cases measure.

Without a brief With Resonue

Launch week, scattered one wave

Monday: the feature ships tomorrow. Everyone needs to be talking about it by Thursday
Tuesday: half the team hasn't posted. The other half is waiting to see what everyone else says first
Thursday: three people post. Generic captions, no shared angle, launch week noise buried in the feed

One brief goes on the calendar Monday morning: angle, tone, and do's and don'ts
Seven people post inside 48 hours, each in their own words
One beat, every voice: the launch lands as a wave, not as noise

Signal · none

3 of 7 Voices posted by Thursday, each with their own generic caption.

Signal · live

7 of 7 Covered inside 48 hours from one brief, each in their own words.

The loop

A window, a draft, a score, and the person's own numbers.

01 Written once

Run comms like a sprint, not a scramble

A brief is what you want talked about, laid on a calendar the way engineering lays out a sprint: for these days everyone is on the launch, for those days it is the customer story. Every brief carries a real window with a start and an end, and a priority, high, medium or low, so when two windows overlap, voices know which one wins. Nobody gets chased. The brief sits on the shared calendar and it is there in Compose when each voice comes in to write.

Date-range briefs, color-coded by priority, on a real calendar
Overlapping windows resolved by priority, not by guesswork
Every post rolls back up to the brief it covered, so you know which brief an engager actually reacted to

02 One click, whenever they sit down

Same brief, a different draft for every voice

One brief goes to the roster. What comes back is not a shared caption to copy and paste. Each voice generates their own starting draft, anchored to the brief but built from their own three best-performing posts and the topics they already own, written in their own register, aimed at the ideal customer profile the workspace defined. Not a template with a different name swapped in.

Priya's draft doesn't read like Theo's, and neither reads like marketing wrote it.

03 Before publish

Score it before it goes out, not after

Paste a draft in and Rosa scores it 0 to 100 against your own data, the topics and the posts that already worked for this brand, broken into topic fit, hook strength, format fit and tone match so the score is an argument rather than a verdict. The goal was never the post that gets 200 likes. It is the post built to land with the accounts already warming up.

The score reads the whole team's history, pooled. The starting draft in step two is the part built from one person's own posts.

04 Mid-window

See who covered it while you can still do something

Resonue matches the posts that actually went out against the brief they cover, so the roster tells you who has posted and who has not, days before the window closes rather than at the post-mortem. For contracted partners it goes further: a cadence, a start and an end date, and a live status, honored, slipping or off contract, with the shortfall and the days of silence counted.

05 The reason it survives week six

Every person gets a page of their own numbers

This is the step that decides whether any of the others still exist in March. Someone who posts four times and hears nothing back stops posting. Someone who can open their own page and see who they reached, how many of them are people the company actually wants, and which of their posts did it, posts again. The program does not survive on enthusiasm. It survives on feedback.

More to come

On the workbench now. None of it is in the product today.

The weekly brief in Slack
A content partner portal
In-product contract management
Trained brand fit model

A worked example

One brief, from the calendar to the follow-up.

An illustrative walkthrough, not a customer story. A team is speaking at a conference in six weeks, and wants the posting around it to be something other than three people remembering on the day.

Six weeks out

A high priority brief goes on the calendar with a short window: everyone talks about the event and who is speaking, then goes quiet until the follow-up. It is written down once instead of re-explained in five separate messages.

During the window

Each voice generates their own draft from their own top posts and scores it before publishing. The roster shows who has covered the brief and who has not, with days left to fix it.

The follow-up

Every post rolls back up to the brief it covered, so you can see which brief an engager actually reacted to. Sales walks into the room with names and roles instead of a badge scanner.

The briefs calendar, priority windows, per-voice drafts, brief coverage and engager tracking in this example are shipped today. The event and the names are made up.

If you pay for some of these voices

A contracted partner is a voice with an invoice attached

Everything on this page applies to content partners, and the program adds the half that money demands: cadence tracked against the contract, honored, slipping or off, a delivery history per partner, a score from 0 to 100 graded A to D with the whole calculation shown, and the accounts each partner's posts actually reached.

Content partners, piloted →

Before
you ask

No, and it is the line we will not cross. Rosa drafts and scores, a person publishes. Nothing goes out under anyone’s name without them reading it first. If you want an autopilot, this is the wrong tool.

The brief sits on the shared calendar with its window and its priority, and it is there in Compose when that person comes in to write. There is no email or notification firing at a voice: it is a place the work waits, not a thing that chases people. The weekly summary email goes to the people on the workspace, not to the voices.

A brief covers the whole roster by default. If you run contracted content partners, you can point a brief at particular partners, because different partners reach different corners of your market. Employee and external voices are not targeted individually today.

Advocacy usually dies because writing from a blank page is work and nobody ever shows the person it did anything. A brief with a window removes the blank page, a draft built from that person’s own best posts removes most of the writing, and a page of their own numbers gives them the reason to do it again. We are not promising enthusiasm, we are removing the two reasons it stops.

Advocacy programs do not die because people refuse.

They die because nobody gives anyone a reason to post again. The briefs, per-voice drafts, draft scoring, coverage and per-person numbers here are shipped today. See what all that posting produces, person by person or as a number.

Get early access See pricing

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