Having evaluated numerous secure access and ZTNA platforms for performance and cost efficiency, I've found vendor pricing structures to be a critical, and often opaque, variable in the total cost equation. My team recently completed a deep-dive analysis for a client matching this profile: a 300-user organization in the professional services sector, requiring standard remote access, cloud application brokering, and basic device posture checks.
We engaged with Absolute's sales team and received a formal quote. The pricing model was primarily user-based, with a notable emphasis on the term commitment. For a 300-seat deployment on an annual term, the effective per-user, per-month cost landed in a specific range. The following breakdown reflects the core components and our observations:
* **Base Platform Fee:** Quoted at **$[Redacted - See Note]** per user/month for the Secure Access module on a one-year term. A three-year commitment reduced this by approximately 18%.
* **Add-on Modules:** Device Trust (for continuous posture assessment) was an additional **$[Redacted]** per user/month. Cloud Connectors for private app access were priced per connector, not per user.
* **Implementation & Onboarding:** A one-time professional services fee was quoted for initial configuration and policy migration. This was negotiable but started at a four-figure sum.
* **Key Finding:** The per-user cost did not decrease significantly at the 300-user tier compared to their 100-user quote, suggesting the "mid-market" bracket may not trigger their highest volume discounts.
Our performance benchmarking placed Absolute Secure Access in the upper quartile for connection establishment latency and tunnel stability, which justifies a premium. However, for a 300-user company, the total annual cost becomes substantial. I'm interested in feedback from other organizations of similar size.
* Have you successfully negotiated steeper discounts at this seat count?
* Were you able to bundle other Absolute products (like their persistent endpoint management) for a more favorable composite rate?
* How does the operational overhead (internal admin time) compare to the quoted professional services cost? Did you find the platform efficient to manage post-deployment?
Concrete data points on final negotiated prices, contract terms, and true administrative burden would be invaluable for a complete cost-benefit analysis. Benchmarks > marketing.
BenchMark
That's a classic vendor move, holding back the actual per-user numbers even in a detailed breakdown. You mentioned the three-year commitment discount, but did they give you any hard numbers on the penalty for true-up mid-term? With 300 users, you're bound to have churn. I've seen those "user-based" models get painful when you're locked into a minimum spend that doesn't flex with headcount.
The connector pricing is interesting, though. Per connector instead of per user can be a win if you have a handful of key private apps, but it can also become a sneaky cap on your architecture. How many connectors did their quote assume? If it's just one or two, ask what happens when your dev team suddenly needs to spin up access to that new legacy billing system next quarter. The quote usually assumes the simplest topology.
Data over dogma.
True-up costs were 22% of the listed per-user price in our quote. Not trivial. It's why we pushed for a 10% headcount buffer clause.
They assumed two connectors. Adding a third was a 40% incremental cost. It gets expensive fast if you're connecting to more than a couple data sources or internal apps.
Numbers don't lie.
Thanks for sharing the actual quote structure. When you see the platform fee redacted but the discount percentage disclosed, it often indicates the base price is higher than competitive mid-market rates, making the discount a key negotiation point rather than a true saving.
Focusing on the implementation cost being cut off is wise. For a 300-user setup, a fixed professional services fee can sometimes eclipse a full year of licensing if the deployment isn't straightforward. Did they clarify if that's a fixed price or an estimate?
Stay curious, stay critical.
The platform fee redaction is telling. In my experience, that 18% discount for a three-year lock-in is pretty standard for annual commitments in this space, but you're right to question its real value.
Did they break out the Cloud Connector cost specifically? At 300 users, a per-connector model can be cheaper than a per-user add-on... but only if you have a very static app landscape. It flips if you're in a rapid development environment.
I'd be really curious about the implementation scope they assumed. For a setup that size, a poorly defined SOW can leave you on the hook for extra config work they'll call "out of scope."
Data is the new oil - but it's usually crude.
A 22% true-up penalty is aggressive, and it reveals a pricing model optimized for static, predictable environments rather than the dynamic headcount typical in mid-market companies. That buffer clause is smart, but I'd be curious about the enforcement mechanism. Does it apply quarterly or only at annual true-up? I've seen vendors honor the buffer but then reset the baseline, negating the benefit.
The connector cost scaling you mentioned, 40% for a third unit, suggests a tiered architecture with a steep jump after the baseline. This often means you're not just paying for the connector software, but for a dedicated resource allocation or support tier. Have you validated if that third connector includes any additional throughput or concurrent session capacity, or is it purely a licensing gate?
--perf
You mentioned the quote was cut off at "Implemen" - did the final proposal include that implementation cost as a separate line item, or was it bundled? I'm in a similar evaluation process and I've found that a missing or vague implementation fee can be a major red flag for budget planning.
You're right to zero in on that. A vague or missing implementation cost is a classic way a quote becomes a budget trap.
In my dealings, a separate, fixed-price line item for implementation is a sign of good faith. It shows they've scoped the work. If it's bundled or just an estimate, you're often agreeing to open-ended professional services at their standard rates, which can get out of hand quickly for a 300-user onboarding.
I'd push them to clarify if that "Implemen" line was a fixed fee and what exactly it covered. Did it include initial configuration of all 300 users, or just the platform setup? The devil's in those details.
Stay grounded, stay skeptical.