Verified Purchaser badge

Verified purchaser

Member since: Jan 2011Deals bought: 715
5 stars
5 stars
Posted: Oct 29, 2020

Great concept!

In a world of endless document sharing, meetquo's concept is fantastic: have a fixed start and end of a document's editing life. The built-in e-signature system with careful auditing is also awesome.

Capping video replies to a minute is awesome to reduce the noise. Nested comments is great.

Few thoughts based on my limited testing:

1. There's one premise in the core design that I do not necessarily agree with: all meeting participants exist in a team indefinitely. In an internal setting, I can see this typically being the case. In a setting with vendors and clients, this is often not the case, so the mechanics of creating a temporary meeting environment may require a temporary team with temporary members.

Compare this to a shared Google Doc or Word Online Doc, which can be easily created by you in a private folder that is only yours, but then shared via a single anonymous link for viewing and editing. The shared document is more flexible because you aren't required to invite people to a permanent team and the experience for them is more temporary. For them, it's this one document via this one link, and typically do not even know the name of the folder the document exists in.

In my world, even if a meeting exists in a series of meetings for me (or my team), I would prefer external third-parties simply have a more anonymous temporary link instead of a full account creation.

To clarify an example, if you were holding a sales meeting with Prospect A, you'd basically need to create a Team called "Prospect A", because a team of "Sales - Prospects" may be off-putting to a prospect. You could also just create a team called "External" for all meetings with outside participants, but you may quickly end up with an absurd number of members to that team. Additionally, you may want to delete this team after a deal seems unlikely, but then the prospect would potentially see they aren't a member of this team any longer. In an environment of isolated meetings (or typical modern shared documents), the prospect would see none of this. They would only see their one link to their one meeting, and everything else would be hidden.

2. There appears to be an interesting permission limitation for administrators. Let's say you create Team A, Meeting 1, and invite John and Mary. All of that works as expected. Now, John and Mary have accounts and are indefinitely members of Team A. They can create meetings with each other, within Team A, and unless they invite you, you may have no idea the meeting exists, much less the content of the meeting. It is possible I missed something here or this is a feature in development. It is also possible this is an expected behavior.

Thank you for bringing meetquo to AS! Best of luck with your promo! I think this SaaS has a bright future!

Will

Founder Team
Anna_Meetquo

Anna_Meetquo

May 9, 2024

Hello Will,

We were really happy to read your review. Thank you!

Regarding your comments, let me start by point #2: It's an expected behaviour that users only see the meetings they are involved with (as meeting owners or as attendees/guests). We chose this behaviour for 2 main reasons:

1) Privacy: some of our clients use Meetquo to work with their clients, and it's quite important for them that the clients can't see the other meetings (even just being able to see the meeting titles could become a privacy issue sometimes)

2) Simplicity: we want Meetquo to become a repository of decisions and meetings made, but in order to be really useful, we believe that those decisions should mean something to the user who is seeing them (e.g. if I'm part of the financial team, to see a meeting of the Design team does not add any value and can be distracting).

That being said, we're continuously learning from our users and the behaviour may change or evolve if we receive feedback about it being wrong.

Finally, regarding your first point, having pure guests (users who don't need to create an account and password to access a meeting and participate in it) is something that has been in the works for some time now. We do have 3 main concerns to be resolved at 100% before we launch this feature:

1) It must be easy to use for both guest and meeting admin: a magic link is probably the easiest way, we'll agree on that.

2) It must be legal: we're tracking some data to create the "Audit trail" when the user signs the outcomes, and the user will need to accept those terms, so even if there is no account creation we need the guest to accept the conditions, and that should be easy to manage too.

3) It must be secure: the moment we create a magic link, anyone with that link could see the content of the meeting. We know this already happens in other platforms (like Google Docs, when you create a link through which anyone can see the content and even edit it), but we want to be the best, not just "as safe as...".

So, once again, thank you for taking the time to do a large review and, of course, thanks for the 5 tacos!

Helpful?
Share
Ratings