Chapter 19

The Next Conversation Worth Your Hour

The Hour Problem

It is 2:00 on a Tuesday afternoon and you have one open hour before the next thing. Here are four ways to spend it, all of which would count as work.

You could reply to the twenty-odd comments that accumulated under yesterday’s post. Several are friendly, two ask reasonable questions, and one is from somebody who seems to be building nearly the same product and would like to compare notes. You could take a call with an operations manager at a forty-person firm who replied to a message last week saying, in substance, that they currently pay a contractor to do the thing your application does and would like to see it. You could spend the hour improving the outreach sequence, which has been producing replies at a rate you are not proud of and which you suspect could be fixed with better wording. Or you could interview a user who has been enthusiastic about the product for a month, has requested three features, and works at a company where, as far as you can tell, they have no budget and no ability to approve a purchase.

Every option is defensible. Every option will produce something you can point to at the end of the hour. Their expected commercial value is not remotely similar, and for most of the founders I have watched, including me on plenty of Tuesdays, the choice tends to be made by whichever option is closest to hand rather than by which one could change the business.

That is the problem this chapter is about. The previous two chapters were about access: how a relevant buyer comes to encounter the offer, and what trust arrives with them when they do. Once access starts working, even a little, a new constraint appears that founders rarely plan for. The bottleneck stops being can anyone find us and becomes which of these interactions deserves the founder’s attention. Before a business has a repeatable channel, a sales team, or a marketing budget worth the name, the founder’s hours are the acquisition system. There is no other one. Every conversation the founder has is a conversation some other person did not get, and every hour spent on an interaction that cannot alter the commercial hypothesis is an hour the hypothesis stays exactly as uncertain as it was.

I did not treat my own time this way for a long time, and I understand why. Conversations feel like progress because they are visibly commercial. A founder who spends the afternoon coding can worry that they are hiding in the product. A founder who spends the afternoon in calls and comment threads and outreach tooling has clearly been doing the commercial work, and the calendar proves it. The trouble is that the calendar records that conversations occurred. It does not record what they were capable of teaching.

Builders are especially exposed to this because we like queues. Give an engineer a list of things to respond to and the engineer will respond to them, in order, with care, until the list is empty. It is a good instinct for a support inbox and a poor one for early acquisition, where the items in the queue differ by orders of magnitude in what they can reveal. The twenty comments and the operations manager’s call arrive in the same notification tray with the same visual weight. Nothing in the interface suggests that one of them is worth roughly nothing commercially and the other might be the most informative hour of the quarter.

So the useful question is not how many conversations you can have this week. It is which conversation, if it happened, could change what you believe about the buyer, the problem, the offer, the price, the trust required, or the path. That is a different way to rank a calendar, and it produces uncomfortable results. Some flattering conversations move to the bottom. Some awkward ones, with people who are skeptical, busy, and unlikely to become friends, move to the top, because they are the ones close enough to a real decision that their reaction contains information.

None of this means the low-value interactions are worthless in every sense. The commenter building a similar product might become a useful peer. The enthusiastic user without a budget might describe the workflow better than anyone with authority ever will. Community goodwill and public responsiveness have their own jobs, and I would not tell a founder to ignore everyone who cannot sign a contract. The claim is narrower. When the founder’s hours are the acquisition system, those hours should be allocated according to what an interaction can reveal, and most founders are allocating them according to what an interaction feels like.

The rest of this chapter is about how to tell the difference before the hour is spent. That requires a clearer idea of what a conversation is for.

Fit, Pain, and Whether the Problem Is Live

The first thing I want to know about a prospective conversation is whether the person resembles a buyer, and I mean that in the sense we established in Part II, not in the sense of a persona sheet. Job title, company size, and industry are useful as rough filters. They are not the thing. The thing is whether this person lives with the problem the product addresses, whether that problem costs their organization something measurable, and whether the cost is currently causing anyone to do anything about it.

Those three questions are worth separating because they fail independently, and each failure produces a different kind of low-value conversation.

A person can be in the right industry, at the right size of company, with the right title, and simply not have the problem. The head of operations at one logistics firm has an ugly reconciliation process between two systems. The head of operations at a nearly identical firm switched platforms two years ago and does not. Both will take the meeting. Only one of them can tell you anything about whether your product solves an expensive problem, because only one of them has it. The other will offer opinions, and opinions from people without the problem are the most abundant and least useful commodity in early-stage selling.

