quality_assurance · saas · workflow
Sourcegraph Code Search and Batch Changes projected to save Nine 1200 hours and $276K in six months
Nine's developers could not search for code patterns and dependencies across their hundreds of repositories, making critical information time-consuming to find. Engineers also had to manually create hundreds of pull requests for uniform changes, and significant code duplication across microservices was difficult to manage.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Developer searches codebase
Developers need to find code patterns, snippets, or dependencies across hundreds of repositories and code hosts.
Tools used
SourcegraphCode SearchBatch Changescode monitoring
Outcome
Sourcegraph is projected to save Nine's Platform Engineering team up to 1200 hours annually and $276K in six months, while producing a remarkable boost in developer productivity, reducing the risk of human errors, and enabling rapid fixes for security vulnerabilities.
Results
Time savedup to 1200 hours annually
Cost replaced$276K
Grounding & classification
Source type: vendor customer story
25 fields verified against source quotes.
enterprise searchcode diff prknowledge basefailure mode describedmetric backednamed customersource backedtools describedworkflow describedmediacost reductionemployee productivityerror reductiontime savedvendor customer storyquality assuranceagentic task execution