Today I've finished the MVP for the side project I was developing for the last 3 months.
The motivation
Working in different companies - I've noticed some patterns on the way the meetings are held.
Sometimes the agenda is missing or does not have timeframes.
The meeting starts with someone doing the "google set timer" part which is repeated for each topic.
The meeting agenda and notes are usually stored in a google doc.
Once the notes are filled up and the agenda is moving up - it's easy to lose the focus and go off topic.
Also I've noticed that is hard to track the time at the same time you are trying to note something.
All the above-mentioned points drag the productivity below the optimal level.
To address those problems - I started a small fun project which turned in a full sized MVP which I decided to share with you.
The project
- WHY does Plainee exist:
Plainee helps you to organize and lead efficient and productive meetings in a simple and intuitive way.
- HOW does it work:
It offers you the possibility to bring all needed tools in one place and focus on the process itself.
- WHAT does it do:
It gives you a simple way to create meetings, invite participants and lead the meeting in real time.
Project status
Currently the project is in an MVP with a simple landing page, and under the hood is an app with the possibility to create meetings/templates, launch meetings and invite others to join (yet in readonly mode).
The meetings are saved in your account and they can be reviewed and downloaded as docx or pdf.
Here I want to ask you a few questions:
1. Does the problem, I'm trying to solve really existing?
2. Is my MVP on the right way of fixing this problem?
3. Would you or your employer buy a subscription in order to use this product?
4. What feedback can you give me on the current MVP?
Congrats on getting your project to the MVP stage. Right now the landing page seems to do a reasonable job (IMO) at pitching the 'WHY' as you've laid out in your comment here, but as it stands it doesn't showcase the how/what.
Per q1, Meetings at my organization currently tend to be pretty freeform, so I can't say if it's a problem that really needs solving, though I'd personally appreciate if things had somewhat more structure as described by your MVP.
Per q2/4, without signing up, it's not entirely clear. I'd recommend the getting started page either having more detail or having a learn more page which shows the workflow your application provides with basic screenshots prior to requiring a sign up. As per the application itself, the way you describe the 'WHAT' here seems like you may need to be cautious about the scope of the application. Typically organizations will have existing tooling for meetings to occur in (just a normal conference room reservation, slack, teams, gotomeeting, etc, etc, etc). The pitch of the idea seems to have your project being an organizational tool on the side, so creating meetings/inviting individuals is likely being done elsewhere and the tooling you provide would fall into managing the flow of the meeting.
Per q3, given that meetings are not currently managed in this style my current org would likely not use such a tool even at no cost.
Seems like the landing page should be improved in order to communicate clearly (and visually) the "HOW/WHAT" part without pushing the visitors to sign up.
3 comments
[ 2.8 ms ] story [ 20.5 ms ] threadToday I've finished the MVP for the side project I was developing for the last 3 months.
The motivation
Working in different companies - I've noticed some patterns on the way the meetings are held.
Sometimes the agenda is missing or does not have timeframes. The meeting starts with someone doing the "google set timer" part which is repeated for each topic. The meeting agenda and notes are usually stored in a google doc. Once the notes are filled up and the agenda is moving up - it's easy to lose the focus and go off topic. Also I've noticed that is hard to track the time at the same time you are trying to note something.
All the above-mentioned points drag the productivity below the optimal level. To address those problems - I started a small fun project which turned in a full sized MVP which I decided to share with you.
The project
- WHY does Plainee exist: Plainee helps you to organize and lead efficient and productive meetings in a simple and intuitive way.
- HOW does it work: It offers you the possibility to bring all needed tools in one place and focus on the process itself.
- WHAT does it do: It gives you a simple way to create meetings, invite participants and lead the meeting in real time.
Project status
Currently the project is in an MVP with a simple landing page, and under the hood is an app with the possibility to create meetings/templates, launch meetings and invite others to join (yet in readonly mode). The meetings are saved in your account and they can be reviewed and downloaded as docx or pdf.
Here I want to ask you a few questions:
1. Does the problem, I'm trying to solve really existing?
2. Is my MVP on the right way of fixing this problem?
3. Would you or your employer buy a subscription in order to use this product?
4. What feedback can you give me on the current MVP?
Thank you!
Per q1, Meetings at my organization currently tend to be pretty freeform, so I can't say if it's a problem that really needs solving, though I'd personally appreciate if things had somewhat more structure as described by your MVP.
Per q2/4, without signing up, it's not entirely clear. I'd recommend the getting started page either having more detail or having a learn more page which shows the workflow your application provides with basic screenshots prior to requiring a sign up. As per the application itself, the way you describe the 'WHAT' here seems like you may need to be cautious about the scope of the application. Typically organizations will have existing tooling for meetings to occur in (just a normal conference room reservation, slack, teams, gotomeeting, etc, etc, etc). The pitch of the idea seems to have your project being an organizational tool on the side, so creating meetings/inviting individuals is likely being done elsewhere and the tooling you provide would fall into managing the flow of the meeting.
Per q3, given that meetings are not currently managed in this style my current org would likely not use such a tool even at no cost.
Seems like the landing page should be improved in order to communicate clearly (and visually) the "HOW/WHAT" part without pushing the visitors to sign up.