Browser-agnostic meeting join wrapper for enterprise IT

The moment that crystallizes this problem for an IT lead isn't the first complaint — it's when someone misses a client call because the conferencing link opened in the wrong browser and threw an error. That's when someone asks: why can't the meeting just work, regardless of which browser the employee opened it in?

The structural reason this isn't fixed inside the conferencing product is that vendors build for their primary install base. Chrome dominates globally, so Firefox and Safari edge cases get deprioritized. A vendor fixing Safari bugs gets no competitive credit — users don't switch to a conferencing tool because it works in Safari. They switch for features, price, or corporate mandate. So the fix never gets prioritized, and the complaint threads grow.

What users describe is specific: the meeting 'opens in a separate box sometimes, stays in the current tab other times,' it's 'slow and clunky' in non-Chrome browsers, and Firefox users 'sometimes have to switch' mid-workflow. What's missing is something that intercepts the meeting link before the browser tries to handle it natively — detects the browser environment, and routes to the best available join method (native app, specific browser, or a compatibility shim) without the user having to know any of this.

This is a business rather than a feature because the conferencing vendor has no incentive to build it — it would require them to actively support competitor browsers and flag their own compatibility failures. IT teams at organizations with Mac-heavy workforces or browser diversity policies are the ones paying the cost in helpdesk hours and lost meeting time, and they need a fix that works across whichever conferencing tool their org uses.

What to build

Build a browser extension and companion IT admin dashboard that intercepts video conferencing join URLs (for a configurable list of vendors), detects the current browser and OS, and automatically relaunches the meeting in the native desktop app or a compatible browser — with IT able to set fallback rules per vendor and per OS from a central config.

Where to start

Target Mac-heavy companies (design agencies, media firms, marketing teams) where Safari and Firefox use is highest and the Adobe Connect or Chime complaint rate is most acute — sell via a one-page IT admin sign-up with a free 30-day trial covering up to 50 users.

The hard part

Browser extensions require separate builds for Chrome, Firefox, and Safari, and Safari's extension policy is significantly more restrictive — meaning the fix for Safari users requires the most work to distribute to exactly the population that needs it most.

How it makes money

Per-seat annual license charged to the IT department, around $3-5 per user per year — cheap enough to approve without a formal procurement process, but meaningful at 200+ seats.