Pre-join readiness check for external meeting participants

The moment that triggers looking for this is specific: you're running a high-stakes external meeting — a job interview, a client demo, a vendor negotiation — and the person on the other side can't get in. 'Links did not connect correctly and we could not share screens in the web-based version.' 'Candidates try to join the interviews but sometimes it never allows them due to a few technical issues.' The host doesn't find out until the meeting start time, which is the worst possible moment to debug someone else's browser.

This gap persists because conferencing vendors optimize for the moment of the call, not the five minutes before it. Their diagnostic tools, if they exist at all, are buried inside the meeting room itself — which means by the time you discover a participant has an incompatible browser or a blocked firewall port, everyone is already waiting. The IT team at the host company doesn't control the participant's device. The participant doesn't know what to check. And the host is running their 11am calendar back-to-back.

What's actually needed is a pre-join URL — sent alongside the meeting link — that runs a silent diagnostic on the participant's device before the meeting day: camera and microphone permissions, browser compatibility, whether the specific conferencing domain is reachable from their network, and whether they'll be prompted for a plugin download. The check takes 30 seconds, surfaces exactly what's broken in plain language, and sends the host a summary. 'Participant on Firefox 89 — screen share will fail' is something you can act on the night before.

This is a business because high-stakes external meetings recur on a schedule — every recruiter runs multiple interviews a week, every AE runs multiple demos, every consultant runs client calls. Each failed join has a concrete cost: a rescheduled interview costs a recruiter 30-60 minutes and delays a hire. Selling to the coordinator who owns the calendar, not the conferencing vendor, means you own the relationship regardless of which video tool they use.

What to build

Build a lightweight web page that runs a 30-second browser diagnostic — camera/mic permissions, WebRTC reachability to the target conferencing domain, browser version compatibility, plugin requirements — and emails the meeting host a plain-language readiness report for each participant who runs it, integrated as an optional link appended to calendar invites via a Chrome extension or Outlook add-in.

Where to start

Recruiting teams at mid-size companies are the best entry point — they run high volumes of structured interviews, already track candidate experience metrics, and have felt the pain of a technical failure costing them a candidate they wanted to hire.

The hard part

Getting participants to voluntarily click a second link before the meeting is a behavioral adoption problem — the value only materializes if external guests actually run the check, and you can't force them to.

How it makes money

Per-seat monthly subscription charged to the host-side team (recruiter, AE, EA), priced per coordinator or per active meeting room, not per external participant.