Mid-Ohio Food Collective credits Claude with cutting feature delivery to 24–36 hours
State-by-state customization was a bottleneck for its food-bank software. The new workflow keeps staff responsible for interpreting rules and approving code.
Loading page…
State-by-state customization was a bottleneck for its food-bank software. The new workflow keeps staff responsible for interpreting rules and approving code.
Listen to this story
Mid-Ohio Food Collective says Claude-assisted work is making FreshTrak’s state-specific deployments faster, helping the nonprofit expand a platform used by about 2,500 food-access sites and serving 35,000 families daily. The reported gains come from an Anthropic customer case study, not an independent benchmark: engineers and local program staff still interpret state rules and approve changes, while automated tests and code review remain release requirements. The approach is also widening who can contribute code, as FreshTrak prepares a mobile app for families.
FreshTrak’s adaptations must account for varying state eligibility rules, reporting formats, and consent language.
Claude Code received the full codebase and a new state’s regulations, then generated a working, tested implementation for human review.
A technical support employee’s first Slack-submitted code change reached production the next day after phone guidance.
Software changes that once took months are reaching food banks in little more than a day, according to Mid-Ohio Food Collective. In a new Anthropic case study, the nonprofit says Claude-assisted development has cut FreshTrak feature delivery from two to three months to 24–36 hours, while halving partner onboarding and training time.
FreshTrak operates at about 2,500 pantries, soup kitchens, shelters and food banks nationwide, serving an average of 35,000 families daily. The figures and time savings are customer-reported results published by the tool’s supplier, not an independent benchmark.
Taking FreshTrak to another food bank was not simply a matter of installing the same software. Each state brought different eligibility rules, reporting formats and consent language. The team had adapted those requirements by hand, making expansion a recurring development job.
The turning point, the organization says, came when Claude Code received the full FreshTrak codebase alongside a new state’s regulations. It produced a working, tested implementation that fit the existing software. Engineers and local program staff still interpret requirements, check every implemented rule against state guidance and approve the work before release.
The Food Collective attributes the onboarding improvement to state-specific adaptation that once required months of manual work now taking days. Several additional food banks are being onboarded.
Engineers brief Claude Tag through Slack, where it works through the codebase and opens a pull request—a proposed code change—for review. They use Claude Code for deeper work, including restructuring older code and changes spanning multiple services.
Contributors now include staff outside engineering. Software engineering director Mark Mollenkopf describes a technical support employee who received phone guidance on her first task. Her proposed code change arrived through Slack and reached production the next day.
Previously centered on pantry-side check-in, FreshTrak is expanding into a mobile app described as launching this fall. Families will be able to find open pantries, create a profile once and reserve visits at participating locations. The team used Claude to build those user-facing steps and the software connections behind them.
Loading discussion...
Join the conversation
Explain where expert review should matter more than the author’s job title.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.