Objection Handling
Common objections and how to address them effectively
Objection Handling
Objections are a natural and healthy part of any sales conversation. They signal that the prospect is engaged and thinking critically about the decision. This topic prepares you for the most common objections you will encounter when selling Project Green and gives you frameworks for addressing each one with confidence and credibility.
"We already have monitoring"
This is the most frequent objection and it comes in many forms: "We already use Datadog," "Our vendor has a management portal," "We built something in-house," or simply "We are covered." The key is to explore what "monitoring" actually means in their context before responding.
Start by asking questions rather than countering immediately. What exactly are they monitoring? Which devices and vendors are covered? What kind of alerts do they receive, and how actionable are those alerts? Can they see all of their sites from a single view? In most cases, digging into these questions reveals significant gaps that the prospect may not have considered.
Acknowledge the value of what they already have. Never dismiss their current solution -- they chose it for a reason, and telling them it is inadequate will put them on the defensive. Instead, position Project Green as a complement or an upgrade. "Your current tool does a great job with X. What Project Green adds is Y and Z, which are specifically designed for AV and collaboration environments."
Provide specific examples of what generic IT monitoring tools miss in AV environments: they may detect that a device is online but not that its audio quality has degraded, or that a display is powered on but showing the wrong input. AV monitoring requires domain-specific intelligence that general-purpose tools were not designed to provide.
Prepare a comparison framework that the sales rep can walk through with the prospect, showing their current coverage versus what Project Green provides. This should be a collaborative exercise, not a competitive takedown.
"It's too expensive"
Price objections are rarely about the absolute cost -- they are about perceived value relative to cost. When a prospect says "it's too expensive," what they usually mean is "I don't yet understand why this is worth the investment." The solution is not to discount, but to build value.
Start by understanding the context of the objection. Is the budget genuinely constrained, or has the prospect simply not built the internal business case yet? Are they comparing to a specific competitor's price, or to the cost of doing nothing? Each scenario requires a different response.
If the objection is about perceived value, revisit the ROI conversation. Walk through the cost of downtime calculation, the time savings analysis, and the truck roll reduction numbers from the ROI and Business Case topic. Most organizations spend far more on the consequences of poor AV management than they would spend on Project Green. Help the prospect see the total cost of their current approach.
If the objection is about budget constraints, explore creative solutions: phased rollouts that start with the most critical sites, different licensing tiers that match their current needs with room to grow, or timing the purchase to align with their budget cycle. The goal is to find a path forward that works for both parties without undermining the product's value through heavy discounting.
Address the discount question directly with sales reps. Discounting should be a last resort, not a first response. Every discount teaches the customer that the list price is not real and sets a precedent for future renewals. If a discount is necessary, tie it to something of value -- a longer commitment, a case study agreement, or a reference customer arrangement.
"We don't have the resources"
This objection typically means the prospect is worried about the effort required to deploy, learn, and manage a new tool. They may be short-staffed, already overwhelmed with projects, or burned by past tool implementations that required more effort than promised.
Address the deployment concern first. Describe Project Green's implementation process in terms of time and effort: how long does a typical deployment take, what is required from the customer's team, and what does Cyviz handle? If the deployment is lightweight and fast, say so with specifics. "Most customers are up and running within X days, and your team's involvement is limited to Y."
Tackle the ongoing management concern. Emphasize that Project Green is designed to reduce workload, not add to it. The whole point of the platform is to automate the manual tasks that are currently consuming their team's time. Position the short-term effort of deployment against the long-term savings in daily operational work.
If the prospect is genuinely short-staffed, explore whether Project Green could be deployed and initially managed by a Cyviz partner or the Cyviz team itself. Managed service options, if available, can overcome the resource objection entirely. If such options exist, describe them here.
Provide a suggested response framework: empathize with their resource constraints, acknowledge that tool fatigue is real, explain specifically what makes Project Green different in terms of deployment effort and ongoing overhead, and offer a pilot or proof of concept that lets them experience the value with minimal commitment.
"Security concerns"
Security objections are increasingly common, especially in enterprise and public sector sales. Prospects want to know what data Project Green collects, where it is stored, how it is protected, and whether it introduces any new attack surface into their environment.
Provide a clear, concise overview of Project Green's security architecture. Describe the data flow: what data is collected from devices, how it is transmitted (encryption in transit), where it is stored (encryption at rest), who has access, and what retention policies apply. Sales reps need to be able to answer these questions confidently without needing to escalate to a technical resource.
Address the most common security questions: Does the platform require inbound firewall rules? Does it need access to the corporate network? Is data stored in the customer's region? Is the platform SOC 2 compliant (or pursuing compliance)? Does it support SSO and role-based access control? Provide clear yes/no answers with brief explanations.
Prepare sales reps for the security questionnaire. Many enterprise prospects will send a vendor security questionnaire as part of their evaluation process. Describe the process for handling these questionnaires: who fills them out, what the typical turnaround time is, and whether a pre-filled version is available. The faster and more completely a security questionnaire is returned, the more confidence the prospect has.
If there are areas where the security story is still maturing (for example, a compliance certification that is in progress but not yet complete), be transparent about that. Prospects respect honesty about what is in place today and what is on the roadmap far more than vague assurances.
"We want to build our own"
Some organizations, particularly those with strong internal engineering teams, will consider building a custom monitoring solution rather than buying one. This is a legitimate option and should be treated with respect, but it comes with significant hidden costs that the prospect may not have fully considered.
Start by acknowledging the appeal of building in-house. A custom solution can be tailored exactly to the organization's needs, integrated tightly with existing systems, and maintained by people who understand the environment intimately. These are real advantages, and dismissing them will alienate technical stakeholders.
Then, methodically walk through the true cost of building. The initial development is just the beginning: the prospect also needs to account for ongoing maintenance, updates as device manufacturers change their APIs or protocols, scaling as the environment grows, documentation and knowledge transfer as team members change, and the opportunity cost of diverting engineering resources from their core business.
Provide a build-versus-buy analysis framework. Help the prospect compare the total cost of ownership over three to five years for both options. Include not just development costs but also the cost of delay (a custom solution will take months or years to reach feature parity with Project Green), the risk of key-person dependency (what happens when the engineer who built it leaves?), and the ongoing investment required to keep pace with a commercially developed product.
Position Project Green as a foundation they can build on rather than a replacement for their technical ambition. If the platform offers APIs, extensibility, or customization options, highlight those. The message is: "You get 80 percent of what you need out of the box on day one, and you can build the custom 20 percent on top of it, rather than building 100 percent from scratch."
Include a suggested closing question for this objection: "If you could have a production-ready monitoring platform running across all your sites within weeks instead of months, and your engineering team could focus on the custom integrations that are unique to your environment, would that be valuable?"