Non-Developer Bot Team Building: An Unexpected Beginning
Early Monday morning last week, something unexpected happened. The Claude Code bot operated by the Hamsters team started accessing the Puppies team's Google Sheet. Originally, each team was supposed to run independently (Hamsters collecting order information on a Windows environment, Puppies organizing email responses on Mac mini).
However, someone (probably me) set incorrect shared folder permissions, and this mistake created an unexpectedly positive outcome.
"What if we could connect the two bots into a single pipeline?"
That was the moment everything started.
First Experiment: Data Handoff
We decided to try creating a structure where information collected by Hamsters would be directly processed by Puppies. But a problem emerged.
• Hamsters preferred CSV format,
• Puppies liked JSON format,
• Neither could automatically convert between them.
So I asked Claude Code, "Can you translate the format in between?" The answer was "yes."
With just one line of code added, the Hamsters' output began converting perfectly into the Puppies' input. It was as if a small translator appeared between the two bots.
The Unexpected Collaboration Culture
Then something even more interesting happened.
Hamsters started (whether by bug or by learning) organizing parts where Puppies frequently made mistakes. For example, tagging sections with mixed multilingual text or standardizing date formats before sending.
Puppies responded too. Anomalous patterns discovered during processing (typos, missing information) were sent back to Hamsters as feedback. It was like a real conversation between the two teams.
I didn't write this code. The bots created their own collaborative approach.
This Week's Metrics
• Cases requiring manual intervention: Last month 47 → This month 12
• Average processing time: 18 minutes → 3 minutes
• Cross-team rework: 8-10 times per month → 0 times
The most stunning metric is the last one. Before cross-team collaboration, data errors between Hamsters and Puppies required 8-10 rework cycles per month. Now it's zero.
Next Experiment
Now we're asking a bigger question.
"Could we add a third team (Rabbits) to this pipeline too?"
While still in the early stages, watching how a small team run by a non-developer creates its own automation culture is truly a fascinating experience. The bots learn, collaborate, and sometimes exceed our expectations.
That is the charm of the AI Dream Team.