When2meet Alternative for Cross-Company Expansion Deal Committee Scheduling

Manual When2meet grid tutorial for a cross-company expansion committee

Walk the manual When2meet method first, because every operator asking whether to move off the grid needs to see exactly what the grid is doing on their behalf. The working example is a $450K expansion from an existing $600K ARR customer into a second business unit, with a target close inside the current quarter. The vendor is a Series B SaaS company with a founder still on late-stage deals. The customer is a mid-market enterprise on Microsoft 365. The vendor is on Google Workspace. Six required calendars, two tenants, one 60-minute expansion committee call to green-light the order form.

1. Name the expansion outcome in one sentence

   Write the decision the committee must produce. Pick one: green-light a new business unit expansion at $450K ACV, approve a new geography rollout with regional data-residency commitments, or bless a new product line addition to the existing MSA. Each outcome carries different required attendees, different procurement paths, and different existing-power-user politics. A committee call with three possible outcomes lets everyone bring the wrong prep and defends the wrong quorum rule. On a $450K expansion, wrong prep is a two-week slip.

2. Build the six-person committee matrix

   List roles, not names. Names change every quarter on both sides; the decision rights on an expansion committee do not. Mark a role required only if the committee cannot produce its stated outcome without that role. An expansion approval without the customer economic buyer is a scoping call. An expansion approval without the existing power user is a bake-off invitation. An expansion approval without vendor CS is a promise the delivery team has not signed off on.

   Role	Primary calendar	Vote weight	Representation rule
   Customer champion	Microsoft 365	Required	Owns internal socialization; cannot be replaced
   Customer economic buyer	Microsoft 365	Required, single approver	Only voice that authorizes new budget; no delegate
   Customer existing power user	Microsoft 365	Required	Reference authority on new BU fit; blocks or blesses
   Customer procurement	Microsoft 365	Informed	Reads MSA/order form changes; joins only if terms shift
   Vendor CS lead	Google Workspace	Required	Owns delivery commitment; peer covers only for PTO
   Vendor AE	Google Workspace	Required	Owns commercial terms; no delegate
   Vendor founder	Google Workspace + personal Google	Required for >$250K ACV	Signals strategic commitment; recurrence pauses if out

3. Choose the intersection of committee time zones

   Log every committee member's working hours in their local time zone. A customer economic buyer in Chicago on Central, a customer existing power user in Frankfurt on Central European, a customer champion in New York on Eastern, and a vendor bench in San Francisco on Pacific gives a genuine intersection of roughly two hours per day on Tuesday, Wednesday, and Thursday. Do not propose slots outside that intersection. A When2meet grid does not enforce time zones and will happily surface a green cell that is 6:00 AM for the economic buyer, which is precisely how the customer forms an early opinion that the vendor does not respect the buyer's calendar.

4. Generate the When2meet grid URL

   Open when2meet.com. Name the event Expansion Committee - [Customer] Q3. Set the date range to the next five business days. Set the earliest and latest possible times to the intersection window. Click Create Event. The site generates a public URL with no authentication, no per-invitee access control, no calendar sync, and a persistent ad rail down the right side of the grid. Copy the URL. Do not send it yet. Open the URL in an incognito window and confirm what a customer economic buyer will actually see on first click, including the ads.

5. Draft the invite email carefully

   A When2meet invite ships as a plain email from the vendor AE's Google Workspace address to six recipients. Write a three-sentence body: the expansion outcome the committee is being asked to green-light, the target duration (60 minutes), and the grid URL. Do not paste the URL as raw text; enterprise mail filters treat raw when2meet.com URLs as low-reputation. Wrap the URL in an anchor with the visible text Vote on committee availability. Even wrapped, expect one of the six invites to land in quarantine. Budget 24 hours for a resend to the missing voter.

6. Chase votes across two tenants

   Every 12 hours after the invite, the vendor AE checks the grid, notes which of the six committee members has not voted, and pings the customer champion to nudge the customer side. The champion pings the economic buyer. The economic buyer pings the existing power user. Reply-all archaeology begins. Budget 15 minutes of vote-chase per committee member per round. Six members times 15 minutes times two rounds is three person-hours of committee time per expansion deal, and the customer economic buyer's hour is the most expensive input on the entire deal. This is the herding-cats cost the grid does not price.

7. Resolve conflicts by manual overlay

   When votes close, the grid shows a colored overlay of who is available at which cell. It does not show why a cell is red. The customer economic buyer's Tuesday 10:00 red cell might be a board prep or a doctor appointment; the vendor AE has no way to know and no way to ask without another reply-all. Pick the darkest-green cell that hits at least five of six required voters. Escalate the missing voter to the customer champion by side channel. On roughly 30 percent of expansion committees, no cell hits all six required voters and the entire poll re-runs with a new date range. That is a full week lost.

