The live layer of the chain.

Session-granular intelligence, when you need it most.

Reckoner works at industry scale, surfacing patterns across weeks of public signal. Sonar brings that intelligence to your firm every day — peer-benchmarked, anchored to real customer voice, delivered to the desk that needs it. Pulse is the third layer: it watches individual customer journeys as they happen, flags deterioration in seconds, and surfaces the live evidence before the abandonment rate moves in tomorrow's report.

The resolution shift is deliberate. A daily briefing tells you that your Loans journey has a friction problem. Pulse tells you that the problem is active right now, on Step 3, in the current session cohort. The difference between "this week" and "this session" is the difference between a retrospective finding and one that still has time to inform a decision. That is what Pulse is being built to provide.

How Pulse differs from the rest of the chain.

Each product in the chain operates at a different latency and carries a different risk posture. Pulse is harder to build and harder to govern — which is why it comes last.

Reckoner and Sonar run entirely on public signal — no internal data exchanged, no customer PII involved. Pulse is different in kind: it requires access to the firm's own session telemetry, which means it runs inside the firm's environment, not across it. That access requires a different integration model, a different governance posture, and a higher bar for enterprise readiness on both sides. Those requirements are the reason Pulse is in development rather than live today.

Pulse senses. The firm decides.

The distinction between observation and intervention is not semantic — it is the architectural and governance boundary that makes Pulse viable inside regulated firms. Pulse will surface what is happening in the live customer journey. It will not act.

The firm chooses how to respond to what Pulse surfaces. For firms that have a decision framework in place, that response typically flows through CJI Lever — the decision layer that sits immediately downstream of Pulse in the chain. Lever provides the structured modes (Autonomous, Guided, or Customer-led) through which firms translate a live Pulse signal into an action. The responsibility for that action remains with the firm, governed by its own policies and its own regulatory obligations. That is how the chain is designed to work.

Built inside your environment.

When Pulse ships, it will run on the firm's own session telemetry, inside the firm's own infrastructure perimeter. CJI does not receive a copy of your customers' journey data. Pulse processes signal at source and returns an intelligence output — a structured observation about what is happening, for whom, at what moment in which journey. The raw signal stays where it belongs.

Shaping the live-insight format.

Pulse is being engineered now. The Day-90 vision above describes what it should return when live — but the format, integration model, and governance standards that will make it useful inside a regulated firm are still being defined. The most useful input at this stage comes from the insight and product leaders who will eventually rely on it: the teams who know where their live-session evidence is weakest, what a real-time observation needs to contain to be actionable, and what governance constraints the output must satisfy before it reaches a decisions desk.

If your team is building a live-intelligence capability inside a regulated consumer-service firm, we would welcome a conversation now — before the integration design is fixed. Early input shapes what Pulse becomes.