A person can have the problem and not have the cost. Plenty of problems are real and irritating and financially trivial. If the reconciliation takes forty minutes a month and is done by whoever is least busy, the firm has a problem and no reason to spend money on it. The conversation will be friendly. The person may genuinely want the tool. It will not teach you whether anyone will pay, because for this person the rational answer is no, and you already knew that before the call if you had asked about the cost.

And a person can have an expensive problem that is not, at the moment, live. This is the failure that catches careful founders, because the fit is real and the pain is real. But the problem sits in a category the organization has decided to tolerate. Nobody is assigned to it. No budget line exists for it. No deadline is attached. It comes up at the quarterly meeting, everyone agrees it is annoying, and it goes back to sleep. A conversation with that buyer can be informative about the problem and almost uninformative about purchase, because the question “would you act on this?” has already been answered by the organization’s behavior, and the answer is “not yet.”

That is why I rank conversations partly by the evidence of current behavior. What is the person already doing about the problem? A spreadsheet, a contractor, a part-time employee, a monthly fire drill, a workaround so ugly they are embarrassed to describe it. Existing spend and existing labor are the most reliable signals I know that a problem has crossed from annoying into economic, and a person who can describe the workaround in detail is somebody whose reaction to your offer carries weight. They are comparing it to something real. A person who has no workaround, because the problem has never been worth solving badly, is comparing your product to nothing, and “better than nothing” is not a purchase decision.

None of this requires an interrogation before agreeing to talk. Most of it can be learned from two or three questions in the message exchange that precedes the call, or from the first five minutes of the call itself. What do you do today when this happens? Who does it? What does it cost you in time, money, or risk when it goes wrong? Founders often skip those questions because they sound presumptuous, and instead spend the first twenty minutes demonstrating the product to somebody who, it turns out, does not have the problem. Asking early is not rude. It is respectful of both people’s time, and the answer usually tells you more about the conversation’s value than anything the person will say about the software.

There is one exception worth naming. Sometimes the most informative conversation is with somebody who has the problem intensely and cannot buy. A team lead who runs the workaround personally may understand it far better than the director who owns the budget. That conversation is worth having, not to sell, but to learn the shape of the problem in enough detail that the later conversation with the director is sharper. The mistake is not talking to the team lead. It is coming away from the team lead believing you have evidence about purchase.

Which raises the second condition. Having the problem, and even paying for the workaround, does not mean a person can decide anything.

Authority and the Distance to a Decision

The persona chapter made the point that the payer, the user, and the champion are often three different people. This chapter has a narrower use for that distinction. When deciding who to spend an hour with, I want to know how far the person sits from the decision, because that distance determines what their reaction can prove.

A person with authority can do something after the conversation. They can approve a pilot, sign something, allocate budget, or at least say a credible no. Their reaction is therefore evidence about purchase, not merely about preference. A person without authority can be interested, helpful, and right about everything, and still only tell you what they would do if the decision were theirs, which it is not. Both conversations can be worth having. They are not worth the same.

Authority is also less visible than titles suggest. In the CTO story from Part II, the person who looked like the decision-maker on every persona exercise turned out to be nowhere near the consequence, while a director of operations who received a forwarded message owned the budget, the staff, and the recurring cost. One conversation with him was worth more than the entire CTO list, not because directors of operations are better people, but because he was close enough to the decision that his behavior meant something. He could agree to a paid pilot. He did. A CTO nodding politely could not have produced that evidence no matter how well the meeting went.

So the question before a conversation is not only “does this person have the problem” but “what could this person do if they were convinced?” The answers sort roughly into three groups. Some people can decide. Some cannot decide but can move the decision: they influence the person who can, they would run the evaluation, they would be blamed if the tool failed, or they control access to the process the tool touches. And some can do neither. They can use the product, admire it, request features, and recommend it to nobody in particular.

