product docs integrations use-cases changelog pricing Get API Key
// customers · results shipped this week

Teams that ship on evidence, not opinions.

From seed-stage to public companies, engineering and growth teams run their experimentation program through Crawltic's API, and let the numbers decide what ships.

Read the case studies Talk to Sales
wins.wall — decisions across the customer network
streamingdecided today: 1,284median time-to-decision: 3.1 dayssources: api · mcp · cli
NIMBUSCLOUDPIXELFORGEHOLOSTACKQUANTALOOPVELLUMORBITALLATTICEWORKSNORTHWIND LABS NIMBUSCLOUDPIXELFORGEHOLOSTACKQUANTALOOPVELLUMORBITALLATTICEWORKSNORTHWIND LABS
// featured · nimbuscloud
NCNIMBUSCLOUD

Pricing experiments moved from a dashboard into the deploy pipeline.

NimbusCloud's pricing team waited two weeks for every test to be configured by hand. They rebuilt the program on Crawltic's API: experiments are declared next to the code, launched by CI, and shipped automatically once revenue-per-visitor clears a 95% threshold.

  • Experiment definitions live in the repo and go through code review
  • Revenue metrics piped in from Stripe, joined in Snowflake
  • Auto-ship on 95% confidence plus a 20k-visitor quota
"Time-to-ship on a pricing test went from two weeks to same-day. The data team writes experiment logic straight from our pipeline now."VP Engineering, NimbusCloud
nimbuscloud / pricing-program — before vs after
Experiments shipped per quarter9→9
Time to decision14.0 days→14.0 d
Revenue per visitor$38.10→$38.10
annual-toggle (B)monthly default (A)RPV · live
RPV lift
+17.8%
Confidence
97.1%
Visitors
48210
Case studies

Three teams, three kinds of win

An agent-launched onboarding test, a guardrail that stopped a bad rollout, and a churn experiment measured on the metric that actually matters.

PFPIXELFORGE

An AI agent launched the test, and the test shipped itself.

PixelForge's growth agent talks to Crawltic over MCP. Mid-conversation it proposed an onboarding checklist, created the experiment, and set the ship rule. Four days later the variant cleared 98% confidence and rolled out with no human in the loop.

"Our own agent can spin up an experiment mid-conversation. No dashboard tool offers that."Head of Growth, PixelForge
mcp serveractivation rateauto-ship
onboarding-checklistRunning · agent-launched
Control
Empty workspace
Activation rate0.0%
Time to first project20.0m
Visitors0
+24.7% lift
Variant B
Guided checklist
Activation rate0.0%
Time to first project20.0m
Visitors0
P(B beats A)50.0%
HSHOLOSTACK

A guardrail caught a latency regression at 2% exposure.

HoloStack ramped a new edge cache behind a Crawltic rollout. Conversion looked flat-to-positive, but p95 latency nearly doubled. The latency guardrail tripped within the hour and paused the rollout before it reached more than 2% of traffic.

"Auto-paused before it hit more than 2% of traffic. We found out from the Slack alert, not from customers."Staff Engineer, HoloStack
guardrail metricsp95 latencyprogressive rollout
edge-cache-v2 · rolloutRamping · 2% exposure
Control
Origin cache
Conversion0.00%
p95 latency180ms
Requests0
Guardrail tripped
Variant B
Edge cache v2
Conversion0.00%
p95 latency180ms
Requests0
P(latency regression)50.0%
QLQUANTALOOP

Measured against churn, not a click-through proxy.

Quantaloop's billing team had been judging plan nudges on click-through. With a custom 30-day churn metric fed from their subscription data, the winner changed: the annual-plan nudge cut churn by a quarter while lifting revenue per user.

"Custom metrics changed which variants we would have shipped."Data Science Lead, Quantaloop
custom metrics30-day churnsequential testing
annual-plan-nudgeRunning · day 18 of 30
Control
Monthly default
30-day churn9.0%
ARPU$40.00
Subscribers0
-25% churn
Variant B
Annual nudge
30-day churn9.0%
ARPU$40.00
Subscribers0
P(B beats A)50.0%
// aggregate impact · trailing 12 months

What the whole network ships.

0K
experiments shipped
+0%
median lift on shipped variants
0 days
median time-to-decision
0%
decisions made automatically
lift-distribution.live — 18,412 shipped experiments
median +7.2%
-6%+1%+8%+15%+22%
Negative results caught
2140
Rolled back
11.6%
Revenue attributed
$412M
In their words

What teams say after the switch

NCNIMBUSCLOUD
"We replaced two dashboard-only tools with Crawltic's API. Pricing tests now ship the same day they're written."
VP Engineering NimbusCloud +17.8% RPV
PFPIXELFORGE
"The MCP server means our own AI agent can spin up an experiment mid-conversation and ship the winner on its own."
Head of Growth PixelForge +24.7% activation
HSHOLOSTACK
"Guardrail metrics caught a latency regression an hour into a rollout and paused it before it hit more than 2% of traffic."
Staff Engineer HoloStack 2% max exposure
QLQUANTALOOP
"Custom metrics let us test against churn directly instead of a click-through proxy. It changed which variants we ship."
Data Science Lead Quantaloop -25% churn
VLVELLUM
"Sequential testing means our PMs can check results whenever they like, without a statistician telling them they broke the test."
Product Lead Vellum 41 tests / qtr
ORORBITAL
"CLI-first fits how we already work. Experiment results are written into our release notes straight from CI."
Platform Engineer Orbital -32% time to first call

Your results belong on this wall.

Tell us about your experimentation program and we'll have your first test running this week.

Talk to SalesSee Use Cases