Start with the decision
Before discussing screens, define what a visitor or user needs to decide. A website might need to explain a complex service. An application might need to help someone complete a recurring task. Those are different problems and deserve different structures.
Make the brief useful
Write down the audience, the essential journey, the constraints and the evidence you already have. Separate facts from assumptions. A short brief that makes decisions easier is more useful than a long list of features.
Agree on the next step
Choose the smallest coherent release that can serve the real need. Set expectations for content, integrations and ownership early, so the design and development can move in the same direction.