Inspiration

Meenoe was born out of a need for getting back my time and ability to focus on actually doing work, not just continually having meetings to talk about it. For years I have had to sit through countless 2 hour long meetings while each department representative, or another meeting member speaks about things that have nothing to do with me, only for me to say "no updates on my end" one hour and 15 minutes into a meeting that probably could have been an email or text message.

What it does

Meenoe transforms how teams collaborate by replacing traditional meetings with intelligent, asynchronous workspaces called "Meenoes." Instead of scheduling rigid meetings that interrupt deep work, teams create living collaboration hubs where members contribute when they're most focused. Each Meenoe features dynamic agenda items, threaded discussions, file sharing, and 21 specialized micro-apps for everything from brainstorming to decision-making. The platform's agentic AI automatically generates workflows, tracks progress through intelligent action chains, and adapts to team patterns. This approach eliminates meeting burnout while actually improving coordination, allowing teams to make better decisions and giving remote members equal participation in collaboration.

How we built it

I started building Meenoe with just an idea on how I could solve this problem that I had, conceptualizing my pain points and looking at how it impacted my ability to work. Then I went into research mode looking deeply at how much of a real world problem this is - being astonished by the vast amounts of people who struggle with this very same problem. I documented the pain points or real people and used this to build the main concept for what I call the Meenoe core. On paper the core of Meenoe looked good so it was time to start testing some builds in Bolt! Being my first time building an app of this scale (a huge step up from building WordPress websites), I wasn't sure where to begin, but I dug in and hacked away at the keyboard trying to build a functional prototype of the Meenoe core, which consists is what captures the entire life cycle of a meeting in asynchronous systems.

Challenges we ran into

My very first attempt at building this failed miserably. For some reason the previews of the app just stopped working and I found myself burning tokens trying to just get the preview of the app working. I scrapped the project and started over, this time with a more modular approach which worked. Not having a team of developers was also a challenge, but I leveraged the power of AI to help me to conceptualize the ideas, understand new programming languages, learn the ins and outs of building an app prototype and getting it to work within the allotment of tokens. This process taught me a lot about orchestrating my ideas into plans and executing them sequentially. Throughout the development, I faced several other challenges like deploying to Netlify with a SPA built, the "create new" Meenoe page where the core of the prototype was built was just not showing up, and I was unable to get the front end SPA we built for the prototype working in Netlify - even though it worked perfectly within Bolt.new. Our attempts proved futile as the AI kept overwriting our styles, and key functionality of the app as the project grew in size.

Accomplishments that we're proud of

Despite the challenges, we're proud to say that we have accomplished our goal of building a functional prototype that we will continue to build into a fully functional SAAS application in the upcoming weeks. We implemented an agentic AI system that actually creates the Meenoe for you and does a lot of the heavy lifting allowing you to talk to the Meenoe AI with natural language and get work done much faster. The dynamic actions are functional and display a deeply integrated system that allows for users to track every bit of their work process without getting lost or missing out on key updates. we implemented the ground work for robust completion triggers within each action that is created, allowing users to determine due dates and deadlines, set recurring schedules, tag it as fluid where it never closes, set conditions for completion of an action, for example if we get a majority vote or an action meets a certain percentage of completion. We created the ground work for real time collaboration, adding, removing and managing users on a meenoe, inviting guests, and tracking their occupancy levels (currently displayed as a loading bar when selecting users to be added to the Meenoe). The core functionality is established, and the system is now ready for the next steps in the development process.

What we learned

Throughout this process we learned a lot about the differences between front end and back end design. I learned a lot about navigating the Bolt.new system and maximizing my token usage and how to duplicate a project to clear the context of the chat as the project grows. I learned a lot about how apps are actually developed and the importance of having a proper plan prior to just building. Most importantly I learned how to solve a real world problem and I am excited to fully build this out to help tons of other people like me regain their productive hours stolen from them by unproductive meetings.

What's next for Meenoe

With the foundation laid, I will continue to build out the complete Meenoe application. I have mapped out a development plan to get the app to a fully functional MVP within the upcoming weeks. From there I plan to go into closed beta and get real feedback from real users on the app, iterating on the app based on their feedback with particular emphasis on their pain points and criticisms. From there I plan to explore venture capital to rapidly scale the application, and expand the reach of the application. Meenoe isn't just another hackathon idea - Meenoe is the platform that will reimagine the way everyone works, and change the world's views on meetings and productivity.

Built With

Share this project:

Updates