Prospecting
/Prospecting Weekly Review
Prospecting Weekly Review
Prospecting Weekly Review turns a week of prospecting activity into a role-specific view of what moved, why it moved and what needs to happen next, reading Prospect State against the team's own goals, ICP, persona, signal, messaging and territory logic, and recommending priorities and upgrades for rep, manager, leader and RevOps to challenge and approve.
Prospecting
What actually changed in prospecting this week, and why?
What changes across the three columns isn't whether the numbers get reported, it's whether the review explains what moved and why, ties it to the team's own goals, ICP, persona, signal and messaging logic, and turns it into decisions rather than another dashboard to read out loud.
01 | The Current Way
02 | AI Added On
03 | AI-Native
Before the review
Built from scratch, every week
Someone pulls dashboards, spreadsheets and rep updates together before anyone can sit down and look at them.
Numbers recapped, not explained
It can summarise the dashboard and flag which metrics moved, but doesn't say why they moved or what it means.
Movement and causes ready
Prospect State read against the team's own goals, ICP, persona, signal and messaging logic already shows what moved and why, before the meeting starts.
During the review, by role
One read for the whole room
Whoever's presenting decides what everyone sees, so reps, managers and leaders sit through the same slides, whatever their role actually needs from the numbers.
Same summary, every role
A bolted-on summary reads the dashboard back the same way to reps, managers and leaders, with nothing tailored to what each needs to decide.
Each role sees their own view
Reps see personal focus, managers see team performance and where to intervene, leaders see pipeline creation, and RevOps sees how the logic itself is performing.
Deciding what happens next
Action items, disconnected
What gets agreed lives in someone's notes or a follow-up email, separate from why the numbers moved in the first place.
Change flagged, not recommended
It can call out which metric shifted, but stops short of recommending what a manager or leader should do about it.
Priorities tied to causes
Recommended interventions are tied directly to what caused the movement, and a manager or leader challenges, adjusts or approves them before anyone acts.
The week that follows
Nobody checks back
The next review starts from a blank dashboard again, so whether last week's decision actually worked never gets examined.
Fresh recap, no memory
The following week's summary reads the new numbers the same way as last week's, with no link back to what was decided or why.
Last week carried forward
The next review opens already knowing what was decided last time and what happened since, so the conversation picks up where last week's left off.
Over weeks, the standard itself
Assumptions never revisited
Nobody goes back to check whether the ICP, messaging or signals the team is working from are still the right ones.
Same logic, every week
It keeps summarising against the same targets and messages every week, regardless of whether they're the ones actually producing pipeline.
Evidence upgrades the standard
Weekly evidence builds pressure to update ICP, persona, signals or messaging, and each upgrade, automatic or reviewed as RevOps sets it, changes what next week's review measures against.
It reads Prospect State and the week's outcomes against the team's own goals, ICP, persona, signal, messaging and territory logic, and returns movement, exceptions, causes and recommended priorities, surfaced differently for rep, manager, leader and RevOps, with the reasoning behind each read traceable.
It cuts the recurring cost of assembling the weekly review by hand and improves pipeline productivity, because corrective action happens while it can still change the week's outcome.
One system that understands, decides, acts and learns.
Every GTM signal flows through an AI-native operating layer into a system that runs on the surfaces your team already uses.
Explore the GTM System →Account & Contact State
Buying Signals
Territory Coverage
Propensity
Lead & Account Routing
Sequence Selection
Meeting Prep
CRM Updates
Alerts & Escalation
Upgrade Targeting
Upgrade Messaging
Upgrade Sequences
The GTM teams that learn fastest will win.
Build yours a system that learns. An advantage competitors cannot buy back: years of success and failure, codified.
Frequently Asked Questions
AI-native GTM Systems didn't exist two years ago - here are the questions everyone wants answered.
Talk to Us→Prospecting Weekly Review doesn't change ICP, persona, signal or messaging logic on a single volatile week's evidence alone. It surfaces the evidence and a recommended upgrade, and a manager or RevOps challenges the conclusion and adjusts it. RevOps sets each rule as automatic or human-in-the-loop, and owns the call either way.
Reps, managers, leaders and RevOps all read from the same underlying Prospect State and company logic; only the view changes. A rep sees personal focus, a manager sees team performance and where to intervene, a leader sees pipeline creation, and RevOps sees capability and logic performance. Nobody works from a different set of numbers, only a different cut of the same ones.
The weekly review reads Prospect State as of the moment it's opened. Movement, exceptions and causes reflect whatever has actually changed in the week's prospecting activity and outcomes, so the meeting starts from what's true now rather than from a report someone had to reconcile first.
Prospecting Weekly Review's recommendations do improve over time, because each week's evidence feeds into whether the ICP, persona, signals, messaging or a skill needs to change. When the same gap keeps showing up in the numbers, that pattern builds pressure for an upgrade. When it's applied, it changes what the next review measures against, and the sourcing, messaging and signal capabilities that share that logic pick it up too, on the automatic-or-reviewed terms RevOps has set.
A weekly prospecting review should show what moved in the week's prospecting activity, why it moved, and what each role needs to do next. Prospecting Weekly Review covers movement, exceptions and causes against the team's ICP, persona, signal, messaging and territory logic, then surfaces recommended priorities and upgrades by role.
RevOps should review prospecting performance by looking past pipeline numbers to capability and logic performance, checking whether the ICP, persona, signals and messaging behind the week's results are still the ones producing pipeline. Prospecting Weekly Review surfaces this view directly, and RevOps challenges the conclusions. Each resulting change runs automatic or reviewed, as RevOps has set it.