The Always-On Growth System: Dispositions, PQLs, and Lead Recycling

The strongest growth systems are not built around better outbound copy. They are built around memory. A team improves yield when it knows which leads to exclude, which ones to recycle, which accounts are warming up inside the product, and which old "not now" reply deserves a fresh sequence six months later.

That is the operating pattern we see across high-performing Prospectory workflows. The market does not need another prompt for better outbound copy. It needs a system that remembers what happened to every lead and turns that memory into the next best action.

This is the operating model: lifecycle dispositions, product-qualified signals, enrichment, exclusion logic, and routing agents working from the same account state. Build that, and messaging becomes the last mile because the system has already answered the harder questions: who should hear from us, why now, through which channel, and what should we avoid spending money on?

The Shift From Campaigns to Growth State

Most revenue teams still operate like the database resets every quarter. Marketing launches a campaign. SDRs work a list. Product sends usage alerts. Paid media retargets anyone who clicked enough pixels. Customer success worries about churn. Each team sees a different version of the same account.

The always-on model starts from a different premise: every account has a current growth state, and every signal should update that state. A reply, a no-show, a trial activation, a credit-usage spike, a competitor install, a bad-fit reason, and a pricing-page visit are not separate events. They are state changes.

That difference matters because campaigns optimize for the next send. State models optimize for the next decision. If an account replied "reach out in six months," the system should not bury that note in CRM history. It should create a timed recycle play, suppress paid retargeting for the wrong interval, watch for new product or hiring signals, and tell the rep exactly why the account came back.

The core question changes from "what campaign should we run?" to "what changed about this account since the last action?"

This table looks basic, which is the point. Most teams do not fail because their model is not sophisticated enough. They fail because the five states above live in five tools with five owners and no shared rule for what happens next.

Why the Disposition Tag Is the Growth Team's Most Underrated Asset

Disposition data is usually treated as administrative cleanup. The SDR closes a task, picks a reason from a dropdown, and moves on. Growth teams that compound learning treat that tag as a routing, budget, and model-training input.

A good disposition tag answers three questions:

1. 1Should this account ever be contacted again?
2. 2If yes, what has to change before the next touch?
3. 3Should we keep spending paid media or enrichment dollars on it?

That third question is where money hides. If the only thing your paid system knows is that someone visited a page, it may retarget bad-fit traffic for weeks. A single exclusion tag can stop that spend. "Agency vendor," "student researcher," "too small," "unsupported geography," "competitor," and "consultant researching for client" should not all enter the same ad audience or SDR recycle queue.

Here is a practical disposition taxonomy:

The last row is the one most teams miss. False-positive intent is not a dead end. It is feedback. If twenty accounts with the same behavior all disposition as "false positive intent," your scoring model is overweighting that signal. The answer is not to yell at reps for weak follow-up. The answer is to change the weight.

Turning "Reach Out in Six Months" Into a Revenue Play

A "reach out in six months" reply is not a rejection. It is one of the rare cases where a prospect gives you timing data in their own words. The mistake is treating it as a future task with no context.

The right motion creates a recycle record with three fields: why the prospect deferred, what condition would make the account worth contacting, and what signal should override the waiting period. That last field is critical. If the prospect said to come back in January because budget resets then, but the company hires a VP of Revenue in October and starts searching for your category in November, the system should not wait until January.

The recycle play has four phases:

1. 1Capture the reason. "Budget resets in Q1" and "too busy right now" are different plays. The first is budget timing. The second is weak intent unless another signal appears.
2. 2Set a pre-window date. Restart 14 to 30 days before the stated window, not on the exact date. Buyers start planning before they buy.
3. 3Monitor override signals. Funding, executive change, product usage, hiring, competitor dissatisfaction, or category research can bring the account forward.
4. 4Return with memory. The next message should make it obvious you remembered the original context without sounding like a database record.

Bad recycle copy:

Hi Jamie, checking back as requested. Are you ready to discuss Prospectory now?

Better recycle copy:

Jamie, you mentioned Q1 budget planning was the right window when we traded notes in July. I saw your team is now hiring for RevOps analytics, so I pulled together the two routing gaps teams usually hit before that role starts. Worth sending over?

The second version works because it uses the old timing clue and a new signal. It does not ask the buyer to remember you. It explains why the account came back into motion.

PQLs Need Account Context, Not Just Product Usage

Product-qualified lead scoring often breaks because teams confuse usage with readiness. An account using 80% of its credits month over month may be expanding, abusing a free tier, testing a workflow for one department, or heading toward churn because the usage is concentrated in one overloaded user.

Usage is a signal. It is not the decision.

