The Discovery Call Is Not a Formality. It Is Where You Qualify the Client.

by Arif Ikhsanudin, Backend Developer

Most contractors treat the discovery call as an audition. The better frame: it is a mutual evaluation, and the contractor who asks better questions usually wins.

The Asymmetry Most Contractors Accept

In most discovery calls, the dynamic is roughly: the client asks questions to evaluate the contractor, the contractor answers and tries to impress, and at the end the client says they will be in touch.

This dynamic treats the contractor as the less powerful party in the room — someone who needs to prove themselves before being permitted to work. Some contractors accept this framing and play along. The more effective ones recognize that the call works better as a genuine two-way evaluation.

The client is not your employer. They are a potential business partner. Both parties need to decide whether this makes sense. That is what a discovery call is.

What You Are Trying to Learn

Before the call, be clear about what you need to know to decide whether to proceed:

The problem and the stakes. What specifically needs to be built or fixed? What happens if it does not happen? Is this a critical path item or a nice-to-have?

The decision-making structure. Who is the actual decision-maker? Is the person you are talking to the one who approves the contract? Or is there someone else involved who you have not met?

The timeline and the reason for it. Is the deadline real and external (a launch, a compliance requirement, a board commitment) or is it aspirational? This tells you a lot about how the engagement will be managed.

The budget range. You do not need an exact number on the first call, but you need to know if you are in the same ballpark. A brief probe — "Do you have a rough sense of the budget you're working with for this?" — surfaces whether the conversation is worth continuing before anyone invests more time.

What has been tried before. If they have already worked with other contractors on this, why are they looking for someone new? What did not work? This is some of the most valuable information you can get.

The Questions That Signal Expertise

The questions a contractor asks on a discovery call communicate as much as the answers they give. Questions that show you have done this before:

  • "What does a successful outcome look like six months after this is shipped?"
  • "What's the biggest risk to this project from your perspective?"
  • "Who else will be depending on this system once it's live?"
  • "Is there existing infrastructure this needs to integrate with, and do you have documentation for it?"

These are not gotchas. They are the questions an experienced engineer asks because they know from experience that these are the things that determine whether a project goes well.

The Red Flag Screening

Discovery calls are also where you screen for engagements that are likely to go badly. Some signals worth taking seriously:

  • Vague answers about scope. If the client cannot articulate what they need at a high level, the engagement will be defined by constant back-and-forth and shifting requirements.
  • Pressure to start immediately without a signed agreement. "We'll sort out the contract later" is where many scope and payment disputes begin.
  • Unusual pushback on basic professional expectations. If asking about a deposit or a statement of work produces a negative reaction, that is data.
  • Stories about previous contractors that do not add up. If every past contractor was incompetent or difficult, consider what the common element is.

You do not need to confront any of these in the call. But they are worth weighing before you send a proposal.

Closing the Call With Clarity

The best way to end a discovery call: summarize what you heard and ask if you got it right. "Based on what you've shared, it sounds like you need X by Y, the main concern is Z, and the budget is in the range of A. Is that right?"

This does two things. It confirms you understood. And it moves the conversation from vague to specific, which makes the proposal you send afterward much sharper.

A discovery call is not a chance to impress the client — it is the chance to figure out whether this is a client worth impressing.

Scale Your Backend - Need an Experienced Backend Developer?

We provide backend engineers who join your team as contractors to help build, improve, and scale your backend systems.

We focus on clean backend design, clear documentation, and systems that remain reliable as products grow. Our goal is to strengthen your team and deliver backend systems that are easy to operate and maintain.

We work from our own development environments and support teams across US, EU, and APAC timezones. Our workflow emphasizes documentation and asynchronous collaboration to keep development efficient and focused.

  • Production Backend Experience. Experience building and maintaining backend systems, APIs, and databases used in production.
  • Scalable Architecture. Design backend systems that stay reliable as your product and traffic grow.
  • Contractor Friendly. Flexible engagement for short projects, long-term support, or extra help during releases.
  • Focus on Backend Reliability. Improve API performance, database stability, and overall backend reliability.
  • Documentation-Driven Development. Development guided by clear documentation so teams stay aligned and work efficiently.
  • Domain-Driven Design. Design backend systems around real business processes and product needs.

Tell us about your project

Our offices

  • Copenhagen
    1 Carlsberg Gate
    1260, København, Denmark
  • Magelang
    12 Jalan Bligo
    56485, Magelang, Indonesia

More articles

Seattle Backend Salaries Hit $175K Because Big Tech Sets the Floor — Here Is How Startups Compete

You wrote a job post with a salary range you thought was competitive. Then you watched every qualified applicant ghost you after the first screen.

Read more

How to Politely Push Back on Unreasonable Demands

Clients can sometimes ask for the impossible—or the unreasonable. Here’s how to set boundaries without burning bridges.

Read more

Spring Boot vs Micronaut — Which One I'd Pick for a Greenfield Service

Micronaut's compile-time DI and sub-second startup make a compelling case on paper, but the real question is whether the ecosystem maturity gap and steeper learning curve are worth it for your actual deployment context.

Read more

Red Flags That Predict Software Project Failure

“It’s probably fine… we just need a bit more time.” That sentence has quietly preceded more failed projects than anyone admits.

Read more