Quick answer: Ask for the listing, confirm the exact product and compare the complete installed scope. Explain the design, installation, testing, handover and support you are quoting. CASE dealer pricing belongs behind an approved business account or direct quotation. If the budget needs to change, offer a clearly documented scope option; do not invent warranty or performance claims to defend the price.
On this page
Start with a fair comparison
“I found it cheaper online” is a request to understand the difference. The customer may be comparing a camera with a complete installation, or two genuinely similar offers. Ask to see the link and the customer’s required outcome before reaching a conclusion.
Use the installation proposal template to compare the complete SKU/lens/revision, accessories, condition, quantities and each seller’s actual terms alongside the installed scope. Do not assume another seller is unauthorized, a product is counterfeit or its warranty is invalid. Identify what is known, what is excluded and what still needs written evidence.
| Item to compare | Your proposal | Other offer / evidence |
|---|---|---|
| Exact equipment and quantities | [Schedule and revision] | [Exact listing or written offer] |
| Survey, mounting and cable route | [Included scope / assumptions] | [Included/excluded/unknown] |
| Network and recording setup | [Responsibility and tested requirement] | [Responsibility to confirm] |
| Commissioning and user handover | [Checks, authorized users and records] | [Demonstrated deliverables] |
| Warranty and service | [Written SKU terms; labour/transport separately] | [Written terms and service route] |
| Maintenance and changes | [Included visits and exclusions] | [Included/excluded/unknown] |
Unknown is a useful answer. Ask for written information rather than filling the comparison with assumptions. Compare total scope and responsibility, including items the customer would otherwise need another contractor to provide.
Explain channel protection accurately
CASE is supplied through a protected professional channel. Anabon’s policy keeps CASE sell pricing private through secure login, approved business accounts and direct quotations; this article does not publish equipment prices. That is a channel policy, not proof that no public listing can ever appear.
If a listing appears inconsistent with Anabon’s channel policy, send security camera technical support the URL, date and full SKU for routing and review. Do not promise removal or claim an enforcement outcome. Keep the customer conversation about the actual equipment, installed scope and support; a public listing alone does not establish the seller’s authorization or warranty status.
Anabon serves professional B2B partners with distribution and agreed project support. Define the customer-contact and service route for the actual job; a channel relationship does not guarantee exclusivity, margin or a competitive proposal. Keep purchasing terms private and make your independent selling decision from the real scope and costs.
State warranty and support in writing
Use the approved terms for the exact supplied SKU and project. Do not say “six years on everything” or copy a general category duration across every camera, recorder, accessory and drive. Catalog badges and general programme categories can differ. Obtain the written confirmation needed for the items you propose.
Use the warranty and RMA process guide to explain the partner service route, then confirm actual product, workmanship, diagnostic labour, site-visit, freight and maintenance terms separately. A long product warranty is not automatically free on-site service. State assessment and potential charges from the written agreement rather than promising approval or immediate replacement.
Documentation claims need the same care. Say which records you will supply for the equipment and requirement. Do not imply that a competitor lacks documentation or that every CASE product meets every NDAA, TAA, insurance or integration condition.
Use a calm five-step answer
- Acknowledge: “Please send the link. Let’s check whether it is the same equipment and scope.”
- Clarify: “Which parts of the installation, setup and support are included?”
- Explain: “Our proposal identifies who installs, tests and hands over the working system.”
- Offer options: “We can review a phased scope or a different documented design against your priorities.”
- Confirm: “I will put the included work, limitations and agreed next step in writing.”
Pause after the comparison. If the alternative is genuinely equivalent, decide commercially whether to revise the offer or decline. A rule that you must never adjust a quote is no substitute for understanding the job’s costs and risks.
Change scope without hiding the trade-off
A phased design may cover agreed priorities first while leaving a temporary limitation or requiring another visit. Use the installation pricing method to review extra mobilization, future provisions and actual cost assumptions. Explain the trade-off and obtain the required scope approval; do not quietly remove essential tests or safety work to meet a price.
If the customer supplies hardware, define compatibility checks, acceptance criteria, installation scope and support responsibilities before accepting it. Do not use a blanket “no warranty” statement that could misdescribe your own obligations. Have the actual terms reviewed for your jurisdiction.
Put the included work, exclusions, dependencies and approved changes in a clear comparison. Keep equipment identifiable even if commercial totals are grouped. Supplier costs, account credentials and private CASE price figures do not belong in public examples.
FAQ
Should I hide equipment identities to prevent comparison?
Use the private-pricing guide to distinguish protected purchasing terms from the customer’s equipment schedule. Identify the actual items and service scope accurately so the customer can compare and maintain the system; hiding model identity is not a substitute for explaining value.
Can I promise that the app or warranty is better?
Only make a supported comparison of actual versions and written terms. Confirm CASE Connect functions by model, software and configuration; do not promise unspecified app parity or universal remote access.
If a technical or documentation difference remains unresolved, confirm the complete model/revision, supported function and available written record before presenting it as a selling point. Keep customer incident records and credentials out of a generic comparison.
