A worker that forgets who it met is an appointment setter.
Appointment setters are a commodity. A worker that accumulates a picture of who matters, how they relate, what they care about and who controls the money is something else entirely. That picture is the asset that compounds, and it is the one thing a competitor cannot copy, because it was built out of your own conversations.
The temptation is to treat relationship mapping as something the sales application does. It is not, and the reason is that the vocabulary differs while the structure does not.
Maps decision makers, evaluation committees and budget authority. Who signs, who blocks, who was in the room last time.
Maps owners, co-owners, agents, lien holders and the bank behind the file. Same structure, entirely different nouns.
Maps who can actually agree an arrangement, which is frequently not the person on the account.
A stakeholder map built over eighteen months survives a prompt revision, a version change and a personnel change on your own side. Putting it in application code would tie institutional memory to a release, which is how companies end up with a CRM full of names and no idea who matters.
"Reach the economic buyer" only means something if the system knows who that might be and how to get there. Referral chains are paths through a graph whether or not anyone admits it, and a system that cannot walk them is guessing.
Held as a graph rather than as records, because the questions that make it valuable are questions about paths.
| Entity | What it is |
|---|---|
| Organisation | A legal or operating entity, typed as prospect, customer, competitor, partner, adviser, regulator, supplier or intermediary. It may be several of these at once, to different parties |
| Person | A real human, who may be unresolved. Identity is provisional until evidence supports it |
| Position | A role within an organisation, as a thing in its own right. "The CISO at Bank A" exists whether or not anyone knows who holds it |
| Account | Your commercial view of an organisation, which is not the organisation itself |
Separating organisation from account matters more than it first appears. A competitor is an organisation you track and will never sell to. A regulator is an organisation whose publications drive urgency and which nobody will ever call. If the only container available is an account, all of these become either absent or fake accounts, and the second is worse than the first.
An edge without a source and a date is an opinion, and the system does not store opinions as facts.
Relationships are typed, directional, time bounded, and carry a source and a confidence. Employment and role history. Hierarchy. Who knows whom, and who referred whom at what permission level. Who sponsors an initiative and who quietly opposes it. Who controls a budget and who merely influences the person who does. How the organisations around an account compete with, supply or advise each other.
An inferred reporting line is recorded as an inference, at lower confidence, and becomes something the worker tries to validate in the next conversation. A guess dressed as a fact is worse than an admitted gap.
"Used to report to" is intelligence. "Used to work there" is how you find the person who can introduce you. History is not clutter to be tidied away.
"You'd want to speak to whoever runs security" is a real and useful piece of intelligence. A system that cannot hold it discards the most common output of a first conversation.
Because it is a number someone will trust. Sentiment, influence, disposition and relationship strength are not properties of a person. They are dated assertions with a source.
Sentiment over time is a series, so the change within one call sits inside a longer arc. An account cooling over two quarters becomes visible while it is still recoverable.
An assumption is simply an unvalidated observation. A conversation that contradicts one writes a new observation, marks the prior contradicted, and surfaces the correction. Nothing is silently overwritten.
"High influence" resolves to the observations that produced it and the conversations they came from. Nothing corrodes trust in a system like a confident rating nobody can explain.
Who controls it, who influences them, which initiatives draw on it, when the cycle opens, and what a given role can approve without escalating. This is what turns "they mentioned money" into something a ladder can act on. An initiative with an identified funding source, an owner and a cycle date is a qualified opportunity. An initiative without one is a conversation.
Deterministic matching first, scoring second, and above a high threshold the system proposes a merge rather than performing one. Who approves is configurable: automatic above a threshold you set, the paired human who has met both of these people, or a named data steward. Every merge records what was combined and on what evidence, so it can be undone.
Customers and prospects flow both ways: contacts, opportunity qualification, activity and stakeholder changes, each carrying its provenance and never overwriting a field a person typed. Every organisation type has its own policy, being full bidirectional, inbound only, outbound only or local, configured per customer because one organisation's data hygiene rules are not another's.
Competitors, regulators, advisers, intermediaries, unbound positions and people known only by role. Most CRMs have nowhere sensible to put a competitor's head of product or a vacant seat at a prospect, and pushing them there degrades your own data, which is the fastest way to lose an administrator's goodwill.
A model is justified by the questions it makes cheap.
That last one is not a result set. It is a work list.
Ask anyone who does this job for a living what their week looks like and they will not describe tasks. They will describe lists.
The prospecting list. The renewal book. The quarterly touch on accounts that have gone quiet. The arrears run. The follow up from last month's event. Most systems have somewhere to record a single task and somewhere to record a multi-step process, and nothing at all for the shape in between: a set of subjects to be worked, at a rhythm, until a coverage condition is met. That gap is why so much operational work ends up in a spreadsheet someone exports on a Monday and nobody trusts by Thursday.
| Unit | Scope | The question it answers |
|---|---|---|
| Objective ladder | One conversation | What am I trying to achieve right now? |
| Flow | One subject, several steps | What happens next, procedurally? |
| Task | One action on one subject | What must be done, and when? |
| Work list | Many subjects, over time | Who has not been worked yet, and are we on track? |
Collapsing any two of these produces a failure everyone will recognise. A list implemented as a pile of tasks loses coverage, because a task knows whether it was done and nothing knows whether the set was finished. A list implemented as a process loses pacing, because a process advances on events rather than on capacity, and a virtual worker with capacity will burn a quarter's list in an afternoon.
These get conflated constantly, and separating them is what makes the rest tractable.
| Axis | The question | The answers |
|---|---|---|
| Origin | Where did this come from, and therefore why are we contacting these people? | Target account coverage, an intelligence operation, a marketing or event campaign, observed lead activity, or a cold and sourced import |
| Cadence | How often is it worked? | One time, calendar recurring, rolling, anchored to an external date, or continuous while a condition holds |
| Lifespan | How long does the list itself exist? | Ephemeral, temporary with an expiry, or maintained indefinitely |
Every combination happens. A target account book is coverage origin, recurring cadence, maintained lifespan. A rented marketing list is cold origin, one time cadence, temporary lifespan with a hard expiry. A competitor watch list is intelligence origin, rolling cadence, maintained lifespan, and nobody on it is ever called. A webinar follow up is marketing origin, date anchored cadence, ephemeral lifespan.
An event outcome, a batch of enquiries, the follow up from one content action. Created, worked, closed.
Rented and third party marketing lists. The expiry is enforced rather than advisory, and rows that were never worked are deleted rather than archived, because there was never a reason to hold them beyond a contact that did not happen.
Target account books, competitor watch lists, alumni and former champion lists, renewal books. Membership evolves, the definition is curated, and each has a named owner.
A competitor watch list exists to be observed. So a list declares a work type, being conversation, research, enrichment, verification or review. That is what lets a competitor or regulator list live in the same machinery as a prospecting list with no possibility of somebody dialling it.
Named, and reviewed periodically, in a review that questions the account set itself rather than only its coverage. An unowned standing list is how an organisation ends up working a strategy nobody currently believes in.
A list is not a neutral container of names. Its origin determines its objective, its cadence, its lawful basis, its priority and what counts as success.
| Origin | What declares it | The objective | Success is |
|---|---|---|---|
| Target account coverage | A named account set | The conversion ladder, plus covering the account's own map | Positions covered and qualification depth, not calls made |
| Intelligence operation | A declared target: a person, a position, an initiative, a competitor, a topic | Learning. The declared questions become the ladder | Questions moved from unvalidated to answered |
| Marketing and event | An event, a campaign or a content action | Stage appropriate: invite, confirm, attend, follow up | Conversion inside a short and unforgiving window |
| Lead activity | Observed behaviour on your own properties | Speed first, then qualification and routing | Time to first contact, measured in minutes |
| Cold and sourced | An import, or a query over the ideal customer profile | Discovery and permission before anything else | Contact rate, and how many people become genuinely known |
It is a first class object, and the understatement matters because the questions people actually ask are campaign shaped rather than list shaped.
What did the autumn programme cost. Did it hit its number. Which of its three stages produced the pipeline. Would a different message have done better. None of those is answerable from a list.
| Element | What it carries |
|---|---|
| Goals | Its own targets, chartered to a marketing owner, delegated from the reps whose accounts are in scope, or both |
| Lists | One or many, each with its own origin, cadence, lifespan and stage. An event campaign is five |
| Anchor and timeline | A target date, with every date anchored list inside it moving when that date moves |
| Budget | Its own ceiling, with the cost of every attempt in every list attributed to it |
| Workers | Which workers may draw from its lists, and what share of their capacity it claims |
| Assets and messaging | The approved collateral, openings and positioning, versioned with the campaign |
| Compliance profile | Lawful basis, jurisdictions and disclosure set, resolved once rather than per list |
| Variants | Where an approach is being tested, the alternatives and how membership divides |
A coverage list is not the contacts somebody chose. It is every subject at these accounts that satisfies a condition: every unbound position that matters, every contact untouched in ninety days, every person newly arrived in a relevant seat. The denominator is the map as you currently understand it, so a short list at a large account is a data quality finding, not an achievement.
The weakest basis in the system, so it carries the heaviest checks: a lawful basis declared per row rather than per file, tested against consent, suppression and registry status before anything is admitted, an expiry on the list itself, and rejected rows retained with a reason rather than dropped.
The origin that does not exist in a conventional sales tool, and the one the relationship graph makes possible.
A target may be a person, a position, an initiative, an organisation, a competitor or a topic. Attached to it are the questions to answer: who is leading this programme, when does the incumbent's contract renew, who actually approved the last purchase, is this funded or aspirational.
Who holds a position adjacent to this initiative. Who has moved from the competitor into your portfolio. Who advises this organisation. Who was referred by someone already inside it. The list is the answer to "who could plausibly tell us", and it re-resolves as the picture changes.
Everywhere else the conversion ladder is primary and intelligence is opportunistic. Here it is the other way round: the declared questions are the ladder, and a meeting is the standing objective, taken gratefully when it appears.
An operation closes when its questions reach the required confidence, or when it expires. A hundred pleasant conversations that answered nothing is a failed operation, and the platform says so rather than reporting the call volume.
A sequence over the same population, generated as the event's own state advances, each with a window that closes.
| Stage | Who is on it | The failure mode |
|---|---|---|
| Invitation | The target audience, resolved from the account map and the campaign criteria | Inviting after the deadline, which reads as incompetence |
| Registration chase | Invited, not yet registered | Continuing after they registered, which reads as not listening |
| Confirmation | Registered | Silence. A missed confirmation is a no-show |
| Attendance reconciliation | Registered, attended or not | Treating a no-show as an attendee, the most common data failure in event marketing |
| Follow up | Attended, split by engagement | Following up three weeks later, which is worth almost nothing |
Offsets forwards and backwards from the event rather than a set of fixed times. A conference postponed by a fortnight shifts every list in its campaign automatically, which removes the single most common source of embarrassing outbound in event marketing.
Registration, cancellation, attendance and no-show arrive from the event or webinar platform and move a person from one list to the next. Nobody re-runs an export, and nobody chases someone who already signed up.
The most common source of real work in a marketing led business, and the one most often handled badly.
| Activity | What it usually means | How it is handled |
|---|---|---|
| Gated asset download | Active research, and an identity you hold because they gave it | Immediate item, opened on the asset they took rather than on a product pitch |
| Demonstration or contact request | Explicit intent | Highest priority in the system, measured in minutes |
| Pricing page, repeatedly | Late stage evaluation, often by somebody who has never spoken to you | Item, with the account's existing thread checked first |
| Documentation or specification pages | A technical evaluator, frequently not the person in your CRM | An unbound position worth resolving, more than a lead worth calling |
| Chat abandoned mid-conversation | A question that went unanswered | Item, opened by referencing the question |
| Email or sequence engagement | Attention without commitment | Priority uplift on an existing item rather than a new one |
| Trial or free tier signup | Product led intent | Its own flow, with usage as the qualifying signal |
| Return visit after a call | The conversation is still alive | Signal on the existing thread, not a new list entry |
A form completed eleven minutes ago and one completed four days ago are not the same work, and a queue that treats them alike will lose the first. This is the one origin where the measure is time to first contact and a shortfall alerts in minutes.
A page view has no person attached until an identifying action resolves it. Identifying the visiting organisation from network or firmographic data is an organisation level signal: it may raise an account's priority or create a research task, and it never identifies a person or authorises contacting one.
Turning a work email address into a full profile from third party sources is not implied by someone downloading a document. It is recorded as its own event with its own basis, and configured deliberately rather than switched on by default.
A static list is a snapshot. A dynamic list is a standing question.
Enumerated at a moment in time. Right for a bounded campaign, and its virtue is an exact denominator, so coverage is a fact rather than an estimate.
A question asked of the relationship graph and re-asked at the start of every cycle. An account that starts showing initiative signals on Tuesday is in scope on Tuesday, and nobody has to remember to re-export anything. This is what makes work lists the operational face of the intelligence system rather than a second set of data that drifts away from it.
Treating a recurring book as though it exhausts is the most common mistake in this area.
The priority calculation is deliberately arithmetic and inspectable, composed from list priority, time since last contact, how fresh the signal was that put the subject on the list, attempts already made, and how far behind pace the cycle is running. A seller or a supervisor will ask why this call and not that one, and the answer has to be a list of numbers rather than a model's opinion.
Said as a fact rather than an estimate. That sentence is what the whole structure exists to produce.
The current pace will miss the target before the cycle closes. Raised early enough to do something about it, with the gap quantified rather than described.
Everything eligible was worked before the cycle ended. For a campaign that is success. For a recurring book it usually means the membership rule is too narrow, and it is reported as such rather than celebrated.
Subjects exist, capacity exists, and nothing is being worked, which almost always means an eligibility rule is excluding everything. Silent by nature, so it is detected deliberately.
Proposed from the membership, the capacity available and the historical contact rate, and overridable by a supervisor with a recorded reason. A derived target is defensible on the first cycle where a declared one is a guess, and a supervisor who consistently overrides it is telling you the derivation is wrong, which is a more useful signal than the target itself.
Supplied and third party lists are accepted, on one condition: whoever imports declares a lawful basis for contact, per row rather than per file. Each row is resolved against people you already know, checked against consent, suppression and registry status, and anything that fails is recorded as suppressed with a reason rather than dropped. "Why is this person not being called" is a question that gets asked and needs an answer.
A conversation held under a list changes the picture. The changed picture changes who is on the list next time. That is the difference between a campaign tool and a worker that gets better at knowing who to talk to.
The most useful demonstration of this is not a diagram. Give us a real account from your own pipeline, and watch the worker build the picture from a single conversation.