For Revenue Ops Revenue act

Finally pilot the channel nobody could measure, on a job that never skips a night.

Every engager on every voice, your own team first, paid partners as you scale, scored by heat and ICP fit, rolled up by company, with buying committees flagged before sales notices. The reason it holds up in a forecast is that it is not a report somebody runs: heat decays and recomputes at 03:00 UTC every night, for every person you have ever captured, so the board is current when you open it rather than current as of whenever it was last refreshed.

Get started Talk to us

Built for RevOps and demand gen leaders who own the pipeline number and need attribution, not vibes.

scoring.agent / heatrescored=2140, last run 03:00 UTC

Amelia ReyesHead of RevOps, Lattice9.2

Jonas KellerVP Marketing, Northwind8.7

Priya ShahDemand Gen Lead, Fintra7.4

icp.profiles / where every score starts

You define your ICP. Everything downstream is graded against it.

Titles, industries, company sizes, and geographies, in your own words, once. Run more than one profile if you sell into more than one segment, each engager gets the best grade across all of them. From that point on, no engager, no account, and no buying committee gets scored against a generic default, only against the ABM universe you actually defined.

Multi-ICP, best-match grading, per engager
Heat score and buying committee detection both read from the same ICP
Change the definition and every score recomputes against it on the next nightly run

icp.gradingbest match across your profiles

ICP: Mid-market SaaS, VP+Profile A

Amelia Reyes, Head of RevOpsICP A

Jonas Keller, VP MarketingICP A

Priya Shah, Demand Gen LeadICP B

MarchAmelia at Northwind likes three of your posts. Nobody notices, one like doesn't move a pipeline number.

AprilHer colleague Jonas likes two more. Still nothing, it's a different name on a different post, in a different month.

MayA third person from Northwind comments on your launch post. Three people, three months, one account, zero visibility.

With ResonueEvery one of those signals rolls up to the same account. The night the fourth person crosses the line, the 03:00 run flags Northwind as a forming buying committee, and it is on the board the next morning. Nobody had to notice.

01how the score gets built3 scheduled, 1 you start

From a like to a routed lead, with the actor named at every step

Four steps, and it matters which of them you have to be present for. Two run on a clock. One is the one job that costs money per call, so it never starts itself. The last one is yours by design.

01watch.agent0 */6 * * *

The post is swept

Every six hours, every tracked LinkedIn post is re-read and the growth in its likes, comments and reposts is recorded against what was already stored. Nobody presses anything.

02capture.agentyou start it

The people are resolved

The one step that is not on a timer, because resolving a person calls a paid provider. You press it, it targets only the posts whose engagement grew, caps itself at ten posts a run, tells you what is left, and enriches only the profiles it has never seen.

03scoring.agent0 3 * * *

Heat and ICP scored, then rescored

Decay weighted, multi touch heat (this week's like beats one from three months ago) plus an A / B / C grade against your own ICP definition. Recomputed for the whole base every night, so warm accounts cool on their own.

04youthe decision

Rolled up, then worked

4 or more people from one account across 3 or more posts is flagged as a forming buying committee, on the same nightly run. What you do with it is not automated and is not going to be.

This is Act Two. Step 01 only happens because Marketing already structured the resonance those engagers reacted to. See how that gets built →

scoring.agent / heat and ICP grading

Know who's warm, not just who's active

Heat is decay weighted and multi touch, so a like from this week outweighs three from last quarter. That only stays true if something recomputes it, which is what the 03:00 run is for: every engager, every night, decayed and rescored, with the ICP grade refreshed against the profile you defined once in your own words.

engagers.listas of last night's run

Amelia ReyesHeat 9.2

Jonas KellerICP A

Priya ShahICP B

scoring.agent / buying committee detection

See the deal forming before sales does

When 4 or more people from a target account engage across 3 or more posts in a quarter, the nightly run flags it as a buying committee, with names, roles, and individual heat, so the AE handoff starts with context instead of a cold list. The flag appears because the threshold was crossed, not because somebody was watching that account.

Amelia R.Head of RevOps

Jonas K.VP Marketing

Priya S.Demand Gen

Theo A.Sales Director

Northwind Co.

4 engagers, 3 separate posts, one quarter, flagged as a forming buying committee, before an AE ever picks up the phone.

pipeline.board / reporting

A board ready number for a channel that never had one

Warm accounts flow into a pipeline board organized by deal stage, with influenced pipeline and revenue tracked alongside it. A 30 day momentum report rolls up new engagers, new warm accounts, and which accounts are heating up, ready for your next pipeline review. This is where the machine stops: the board is kept current for you, and then it waits for a person to move a card.

Pipeline board by deal stage, not a spreadsheet export
Influenced pipeline and revenue, tracked automatically
30 day momentum report on demand

pipeline.boardcurrent on open, waits for you

Warm accounts

Influenced pipeline

$184k

Coming, not shipped yet

CRM sync (HubSpot, Salesforce) Heat score as a lead field Weighted attribution + traceability Re-engagement flagged on the pipeline board The weekly brief posted into a Slack channel

Two of those are worth being precise about, because the halfway versions are already shipped. A customer or churned account starting to engage again is detected today, inside the weekly brief that lands every Monday by email; what does not exist yet is that signal shown as a flag on the pipeline board itself. And the weekly brief is delivered by email in production right now: Slack is the missing channel, not the brief.

Without Resonue

Isolated likes and comments, one name at a time, no memory across months
A buying committee that forms in silence and gets discovered by accident
A pipeline review with a channel nobody can put a number on
Whatever number exists is as fresh as the last time somebody had an afternoon
Sales finds out an account was warm after the deal already moved on

With Resonue

Every engagement resolved to a person, scored by decay weighted heat
Committees flagged automatically at 4 or more people, 3 or more posts, one quarter
Warm accounts and influenced pipeline, ready for the review
Recomputed at 03:00 UTC every night, so nothing is stale and nothing is manual
Sales gets the handoff with names, roles, and heat, before the account goes cold

the forecast question

An untracked channel can't be defended. A scored one can.

Once influenced pipeline has a number attached, it stops being an anecdote in a QBR and starts being a line you can forecast against, the same way you already forecast every other source.

Plan, per year

$5,988

←

One deal, example

$10,000

Illustrative example, not a projection. One $10,000 deal covers roughly 20 months of the Starter plan. The real return is a source you can finally forecast instead of write off as unmeasurable.

02questionsanswered plainly

Before you ask

q01Can we see what actually ran, and why a score is what it is?

Yes, and that is the point of storing it rather than computing it on the fly. Every heat score traces back to the individual engagements that produced it, with their dates and their decay. Every content partner score is stored with the raw inputs behind it. If a run fails it retries twice more, a minute apart, and then reports itself as failed rather than going quiet: a job that lies about having run is worse than one that did not.

q02Does heat land in our CRM today?

Not yet. HubSpot and Salesforce sync is on the roadmap, not shipped. Today, heat and ICP grade live in Resonue's engager and company views, exportable manually while sync is in progress.

q03How is heat score actually calculated?

Decay weighted and multi touch: recent engagement counts more than old engagement, and someone who's engaged across several posts scores higher than a single like. It's computed, not narrated, and every score traces back to the underlying engagements.

q04Do we set our own ICP, or is it generic?

You define it. Titles, industries, company size, and geography, in your own words, once. Every engager is then graded A, B, C, or off ICP automatically against that definition.