8. Send the calendar invite manually

   The vendor AE opens Google Calendar, creates a 60-minute event at the winning cell, adds the six committee members by email, attaches a Google Meet or Microsoft Teams link based on the customer's stated preference (procurement teams increasingly reject Meet for security review reasons), pastes the expansion outcome in the description, and sends the invite. The customer side receives it in Outlook. Somewhere between the vendor's Google timezone and the customer's Outlook timezone, roughly one in ten invites lands with a one-hour daylight-saving offset. Verify by asking the champion to confirm the time in the champion's local zone.

9. Track acceptance and re-chase declines

   Watch the Google Calendar attendee response panel for the next 24 hours. A tentative from the customer economic buyer counts as a decline for expansion committee purposes; the buyer's calendar is the one that most commonly shifts. If any required attendee declines or goes tentative, the vendor AE reopens the grid, re-runs a truncated vote against a same-week alternate slot, and hopes the customer champion still has social capital to spend on a second round. Two vote rounds on the same expansion is a real trust hit with the economic buyer.

10. Run the failover slot

    Hold one 60-minute alternate slot earlier in the same week as pre-approved failover inventory. Give it an ID such as EC-WED-1400 and a status: reserved, activated, or released. The failover exists so that a broken primary slot does not push the expansion committee a full week and slip the deal into the next quarter. On a $450K expansion where the CFO wants recognition inside the current quarter, a one-week slip is a real forecast miss. Weekly expansion cadence is the whole point.

Why the When2meet grid breaks for cross-company expansion committees

The manual When2meet method is useful because it puts the operating rules on the page. On a $450K cross-company expansion with a six-person committee across two tenants, it also puts the vendor brand on a public ad-laden grid page and hands the customer economic buyer a first impression the vendor does not get to take back.

The brand-damage tax

An expansion committee is a moment of trust. The customer is choosing to give a vendor more budget, more attack surface, and more organizational dependency. The customer economic buyer is not clicking a When2meet grid for the first time and thinking about scheduling; the buyer is thinking about the vendor's judgment. A public URL with 2000s HTML, a persistent ad rail, and no visible security posture is a data point the buyer will factor into every subsequent conversation. A six-figure expansion is not the deal to save $12 a month by shipping a consumer grid into the customer's inbox. The brand-damage tax is not on the price sheet but it is on the deal.

No calendar sync means vote drift

When2meet captures one static snapshot of availability per invitee. Real calendars keep moving. In the 48-hour vote drift window between the first click and the last, a customer economic buyer will accept a board prep block, an existing power user will catch a customer escalation, a vendor CS lead will get pulled into an onboarding overrun, and the vendor founder will pick up an investor coaching call. None of those events refresh the grid. The winning slot from the grid is often already double-booked by the time the confirmation calendar invite lands. The vendor AE finds out on the day of the committee call, in the least recoverable way.

Cross-tenant IT admin blocks on When2meet emails

When2meet delivers grid invites over unauthenticated email from a domain most enterprise mail filters treat as low-reputation. Fortune 500 customer economic buyers receive the grid link in quarantine roughly one time in three. Corporate proxies also block the ad-laden grid page itself in about 20 percent of enterprise networks, which forces the customer to open the vote on a personal device. On a live expansion under active procurement review, opening a vendor-scheduling URL on a personal device is a compliance flag the customer procurement team will absolutely note. The vendor never sees the flag but the vendor absolutely pays for it in the next round of the negotiation.

Privacy exposure through public grid URLs

A When2meet grid URL is public and unauthenticated by design. Anyone with the link can see every committee member's name, availability pattern, and voting history. A customer procurement contact browsing the grid can infer which vendor accounts are stacked on the same day, which is competitive intelligence exposure on a live negotiation. If the customer champion forwards the link to a colleague, the vendor hands committee membership to anyone downstream of that forward, potentially including a competing vendor in a bake-off. There is no per-invitee access control and no revocation. On a $450K expansion, that is a calendar exposure anxiety operators cannot ignore.

When2meet vs Doodle vs WonderCal for a six-person expansion committee

These three options solve different parts of the cross-company expansion committee. When2meet is the free consumer grid. Doodle is the mid-market fallback with connected-calendar features on paid tiers. WonderCal keeps masked busy state aligned across every connected vendor-side Google and Outlook account, including the founder's personal Google, so the availability the customer sees is current when the committee vote closes. Most founder-led expansion motions end up on WonderCal for the vendor side once the first grid causes a slip on a live deal.