Discovery Call Agenda

When to use this

• You want to qualify leads fast without sounding interrogative.
• You want to price work based on outcomes and constraints.

How to use this agenda

A discovery call agenda is a small piece of sales infrastructure. It is not a script you read word-for-word. It is a timeboxed structure that keeps the call calm, keeps you out of free consulting, and produces the notes you need to write a scoped proposal.

The template on this page is intentionally short: five sections for a 30-45 minute call. Copy it into your notes doc, use it live, and then reuse those notes to draft a Statement of Work.

If you are still building pipeline and want a simple approach that does not require an audience, start here: Find clients without an audience.

Quick start checklist

The goal is simple: walk out of the call with enough clarity to do one of these things confidently:

• say yes and propose a scoped first phase
• say no and explain why (briefly, politely)
• propose a smaller paid step if the uncertainty is too high

Before you join the call:

1. Open a notes doc and paste the agenda template into it.
2. Pre-fill the header: company, attendees, role of each person, and any context you already have.
3. Pick one outcome for the call: qualify, scope phase one, or decide the next step.
4. Decide your boundary for depth. You can be generous without designing the solution for free.

After the call, your follow-up is where deals either move forward or die. A clean recap and a crisp next step beats a perfect call with no close.

How to run a calm call

Calm is not a personality trait. Calm is structure. When you know what comes next, you do not rush, you do not over-talk, and you do not try to win the client in a single breath.

Here are the mechanics that make the call feel grounded:

• Start with a frame: timebox, agenda, and what happens after the call.
• Ask permission to interrupt: it lets you manage time without sounding abrupt.
• Use short recaps every 10 minutes to confirm you are hearing things correctly.
• Separate understanding from solving: your first job is clarity, not cleverness.
• End with a decision: next step, decision timeline, and who owns it.

If you tend to get anxious, pick one habit to practice: slow down, pause after questions, and take a breath before you answer.

If the call drifts into solution brainstorming, note it and redirect: "That's helpful. I'm going to capture it. Can we finish constraints so I can propose the right next step?"

The 5-section discovery agenda (30-45 minutes)

The template is deliberately plain. You are not trying to impress the client with a fancy process. You are trying to discover reality:

• why this matters now
• what is true today (not what people hope is true)
• what constraints shape the work
• what a safe first phase looks like
• what happens next and who decides

Treat the agenda as your notes structure. If you write down clean answers, you will have clean scope.

1) Context (5 min)

Context is your anchor. Without it, the call turns into a random tour of symptoms. Your job is to surface the trigger, the stakes, and the definition of success.

Core questions (from the template):

• What prompted this now?
• What does "success" look like in 30/60/90 days?

Useful follow-ups (pick a few, do not machine-gun them):

• What happens if you do nothing for the next 90 days?
• What have you tried so far? What worked? What did not?
• Who is feeling the pain most: sales, ops, support, engineering?

Notes to capture:

• the trigger and why now
• their definition of success in 30/60/90 days
• the stakes if this drags on (time, money, risk, reputation)

2) Current state (10 min)

The current state section is where you stop guessing. You want the concrete version of the story: the workflow, the tools, the handoffs, and where it breaks.

Core questions (from the template):

• What is happening today (process + tools)?
• Where does it break? What is the cost of delay?

When people answer vaguely, ask for a recent example: "Walk me through the last time this happened, step by step."

Useful follow-ups:

• Where does work pile up? Who notices first?
• What systems are involved (and who owns them)?
• What is the current workaround, and where does it fail?

Notes to capture: the real workflow (not the documented one), the systems and owners, and the failure points that drive scope.

3) Constraints (10 min)

Constraints decide the shape of the project more than ideas do. Two clients can describe the same problem and require completely different approaches because the constraints are different.

Core questions (from the template):

• Timeline and deadlines
• Stakeholders and approvals
• Access, data, compliance constraints

If you skip constraints, you will end up promising a timeline you do not control.

Useful follow-ups:

• What is the real deadline, and what drives it?
• Who needs to approve the work, and at what points?
• What access do you have today? What access might take time?
• What review cadence is realistic for your team?

Notes to capture: timeline drivers (not just dates), decision process, and all the "waiting" risks (access, approvals, reviews). This is also a good place to set expectations about client responsibilities later when you draft a SOW.

4) Scope and boundaries (10 min)

Scope and boundaries is where you turn reality into a safe first phase. You are not committing to the full transformation. You are defining the smallest set of deliverables that creates progress, with explicit exclusions.

Core questions (from the template):

• What is in scope for the first phase?
• What is explicitly out of scope?

If the client wants everything, pick a first phase that earns the right to do the next phase. The call is not the place to design a giant roadmap. It is the place to agree on a boundary that protects both sides.

Useful follow-ups:

• If we could only do one thing in the first phase, what would make the biggest difference?
• What does "done" mean for that deliverable?
• What assumptions must be true for this to work?
• What should we explicitly exclude so nobody is surprised?

Notes to capture: a draft first-phase deliverable list, a definition of done for each, and exclusions. If reality changes, handle it as a change request, not a surprise.

5) Next step (5 min)

The next step is a decision, not a vibe. If you end the call with "Sounds good, we'll follow up," you are training your pipeline to stall.

Core questions (from the template):

• Proposal approach (hourly/project/retainer)
• Decision timeline
• Who signs? Who pays?

