The discovery call that separates you from the seven other shops.
Senior buyers form their read in the first fifteen minutes of a discovery call. What they listen for is the difference between a vendor who has run a business and a vendor who has delivered code. The questions that signal one, the phrases that signal the other, and a script that reliably surfaces the right one.
A VP of engineering at a growth-stage US company is on her seventh vendor discovery call this week. She will make a shortlist of three by Friday. In the first fifteen minutes of your call she is going to decide whether you make the list. She will not tell you what she is listening for. Here is what she is listening for.
She is listening for the difference between a vendor who has run a services business and a vendor who has delivered code. Both can do the work. Only one can be trusted with the account after the sale. Everything she notices in the first fifteen minutes is trying to sort you into one or the other.
What she stops listening for immediately
Team size. She does not care how many engineers you have. She cares whether you can staff the specific engagement she is describing with the right seniority mix, and she will find that out in question three.
Years in business. Years signal survival, not competence. She has seen twelve-year-old shops with two accounts and three-year-old shops with a client roster she recognizes.
Tech stack breadth. "We work across React, Vue, Angular, Node, Python, Go, Java, Rust" tells her you are a body shop. She wanted to hear that you have opinions.
Awards, certifications, partner tiers. She discounts these to zero unless they are structurally relevant, which she will assume they are not until proven otherwise.
What she starts listening for immediately
The questions you ask her before you pitch. A vendor who runs a business asks about her business first. A vendor who delivers code asks about her stack first. Which one you are gets decided in your first four minutes.
The specificity of her answers when she does ask about you. "We staff every engagement with a lead engineer at 40%, two mids at 100%, and a PM at 20%" tells her you have a delivery model. "We flex the team based on the project" tells her you do not.
Whether you push back on anything she says. If she describes an engagement scope that has an obvious flaw and you nod through it, she has learned you will nod through everything. If you name the flaw politely and propose an alternative, she has learned you can be a partner.
The five questions that signal you have run a business
Ask these in the first ten minutes. Every one of them signals experience without claiming it.
One: "Before we talk about the project, help me understand the business context. What has to be true about this engagement for it to be judged a success internally, six months after we ship?" That question tells her you know engagements are judged by internal narrative, not by shipping.
Two: "Who is going to be the day-to-day owner of this on your side, and what have you seen work and not work with previous vendors in that seat?" That question tells her you understand the client's operational reality.
Three: "When we hit a scope disagreement mid-project (we will), what is your preference for how we surface it and resolve it?" That question tells her you expect friction and have opinions about handling it.
Four: "What is the internal risk story on picking an offshore vendor for this? What does your director need to hear from you to sign off?" That question tells her you understand her memo problem.
Five: "What is your budget range, and if we came in significantly under it, what would that make you think?" That question tells her you understand pricing signals.
The phrases to stop using
"World-class team." Everyone says this. Nobody believes it.
"We are passionate about." Passion is not a differentiator. Skill is.
"End-to-end." Reads as "we do everything, so we specialize in nothing."
"Best practices." She wants your opinion, not the industry's.
"We treat every client like a partner." Every vendor says this. Very few show it in the discovery call.
The move that ends the call in a shortlist
At the end of the call, summarize what you heard back to her in three sentences and name the one thing that concerns you about the engagement. Not a pitch, not a next step. A concern.
"Based on what you described, I think the interesting engineering problem is X. I think the political risk to you internally is Y. And the thing that concerns me about the engagement, honestly, is Z, and here is why."
That closing does something almost no other vendor does. It ends the call with a signal that you were listening, that you understand her internal context, and that you have skin in the outcome. Vendors who end this way make the shortlist substantially more often than vendors who end with "any questions for us?"
- 01Senior buyers sort you into "runs a business" or "delivers code" in the first fifteen minutes. Everything else follows.
- 02Stop leading with team size, years in business, and stack breadth. She is discounting all three to zero.
- 03Ask five specific questions early. They signal experience faster than any pitch.
- 04The five stock phrases (world-class, passionate, end-to-end, best practices, treat like a partner) mark you as a body shop. Cut them.
- 05End the call by naming what concerns you about the engagement. That closing gets shortlists.
- What single question separates a serious offshore agency on a discovery call?
- Ask what the buyer will tell their board if this engagement lands and what they will tell their board if it does not. It surfaces the political stakes that decide renewals and reveals whether the buyer has actually thought the project through.
- How long should an offshore discovery call run?
- Forty-five minutes with a five-minute buffer. Enough time to reach the second layer of every question. Short enough that the buyer's calendar respects it and long enough that your team is not the reason a decision slipped a week.
- What should an agency send after a discovery call?
- A written recap inside 24 hours: the problem in the buyer's language, the constraints you heard, the two or three shapes a first engagement could take, and the specific next step you are proposing with a date attached.
Get vetted. Get listed. Get the paper that survives the memo.
Twelve-minute intake, three-day turnaround. A passing scorecard is the shortest path from a good deck to a serious shortlist.