Number of Seats/Users: Automox offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows Automox that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from Automox. Automox reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: Automox offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from Automox. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: Automox often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that Automox is generally seen as a strong, modern patch management platform, but with some cost and reliability concerns that matter when you’re budgeting or negotiating contracts.

From what Spendbase clients tell us, the biggest strengths are:

• Ease of use & setup
• Simple, clean dashboard
• Fast deployment of the lightweight agent
• “Set-and-forget” patch policies once configured
• Automation & coverage
• Automated patching for OS and many 3rd‑party apps
• Cross‑platform support: Windows, macOS, Linux
• Ability to push scripts, software, and custom policies at scale
• Worklets & community content
• Built‑in worklet catalog with ready-made scripts
• Community scripts help solve common tasks quickly
• Operational impact
• Reduces manual patching workload
• Supports compliance and vulnerability reduction
• Helpful, responsive support team

At the same time, our internal feedback highlights consistent pain points you should factor into pricing and renewal conversations:

• Cost & licensing
• Per‑device pricing is often described as “on the higher end”
• Less attractive for small teams, startups, or companies in developing markets

• No free tier for very small environments
  → This is exactly where Spendbase can usually secure discounts by adjusting license volumes, contract length, and bundling.

• Agent and status reliability

• Devices sometimes:
  • Go offline or lose connection
  • Take a long time to sync or register
  • Get stuck in “pending update” or queued states

• Clearing these states can require reboots, agent reinstalls, or support tickets.

• Visibility and troubleshooting

• Limited insight into:
  • Real‑time install progress
  • What an endpoint is doing during an update
  • Detailed logs for failed updates

• Some patch failures are hard to diagnose.

• Features and technical depth

• Worklets are powerful but often require strong PowerShell / scripting skills.
• Some clients want:
  • Better remote desktop
  • Driver patching
  • Mobile device management
  • On‑prem/offline‑friendly options

In summary, Spendbase clients see Automox as a very capable, automation‑friendly patching tool with clear ROI on time saved. The main blockers are price and a few reliability/visibility gaps—both of which we keep in mind when negotiating discounts and right‑sizing contracts.