The middle group deserves more respect than founders usually give it, because in most organizations of any size, the decision is not made by one person in one meeting. It is assembled. A champion who cannot sign can still tell you what the signer will ask, what happened the last time somebody proposed a tool like this, and whether the budget is real or theoretical. That is high-value information. The thing to avoid is treating a champion’s enthusiasm as though it were the decision. The champion may love the product and be unable to carry it past a procurement question you have never heard of. The trust chapter covered why. Here the point is simply that a conversation with a champion should end with a clearer picture of the decision path and the person who owns it, or it has not done its job.

The third group is where the hour problem gets expensive. People with no authority and no influence are often the easiest to talk to, precisely because nothing is at stake for them. They reply quickly. They are available. They are kind. A founder can fill a week with them and feel productive. I have done it. The conversations were enjoyable, and I could not, afterward, name a single belief they had changed.

There is a version of this mistake that looks more sophisticated. The founder targets senior people, on the theory that authority is what matters, and ends up with a calendar full of executives who have authority over everything and attention for nothing. A managing partner can approve the spend. Whether the managing partner has any idea how the reporting workflow currently runs, or cares, is a different question. Authority without proximity to the problem produces a conversation in which the person could decide but has no basis for deciding, and those tend to end in “send me something,” which is not a next step so much as a polite way of returning the hour.

The useful target is usually the person who is close to both: near enough to the consequence to understand it and near enough to the decision to act on it. In a small firm that may be the owner. In a larger one it is often a director or a senior manager who owns the process and its budget, one level below the title that looks right on paper. Finding that person is worth more preparation than founders typically give it, because it is the difference between a conversation that can produce a decision and one that can only produce a compliment.

Even the right person, though, can be the wrong conversation this month. Authority tells you whether a decision is possible. It says nothing about whether one is coming.

Timing

Founders tend to treat timing as luck, which is a reasonable way to describe something you have not tried to observe.

A buyer’s readiness to act is not random. It is usually attached to something: a contract renewal, a new hire who inherited the workaround and hates it, an audit, a lost client, a busy season approaching, a system migration already underway, a manager who was just asked why the numbers were late again. The trigger does not create the problem. The problem was there all along. The trigger is what moves the problem from the tolerated category into the category where somebody is willing to spend an afternoon evaluating a solution and a budget line paying for it.

For conversation ranking, this matters because a buyer with fit, pain, and authority who has no trigger is, for now, a well-informed person with no reason to decide. The conversation can still teach you about the problem. It cannot teach you much about purchase, because the honest answer to “would you move on this?” is “not this quarter,” and you will hear it as “yes, eventually,” which is the most commercially misleading sentence in the language.

I would rather have the conversation with the buyer whose trigger is visible. The firm that just lost a client over a late deliverable. The operations lead who mentioned, in passing, that the person who ran the spreadsheet is leaving in March. The agency whose largest customer has started asking for reporting it cannot currently produce. Those people are not more important than the others. They are closer to a decision, and proximity to a decision is what makes their reaction informative.

Triggers are also unusually easy to ask about, and unusually rarely asked about. “What made you reply now?” is a better first question than “tell me about your business,” and the answer often reveals whether you are talking to someone in motion or someone being polite. If the reply is “I’ve been meaning to look at this for a while,” the timing evidence is weak. If the reply is “we have a new client starting in six weeks and we can’t do this by hand for them,” you have learned what the buyer’s urgency is made of, and you can shape the rest of the conversation around it.

There is a temptation here that the book has warned about before, and I will only gesture at it. When a founder discovers that timing matters, the next idea is often to manufacture it: countdown timers, expiring discounts, “only three pilot slots left” for a product with no capacity constraint. The purchase-moment chapter already explained why invented urgency is a poor substitute for real urgency and a good way to spend trust you have not yet earned. The point here is different and quieter. Real triggers exist in the market whether or not you invent fake ones, and the founder’s job during the early period is to notice them and prioritize the people who have them.

That has a useful side effect for how outreach and content get designed, which the previous chapters left open. If you know what the triggers look like, you can often recognize them from the outside. A job posting for the role that currently runs the workaround. A public complaint about a competitor. A regulatory date approaching. A new integration announced by a platform your buyers use. None of those is proof. Each is a reason to move a particular conversation up the queue.

Timing is the condition founders most often ignore because it is the one that makes them feel least in control. You can choose whom to contact. You cannot choose when their problem becomes urgent. But you can find out, and you can spend your hour with the person for whom the answer is “now.”

