Skip to main content
usedby
Search tools, companies

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, August 2026. Captured by usedby on Oct 7, 2026.

What happened

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.

From the page. harness.io, captured Oct 7, 2026

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, Keller Williams. Source, captured Oct 7, 2026

What the story claims, and what we checked

We compared the story with its live page on Oct 7, 2026.

  • The figure: 23CheckedPrinted word for word on the page, near the name of Keller Williams.
  • The passage quoted aboveCheckedCopied word for word from the page, near the name of Keller Williams.
  • The publication dateCheckedRead from the page’s own metadata, never guessed.
  • Keller Williams uses HarnessCheckedConfirmed line. Latest check across sources: Oct 7, 2026.
  • The result itselfNot checkedWe quote it; we did not measure it.

Same company, same tool or same industry.

50%“a 50% decrease in overall production outages”Ancestry uses Harness. Another customer of Harness40%“Maintenance time cut by more than 40%, saving each QA engineer 2–3 hours per day previously spent on script fixes.”Gameopedia uses Harness. Another customer of Harness4x“4x improvement in delivery frequency and speed”Gentera uses Harness. Another customer of Harness