You found a dev agency that looks like a good fit. You filled out the contact form. The discovery call is on the calendar.
Now what?
Most business owners walk into that first meeting with a rough idea in their head and a lot of unanswered questions. That is fine, agencies expect it. But showing up with even a little preparation makes a big difference. You get a more accurate quote, a shorter path to a signed agreement, and a clearer sense of whether this agency is actually the right fit for your project.
This guide covers exactly what to prepare, what to expect during the call, and the questions worth asking before you hand over a deposit.
Why the First Meeting Sets the Tone for Everything
The discovery call is not a sales pitch. At least, it should not be. A good agency uses this time to understand your project well enough to price it accurately and tell you honestly whether it is the right fit.
What you bring to that conversation determines the quality of what comes back. A vague description gets you a vague quote with wide ranges and a lot of asterisks. A clear description gets you a specific number, a realistic timeline, and a proposal you can actually evaluate.
The first meeting is also your opportunity to evaluate them. Notice how they listen. Notice whether they ask smart follow-up questions or jump straight into pitching their portfolio. The way an agency handles a discovery call is often a preview of how they handle a project.
What to Have Ready Before the Call
You do not need a technical specification. You do not need wireframes or a design mockup. You do not need to know what programming language your project should use.
Here is what you do need.
A one-sentence description of the problem you are solving.
Not what the product does, what problem it fixes. “My team spends 90 minutes every morning manually entering new leads from our contact form into our CRM” is useful. “I want to automate my business” is not. The more specific you are about the pain, the better the agency can scope a solution that actually addresses it.
A rough list of the features you think you need.
Write down every feature that comes to mind, then cut the list in half. Keep only the features that are essential for the product to be useful on day one. Everything else can be Phase 2. Agencies call this an MVP, a minimum viable product, and it is almost always the right starting point. If you are not sure how to think through this, our post on how to write a project brief covers this process in detail.
A list of the tools your business already uses.
If your project needs to connect to your CRM, your payment processor, your email platform, or your booking software, that affects the scope and the price. Missed integrations are one of the most common sources of budget surprises. Write down every software tool your business depends on and be ready to share that list.
A budget range.
You do not need to name an exact number. A range like “$3,000 to $8,000” or “I have up to $15,000 for this” is enough. Sharing a budget lets the agency tell you what is achievable within your constraints rather than sending you a quote that is three times what you had in mind. If you have no idea where to start, our post on what to expect working with a dev agency includes a breakdown of how project scope connects to cost.
A timeline, if you have one.
If you are building toward a product launch event, a partnership deadline, or a funding announcement, say so upfront. Hard deadlines affect how a project gets resourced and whether the timeline is even achievable. If you have no hard deadline, that is fine too, but sharing a preference like “we want to launch within 10 weeks” gives the agency something to plan around.
What to Expect During the Meeting
A professional discovery call runs 30 to 60 minutes. Here is what that time should look like.
The first 15 to 20 minutes will be the agency asking you questions about your project, your business, your users, and your goals. Let them drive this. A good agency asks about the problem before they talk about solutions.
The next 10 to 15 minutes is usually a discussion of scope, what is in, what is out, and what decisions need to be made before a quote can be generated. Some agencies can give you a ballpark on the call. Others need a few days to review the scope before sending a formal proposal. Both are normal.
The last 10 minutes or so should be yours. Ask your questions. Get a sense of how they work and whether the relationship feels like the right fit.
By the end of the call, you should leave with:
- A clearer picture of what you are actually building
- A rough sense of timeline and cost
- A clear next step (when the proposal arrives, what it will include)
- A gut feeling about whether this is the right team
If you leave feeling confused or pressured, that is a signal worth paying attention to.
The Questions Worth Asking
Not every agency runs a clean process. These questions help you separate the ones that do from the ones that do not.
How do you handle scope changes mid-project?
The honest answer is: they cost extra, and here is how we figure out the price. Any agency that says “we handle scope changes at no charge” is either building a massive buffer into the original price or is going to cut corners somewhere to make up the difference.
Who owns the code when the project is done?
The answer should be: you do. Walk away from any arrangement where the agency retains ownership of your codebase or where your product only functions on their proprietary platform.
Do you give fixed pricing or hourly billing?
Fixed pricing on a defined scope protects you. Hourly billing with an open estimate is a risk. If an agency prefers hourly, ask them for a hard cap, a maximum number of hours they will bill before flagging a conversation about scope. Get that in writing.
Can you show me examples of projects similar to mine?
You are not just evaluating the visual design of their past work. You are looking for evidence that they have built something in the same category, a booking system, an integration, a customer-facing web app, and that it shipped to real users. Ask what happened after launch.
What does your communication look like during a project?
Good agencies communicate proactively. You should expect a regular update (weekly at minimum) without having to ask for it. If an agency is vague about this, “we’ll be in touch when there’s something to share”, that is a warning sign.
What does the handoff look like?
When the project is done, you need to be able to manage it. Ask what documentation you will receive, whether there is a walkthrough session, and what the process is for reporting bugs after launch. A professional agency plans for the end of the project before the project starts.
Red Flags to Watch For
Some things signal that a meeting is going in the wrong direction.
The agency talks far more than they listen. They present their portfolio before asking a single question about your project. They struggle to explain in plain language how the project would work. They cannot give you even a rough timeline or cost range after a 45-minute conversation about your project. They pressure you to sign before you have had time to review a written proposal.
None of these are catastrophic on their own. But if you notice two or three of them in a single call, trust that instinct.
After the Call: What Comes Next
Within a few days, a professional agency should send you a written proposal. This document covers the project scope, the deliverables, what is explicitly out of scope, the price, the payment terms, and the timeline.
Read the out-of-scope section as carefully as you read the scope section. That list is what prevents budget surprises from appearing six weeks into the project.
Before you sign, make sure you understand:
- What exactly you are getting when the project is complete
- What the revision process looks like during development
- What happens if something goes wrong and the timeline slips
- When payments are due and what triggers each payment
If anything in the proposal is unclear, ask before you sign. That conversation is much easier before work starts than during it.
Key Takeaways
- You do not need technical knowledge to prepare for a discovery call, you need to be able to describe your problem clearly
- Write down your core features and cut the list in half before the meeting, only include what is essential for launch
- Share your existing tools, your budget range, and your timeline preference upfront, vague inputs produce vague quotes
- The questions that matter most: who owns the code, how are scope changes priced, and what does the handoff look like
- A good agency listens more than it talks in the first meeting, treat the call as a two-way evaluation, not a pitch
- Do not sign anything before receiving and reading a written proposal with a clear scope and out-of-scope list
Ready to Have That First Conversation?
Bring what you have, a rough idea, a problem you want to solve, or even just a list of questions. Our discovery calls are real conversations, not sales presentations. Whether you need MVP development, workflow automation, or a custom website, we will help you figure out the right next step and give you a clear picture of what building it would actually involve.
No commitment required. No technical knowledge needed.