Your people
Users, meeting format and duration.
Review the number of users, interior arrangement, services and delivery route.

Review relevant product information, project references and site conditions before confirming the configuration.
Published SOP references. A similar category does not prove an identical configuration.

Review this reference’s own use, scope and site conditions.
View published project ↗A clear requirement helps make the next conversation more useful.
Start with what the pod will be used for, the number of people and where it will go. You can discuss a category before committing to a model.
Tell SOP which product and options you are considering. Confirm the offered scope, layout and documentation before treating an option as included.
Ask for supporting information for the actual configuration. Different sound ratings and test methods should not be treated as interchangeable.
Your intended use, preferred product, quantity, destination and site information make a useful starting point. Include configuration requirements if you have them.
Share your requirements. We'll help you work through the next steps.
Confirm exact dimensions, access, services and the offered scope using the original product details. Requirements vary by product and application.