Even then, one more condition remains, and it is the one most likely to be missing when everything else looks right. The person may have the problem, the authority, and the trigger, and still tell you nothing true.

The Next-Conversation Queue

I am going to describe a scoring method, and then I am going to tell you not to trust it very much. Both halves are sincere.

The method exists because the alternative, choosing conversations by whichever notification arrived most recently, is worse. The distrust exists because the moment a founder puts numbers on human beings, the numbers acquire an authority they have not earned. Treat what follows as a way of forcing yourself to ask the right questions about each conversation before you spend the hour, not as a formula that produces the answer.

For each conversation you could have this week, rate the person on the conditions this chapter has walked through. Do they resemble a plausible buyer, meaning they live with the problem in a context where it matters? Is there evidence of economic pain, ideally an existing workaround, spend, or labor you can name? Do they have authority, or credible influence over the person who does? Is there a visible trigger that makes action plausible soon? Can you reach them in a way that lets a serious conversation happen, and does the trust path they arrived through give them any reason to take you seriously? And will they tell you the truth?

A simple scale works: zero, one, or two for each, where zero means “no evidence,” one means “plausible,” and two means “observed.” I would not use a ten-point scale. Nobody knows the difference between a six and a seven, and the extra precision mostly serves to make the spreadsheet look more scientific than the underlying knowledge. Add the scores if you like. Then read the rows, because the sum hides the thing that matters, which is usually a single zero.

A prospect who scores two on everything except authority is a superb source of problem understanding and a poor use of an hour if what you need this week is purchase evidence. A prospect with a visible trigger, real pain, and real authority who arrived through a cold message and scores zero on trust is worth the hour, but the hour should be spent differently: less demonstration, more establishing why they should believe you. A prospect who scores one across the board is the most dangerous row in the table, because nothing disqualifies them and nothing recommends them, and founders fill weeks with ones.

Then do the part the spreadsheet cannot. Look at the ranking and ask whether it matches your judgment, and where it does not, ask why. Sometimes the score is wrong because a condition was scored optimistically. “Plausible authority” often means “has a senior-sounding title,” which is not the same thing. Sometimes the judgment is wrong because it is being pulled by how pleasant the person is, and the score is doing its job by pointing that out. The exercise is a conversation between the two, and it takes about twenty minutes for a list of ten.

A hypothetical makes the stakes concrete. Suppose you sell a workflow tool to operations teams, and a university course has adopted the free version for a class project. Fifty students are using it. Several have written glowing messages. A few have asked for features. Meanwhile one operations manager at a mid-sized firm replied to an outreach message saying she currently pays a contractor about $1,500 a month to do the work manually and would like to see how the tool handles a real month of her data. Fifty conversations are available on one side and one on the other. The fifty will be warmer, easier, and more numerous, and they will generate a great deal of encouraging activity. They score zero on economic pain, zero on authority, and zero on trigger. The one scores well on nearly everything and carries a specific number you can test a price against. There is no version of the early acquisition problem in which the fifty are the better use of the week, and there are many founders who would spend it on them anyway, because fifty feels like traction and one feels like a meeting.

The founder with the large audience from two chapters ago faced a version of the same choice. Six consultant conversations against another six thousand impressions. The six won not because six is a magic number but because each of those conversations could produce introductions to buyers with the problem, and none of the impressions could.

The queue also changes what counts as a good week. A founder who measures acquisition by activity reports the number of calls held. A founder who measures it by evidence reports something different: which beliefs were strengthened, which were weakened, which conversation produced a commitment or a specific refusal, and what the next test should be. Three conversations that moved the buyer hypothesis are a better week than fifteen that did not, and it takes some discipline to say so out loud when the fifteen looked busier.

I will end with the caveat that started the section. The score is a way of noticing. It is not the decision, and it should be revised every time a conversation teaches you that one of the conditions was scored wrong. The first time a prospect with a perfect score declines a pilot for a reason you had not considered, the reason belongs in the model.

What the queue cannot do is tell you what to do once you are in the room with the right person. A good conversation is not the goal. It is the point at which the sequence this book has been assembling, buyer, paid problem, smallest offer, price, commitment, trust, path, finally has to run end to end with a real human being on the other side of it. That sequence has a name.