How VolunVerse Overcame Early Growth Challenges and Built a Student-Centric Volunteer Platform

Volunteering has always been a big part of my school and community, but I realized how unnecessarily hard it was for students to find opportunities and keep track of their hours. The biggest issue was keeping track of hours. In my first year of high school, I completed about 90 hours of volunteer work, but it all went down the drain because my teacher took it as an assignment and I never got the record back. I hadn’t made a copy at the time, because I was told we would get it back, but we never did. So, my app not only helps students find opportunities but also prevents them from losing track of past hours. When building the app for this purpose, I found how hard it is for organizations to get volunteers, for students to find opportunities, and for schools to track their students' requirements. The combination of all of these issues made what VolunVerse is today.

The thing that has worked best so far has been finding organizations through direct relationships. Instead of waiting for organizations to find me or respond to my emails, I have found direct relationships with people who need volunteers for their organizations. That’s how I got some of the first real interest in the platform. What hasn’t worked as well is assuming that if an organization emails back, they will join the platform. I have had organizations initially show interest then disappear, while others never respond in the first place. I’ve learned that early on, growth is a lot more personal than just putting a product online and hoping people find it. I’ve also learned that people are much more willing to listen when there is already some kind of connection or introduction. It gives me a chance to explain the idea directly, answer questions, and show why VolunVerse could actually help their organization instead of just being another random email in their inbox.

We’re still early enough that I don’t have one complaint that consistently comes from a large number of users. Most of the feedback so far has been about smaller bugs or parts of the experience that aren’t clear or smooth enough. I have handled these problems by testing the actual user experience rather than only individual features. For example, I’ve gone through the full organization process - from creating an account and verifying an email to submitting an organization, getting approved, and using the dashboard. That has uncovered problems I wouldn’t have noticed by only looking at the code, and I’ve been fixing those before bringing more organizations onto the platform. I’ve also started paying more attention to whether a feature makes sense to someone seeing it for the first time, not just whether it technically works. That has changed how I test updates because I now try to go through the same steps a real student or organization would take and look for anything confusing, slow, or broken.

I think one thing about my market that most people get wrong is they tend to treat volunteer management as mostly an organization problem, when there is also a huge problem for volunteers wanting to discover more. A student might genuinely want to volunteer but have no idea what opportunities exist nearby, whether they qualify, or how to document their hours afterward. VolunVerse isn’t supposed to be there only once someone has already found somewhere to volunteer, but be there through the whole process. I built the process for users to go from discovering an opportunity, to volunteering, to documenting, then finally to verifying their service and tracking it, while giving organizations tools on the other side to reach and manage those volunteers. Schools are another part of that same problem because they often need to know whether students are actually meeting service requirements. I think the market works better when students, organizations, and schools are connected instead of each one having to manage a completely separate system.

The biggest goal is to get VolunVerse into the hands of real students and organizations. I want to grow beyond the initial local organizations, improve the organizer and school tools based on actual use, and keep improving the app and website. The core product is built, so the next stage is adoption, feedback, reliability, and turning it into something communities actually use regularly. I also want to learn which features people actually use the most, so future updates are based on real behavior and feedback instead of only what I think people will need.

3 App Store ratings with a 4.3-star average rating overall.

I was starting from scratch in the volunteer-management software industry, but wasn’t starting from scratch on the knowledge of volunteering, technology, and entrepreneurship. I’m a student myself, so I understood the student side of finding and tracking volunteer work firsthand, as well as my issue of losing my almost 100 hours of community service proof. I started the project when I found out about Figma at about the age of 10. I was playing around with animations, connecting buttons to screens, and creating screens. Then, when I joined a club and started programming, I realized that what I had created when I was 10 in Figma was actually doable. I had taken an entrepreneurship course with Stanford Pre-Collegiate, so with the combined knowledge of my class and my club, I could get it done. I researched everything about app making, testing, server hosting, security, user data, laws, front-end and back-end design to turn the idea into an actual product.

One of my biggest mistakes was focusing on the future of VolunVerse too much rather than right now. I created too many individual features too fast without testing, to the point where I almost lost all of my work. One update and the app would no longer load or work. It took me over a week of reverting to old code before the app came back, but that meant redoing several important features. The total estimated time lost from that setback was about two weeks. It taught me to test changes incrementally and keep stable backups before adding more features, instead of assuming every update will work the first time.