Skip to content
Notifications
Clear all

Step-by-step: How we got approval for OpenClaw's 3-year commitment.

1 Posts
1 Users
0 Reactions
0 Views
(@mattc)
Eminent Member
Joined: 1 week ago
Posts: 17
Topic starter   [#4294]

We've been using OpenClaw for a year. Their product is solid for our observability pipeline, but their pricing page is a maze of "contact us" and vague unit credits. The annual discount was okay, but our CFO saw the per-seat cost scaling with our dev team and started asking hard questions.

The 3-year commitment they offered cut our effective cost by 40%. Getting that approved internally wasn't about the discount alone. It was about de-risking the commitment. Here's the breakdown we presented:

**1. The Technical Lock-In Audit**
We mapped every integration point to prove we could extract our data within a quarter if we had to.
* Data ingestion: Their agent configuration was all in our Terraform. We documented the switch to OTLP.
* Dashboards & Alerts: We exported all JSON definitions and wrote a script to convert them to a Grafana-compatible format.
* Stored data: They provided a full data export API. We proved it worked on a test dataset.

```bash
# Example of their data export curl command we tested
curl -H "Authorization: Bearer $TOKEN"
"$ENDPOINT/api/v1/export?from=2024-01-01&to=2024-01-02"
--output backup.ndjson
```

**2. The Financial Runway Model**
We built two models: one with annual renewals (with projected 15% yearly price increases for new features) and one with the 3-year lock. We showed the 3-year model winning after month 18, even if we had to allocate engineering time to migrate off later.

**3. The Service Level Addendum**
The standard SLA had vague terms on data availability. We negotiated a concrete addendum:
* Data export API availability of 99.5% (critical for our off-ramp).
* A clear, escalating credit schedule for downtime, payable as service extension, not just a refund.

**4. The Kill Switch**
We got them to agree in writing to a pro-rated refund of the remaining commitment if any of three things happened:
* Their core data query performance degraded by more than 30% for us for two consecutive months.
* They removed a core feature we used (specified in an appendix) without a 12-month deprecation path.
* They were acquired by one of our direct competitors.

The takeaway: A long-term commitment is a technical decision as much as a financial one. You need the engineering work done upfront to prove you're not trapped. That evidence is what got Engineering, Security, and Finance to all sign off.


Show me the latency.


   
Quote