# How Teachable uses Retool

**83%**: “83% faster development cycle: Launched enterprise analytics dashboard in 4 weeks versus traditional 6-month timeline”

As published on [retool.com](https://retool.com/customers/teachable-builds-reporting-and-analytics-dashboards). Captured by usedby on 2026-10-08.

- Company: [Teachable](https://www.usedby.ai/companies/teachable.md)
- Tool: [Retool](https://www.usedby.ai/tools/retool.md)
- Industry: [EdTech & E-learning](https://www.usedby.ai/companies/industry/edtech-e-learning.md)
- Teams: Engineering, Product

## What the story says

Teachable used Retool for External Apps to build and launch a customer-facing reporting and analytics dashboard for its enterprise customers. The dashboard shows course creators student engagement, learning outcomes, and revenue analytics.

Summary written by usedby from the source page, in English. The figures are those of Retool and Teachable, not ours.

> With Retool, Teachable accelerated its development process, moving from concept to production in four weeks, versus the six months to a year it would have taken with traditional development methods.

- **1,000 customers**: “Scale: Deployed to initial 100 enterprise users in first month, scaled to 1,000 customers by month two”

> Retool is the shortest path to get something into production with a quick feedback loop. We got a working prototype in front of customers in the first week, rapidly iterating based on their feedback.
>
> Richard Hunt, VP of Engineering at Teachable

## What usedby checked

We compared the story with its live page on 2026-10-08.

- Checked: the figure 83% is printed word for word on the page, near the name of Teachable.
- Checked: the passage quoted above is copied word for word from the page, near the name of Teachable.
- Checked: Teachable uses Retool. Confirmed line. Latest check across sources: 2026-10-08.
- Not checked: the result itself. We quote it; we did not measure it.

---
Source: https://www.usedby.ai/case-studies/teachable-retool · How we check: https://www.usedby.ai/methodology