Preparing for a project discovery call: what to have ready

A discovery call is the first structured conversation about a project. Its purpose is not to agree a price on the spot. It is to understand the problem well enough to recommend a sensible next step.

You do not need a detailed specification. A little preparation, though, makes the conversation far more productive.

Start with the outcome, not the feature list

Before thinking about pages or functions, write down what should be different once the project is finished. For example: enquiries are handled in one place instead of three inboxes, or customers can book without phoning.

Outcomes help separate what is essential from what would merely be nice to have.

Know who will use it

List the groups of people who will interact with the system: customers, staff, managers, partners. For each group, note the two or three things they most need to do. This shapes everything from navigation to permissions.

Gather what already exists

Bring links or access details for anything currently in use:

• Your existing website or application
• Spreadsheets or tools the team relies on
• Brand guidelines and logo files
• Any previous proposals or specifications

Existing systems often contain useful data or reveal constraints that change the recommendation.

Be candid about constraints

Timelines, budget ranges and internal capacity are not awkward details to hide. They are design inputs. A realistic budget range lets a technology partner suggest an approach that fits, rather than one that has to be cut back later.

What you should leave with

A good discovery call ends with clarity rather than commitments. You should expect:

1. A shared understanding of the problem and the outcome you want
2. Initial thoughts on approach and any significant risks
3. Clear next steps, such as a written scope or a follow-up workshop

If you are planning a project, you can book a discovery call with our team.