# How Keller Williams uses Harness

**23**: “from 4-6 releases per year to over 23 within the first year of adoption”

As published on [harness.io](https://www.harness.io/case-studies/keller-williams), August 2026. Captured by usedby on 2026-10-07.

- Company: [Keller Williams](https://www.usedby.ai/companies/keller-williams.md)
- Tool: [Harness](https://www.usedby.ai/tools/harness.md)
- Industry: [Real Estate Assets](https://www.usedby.ai/companies/industry/real-estate-assets.md)
- Teams: Engineering

## What the story says

Keller Williams uses Harness CI and CD to automate its software build, testing and deployment pipelines, integrated with GitHub and JIRA. This replaced a manual, infrequent release process with frequent releases that can be approved via Slack.

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

> Deployment Frequency: We’ve scaled from 4-6 releases per year to over 23 within the first year of adoption—a sixfold increase.

> Since migrating to Harness, we've dramatically increased our deployment frequency. What was once a quarterly process has now become a weekly—and in some cases, daily—occurrence
>
> Brandon Taylor-Nelson, Principal Software Architect

## What usedby checked

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

- Checked: the figure 23 is printed word for word on the page, near the name of Keller Williams.
- Checked: the passage quoted above is copied word for word from the page, near the name of Keller Williams.
- Checked: the publication date is read from the page’s own metadata, never guessed.
- Checked: Keller Williams uses Harness. Confirmed line. Latest check across sources: 2026-10-07.
- Not checked: the result itself. We quote it; we did not measure it.

---
Source: https://www.usedby.ai/case-studies/keller-williams-harness · How we check: https://www.usedby.ai/methodology