Before requesting a board quote, agree what the next build needs to prove. Bring clear answers where you have them, and mark the rest as open questions.
What must the product do?
Describe the user, operating environment, and outcome that would make the development worthwhile. A reference product can explain intent, but it does not replace a brief for your own product.
What must the board connect to?
List known connections, power needs, available space, mounting, and the equipment the board must work with. Flag uncertain requirements before assumptions become specifications.
What already exists?
That might be a block diagram, an existing board, mechanical drawings, firmware, or a working prototype. Identify who owns each input, which revision is current, and what may change.
What should the next build prove?
Is the priority interface compatibility, functional behaviour, mechanical fit, or a review before production? Agree the checks and evidence needed before commissioning the build.
What do we need for the first conversation?
A short, non-confidential overview of the product, current stage, and intended milestone is enough to begin. We can then agree the engineering work, who will make decisions, and what needs validation.