Resonue
how it works / one definition, three schedules

You define the ICP once. The agents run it forever.

Post to a company page and most of what comes back is noise: impressions and likes with no account attached, no way to tell a prospect from a stranger. Resonue starts from the accounts you are actually trying to close. You write that definition down once. After that it is read on a schedule you never touch: every new reaction is graded against it overnight, whether or not anyone opened the app.

you-> watch.agent-> scoring.agent-> brief.agent-> HALT-> you

One human decision at each end. Everything between them runs on a cron expression you can read on this page.

1 icp.profiles / defined by you youonce, by hand

Your titles, industries, sizes, geographies. Your ABM universe.

Set it once, in your own words. Run more than one profile if you sell into more than one segment, every engager is graded against the best match across all of them. This is the one place scoring starts, not a generic default nobody chose.

It is also the only step on this page with a person in it. Nothing here is inferred, nothing is defaulted, and nothing recalibrates itself behind your back. The agents downstream do not decide who matters to you. They apply what you wrote.

Every score downstream traces back to this definition.
icp.profilesyours, not a default
Mid-market SaaS, VP+Profile A
Enterprise IT, Director+Profile B
2 watch.agent / structures your resonance watch.agent0 */6 * * * UTC

Every voice swept four times a day, whether or not anyone is in the app.

Company page, employees, external voices, and content partners, all four counted as one resonance signal. Every six hours the watch agent goes and looks: new posts captured and deduplicated, then one AI pass per post reading topics, sentiment, the brands named in it and which of your briefs it covered. Posts an employee wrote before they joined you are dropped before they can land in your numbers.

The writing side stays yours. Briefs assign the same topic to every voice, and Compose scores each draft against your own resonance data before you publish it on LinkedIn. The agent reads. It never posts.

The posts going out are coordinated, not scattered, and the record of them is current without anyone refreshing it.
voices.rosterlast sweep 00:04 UTC
SCompany pageHonored
AAmelia R., EmployeeSlipping
AJonas K., ExternalHonored
BPriya S., Content PartnerHonored
3 scoring.agent / grades every engager scoring.agent0 3 * * * UTC

Heat, ICP grade, and buying committees, recomputed overnight from step one.

Every reaction gets a decay weighted heat score and an ICP grade, A, B, C, or off. At 03:00 UTC the scoring agent decays yesterday and recomputes today for every engager on the roster, so a person who went quiet three weeks ago cools without anyone marking them cold. When 4 or more people from one account engage across 3 or more posts in a quarter, Resonue flags a forming buying committee, by name and role.

The same run rewrites every content partner's score breakdown with the inputs that produced it, so a number you disagree with can be opened and argued with rather than taken on faith.

Nothing here is scored against a generic default, only against your ICP.
scoring.agentrescored=2140 at 03:00
Amelia ReyesHeat 9.2
Jonas KellerICP A
Priya ShahICP B
4 pipeline.board / worked by you youevery decision, still yours

Warm accounts become pipeline, not a vanity metric.

Warm accounts roll into a pipeline board by deal stage, with influenced pipeline and revenue tracked against it. Rosa turns a hot engager's activity into a ready to send outreach draft, so sales works the room that was already forming, not a cold list.

This is where the machine stops. The board is current when you open it because the overnight run made it current, and then it waits. Rosa drafts the opener and a person reads it, edits it and sends it. Nothing leaves your workspace on a schedule except the Monday brief, and that goes to your own team.

Revenue attributed to your ABM, not to noise.
pipeline.boardcurrent on open, waits for you
Identified
Northwind Co.
4 engagers · Heat 7.8
Engaged
Fintra Systems
6 engagers · Heat 9.0
Committee
Bellwood Group
$62k · 5 engagers
02traceone record, end to end

Follow one reaction all the way through.

The four steps above are the shape. This is the same thing at the level of a single event: somebody hits like on a Monday post, and here is every hand it passes through before it becomes a name on your pipeline board, with the real cadence next to each one. Two of the eight rows are a person. The other six happened while nobody was looking.

trace / one engagement, from reaction to pipeline illustrative record, real cadences
Tue 14:31 a stranger Amelia Reyes reacts to a post your VP of Product published on Monday. Nothing in Resonue knows she exists yet, and nobody on your team saw it happen.
Tue 18:00:07 watch.agent Scheduled sweep, 0 */6 * * * UTC. The post is re-read and the growth in its engagement is recorded against what was already stored.
Tue 18:01:52 watch.agent One AI pass over the post at temperature zero: topics, sentiment, the brands it names, and which of your briefs it covered. Nobody wrote a prompt for it.
Wed 09:05 you You press capture on that voice. This is the one job on the page that is not on a timer, because resolving people costs money per call, so it never starts itself.
Wed 09:05:14 capture.agent It picks its own targets: only posts whose engagement actually grew, ten posts at most in one run, and it tells you how many are left. Amelia is resolved from the reaction, and enriched only because Resonue had never seen her before.
Thu 03:00:19 scoring.agent Overnight rescore, 0 3 * * * UTC. Amelia's heat is recomputed across every touch she has ever made, decayed by age, and she is graded against the best matching ICP profile from step one. Grade A.
Thu 03:00:41 scoring.agent She is the fourth person from Northwind Co. to engage, across five posts this quarter. A forming buying committee is flagged on the account, with the names and the roles.
Thu 09:12 you You open the companies board and Northwind is already on it. Rosa turns Amelia's activity into an outreach draft built on the themes she keeps engaging with. Halt You read it, you edit it, you send it.
Mon 08:00 brief.agent Northwind turns up in the weekly brief, emailed to everyone in the workspace, 0 8 * * 1 UTC. If there had been nothing worth reporting in any of its four sections, it would not have sent at all.

Illustrative record: the names, the account and the timestamps are made up. The cadences are the ones deployed in production today, and the capture step really is the only one you start yourself.

03the differencescheduled vs nobody

A company page generates noise. An ICP-first system closes revenue.

Most companies measure their presence with a follower count and a shrug, on the weeks somebody remembers to look. Resonue is a Sales and RevOps tool: every signal it surfaces, resonance and revenue alike, is computed against the ICP you defined rather than against whoever happened to click like, and it is computed on a schedule rather than when a person gets round to it.

Typical company page
  • Likes and impressions, no account or ICP attached to any of them
  • Every engager looks the same, in your ICP or nowhere near it
  • A buying committee forms in silence and gets found by accident, if ever
  • Someone has to remember to go and look, and nothing happens on the weeks they forget
  • Engagement and revenue live in two tools that never talk
Resonue, ICP-first
  • Every engager graded A, B, C, or off, against the ICP you defined
  • Buying committees flagged by account, with names and roles, on the overnight run
  • Heat and ICP grade route straight to a pipeline board sales can work
  • The board is current when you open it because the 03:00 run made it current
  • One system: resonance and revenue, computed against the same ICP

Define your ICP once. Stop scoring against noise.

See how each seat uses the same ICP: Marketing, Revenue Ops, and Sales.

first sweepwithin 6 hours of your first voice first gradesthe next 03:00 UTC first briefthe following Monday, 08:00 UTC

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