Talk about your next project
GitHub case study

The lesson

Tie the customer’s product shift to the engineering system that made the shift possible, then prove it with named operators and workflow detail.

The move

The story opens with the Knock logo, the GitHub Team label, and the title “Knock pivots to new products, with the help of GitHub’s fast, flexible developer workflows.” A short company profile follows with industry, seats, company size, Knock’s real estate mission, its launch of Home Swap, and its shift from consumer marketing to local brokerage partners. The middle of the story moves from onboarding and remote collaboration into engineering autonomy, including a quote from Cody Stoltman and a quantified build cadence around “4,000 different builds every 90 days.” It then explains Knock’s automated pull request flow, CircleCI pipeline, GitHub Actions use, Slack notifications, and reusable workflows through quotes from Ryan Bruels, James Sumners, and Alex Yuskauskas.

Why it works

  • Our readThe opening grounds the engineering story in Knock’s business shift, so the workflow details have a reason to matter.
  • Our readThe page uses named engineering leaders across roles, which makes the collaboration and automation claims feel operational rather than generic.
  • Our readSpecific toolchain examples, including pull requests, CircleCI, GitHub Actions, Atlantis, Slack, and automated tests, show how the workflow actually runs.

What not to copy

Don't copy Knock’s Home Swap product, real estate market context, or its exact CI stack. Keep the structure of business change first, then engineering constraint, then named workflow detail from the people who run it.

More from GitHub

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.