The homepage has one real customer result: Rain, "Running at the speed of a $1.95B stablecoin company", with "$750k" in "Vendor and salary spend saved". It has no link and no story behind it, and the sitemap has no customer or case study pages. Right beside it, the headline proof ("10×" more runs, "−93%" cost per run, $0.42 to $0.03 a run) carries the line "Figures are illustrative." A risk or compliance buyer who reads that line discounts the whole page. Rivals Taktile and Unit21 lead with named, measured case studies.
First action
Send Rain a one-page draft of the case study with the $750k breakdown and ask for approval.
How to measure it
Homepage-to-demo conversion
- Now
- –
- Target
- +25%
- By
- 60 days
Steps
Get approval
Rain's sign-off on the name, numbers and quotes.
CEO (co-founder) 1 week
Pull the data
Real runs per week, cost per run and steps per case from Rain's run records, with dates.
Forward Deployed AI Engineer 2 days
Write the story
Problem, workflows, rollout, controls and the $750k math, with a customer quote.
CEO (co-founder) 3 days
Publish /customers
An index page plus /customers/rain, added to the sitemap.
Founding engineer 1 day
Swap the chart
Real figures with a measurement period instead of "Figures are illustrative."
Founding engineer 1 day
Link it everywhere
The homepage Rain block, comparison pages and guides that cite Rain.
Founding engineer 2 days
Measure
Case study views, then demo bookings from those sessions.
Founding AI Ops monthly
Why it works
Ask Rain to approve a full case study: the workflows it runs on Runtime (payment support, fraud and transaction monitoring, compliance, cybersecurity, payment ops), the before and after, how the $750k was calculated, and its real cost per run and runs per week over time. Publish it at /customers/rain. Replace the illustrative chart with Rain's actual curve, or with an anonymised aggregate across live customers, and state the measurement period. Link the Rain block, the comparison pages and the guides that already mention Rain to the new page. Add a /customers index so later stories have somewhere to go.
Payments buyers are trained to distrust unverified numbers. One named, measured story backs up the claims every other page makes, and it matches what rivals show, at almost no cost, because the result already exists.
Ready to use
CopyRain case study outline
1. Rain in one line: the card issuer and stablecoin company and its scale 2. The queues before Runtime: support, monitoring, compliance, payment ops 3. Why in its own cloud: data, approvals, audit trail 4. Rollout: first SOP, first agent, weeks to production 5. Results: $750k saved (how it was calculated), runs per week, cost per run over time 6. Controls: approvals, masking, evidence reports 7. Quote from an ops or risk leader 8. What's next, then Book a demo
Risks and how to handle them
Rain limits what can be named
Publish the workflows and ratios, and keep exact volumes private if needed.
Real numbers look less dramatic than the illustration
Show the trend and the measurement period; credible beats dramatic for this buyer.
Evidence
- Your websiteHomepage (checked November 9, 2026): one customer result, Rain, "Running at the speed of a $1.95B stablecoin company" with "$750k" "Vendor and salary spend saved", and no link to a case study; a cost block ("10×" more runs, "−93%" cost per run, "$0.42 / run" to "$0.03 / run", "−29%" total weekly spend) labelled "Figures are illustrative."; four customer logos (Rain, Nixtla, Mono, LineLeap); "Book a demo" is the only call to action and no pricing is shown.Source
- Your websiteSitemap (214 URLs, checked November 9, 2026): 77 comparison pages, 110 guides (16 in Portuguese for Brazil and 33 in Spanish for Chile, Colombia, Mexico and LATAM), 17 open-source model pages, 11 solution pages, 4 blog posts and 2 monthly release Briefs; no customer, case study, pricing, about or careers pages.Source
- Your websiteHomepage Rain block: "Rain runs Runtime for" technical payment support, fraud and risk transaction monitoring, compliance, cybersecurity and payment operations, and "Also" engineering investigations, PR reviews, QA testing and reporting.Source
- Competitor researchRivals' own homepages: Taktile shows Allianz, Mercury and Monzo, "75% less time to onboard" for Faire and go-live in about 4 weeks for Zilch; Unit21 shows a dozen customer logos and case studies (Nexo: 57% of alert reviews automated) under "Most systems generate alerts. Unit21 resolves them."; Sardine cites a Forrester Wave Leader placement. None of the three publishes prices.Source