This chapter is built on the account research philosophy of Jen Allen-Knuth, who spent eighteen years in enterprise sales and closed more than $50M to C-level buyers before founding DemandJen, where she now runs training and workshops on outbound, executive discovery, and creating urgency. She teaches the material through 30 Minutes to President's Club, worked with Gong on an analysis of more than a million executive sales cycles, and publishes almost daily to an audience of roughly a 100,000 sellers.
What is an account point of view?
An account point of view is a problem hypothesis: a specific, falsifiable guess about what is making a named executive's stated objective hard to hit.
Three things make a solid account POV:
Anchored top-down: An account POV starts from an objective the business has stated publicly rather than a low-level pain point. Budget follows stated objectives and a POV anchored to a pain point isn't fundable no matter how real the pain is.
Solution-agnostic: It describes their problem and the cost of their current approach. Your product does not appear in it.
Specific enough to be corrected: Make it specific enough that the executive can't resist correcting you. Their correction is how you get the true current state.
Why an account POV is important
First, executive attention has never been harder to earn. AI made it trivial to spin up a solution, so there are now many more options inside every category and more categories competing for the same budget. In many cases, buyers see a long list of vendors that describe themselves in a similar way that you do.
Second, an executive has a hundred problems they could fund, but budget for only a handful. Their question is whether this problem that you're defining is the right one to solve now.
That said, good sellers help buyers decide that they are solving the right problem. A seller who can say here is what I think is making your stated goal hard, and here is what companies in your position did about it is working on the problem the executive actually has.
Building an account POV has never been easier now that information is available to every seller. Since everyone has access to similar information, judgment separates good sellers from bad ones. By this, we mean drawing a conclusion from public information that other sellers do not draw.
A weak seller sees a generic signal and reacts to it. Something like, "saw you're hiring" or "noticed you raised."
A strong seller slows down and asks what this company is likely to do with that money, how that compares to what their competitors are doing with theirs, and what gets harder for the person they're about to call.
How to present your POV
The next question is how to approach an executive with your crafted point of view.
An executive agrees to a meeting when three things are clear:
Evidence you know what they must deliver this year: This does not include that they "want to grow." This does include the actual goal the company has said out loud, how it gets measured, and whose job depends on hitting it.
Whatchanged: Whatever they are doing today was the right call when they made it. Then something outside the company changed: a competitor, a new entrant, a regulation. The old plan no longer works and it's the seller's job to guide them to the new approach.
A way to measure what doing nothing costs: Sellers lead with what gets better if you buy. Executives are already working out what could go wrong if they change. Give them the number of what it costs to leave things exactly as they are so they understand the cost of inaction.
The next section covers how to build a specific account POV that helps you get closer to the buyer's pain.
Unlike other assets you create throughout a deal, you do not send the account POV to anyone. Rather, it is the argument behind what you do send: the outbound email, the first call, and the slide you eventually put in front of a group of stakeholders. We will walk through how to craft a sharp POV. Steps one through five happen before you speak to anyone. Step six covers how the POV shows up once you do.
A finished POV has five parts.
Part
What it is
The objective
A top-down, publicly stated company goal, not a low-level pain point
The status quo
How companies like them typically solve this, described fairly rather than attacked
The under-appreciated threat
An obstacle to that goal they probably haven't connected to it
The contradicting evidence
Something in their environment that breaks the assumption the status quo still works
The cost of inaction
A way for them to measure what their current approach costs
1 Start with a stated company goal
When doing research on an account, you are after one thing: what this company must achieve this year, stated specifically and measurably.
The instinct is to go read the 10-K, and that's a good start. However, an annual report tells you what a company wants investors to hear. Every other seller can get the same information from a single AI prompt.
An executive talking in public is going to get you closer to what actually matters, in plain language, including where they think they're strong and where the urgency is. If possible, spend your research time on what the executive says in public rather than on formal filings.
Account type
Where the objective lives
Public company
Executives speaking publicly first. Then the IR page, CEO shareholder letter, and the 10-K risk factors
K-12 and higher ed
Search "[school name] strategic plan"
Private company or startup
Recent founder and exec interviews, podcasts, and posts where they talk about growth
Once you have the raw materials, apply judgment to work out what it means for what Jen calls their "growth math." Growth math is the constraint on every corporate decision that suggests a company cannot add spending in one place without cutting it somewhere else. To sell effectively, you must understand what is being deprioritized in order to make space for the new initiative.
2 Respect the status quo before you contrast it
The status quo is whatever they do about this problem today: a tool, a team, a process, or even nothing. Handle the discovery on this carefully. If you attack a prior decision, you will likely get defensiveness in return. If you respect the prior decision, you invite a correction that helps you understand the real current state.
In practice, that means naming their approach out loud before you say anything about its limits, and supplying the reason it made sense. Something like:
Most companies at your size handle this by standing up a team and a tool, usually because it's the fastest thing to get running and it holds up fine until volume changes.
Then ask how their version differs.
Two insights should come out of that.
The executive doesn't have to defend a decision you haven't attacked, so instead of pushing back they correct your description.
You now have a baseline on record, which is what the contradicting evidence needs in order to land later.
3 Find the under-appreciated threat
This is the step that separates a POV from a summary of their press releases.
When the executive made their current decision, the numbers about the business worked. Then, something outside the company changed: a competitor moved, a new player arrived with a bigger budget, a category they were not in came after theirs. Now the numbers do not work, and doing nothing has a cost. That's the underappreciated threat that needs to be uncovered.
"We hold on to what we're doing as long as we can, until someone holds up a mirror and says: you can keep holding on, but these things have changed, which has made the math not work out in your favor."
4 Build the cost of inaction
ROI is a late-stage calculation that measures what improves after they buy. Cost of inaction is the early-stage calculation that measures what their current approach already costs them.
To build the cost of inaction, follow these steps:
Name the failure: Find one specific, quantifiable thing the current approach produces. Inefficiency and misalignment do not count. Example: "enterprise deals stall in security review and procurement."
Count how often it happens: Per month or per quarter, taken from their own reporting rather than your estimate. Example: "five deals a month"
Attach a unit value: What one instance is worth: average contract value, average deal size, or hours of rep time at a loaded rate. Example: "$50,000"
Annualize it, then project it forward: Five deals a month at $50,000 is $3M a year. Then apply the environmental change from step three, which makes next year's figure larger than this year's.
Wherever possible, use the buyer's own data: pipeline reports, cycle times, headcount, win rates. To see this example come together, see the calculation below:
What the current approach costs
Amount
Enterprise deals stalling in security review or procurement
5 per month
Average contract value
$50,000
Revenue delayed or lost each year
$3M
Spend producing that result
$11M a year across reps, programs and tooling
Putting it together
Let's work through a hypothetical scenario to bring this to life. Northfield Software is a mid-market B2B software company, invented here so that every part is demonstrated. Their CEO has said publicly that the company is moving upmarket into enterprise accounts, and they cut the self-serve and SMB team by 15% in Q1. You sell to their VP of Sales.
Here are the five parts filled in for that scenario. Every line is an informed guess, specific enough to be corrected.
Part
The hypothesis
Objective
Move revenue from SMB and self-serve into enterprise accounts, funded by a 15% cut to the SMB team in Q1
Status quo
The same account executives who closed SMB deals are running enterprise deals, on the same process and the same comp plan
Under-appreciated threat
An enterprise cycle adds a security review and a procurement step the team has never run, so deals close a quarter or two later than the plan assumes
Contradicting evidence
Enterprise pipeline is being created at target while enterprise win rates stay at the SMB level, so the problem is conversion rather than demand
Cost of inaction
The SMB revenue they cut is already gone, and the enterprise revenue meant to replace it arrives a year later than planned
Spoken out loud, in the first few minutes of a call, that becomes:
"I'm an outsider looking in, but here's what I think I'm seeing. Cutting the SMB team looks like it was freeing up resources to move upmarket, which makes enterprise win rate the number the whole plan depends on."
Notice the example doesn't name a product, doesn't claim certainty, and doesn't invent numbers. In a real version, "the companies I've worked with" is one named company that looks like them, plus what happened to that company.
5 Write down why power says no
You're rarely working with prospects where 100% of the people agreed to change. It's the job of the seller to identify who the naysayers are, or could be.
Before the call, write down the reasons someone in a position of authority would say no to test whether your POV is specific enough to threaten anyone's priorities. You're asking yourself,
Who would be skeptical of prioritizing this now?
Who would rank something above it?
Who is invested in the status quo, such as whoever chose the incumbent?
Why not wait six months?
If you can't name a single person who would push back, the POV is too generic. Go back and make it more specific.
Then ask your champion the same questions.
Who else needs to be involved gets you a list of people who already agree.
Who's most likely to be skeptical?
Who prefers the status quo?
Who would prioritize something else?
If they can't name anyone, that tells you about their access rather than about the consensus, and you have more of the committee to meet now.
How the POV shows up in the first call
An accurate POV delivered as criticism creates defensiveness so we want to be careful not to attack a decision someone has made. For this reason, do not open with your current approach isn't working, and I can fix it.
To properly present your POV:
Assert what you believe
Justify why you believe it
Invite a correction
You run that pattern for each part of the POV rather than once at the top of the call. For example, the opening carries the objective and nothing else:
"I'm an outsider looking in, so tell me what I've got wrong. Your CEO has been talking about moving upmarket, and from outside it looks like that puts a lot of weight on enterprise win rate. Is that how you'd describe it?"
Then stop and listen for the correction. This is the real objective, and helps you get closer to the truth.
The rest of the POV arrives one piece at a time. Once the objective is right, raise the status quo:
"Most companies your size run enterprise deals with the same reps and the same process, so how does yours differ?"
Once they have described their approach, introduce the contradicting evidence in we language:
"We were surprised to find that security review adds a quarter to these cycles, does that match what you see?"
The cost of inaction comes last, after they agree the problem is real.
The call should feel like two colleagues examining a problem. Ask fewer questions and bring more material that is specific enough to have a conversation about. Executives give their attention to sellers who understand their business.
Reps losing hours every week to manual CRM updates is a valid problem but not one an executive will fund. It names an annoyance rather than a threat to something the company has committed to. The same problem becomes fundable once you connect it to an executive-level goal: those hours come out of enterprise selling time, limiting the amount of accounts a single rep can work.
2 Telling the upside story.
Sellers think: if you change, look at all the good things that happen. Buyers think the opposite: if I change, what could go wrong? It's important to get the buyer thinking about the cost of inaction rather than the potential promise of the solution. This will help them identify that doing nothing is no longer an option.
3 The zero-dollar audit.
Pull every deal your team closed-lost to "budget," "timing," or "went cold" and sum the pipeline value. Those reasons are self-serving. They hide a failure to build a case for change, and they send marketing off to fix pricing when the messaging was the problem.
That number becomes a shared sales and marketing target, and it moves the internal conversation from we need more leads to we need better conversion.
The warnings here come from a heavy AI user. Jen researches every account with Claude, going back and forth with it for five to thirty minutes before a call. She says AI removes any excuse for arriving unprepared. But, it's important to understand what AI can and cannot do.
AI gathers information. Deciding what it means remains the job of the seller. You cannot prompt write my account POV and get something usable. The judgment about which facts matter to this executive stays with you.
To use AI effectively in this stage, prompt for the four questions the POV is built from, one at a time, and in order:
What they must deliver
Who carries it
How they're solving it today
What inaction costs
Tag fact versus hypothesis, and request the source
A prompt that produces usable material looks roughly like this:
"Who is the CEO of [company]? Find their most recent public comments on the 2026 to 2027 growth strategy. Growth math means that if a company funds something new, something else has to pay for it, so tell me what they appear to be starting and what they appear to be stopping to pay for it. Use publicly stated comments only, and tag each one as fact or hypothesis."
Explicit tagging matters a lot in this step. Without explicit direction, a model will hand you its own inference in the same tone it uses for a quote from an earnings call.
Then interrogate what comes back. Ask probing questions like: "where did that come from?" "show me the source," etc. No source means it's a hypothesis and you should it loosely. Taking the first output as the answer is how a POV ends up confidently wrong about a company in front of the person who runs it.
Spar until you can explain the business like you're ten
To break into an account, it's necessary to understand what they sell, who buys it, how they make money, and how their version of this category is different from the next one? The first answer will be generic, so push back. It's also the trick for translating investor language: explain what this actually means like I'm twelve.
