Cleared client reviewProduction systems

Chaos in.
Apps out.

The workflows our customers brought us, and the tools they run now. Every story on this page is one version of that trade.

FeaturedCS.01 · Oct 2026
Banking · CS.01 · Oct 2026

78.3% faster to market at Saxo Bank. Here is what changed.

How Saxo Bank's creative operations team moved requests, approvals, and assets onto one platform and cut median time to market by 78.3%.

78.3% faster to market at Saxo Bank. Here is what changed.: Read the full story
More customer storiesCS.02 to CS.07
EducationCS.02From a manual fraud queue to a daily risk scoreAn edtech platform reviewed suspected fraud case by case. Now a scoring job ranks the cases every day.Read the story TechnologyCS.03Error monitoring in Retool, without a log leaving the regionA regulated client needed production error monitoring. Its data residency rules ruled out the usual tools.Read the story TransportationCS.04How an autonomous vehicle company moved safety review from a BI tool to RetoolThe BI tool behind an autonomous vehicle company's safety reviews, replaced by a production Retool dashboard.Read the story InsuranceCS.05Rebuilding an underwriting app that outgrew itself, one program at a timeThe Retool app had grown organically. The underwriters could not stop writing policies while we rebuilt it.Read the story E-commerceCS.06How a global enterprise automated customer support with AIA support team working through enterprise ticket volume by hand. What we automated with AI, and how.Read the story Healthcare · Pico ClinicsCS.07Pico Clinics: one platform for a global clinic networkPico Clinics ran its clinics in North America and Europe on different systems. Stackdrop built one platform on Retool to unify them.Read the story
Blog
Notes from the build

The stories show what changed. The notes show how

Retool components, SQL and the fixes behind them, written up from real client builds. For the next person who hits the same wall.

Read the blog
ContactLet's chat
Let's chat

Tell us what
you're building

Describe the process that is slowing your team down: the inbox, the spreadsheet, the portal nobody owns. We'll come back with a concrete approach, a rough timeline, and, where it helps, a working prototype within weeks.

What happens next
  1. We read every messageAn architect reads what you sent before anyone replies.
  2. You hear back in ≤ 2 daysA short reply with first questions and a suggested next step.
  3. We scope and prototypeA scoping call, then a working surface, not a slide deck.
Where are you in the process?