Requesting a managed IT quote should be more than filling out a form and waiting for a monthly number.
For an IT provider to develop an accurate recommendation, they need to understand the technology environment they would be actually responsible for managing. That means looking beyond the number of employees and identifying the devices, locations, servers, cloud applications, security requirements, existing IT agreements, and current technology challenges that affect the scope of support.
This is especially important for businesses evaluating managed IT services on Long Island. Two companies with the same number of employees can have dramatically different technology environments. One might operate from a single office with mostly cloud-based applications, while another may have multiple locations, on-premises servers, specialized software, remote employees, and compliance requirements.
The more complete the information you provide, the more useful the initial recommendation will be. Before contacting an MSP, use this guide to gather the business and technology information that can help the provider understand your environment, identify the right level of support, and prepare a more meaningful proposal.
Businesses evaluating managed IT services on Long Island can also review DRP Solutions’ Managed IT service page for an overview of the support available.
Why Accurate Information Matters When Requesting a Managed IT Quote
A managed IT provider is not simply pricing a certain number of computers. The provider is evaluating the scope, complexity, and support requirements of an entire technology environment.
That is why the information you provide can affect the final recommendation.
For example, a 50-employee company operating from one location with mostly cloud-based applications may require a very different level of support from a 50-employee company with 75 devices, multiple offices, on-premises servers, specialized software, and a remote workforce.
Neither environment is necessarily better or worse. They simply require different levels of management.
An accurate quote therefore starts with accurate information.
You do not need to be an IT expert or have every technical specification memorized. A good MSP should be able to help you identify what is missing. However, having basic business and technology information ready can make the initial conversation much more productive.
1. Have Your Employee Count Ready
The number of employees is one of the simplest pieces of information to provide, but it can be an important starting point for an MSP.
Prepare:
- Total number of employees
- Number of employees who use company technology
- Number of remote or hybrid employees
- Number of employees who require IT support
- Anticipated hiring or growth
The total headcount doesn’t always equal the number of supported users.
For example, a 75-person organization may have 60 employees who regularly use company-managed computers and applications. Another business with the same headcount may have every employee using multiple devices and accessing business systems remotely.
It’s also helpful to mention expected growth.
If your company plans to add 25 employees, open another location, or significantly expand remote operations, your MSP should know before preparing a proposal. That information can influence the technology strategy and help prevent you from choosing a solution that fits today’s business but creates limitations six months from now.
2. Create a Basic Device Inventory
The number and type of devices your business uses can have a direct impact on the scope of IT management.
Before requesting an IT support quote on Long Island, try to provide an approximate count of:
- Desktop computers
- Laptops
- Company-owned mobile devices
- Tablets
- Servers
- Network equipment
- Firewalls
- Wireless access points
- Other business-critical connected devices
You don’t necessarily need to provide serial numbers or detailed specifications during the initial conversation. A simple inventory might look like:
45 laptops, 10 desktops, 3 servers, 2 firewalls, 8 wireless access points, and approximately 15 company-managed mobile devices.
That gives an MSP significantly more context than simply saying, “We have about 55 employees.”
It’s also useful to identify whether employees use company-owned or personal devices. A business with a bring-your-own-device environment may have different security, access, and management considerations than a company that supplies every employee with standardized hardware.
3. List Every Business Location
Your MSP should know where your technology operates. Provide:
- Number of offices
- General locations of each office
- Approximate number of employees at each location
- Whether locations are connected
- Remote or satellite offices
- Warehouse, manufacturing, or field locations
- Any planned new locations
For a Long Island business, this could mean identifying offices in Nassau County, Suffolk County, New York City, or other locations where employees regularly work.
Location matters because every additional office can introduce another network, internet connection, firewall, wireless environment, equipment inventory, and support requirement.
A business with one office may have a relatively centralized environment. A business with five locations may require a more coordinated approach to networking, security, remote access, and support.
Providing this information early helps an MSP understand the full environment rather than building a proposal around only the primary office.
4. Identify Your Servers and On-Premises Infrastructure
Servers can significantly change the scope of an IT environment. If your business uses servers, gather whatever information you have about:
- Number of physical servers
- Number of virtual servers
- Server locations
- Primary functions
- Age of the equipment
- Operating systems
- Storage systems
- Backup systems
- Critical applications hosted on the servers
Don’t worry if you don’t know every technical specification. You can simply explain that you have two physical servers, one file server, and one application server, for example. Your MSP can help gather additional information during an assessment.
It’s also important to identify whether your business is transitioning away from on-premises infrastructure.
A company planning to move applications or file structure to the cloud may need a different IT roadmap from a company that expects to maintain its existing file server environment for several more years.
5. Make a List of Your Cloud Applications
Cloud applications have become a major part of modern business technology.
Before speaking with a prospective MSP, create a list of the major cloud platforms employees depend on. This could include:
- Email and productivity platforms
- Cloud file storage
- Customer relationship management systems (CRM)
- Accounting software
- Project management platforms
- Industry-specific applications
- Human resources and platforms
- Communication tools
- Cloud backup services
- Hosted applications
Also identify which applications are considered mission critical. For example, if your business cannot operate without its accounting platform, CRM, or cloud-based practice management system, your MSP should understand that these systems are more than optional software. They are essential business infrastructure.
Cloud applications can also introduce questions about user access, security, licensing, backups, integrations, and vendor management.
The more clearly you identify the applications your business depend on, the easier it becomes for an MSP to understand the technology environment it would be supporting.
6. Document Your Current IT Problems
Don’t only tell an MSP what technology you have. Tell them what isn’t working.
This is one of the most valuable pieces of information you can provide. Create a short list of recurring problems such as:
- Slow computers
- Network outages
- Wi-Fi problems
- Frequent application issues
- Email problems
- Cybersecurity concerns
- Failed backups
- Server problems
- Remote access issues
- Poor response times from your current provider
- Lack of after-hours support
- Difficulty managing vendors
- Outdated hardware
- Employee productivity issues
Be specific when possible.
Instead of saying: “Out network is bad.”
Try: “Employees in our second-floor office frequently lost connectivity between 10 a.m. and noon.”
These details help the provider understand whether the proposal needs to account only for ongoing support or also for problems that may require remediation during the transition. That distinction ca materially affect the recommended scope of service.
7. Gather Your Existing IT Contracts
If you’re currently working with an IT provider, don’t overlook your existing agreement. Have a copy available if possible, along with information about:
- Monthly fees
- Contract expiration date
- Services included
- Hardware agreements
- Software agreements
- Backup contracts
- Cybersecurity services
- Support agreements
- Cancellation requirements
- Equipment owned versus leased
This information can be especially important if you’re considering changing providers.
An MSP may be able to identify services that are currently covered by another vendor, determine which agreements need to remain in place, and develop a transition plan. Your current contract can also help prevent an unexpected overlap between your existing provider and a new managed IT partner.
8. Identify Your Compliance Requirements
Compliance requirements should be discussed early, not after a proposal has already been created.
Tell your prospective MSP if your business must meet specific regulatory, contractual, or industry requirements. Examples may include:
- HIPAA
- PCI DSS
- SOX
- Industry-specific privacy requirements
- Customer security requirements
- Cyber insurance requirements
- Internal security policies
You should also explain what types of sensitive information your business handles. For example, does your organization store healthcare information, financial information, customer records, employee data, intellectual property, or other confidential information?
Compliance requirements can influence security controls, access management, monitoring, backup practices, documentation, and other elements of an IT strategy.
9. Explain Your Backup and Disaster Recovery Environment
An MSP should know how your business currently protects its data. Prepare information about:
- What gets backed up
- Where backups are stored
- How frequently backups run
- Whether backups are monitored
- Whether backups are tested
- How long backups are retained
- Whether you have a disaster recovery plan
- How quickly critical systems need to be restored
You don’t need to provide a technical disaster recovery report for the initial conversation. Simply knowing whether your business has a formal backup and recovery strategy is valuable.
For example, saying “We back everything up to the cloud” may not tell the entire story. Your provider may need to determine what is actually protected, how frequently it is backed up, whether the backups are usable, and how quickly critical systems could be restored.
10. Share Your Cybersecurity Environment
Cybersecurity should also be part of the initial conversation.
Tell your prospective MSP what security tools and processes you currently have, including:
- Antivirus or endpoint protection
- Firewalls
- Email security
- Multi-factor authentication
- Security monitoring
- Password policies
- Employee security training
- Vulnerability assessments
- Cyber insurance requirements
- Incident response procedures
If you’ve experienced a security incident in the past, disclose that as well.
The goal is not to create a list of everything your business is doing wrong. It is to give the provider an accurate picture of the current security environment so any necessary protections, remediation work, or ongoing security responsibilities can be considered when the proposal is developed.
11. Explain How Employees Work
Your workflow structure can influence your IT requirements just as much as your office infrastructure. Tell your prospective provider:
- How many employees work remotely
- How many work in the office
- Whether employees travel
- Whether employees use personal devices
- How employees securely access company systems
- Whether you have multiple shifts
- Whether employees need after-hours support
A company with a traditional 9-to-5 office environment may have different support requirements than a business with employees working remotely at night, traveling between client sites, or operating across multiple locations.
12. Outline Your Technology Goals
Finally, explain where your business wants to go.
This is often overlooked when requesting an IT proposal, but it can be one of the most useful conversations to have. Tell the MSP if you’re planning to:
- Open a new location
- Hire additional emplyees
- Move to the cloud
- Replace aging servers
- Upgrade computers
- Improve cybersecurity
- Implement new business software
- Support a larger remote workforce
- Consolidate technology vendors
- Improve disaster recovery
- Prepare for a compliance requirement
Your IT provider shouldn’t only understand where your technology is today. It should understand where your business is headed. That allows the proposal to account for both immediate needs and future requirements.
Why This Information Affects Your Managed IT Quote
The information above affects pricing because it defines the scope and complexity of the work.
The number of users helps establish the potential support workload. The number of devices determines how many endpoints may require monitoring and management. Locations can add network and infrastructure requirements. Servers introduce additional maintenance and monitoring needs. Cloud applications may require administration, security, and vendor coordination.
Compliance requirements can introduce additional security and documentation considerations. Existing technology problems may require remediation before an environment can be effectively managed. Existing contracts can affect the transition process.
In other words, an MSP needs to understand what is being asked to manage.
That’s why a quote based on incomplete information may not provide an accurate picture of what your business actually needs.
A thorough assessment gives the provider a stronger foundation for recommending the right level of ongoing support. DRP Solutions uses this discovery process to understand the existing environment before recommending a managed IT services plan based on the organization’s actual technology and support requirements.
A Simple Managed IT Quote Preparation Checklist
Before contacting an MSP, gather as much of the following information as possible:
Business Information
- Number of employees
- Number of locations
- Remote and hybrid workforce size
- Expected growth
Technology Inventory
- Computers and laptops
- Servers
- Network equipment
- Firewalls
- Wireless equipment
- Mobile devices
Software
- Cloud applications
- Business-critical applications
- Hosted systems
- Industry-specific software
IT Environment
- Current IT provider
- Existing contracts
- Current support structure
- Backup and disaster recovery
- Cybersecurity tools
Business Requirements
- Compliance requirements
- Cyber insurance requirements
- Critical systems
- Current IT problms
- Planned technology projects
- Business growth plans
You don’t need to have every answer before an MSP. The checklist is simply designed to make the first conversation more productive.
Be Ready for a More Productive Conversation With an MSP
You do not need a complete technical inventory before speaking with an MSP. What matters is having enough information to explain how your business operates, what technology employees rely on, where the current problems are, and what you expect from a new provider.
The discovery process should fill in the technical details you do not know and help determine the appropriate scope of support.
If your business is evaluating managed IT services on Long Island, DRP Solutions can review your current technology environment, identify areas that need attention, and help determine the level of support that makes sense for your organization.
Ready to discuss your IT environment? Contact DRP Solutions to start the conversation.
FAQs
Most businesses should compare two or three qualified managed IT providers rather than choosing solely from one proposal or collecting a large number of bids.
Comparing two or three proposals usually gives businesses enough information to understand differences in scope, service levels, responsibilities, and cost without making the process unnecessarily complicated. The goal should not be to identify the lowest monthly price. Look at whether each provider is proposing comparable services, what responsibilities remain with your company, how support is delivered, and whether any important services are excluded or billed separately. If one quote is substantially lower than the others, determine whether the provider is solving the same problem before treating it as the better value.
Yes. A clear managed IT proposal should distinguish one-time projects or remediation costs from the recurring services included in the monthly agreement.
A new provider may discovery work that needs to be completed before the environment can be managed effectively, such as replacing unsupported equipment, correcting configuration problems, upgrading security controls, or documenting systems that were never properly documented. These costs are different from recurring services such as monitoring, help desk support, maintenance, and ongoing management. Separating them helps businesses understand the initial investment, the continuing monthly cost, and which expenses should disappear once the transition or remediation work is complete.
The right participants usually include the person responsible for technology along with business leaders who understand operations, finances, security requirements, and employee needs.
Managed IT affects more than the IT department, so reviewing a proposal solely from a technical perspective can leave important questions unanswered. Depending on the organization, the review may involve an owner or executive, operations leadership, finance, an internal IT employee, and anyone responsible for compliance or cybersecurity. Each person brings a different perspective. For smaller businesses, one or two people may fill several of these roles.
Ask each provider to explain the assumptions behind the recommendation before comparing prices. Different quotes may reflect different views of your risks, priorities, and required level of support.
Two providers can review the same business and recommend different approaches, particularly if they identify different risks or make assumptions about what they will be responsible for managing. Ask each provider why specific services, upgrades, or security measures were included and what could happen if they were excluded. It is also useful to confirm that both providers evaluated the same users, devices, locations, applications, support requirements, and business priorities. Once the scope is normalized, the proposals become much easier to compare fairly.
Yes. A managed IT proposal can often be revised when new information is discovered or when the business needs clarification about scope, priorities, or responsibilities.
The first proposal does not always have to be the final version. During the review process, your business bay uncover additional systems, clarify support requirements, change a planned technology project, or identify services already covered by another vendor. A prospective MSP may also discover information during its assessment that changes the recommended scope. Those are reasonable reasons to revisit the proposal. The important thing is that revisions remain clearly documented so everyone understands what is included, what has changed, and what the final monthly and one-time costs represent.
