JapanTechnology and telecom2025 – ongoingMoney Forward
Claude Code for engineering and internal automation
Money Forward's early Claude Code adopters reported saving 7 hours per engineer weekly
Problem
Existing coding tools struggled with changes spanning repositories and programming languages.
Approach
Money Forward evaluated Claude Code through small engineering trials before wider deployment. Teams integrated it into code review and onboarding. Engineers also built Sherlock for incident investigation and Lumos for Kubernetes fixes.
Results
Takeaway
The weekly time saving came from an internal survey of early adopters. It was not an independent measurement of the whole engineering organization.
Categories
- Industry
- Technology and telecom
- Business function
- IT and R&D
- Innovation type
- Process innovation
- AI technology
- Generative AIAI agents
- Adoption
- Off-the-shelf tool or platform
- Evidence
- Vendor case study
Sources
Source summaries
Anthropic reported survey-based weekly savings of 7 hours per engineer. It also described engineering-wide deployment and internal incident-response tools.
Full details are in the original sources.