Negotiate Discovery-Call Tasks Before Assigning Them
Use a fictional live dialogue to handle a refusal, narrow a buyer task, defer absent-owner work and record only accepted commitments.
10/24/20263 min read
The final minutes of a discovery call are a negotiation about work, not a chance to announce everyone’s homework. Ask the person expected to perform a task whether the output, effort, authority, and timing are acceptable. A useful close can contain a refusal, a narrower alternative, and an accepted seller task without forcing the buyer into another meeting.
The dialogue below is entirely fictional. It shows agreement being formed during the call, before any recap or AI action extraction exists. The aim is to practice asking and adjusting, then record only the work that survives that conversation.
Set up a concrete evaluation need
Seller Leah and buyer Arun are discussing account-routing software. Buyer operations colleague Mira is also present. Leah needs to understand one routing exception, but she has not established that a live database is necessary or permitted. Arun has twenty minutes available next week, and Mira is not authorized to approve data exports.
Leah starts with the desired decision: “To judge whether a demonstration would help, I need to understand what happens when two teams claim the same account. Could we agree the smallest example that would answer that?” This makes the purpose visible before a task is assigned.
Let the first request be declined
Leah: “Would you be willing to send a recent CRM export before Friday?”
Arun: “No. Preparing it would take too much time, and I cannot approve sharing the records.”
Leah: “Understood. We will not make that an action or treat Friday as your deadline. We can use an invented case instead.”
The refusal changes the proposed work. Leah does not ask Mira to obtain the same export through a different route, and she does not interpret the refusal as lack of seriousness. The real need is understanding one exception, not collecting the largest available dataset.
Negotiate a smaller contribution
Leah: “I can write a synthetic case with two account teams and one duplicate assignment. Arun, could you tell me whether the decision steps resemble your process, without adding customer details?”
Arun: “I can review one page for up to twenty minutes. I cannot review a full workflow or commit to a demo yet.”
Leah: “One page, one duplicate-assignment case, and no demo commitment. Would Tuesday at 14:00 UTC be a reasonable time for me to send it, with your review timing still open?”
Arun: “Yes to that scope and sending time. I will confirm when I can review it after I see the page.”
The accepted contribution is narrow. There is no Friday buyer deadline, no obligation to assess the whole product, and no accepted demonstration. Leah’s delivery time is distinct from Arun’s unresolved review time.
Keep absent authority out of the bargain
Leah: “Mira, should we ask your security lead to join a technical session?”
Mira: “Not yet. I cannot commit their time. If the synthetic case suggests a useful next step, I can ask which internal review route applies.”
Leah: “Then no invitation or security task today. We will leave that as an option, not an assigned action.”
Leah also avoids promising that her engineer will build a custom integration. She can accept responsibility for checking the documented feature herself, but another colleague’s work requires that colleague’s authority and agreement.
Read back the work that was actually accepted
Leah: “I will send the one-page synthetic case Tuesday at 14:00 UTC. You have agreed to review only that case, for up to twenty minutes, with timing to be confirmed. No live export, demo booking, security invitation, or integration build is agreed. Is that accurate?”
Arun: “Yes.” Mira confirms that no action has been assigned to her security colleague.
The resulting accepted-work record has two active rows. Leah owns one synthetic page, with the agreed sending time and duplicate-assignment scope. Arun owns a limited review of that page, with no due date established. A separate boundary note records the declined export and the deferred options without putting them in anyone’s task queue.
Check that the alternative remains proportionate
The NIST Privacy Framework provides general context for considering data-processing purpose and risk. It does not prescribe this dialogue or determine the legal basis for a real data transfer. The synthetic alternative here is an original way to reduce the information requested for this particular evaluation.
Before ending, Leah asks what should happen if her example cannot stay within one page. Arun says to narrow it further rather than expand his task. That answer becomes a scope limit, not an invitation to send an appendix.
The call closes with a manageable exchange that both owners accepted. Its success is not the number of actions created afterward. It is that the requests were tested against effort and authority while the people responsible were present and able to say yes, no, or something smaller.