Scope, budget & next steps
A national rollout, an event network and a single-site installation need different scopes. The starting point is understanding the locations, existing systems and work involved—not choosing a package before those details are clear.
Share what needs to work, where it needs to happen and your target schedule. Purely IT can help define the requirements and work through the scope for a project proposal.
What shapes the quote
These details help establish what is included and identify dependencies before installation is scheduled.
Location count, addresses, site variations and existing conditions shape a rollout. A shared standard helps, but each location may need different preparation or installation work.
List existing equipment, new devices and who supplies them. Reuse, configuration, cabling, network capacity and vendor dependencies need to be considered together.
Cable routes, mounting height, building access, power and equipment placement affect the installation scope. Plans and relevant site photos help explain conditions before a visit.
Installation windows, construction milestones, site contacts and technology-provider coordination all matter. Share opening dates or other fixed deadlines early.
Include load-in, setup, testing, event duration and removal. Identify the systems needing connectivity and any requested on-site support hours so those responsibilities can be scoped.
Agree on acceptance checks, documentation and equipment details, along with any support requirements. Your team should know what the project delivers and what needs a separate arrangement.
Prepare your project brief
You do not need every answer before contacting us. Send what you know, and identify the details that still need review. Leave passwords, access codes and payment information out of the message.
Work through the details
Explore the relevant scope and planning questions before your first conversation.
Bring us the details