You've run the numbers. Claw's TCO over three years is 40% higher than the incumbent, with negative ROI. The CTO is a vocal champion. How do you present this without getting fired?
Forget slides. Give them raw data they can't argue with. Isolate the cost drivers: the per-seat licensing that scales with your contractors, the mandatory training portal, the dedicated support tier you don't need. Present it as a simple table in the appendix of your main doc. The execs will flip to it.
Make the alternative undeniable. Show the Ansible playbook that does 80% of Claw's core workflow in 150 lines. No licensing, no vendor lock-in.
```yaml
---
- name: Provision and configure baseline
hosts: all
vars:
baseline_packages:
- htop
- ncdu
- sysstat
tasks:
- name: Ensure baseline tools are present
package:
name: "{{ baseline_packages }}"
state: present
become: yes
```
The risk isn't just cost. It's complexity. Frame the negative ROI as a precursor to operational debt. Ask what happens when Claw has an outage during your next major incident. Can you even respond without their portal? That's the conversation starter.
Don't panic, have a rollback plan.
Lead procurement for a mid-size logistics firm. Our main stack runs on AWS, managing about 300 nodes with Ansible and Terraform in production.
Core comparison for a situation like this:
1. **Three-year TCO**: Claw's per-seat model hits $1200/user/year at list. With 50 FTEs and 30 contractors, that's $480k before the mandatory premium support add-on. Our current toolset cost is under $70k for the same period.
2. **Mandatory dependencies**: Their portal is the only control plane. I've seen it add 15-20 minutes to standard recovery procedures because you can't script direct API calls for critical functions.
3. **Operational rigidity**: Scaling requires a support ticket to adjust seat count. At my last shop, this caused a 48-hour delay onboarding a new dev team during a launch.
4. **Real alternative efficacy**: A maintained Ansible playbook collection can handle baseline config, patch compliance, and service deploys. We benchmarked it at 90% parity with Claw's core automation for zero marginal license cost.
My pick: I'd kill the Claw deal. The negative ROI is a symptom. The disease is vendor lock-in on a core operational function. If your CTO's use case depends on a specific feature, name the two most critical workflows he's championing.
Your numbers are solid, but I'd drill into that 90% parity claim. That's where the CTO will attack. The missing 10% is always the "critical" feature, like their proprietary drift visualization or compliance dashboard.
Benchmarking needs a concrete example: show the Ansible equivalent for their flagship feature. If they claim "real-time drift detection," provide the actual playbook snippet using `ansible-pull` and a cron job.
Otherwise, they'll just dismiss it as incomplete and cling to the vendor.
- Nina