.svg)
In a 90-day Asia go-to-market validation sprint across Singapore, Malaysia, and Taiwan, one of the fastest ways to lose a good enterprise prospect is to run your home-market discovery script without changing what call one demands. In many B2B sales playbooks, a rep cannot mark an opportunity as qualified unless the buyer shares a budget number on that very first call. A prospect who will not share budget on call one is not necessarily unqualified. You may simply be asking for the wrong output.
Why the First-Call Budget Question Backfires:
When your discovery script demands a dollar figure in the first thirty minutes, you force buyers into a corner before they have any reason to trust you. Enterprise buyers in Singapore, Malaysia, and Taiwan rarely hand internal budget figures to a vendor they just met. If your qualification checklist treats a missing budget number as an automatic disqualifier, your team will drop cautious buyers who could have become real customers two quarters later, while keeping polite talkers who throw out a rough guess just to end the call.
We have argued before that enterprise buying decisions often centre on protecting four things: budget, reputation, compliance, and internal approval. Building on that premise, you can change what call one is designed to capture. Instead of demanding a budget figure upfront, use the first call to map the buyer's internal risks and approval path. Treat this discovery map as a framework to test on your own pipeline, not a proven result.
Four Discovery Questions to Swap on Call One:
The goal of your first call is to leave with four risks and one clear approval path written down. Here is how to reword the four questions that usually shut buyers down:
1. Budget risk: Swap "What is your budget?" for "What would make this spend hard to defend internally?" Asking for a raw number invites a defensive brush-off. Asking what makes the spend hard to defend gets the buyer talking about how their finance team or business unit leader actually evaluates new software. You learn whether the cost needs to be tied to headcount savings, a specific quarterly initiative, or an existing departmental line item, without forcing them to quote a price on the spot.
2. Reputation risk: Swap "Is your current vendor failing?" for "If a rollout like this went wrong, who would feel it first?" Very few Champions want to tell a stranger that they picked a bad vendor last year, because admitting a failed purchase reflects poorly on their own judgment. When you ask who would feel the pain of a bad rollout first, the buyer opens up about operational pressure, service-level expectations, and the internal teams whose trust is on the line.
3. Compliance risk: Swap "Do you have security requirements?" for "Which reviews would a new vendor need to pass?" A yes-or-no question about security almost always gets a vague "yes, standard checks" until legal and IT block the deal months later. Asking which specific reviews a new vendor must pass prompts the buyer to name the actual hurdles early, whether that is an internal cybersecurity audit, data-handling sign-off, or industry-specific vendor registration.
4. Approval risk: Swap "Are you the decision-maker?" for "Who else would want to see this before it moves forward?" Nobody likes admitting on a first call that they lack the authority to sign a contract. Asking who else would want to weigh in removes the ego from the conversation and lets your contact map out the buying committee naturally.
Document the Approval Path Before You Ask for the Number:
Alongside those four risk answers, call one should produce one written artefact: the approval path. Before you move the deal forward, write down the named reviewers, the sequence in which they review, and the specific documents each person expects to see.
Once that approval path is documented, move your budget confirmation to a named later step, such as stage 2 or stage 3. By that point, you know how the deal gets approved, you have helped the buyer articulate the internal case, and you have earned the right to talk numbers. Under this approach, a lead qualifies early when the risks are clear and the approval path is mapped, and it gets disqualified only when neither emerges. Test it on one segment first, and compare stage progression against your current process before rolling it out across the team.
Test Your Discovery Process Before You Scale Headcount:
Running buyer-safe discovery is part of the same discipline as filtering your pipeline and tracking your own stage velocity: you protect your expansion budget by learning how local buyers actually approve software before you hire a full local team. That is why we advise founders to build local presence before permanent headcount and follow a structured validate, enter, sustain sequence. If you want to test how your discovery and qualification hold up with real buyers in the region, start with SBC Expand's approach to entering Singapore, Malaysia, and Taiwan.
.png)
