Understanding Operations and Collections Leaders’ Priorities

Hello. Last time, you drafted an evidence-based ideal customer profile: the kind of lending institution your workflow fits, the collections pressure it faces, and what might make change urgent. That profile identifies a promising account. This lesson looks inside the account at two people likely to influence the decision: the head of operations and the head of collections.

You’ll map each role’s goals, concerns, and decision criteria so that a conversation about collection automation starts with what that leader needs to accomplish, not with a tour of features. Allow about 40 minutes, including the resources and a short drafting pass. Keep your ICP v0.1 nearby; the aim is to make a role map for that type of institution, not for every lender.

An account-level problem becomes several role-level decisions

Suppose your ICP includes lenders whose early-stage delinquency queues are growing faster than their teams can follow up consistently. That is one institutional problem, but it does not create one uniform buying argument.

A head of operations may ask, “Can we handle this volume reliably without adding the same proportion of staff or creating another difficult system to maintain?” A head of collections may ask, “Will this help us reach the right borrowers, improve outcomes, and recognize cases that need a different kind of attention?” Both may care about cost and recovery. Their responsibilities determine which trade-offs they examine most closely.

A useful role map separates three things:

• A goal is an outcome the leader is accountable for, such as dependable capacity or effective borrower engagement.
• A concern is what could go wrong if the current process continues or if a new workflow is introduced.
• A decision criterion is a condition the leader would use to judge whether a change is worth making. It should be specific enough to test, not merely “the technology looks promising.”

Treat these as hypotheses about responsibilities, not personality profiles. Titles and reporting lines vary across institutions. In one lender, collections may own the budget; in another, operations may lead the change, while risk, compliance, IT, or procurement can stop it.

Start with the pressures leaders are trying to balance

Collections leaders rarely have the luxury of optimizing a single number. More accounts to handle can strain staffing and systems. More contact activity may not help if borrower circumstances are poorly understood. Faster handling is not an improvement if vulnerable customers are missed or staff cannot review exceptions.

Read Experian’s discussion as a checklist of possible pressures, rather than proof that your ICP has each one. It was written in a UK pandemic context; the resource constraints and customer-treatment questions are useful prompts, but their urgency and regulatory details must be checked in your target accounts.

The distinction to carry away is that a desired outcome is not permission to ignore a constraint. “Handle more cases” may be attractive to operations, but not if deployment consumes scarce IT capacity. “Increase contact” may sound attractive to collections, but not if staff lose the ability to spot borrowers who need specialist support. Your map should capture both sides of each leader’s judgment.

Map two leaders against the same proposed change

Consider a hypothetical lender evaluating an agent workflow to coordinate follow-up on eligible delinquent accounts. It currently uses staff-managed queues alongside existing systems. The table is a starting hypothesis, not a claim about your customers or your product’s proven results.

The roles overlap: either leader may ask about cost, recovery, compliance, or customer experience. The purpose of the map is not to assign each topic exclusively to one person. It is to identify which evidence each person will need to make a responsible decision.

For operations, that evidence might include a workable integration scope, an account of which tasks remain with staff, and visibility into failed handoffs. For collections, it might include how cases are selected, how staff intervene, and how borrower interactions and outcomes are reviewed. These are examples of evidence to request or verify, not promises to make about an unexamined workflow.

A FICO discussion of collections technology gives a more specific illustration of why “AI” alone is not a buyer goal: it describes uses such as selecting contact times and channels or assigning an appropriate agent to an activity. Read it to distinguish an operational choice from the result a collections leader would care about. It reports views from an earlier survey and is vendor-published, so use it to generate questions, not to establish what today’s prospects will buy.

When you speak to either leader, avoid turning a plausible mechanism into an unsupported result. “The workflow can coordinate eligible follow-up across channels” describes an approach if your product does so. “It will increase recovery” is a performance claim that needs evidence for the relevant accounts and comparison.

Identify whose judgment counts—and who else must agree

Even a precise role map can fail if it assumes that interest equals authority. A head of collections may champion a change but need operations to own deployment. An operations leader may favor the efficiency case but need collections to approve how cases are handled. Both may need separate security, privacy, compliance, finance, or procurement reviews.

The following portions of Enterprise Sales from Y Combinator are useful here. Watch for the difference between understanding an individual’s pain and learning how their institution actually makes a purchase.

Your role map therefore needs a fourth field alongside goals, concerns, and criteria: role in the decision. Record whether a person appears to be the workflow owner, an advocate, a budget owner, a required reviewer, or some combination. Leave authority marked unknown until it is confirmed. A useful, neutral question is: “If this proved valuable to your team, who would need to assess the workflow and approve its use?” That is more informative than assuming the most senior person in the meeting signs the purchase.

Build a role map you can use on the next call

Spend 8–10 minutes extending your ICP v0.1. Use one real customer, pilot, or active prospect that fits it. For each of the two leadership roles, make a short note under these headings:

1. Accountable outcome: What is this leader trying to improve in the collections operation? Use their stated language where you have it.
2. Cost of the current approach: Which queue, handoff, staffing demand, or missed opportunity makes the issue matter to them?
3. Concern about changing: What could make an agent workflow harder to adopt, govern, or justify than the existing approach?
4. Decision criterion: What would they need to observe or verify before supporting a change? Include at least one operational or business criterion and one control or implementation condition.
5. Decision role and evidence status: What part of the decision do they influence? Mark each entry observed, reported, or hypothesis, and note its source.

Keep the map compact—roughly half a page. If you have never spoken with one of the roles, do not manufacture their priorities. Write the most consequential unknown plainly. A map that says “We know the collections leader owns the queue, but do not know who approves integration effort” is more useful than a polished fictional persona.

To make it usable in conversation, put the two leaders’ criteria side by side. Look for a trade-off: for example, collections may welcome more consistent follow-up while operations worries about exception-handling workload. That tension tells you what both leaders would need to examine together. It also tells you where a generic efficiency pitch would be insufficient.

What to carry forward

An ICP tells you which institution may be a fit. A role map tells you why particular leaders might support, question, or block a change. For heads of operations and collections, distinguish accountable goals from concerns, turn both into testable decision criteria, and verify who participates in approval. Keep claims about their priorities tied to what customers have actually said or done.

In the next lesson, you’ll rank your customer evidence to separate strong product–market fit signals from the most important remaining gaps. Your role map will help reveal which apparent signals reflect a real decision-maker’s priority—and which are still assumptions.