Define the product and intended use
Name the product type and explain where and how it will be used. For example, a laundry detergent and a car shampoo belong to different product categories and have different application requirements. Identify the intended user and the setting in which the product will be used.
Describe the performance you need
List the product qualities that matter to your customers and, when possible, provide a benchmark or reference. This helps the development discussion focus on the required application rather than assumptions about what a product should do.
Bring the commercial and packaging details
A useful brief includes a target cost, an estimated starting quantity, preferred pack size or packaging format, and any branding or label direction you already have. These details help clarify the scope for formulation, filling, packaging, and manufacturing support.
Identify documentation and claim questions early
If you need safety or technical references, mention the specific product and document. Skylark describes MSDS as a safety and handling reference, TDS as technical and application information, and COA as a batch-level quality reference. Product documentation and availability depend on the qualified product line and production requirements.
If you plan to make ingredient, environmental, or other product claims, raise them during development so they can be assessed for the specific formulation and its supporting information.
Use the brief to start a conversation
You can begin with an idea and the details you already know. Skylark can review the inquiry and discuss relevant OEM, private-label, formulation, packaging, and manufacturing requirements for that project.