How much research does one account deserve?

The question

I judge account research by the decision it enables and the question worth checking next.

Research is central to how I want Mach to work. I want it to change whom the seller approaches, what they ask, which offer may be relevant, or whether they should wait. A company summary can be accurate and still leave those decisions unresolved.

That gives me a practical stopping question: what could another source change?

I would settle the decision before setting a timer

In an r/salesdevelopment discussion[1], an SDR whose author name now appears as [deleted] described manual research that left them able to send only “a handful of emails a day.” They were checking profiles, company search results and websites.

u/ElectricElephant4128[2] described checking account requirements: “I’ll spend an entire day and finish with a list of like 30 leads”. u/ReachBeautiful1268[3] suggested, “Set a timer for 2-7 minutes.”

A different context produced a different answer. In an enterprise-sales discussion, u/shadowman180[4] described UK payments work and wrote, “Research takes 30-45 mins and another 15 to draft messages.”

Those are individual practices. I would not turn either interval into the team’s standard without first defining the decision. Preparing an initial question and preparing for an evaluation involving several teams require different evidence.

My read is that a time limit becomes useful after the seller knows what must be learned. Otherwise it can reward either stopping too early or continuing without a purpose.

Give the research a job

Consider a fictional seller offering payroll software to retail businesses.

Before a first conversation, I would want the research to establish whether the company fits the offer, whether the person’s role is current and relevant, and whether a colleague is already working the account. If payroll ownership is unclear, that may be the question the seller asks.

Now give the same account an active evaluation, several business units and a known implementation deadline. I would expect more preparation: prior conversations, current tools, the teams affected, who approves a change and what the buyer has already requested.

I would deepen the research as the next decision becomes more consequential.

For an existing account plan, I would start with what is already known and check what could have changed. Rebuilding a company profile while missing a recent buyer conversation is the wrong order of work for this decision.

Marcus Chan’s Salesforce discovery guide[5] treats discovery as continuing through the sale and potentially involving several people. I agree with leaving room for that learning. Public research should prepare the seller to listen and ask specific questions.

More research has a cost; missing research does too

The team pays for data and tools. A person spends time checking the answer. An opportunity can change while that work continues.

Stopping early has consequences as well. An old role can point to the wrong person. A missed relationship can interrupt a colleague’s deal. An unchecked customer result can put an unsupported claim into a proposal.

I would use three questions before extending a run:

Step 1: What decision could this source change?

Step 2: What happens if the missing fact is wrong?

Step 3: Who is best placed to answer it?

A current account owner may resolve the relationship question. A buyer may be the only person who can explain whether the problem is a priority. Another general company page may repeat the summary without helping either decision.

This is why I want open questions retained. An honest gap gives the next seller a choice about what to check.

Show what the research covered

“Nothing found” is too little for me to judge the next step. I want to know whether a source was read, returned nothing useful, failed or was skipped.

Mach’s configurable research-agent model has those 4 coverage states, plus open questions and conflicts. It also has separate model and data budgets. These structures can explain the boundary of a run. They cannot establish that the boundary was right for the seller’s decision.

A run can hit its budget before finding an important fact. It can also spend more and produce another version of information already known. I want the review to connect spending and coverage to what changed in the account decision.

Method and scope: Coverage, budget and engine-selection statements were checked against the November 5, 2026 source snapshot. They describe the configurable research agent; a separate path is configured as the default. No optimal duration, live-run quality or customer outcome was measured.

Review the decision the brief enabled

For a sample of accounts, I would compare the brief with what happened next. Could the seller find the relevant person, see the existing relationship, support the claim they used and name the next question?

I would keep examples where an added source changed the action, and examples where a missing fact caused rework. If the same gap keeps causing the problem, that is a reason to add a check at that stage.

The output I want is evidence the seller can use, including a reason to stop. A source that changes the decision should stay beside the decision, as in carrying the original clue into the handoff.

Which fact has most often changed your decision to contact an account after the research was already done?

How this post was made: AI assisted the research and drafting from supplied product principles. Public quotations and handles were checked on November 5, 2026. Implementation details were checked against the dated source snapshot. The fictional examples are labeled.

Related reading

This post is part of our guide to account research with a source for every fact.

Related reading: The Brain: check sources and correct what Mach learns and An account research brief for software services teams.