You do not need to quote a final price live. You do need a clear path: who decides, by when, and what you will send.

If pricing comes up (and it often does), anchor on the model and the scope boundary. If you need help picking a model, start with set freelance rates and use the rate calculator to set a sustainable floor before you negotiate anything.

How to avoid free consulting (and still be helpful)

Many freelancers lose money in discovery because they confuse two different things:

• Discovery is understanding the problem and constraints well enough to scope the work.
• Consulting is designing the solution and delivering implementation-ready recommendations.

You can be generous in discovery without doing the job. The trick is to give frameworks and options, not finished answers.

A simple way to manage depth is to answer at three levels. Start shallow and only go deeper when the relationship has commitment:

1. Level 1: what I need to know. You ask for the missing context that would change the approach.
2. Level 2: the approach. You outline a few plausible paths and tradeoffs.
3. Level 3: the plan. You turn one path into steps and risks. This is usually paid.

Scripts you can use when a client pushes for a free plan:

If you struggle with this boundary, tighten your call goal: you are not trying to prove you are smart. You are trying to decide if there is a scoped project you should take on.

How to turn notes into a scoped SOW (and a clean proposal)

The fastest path from call to paid work is a written scope boundary. Your notes already contain it. You are just translating the call into a document that makes agreement boring.

Use the Statement of Work (SOW) template and map your discovery notes into it.

A practical mapping from agenda to SOW

• Context becomes SOW Summary: the outcome, what changes for the client, and the success definition.
• Current state becomes Scope details: what systems and inputs are involved, and what "done" means in the real world.
• Constraints becomes Timeline and Responsibilities: access needed, review windows, and who approves what.
• Scope and boundaries becomes In scope and Out of scope: deliverables plus explicit exclusions.
• Next step becomes Fees and decision logistics: pricing model, billing schedule, and who signs and pays.

The recap email that prevents confusion

Send a short recap after the call. Keep it crisp. The purpose is not to restate everything. The purpose is to get alignment on reality and the proposed boundary.

Once they confirm alignment, turn the recap into a SOW and send it.

After the SOW is signed, do not improvise onboarding. A clean onboarding process reduces churn and makes delivery smoother. If you want a practical guide, read onboarding, delivery, and retention.

Red flags and deal-breakers

Discovery is where you decide if the work is scoping-friendly and if the client is safe to work with. Watch for patterns that predict chaos, then shrink scope or walk away.

• Vague problem description paired with a demand for a fixed price.
• No definition of success, only a feature list.
• No decision-maker, or nobody can answer "who signs and who pays."
• Pressure to start before access, approvals, or stakeholders are ready.
• Pushing for detailed unpaid recommendations or a full plan.
• Dismissing constraints (security, review time, access) as "not a big deal."
• Negotiating your process before you propose scope.
• Refusing budget ranges while requesting guarantees on time and scope.
• Anchoring you to an internal salary rate instead of business pricing.
• Using urgency to override clarity: "Just start and we'll figure it out."

If you see several of these, add guardrails (smaller phase one, clearer exclusions) or switch to a timeboxed model. Pricing frameworks live in set freelance rates.

FAQ

Do I need a discovery call if the client already has a spec?

Usually yes. A spec is not the same as shared understanding. Discovery is where you learn what is non-negotiable, what is flexible, and what risks are hidden in approvals, access, and timelines.

Should I talk about budget on the first call?

You do not need a final number on the first call, but you do need enough commercial reality to avoid wasting time. A light-touch approach is to confirm whether they are thinking in the right order of magnitude before you write a proposal.

What if they will not share a budget range?

Treat it as a signal. You can still proceed, but you should tighten the next step: propose a small phase one with a clear boundary, or ask what would make the decision to move forward easy for them. If they refuse any commercial discussion, you may be walking into endless revision cycles.

How long should a discovery call be?

30-45 minutes is enough for most first calls. Longer calls often become solution workshops. If the situation is genuinely complex, propose a separate timeboxed discovery engagement with a defined output.

What do I send after the call?

Send a short recap, then a scoped SOW proposal. The SOW is where you make the boundary explicit. Use this: Statement of Work (SOW) template.

What if they ask for a fixed price but scope is unclear?

Fixed price requires fixed scope. If the scope is unclear, you can propose a smaller phase one with explicit exclusions, or use an hourly or retainer approach for the uncertain part. The goal is to price risk instead of pretending it is not there.

How do I decide between hourly, project, and retainer?

Pick the model that matches uncertainty. When uncertainty is high, keep it flexible and timeboxed. When scope is stable, a project price can be fair and predictable. If you want a deeper framework, read set freelance rates.

What if multiple stakeholders disagree on the problem?

Do not guess. Your next step is alignment, not a proposal. Ask who owns the decision, what success means for each stakeholder, and what tradeoff they are willing to accept. If they cannot align, you cannot scope.

Next steps

Scope protects you, but pricing and delivery systems keep you profitable.

• Use the rate calculator to set a floor rate you can sustain.
• Use set freelance rates to pick a model and handle pushback calmly.
• Turn your notes into an agreement with the Statement of Work (SOW) template.
• Then execute with a consistent onboarding and delivery process: onboarding, delivery, and retention.

How to customize

1. Replace questions with those specific to your service and risk profile.
2. Add a section for red flags and deal-breakers.

Related Codex pages