Revenue workstream · Audience & Accounts
Marketing and Sales do not agree which accounts deserve attention.
The TAM is broad, scoring is inconsistent and data vendors add more records than clarity. The result is spend, seller effort and automation aimed at the wrong accounts.
Recognise it
You probably have this workstream if…
Symptoms tell us where to start. They do not prove the root cause. Signal exists for the cases where the evidence is still disputed.
What you are seeing
- Marketing and Sales work from different target-account lists.
- ICP criteria are broad, repeatedly changed or not owned.
- Fit, technographic and intent signals are purchased before the targeting model is settled.
- Campaigns launch before account and buying-group coverage is good enough.
What may be underneath it
- TAM, ICP, campaign audience and seller priority are being treated as the same thing.
- No named owner governs how targeting rules change.
- Data tools are compensating for unresolved business decisions.
Execution path
Evidence first. Then build only what the workstream needs.
The exact scope is agreed in the Workstream Mandate. These are the evidence and build patterns we would expect to pressure-test for this problem.
Evidence LYNR inspects
- Current ICP criteria, account universe and segment definitions
- Opportunity and win patterns by segment, product and account characteristic
- Coverage, enrichment, scoring and intent fields across CRM, MAP and data tools
- Sales usage of target-account lists and feedback on account quality
What LYNR may build
- ICP and exclusion logic grounded in available evidence
- Ranked account universe with practical tiers and ownership
- Buying-group and contact-coverage requirements
- Fit, signal and intent hierarchy with explicit data-vendor requirements
- Governance for refresh, exceptions and Sales feedback
Acceptance test
- Marketing and Sales use one agreed target-account universe.
- Each tier has explicit inclusion and exclusion logic.
- Required account and contact coverage is measurable.
- Scoring and signal rules can be explained and governed by a named owner.
Handback
Your team owns the operating state after LYNR.
Every Sprint is documented as it is built. The receiving owner gets the process, controls and context needed to run it without a standing LYNR pod.
ICP and account model
Tiering logic
Buying-group coverage standard
Signal hierarchy
Data requirements
Governance runbook
Not sure this is the right workstream?
Use the free triage to identify the likely workstream and whether the evidence is strong enough for a direct Sprint.
One problem. One accountable workstream.
If the evidence is clear, scope the Sprint. If it is not, use Signal to establish the root cause and Definition of Done before you spend on the build.