This article is based on reporting originally published at diginomica.com, drawing on an interview with Matt Wyman, then VP of Products at CircleCI.
The Acceleration Problem in Modern Software Delivery
The pace of software development keeps accelerating — and the faster it goes, the more automation it requires. Modern DevOps teams routinely make hundreds or thousands of code changes every day. The shift toward microservices architectures multiplies the number of moving parts that must be coordinated, tested, and deployed reliably. Without a highly automated pipeline, engineering teams quickly hit a ceiling where manual processes become the bottleneck holding back both speed and stability.
This is the problem that CI/CD automation platforms like CircleCI are designed to solve. By automating the build, test, and release workflow, teams can move rapidly without sacrificing quality or increasing risk.
Understanding the CI/CD Pipeline
Before examining how CircleCI fits in, it helps to be precise about what CI/CD actually means, because the terms are often used loosely:
- Continuous Integration (CI): Developers frequently merge code changes back into a shared main branch. Each merge triggers an automated build and test run so that problems are caught immediately rather than accumulating over time.
- Continuous Delivery (CD): The release process is automated so that tested builds can be deployed to production on a regular, predictable cadence. A human decision or approval step may still gate the final release.
- Continuous Deployment (also abbreviated CD): A step further — code is pushed automatically to production as soon as it passes all automated tests, with no manual gate required.
Historically, the testing phase of CI was laborious. User acceptance testing, integration testing, and performance test labs each added time and friction. Automation tools were primarily focused on the deployment stage — making it possible to release at the push of a button — but that was sufficient when teams deployed every few weeks. As organizations move toward continuous deployment, every stage of the pipeline must run as fast as possible.
“We’re the conveyor belt of the factory.”
Matt Wyman, then VP of Products at CircleCI
Case Study: Procore Cuts a One-Hour Test Suite to Minutes
One of the clearest illustrations of what CI/CD automation delivers in practice is CircleCI customer Procore, a SaaS provider of project management and productivity software for the construction industry. With a team of more than 300 software engineers, Procore was being held back by a test suite that took over an hour to run. Long test cycles slowed issue resolution and left developers waiting in queues rather than shipping features.
By adopting CircleCI’s cloud offering, Procore was able to parallelize its test suite automatically — reducing what had been a linear, hour-plus process to a matter of minutes. Failed builds are flagged and reported back to developers almost instantly, minimizing context-switching and wasted wait time.
“CircleCI automatically splits up the test suite and what would be a linear hour plus, we can just do in a few minutes. If one [build] is going to fail, we get that back to the developer instantly.”
Matt Wyman, then VP of Products at CircleCI
For Procore, high availability is not a nice-to-have — it is a product requirement. The platform replaces paper-based processes on construction sites, giving workers immediate mobile access to critical project information. If the application goes down, it undermines the core value proposition.
“If you’re going to replace paper, you need to be available in the way paper always is.”
Matt Wyman, then VP of Products at CircleCI
Lyle Espinola, Senior Software Engineer Team Lead at Procore, explained how faster deployment cycles actually reduce risk rather than increasing it:
“The longer we take to ship things and the more process we put in place there, the more risky things become. We try to deploy as often as possible, while making it as safe as possible. Once we started moving to automatic deploys, we realized how much safer and faster it is.”
Lyle Espinola, Senior Software Engineer Team Lead, Procore
Procore now actively monitors pipeline metrics — queue times, build durations, test run lengths — to continuously optimize how quickly new code reaches production. According to Wyman, this kind of metric-driven culture is a reliable indicator of CI/CD maturity:
“If they start talking about measuring cycle time or cycle flow, we know for sure this is a customer that’s going to be very successful with us.”
Matt Wyman, then VP of Products at CircleCI
Not Everyone Deploys Automatically — And That’s Fine
Continuous deployment is the end goal for many engineering organizations, but it is not where every team starts — or needs to be. CircleCI includes a workflow approval feature that can pause single or multiple jobs until an API call or a designated human approver gives the green light. Some organizations still hold a formal go/no-go meeting before each production release.
“In the best cases, you automate away the decisioning and build test-deploy so that it can constantly be moving … The best organizations find ways to automate away those manual boundaries, but we have organizations that need them.”
Matt Wyman, then VP of Products at CircleCI
The implication for platform design is that a good CI/CD tool should accommodate teams at different points on the automation maturity curve — providing guardrails for those who need them while staying out of the way of teams that have fully automated their pipeline.
CircleCI’s Customer Base and Growth
According to Wyman, CircleCI’s customers arrive through three main channels:
- Self-service sign-ups: The largest group. Developers and teams who discover CircleCI while looking for a faster CI/CD pipeline and simply start using it.
- Open source projects: Major open source projects including Angular, React, and PyTorch use CircleCI, bringing community developers into contact with the platform.
- Enterprise transformation initiatives: Organizations undergoing structured digital transformation programs that want to reliably accelerate software delivery at scale.
At the time of the interview (late 2019), CircleCI reported more than 600,000 developers and 30,000 organizations using the platform. Customers ranged from individual hobbyists to global enterprises including Capital One, Condé Nast, and Samsung.
As a measure of growth: when Wyman joined CircleCI in mid-2017, the platform was running approximately 120,000 builds per day. By late 2019, that figure had grown to 1.2 million builds per day — a 10x increase in roughly two and a half years.
Three Core Principles Behind CircleCI’s Approach
Wyman outlined three principles that CircleCI aims to support for its customers:
- Deploy with confidence: Automation reduces the uncertainty around each release, making it safer to ship frequently.
- Maximize pipeline throughput: Reducing the time from idea to production build to iteration means more value can flow through the pipeline per unit of time.
- Deliver applications as a utility: Particularly relevant for SaaS vendors, applications must be continuously available and reliable — like electricity or running water.
Standardizing at Scale: The Condé Nast Example
For large, distributed engineering organizations, CI/CD automation provides an additional benefit beyond speed: standardization. Condé Nast, for example, operates around 200 different engineering teams globally, each publishing content on their own technology stack. CircleCI’s template configuration files allow individual teams to provision new resources quickly while still operating within organization-wide policy guidelines. When all teams are working within the same pipeline framework, it becomes possible to reason about delivery performance across the entire organization rather than team by team.
The Broader DevOps Automation Landscape
The growth of CI/CD tooling reflects a broader maturation of DevOps practice. Earlier waves of tooling focused on infrastructure-as-code — platforms like Chef and Puppet that made it possible to define and provision infrastructure programmatically. The current focus has shifted toward automating the entire build-test-deploy workflow, with CI/CD platforms sitting at the center of modern software delivery pipelines.
The proliferation of microservices and serverless functions only amplifies this need. Each additional service boundary adds a new artifact to build, a new test suite to run, and a new deployment target to manage. Without automation, that complexity rapidly outpaces the capacity of any engineering team to manage it manually.
For organizations still in the early stages of their CI/CD journey, the Procore example offers a practical starting point: identify the slowest stage in your current pipeline, measure it, then automate it. Cycle time metrics — how long it takes a code change to travel from commit to production — are the single most useful indicator of pipeline health and organizational readiness for continuous deployment.