Overview

Loading video…

Every time someone needed to do one-off group meeting scheduling, they left Meetwith.

Meetwith's group scheduling required users to create a group before they could coordinate a meeting. That works for recurring teams — but for spontaneous or one-off meetings, users had no workflow at all. So they left. Every time someone needed to schedule a quick call with an ad-hoc group of people, they switched to LettuceMeet, Doodle, or plain email.

Problem

No need for recurring group scheduling? No scheduling.

Meetwith's scheduling was tied to its groups feature. To schedule a meeting, you needed to first create a group — which meant every participant needed a Meetwith account.

This made the platform unusable for ad-hoc coordination. If you wanted to schedule a one-off meeting with people who weren't already in your Meetwith groups, the platform had nothing for you.

The Real cost

Every time a user opened LettuceMeet or Doodle instead of Meetwith, that was a lost touchpoint with the product. The gap wasn't just a missing feature — it was a retention leak.

Exploring the solution

A poll link anyone can use — with Meetwith's infrastructure underneath.

The model already existed in the market. Tools like LettuceMeet let you generate a link, share it, collect availability, and schedule — no accounts needed. Users were already comfortable with this pattern.

But Meetwith already had things those tools didn't: a contacts system, connected calendars, and group management. The opportunity was to build the same lightweight scheduling flow, but wire it into what Meetwith already had.

Zero friction for guests

Anyone with a link provides their name and availability. No signup.

Full power for the host

Pull in existing contacts (their calendar availability auto-populates), set guest permissions, control the poll lifecycle, and schedule the meeting.

Bridge to the platform

After scheduling, the host can optionally create a group from the poll participants — turning a one-off interaction into ongoing platform usage.

Solution v1

QuickPoll: generate a link, collect availability, schedule.

QuickPoll lives on its own dedicated section — separate from group scheduling — with clear details explaining the feature and showing ongoing and past poll sessions.

QuickPoll Home

A dedicated page showing what QuickPoll is and all your sessions.

The landing page explains the feature and shows the user's ongoing poll sessions alongside past, scheduled, closed, and deleted sessions. A clear "New Poll" button starts the creation flow.

Creating a poll

Provide meeting details, add participants, set permissions.

The host fills in meeting details, optionally adds participants from their contacts (whose connected calendar availability auto-populates), sets a poll expiry date, and configures guest permissions — whether guests can edit meeting details, schedule the meeting manually, or add other participants.

The date range defaults to 1 month from today — with a simple toggle for custom ranges — so most users don't need to touch it.

After creating a poll

The host sees the availability grid and can start sharing.

After hitting "Create Poll," the host lands on the group calendar view. Slots are empty unless they added contacts from their list — in which case, those contacts' connected calendar availability is already populated. The host can manually add or edit their own availability, and share the poll link with others.

Loading video…

The guest experience

Provide your name, tap your available slots, save.

Guests outside of the host's contacts land on a page showing meeting details, availability grid to add availability and a read-only list of other participants. They provide their availability by importing or adding manually, enter their name, hit Continue, and — they see a summary of others availability and theirs and they can choose to share the poll with others too.

Scheduling the meeting

Select a slot, fill in the remaining details, confirm.

The host sees the meeting details and populated availability grid. When they select a time slot, they provide the remaining meeting details and schedule. They can also extend the poll's availability deadline, or cancel and delete the poll.

Loading video…

We shipped V1 as a beta. The core objective held. The details needed work.

After releasing the beta and users testing it, the core objective was validated — users could collect availability and schedule without creating a group. But the team identified functional and UX improvements needed for the next cycle.

Poll creation order felt wrong

Users expected to set the meeting duration and date range first, then add the title and description. The V1 order didn't match how people think about scheduling.

Inviting participants was too limited

Both hosts and permitted guests needed more ways to add people: invite from contacts, share a link, or invite directly by email.

Email invites needed smarter handling

If an invited email already had a Meetwith account, they should sign in and join with their existing availability config. If they didn't, the flow should guide them to set up an account and connect their calendar.

These were all fixed in the design and it improved the experience for users.

Reflection

Ship the concept, then fix the experience.

V1 validated the core idea. V2 addressed everything the beta surfaced. Trying to get both right in one cycle would have delayed shipping without improving the outcome.

Form field order is a design decision, our users had a way they wanted to follow through on providing the poll details.

Reordering the creation flow to lead with duration and dates — the decisions people make first — was a small change with outsized impact on how natural the flow felt.

Every guest touchpoint is a platform touchpoint.

Email invites that guide new users to create accounts turned a feature for scheduling into a growth mechanism for the platform. That came from thinking about the business problem alongside the UX problem.