A credible PQL model combines product behavior, account fit, buying committee coverage, and commercial context. The strongest signal is not "high usage." It is high usage from the right account, in a workflow tied to a business outcome, with at least one reachable business owner and no active suppression tag.

Here is a minimal scoring function a RevOps team can implement before buying anything new:

type AccountSignal = {
  fitScore: number
  usagePace: number
  activeUsers: number
  executiveContactMapped: boolean
  negativeDisposition: boolean
  churnRisk: number
}

export function scorePql(signal: AccountSignal): number {
  if (signal.negativeDisposition) return 0

  const usage = Math.min(signal.usagePace, 100) * 0.35
  const fit = signal.fitScore * 0.3
  const breadth = Math.min(signal.activeUsers * 8, 24)
  const buyer = signal.executiveContactMapped ? 10 : 0
  const riskPenalty = signal.churnRisk * 0.25

  return Math.max(0, Math.round(usage + fit + breadth + buyer - riskPenalty))
}

The shape matters more than the exact weights. The model refuses to score a negatively dispositioned account, rewards usage and fit, adds points for multi-user breadth, and penalizes churn risk. That is what prevents a product-only score from throwing noisy accounts into sales.

The next step is routing:

{
  "pql_score": 82,
  "account_state": "product_qualified",
  "route_to": "growth_ae",
  "reason": [
    "credit_usage_above_80_percent_for_2_months",
    "fit_score_above_75",
    "executive_contact_mapped",
    "no_negative_disposition"
  ],
  "next_action": "send expansion workflow audit within 24 hours"
}

This is where account agents become useful. Not as magic sellers, but as rule-following coordinators that gather first-party usage, enrich the account, check suppression tags, map contacts, explain the route, and execute the next workflow.

The Three Always-On Plays Every Growth Team Should Build

Start with three plays because they cover most of the upside without requiring a huge RevOps project.

Play 1: High-pacing product usage. Trigger when an account uses 70% to 85% of its monthly credits for two consecutive periods, or when usage grows more than 50% month over month. Enrich the account, map the business owner, check whether usage is spread across users, and route with a concrete hypothesis: expansion, workflow consolidation, or implementation risk.

Play 2: Timed recycle from old replies. Trigger from explicit timing dispositions such as "next quarter," "after budget," "six months," or "after renewal." The play should restart before the window, bring forward accounts when fresh signals appear, and include the original reason in the rep brief.

Play 3: Bad-fit exclusion and score repair. Trigger whenever sales marks a lead as bad fit or false-positive intent. Remove it from expensive audiences, suppress it from SDR work, and log the pattern for score calibration. This play does not create pipeline directly, but it protects the pipeline system from waste.

The implementation checklist is straightforward:

• Create one account-state field that sales, marketing, and product growth all respect.
• Standardize disposition tags before adding more enrichment.
• Require a next-action rule for every high-value state.
• Write suppression rules with the same care as routing rules.
• Audit false positives every month and change scoring weights.

Prospectory fits this motion when teams need account intelligence, signal capture, and routing context around the CRM rather than another disconnected list. The product should appear after the operating model is clear, because the buyer has to understand the system before they can judge the tool.

What To Measure After the System Goes Live

Do not measure an always-on system by raw task volume. Volume is what makes weak systems look busy. Measure the account-state transitions that predict revenue and the waste that disappears.

The most important metric is route acceptance rate. If sales ignores the routed accounts, your system is not credible yet. That may mean the score is wrong, the explanation is weak, the timing is bad, or the workflow is asking reps to do too much manual work. Fix acceptance before optimizing anything else.

FAQ and the First 30-Minute Build

Is this just lead scoring with a new name? No. Lead scoring ranks records. A growth state model decides what happens next, including routing, suppression, recycle timing, and score repair. The action layer is the difference.

Should product-led teams and sales-led teams use the same model? They should share the same account state, but not the same thresholds. A self-serve product may route at usage pace plus fit. An enterprise motion may require usage pace, buying committee coverage, and account tier before sales touches it.

What is the fastest way to start without a data warehouse project? Start with CRM dispositions and product usage exports. Create the five account states from the first table, map the last 90 days of leads into those states, and build one recycle play plus one exclusion play.

How often should the scoring rules change? Monthly for the first quarter, then quarterly once the false-positive rate stabilizes. If sales dispositions contradict the model for two cycles in a row, change the model.

Your first 30 minutes

Pull every reply from the last 180 days that contains "later," "next quarter," "budget," "renewal," or "six months." Tag each one as recycle later, no authority, or weak intent. Then pick the 25 accounts with the clearest timing clue and add a pre-window task 21 days before the stated date.

That small project will teach your team the bigger lesson. The database already contains pipeline signals. The work is making the system remember them, route them, and stop spending money on the leads that already told you they are wrong.