Gather

What started as a way to explore AI development over the summer quickly became something much bigger. All of us were growing into what you might call AI-native builders — learning to move fast, experiment boldly, and use new tools to solve real problems. What began as curiosity evolved into a genuine framework for how we think about building products and innovating within lean startups.

The real spark came when we sat down with Teri. She's a site coordinator running an entire campus food distribution program as a fraction of her job — managing partner organizations, tracking inventory, and trying to reach hundreds of students with almost no infrastructure to support her. Listening to her wasn't just research. It was a reminder of why this kind of work matters. Her pain points were clear: broken communication at every layer, no visibility into what was coming or who was coming, and a network that ran almost entirely on word of mouth and email chains.

We left that conversation with one goal — fix the pipeline, end to end.

What We Built

Gather is a multiplatform communication hub designed to streamline food distribution across the entire network — from partner organizations supplying the food, through site coordinators managing distribution, to students experiencing food insecurity.

At its core, Gather is an end-to-end dashboard platform that synchronizes distribution windows in real time. Coordinators and partner organizations can push inventory updates, log changes, track data, and manage locations — all in one place. When something changes, everyone downstream knows immediately. No email chains. No phone tag. No one person carrying the weight of an entire network.

On the student-facing side, we built and deployed a native iPhone app that puts all of this information directly in users' hands — without them ever having to formally ask. A live map, real-time inventory previews, opt-in notifications, one-tap directions. The goal was simple: make access to food resources feel as frictionless as checking the weather.

Challenges

Honestly? We ran into just about everything.

Bugs that only showed up at the worst times. Miscommunications within our own team about scope, priorities, and implementation details. The very human realities of sleep deprivation, time pressure, and trying to coordinate across a full-stack multiplatform build under a deadline.

There were moments where the irony wasn't lost on us — a team building a communication platform, struggling to communicate. But that friction made us sharper. Every breakdown pushed us to be more intentional about how we worked, which ultimately made the product better.

What We Learned

We learned that the best products come from genuinely listening — not just collecting requirements, but understanding the weight of someone's problem. Teri's words shaped our design principles more than any technical spec did.

We also learned what it means to build as a team under real constraints. Vibe coding and AI-assisted development gave us speed, but the hard parts — scoping, debugging, shipping something coherent — still required us to slow down, align, and communicate clearly with each other.

And we learned that lean doesn't mean small. Gather touches every layer of a complex distribution network. Keeping the product focused while honoring that complexity was one of the hardest design challenges we faced.

What's Next

We hope to deploy Gather beyond St. Thomas and help build this kind of communication network across food donation services everywhere. The infrastructure gap we found here isn't unique — it exists anywhere volunteers and coordinators are doing enormous work with inadequate tools.

Food security shouldn't be a networking problem. We built Gather to make sure it isn't.