Worked example

One arc, end to end: a cold account comes back, and the loop turns it into a meeting, with receipts.

One arc, end to end. The numbers are illustrative; the mechanics are exactly what the platform does.

1

A signal arrives

An account your team closed-lost last year returns to your pricing page.

• To an analytics tool: an anonymous session.

• Here: an event entering the loop.

2

It resolves

Identity matching ties the visit to the account.

• The visitor's earlier anonymous activity re-attributes to the same record.

• The old opportunity, the past emails, the fit you already established: one story again.

3

The score moves

Pricing-page intent from a good-fit, previously engaged account moves Intent and Recency sharply.

• The account flips Hot.

• The reason is attached: not "score changed," but which signal moved it and why it matters.

4

A decision is made

iHarness diagnoses the moment: a win-back situation, not a cold outreach one. Before anything runs, it:

• selects the play whose lever matches,

• chooses the audience slice and the channel,

• states what it expects to happen,

• and writes the trace.

5

You approve

The proposal arrives in Pulse as a stall waiting on your call: the account, the reasoning, the plan, one primary action. You approve; the gate opens.

6

It activates

The activation goes to your outbound channel, personalized against everything the context knows, inside the guardrails:

• the contact is claimed by this one cadence,

• suppression checked,

• your CRM updated rather than overwritten.

7

The outcome comes back

A reply, a meeting booked.

• The outcome joins on the trace ID.

• It credits the decision that caused it, not the last click, not the loudest channel.

8

The loop learns

Expected versus actual is recorded. The next time a closed-lost account warms up, the diagnosis is sharper because this arc happened.

That is the whole platform, once: signal, identity, score, decision, gate, activation, outcome, learning, one trace ID from start to finish.