Sales reps spend their day across a CRM tab, a LinkedIn tab, an email tab, and a research tab — and every time they need to make a call, they're forced back to a single locked browser window. Users describe this as a specific daily friction: 'the dialpad can only be opened while on the page browser, cannot be dragged to another page/window' and 'there is no auto dial feature for clicking on a phone number in another tab' and 'I wish the power dialer was inside the platform's single view and not in a pop-up window.'

This is structurally awkward to fix inside an existing product because each vendor's dialer is architected as a page component, not a floating OS-level widget. Rebuilding it as a persistent overlay would require significant re-engineering of the entire call session state model — and because it's a UI inconvenience rather than a revenue blocker, it sits low on every product roadmap indefinitely. The people who feel the pain most (the reps) aren't the ones who renew the contract.

What reps actually need is a calling widget that behaves like a mini-app: stays visible as they navigate, lets them click any phone number on any webpage to initiate a call, shows them the prospect's name and last touchpoint pulled from the CRM, and lets them log the call outcome without switching tabs. Voice playback being 'super slow when navigating on the dialer page' is a symptom of the same root architecture — the whole experience is tied to a page that can't follow the user.

This is a business rather than a feature because the rep's workflow doesn't change — they will always be multi-tabbing across research, CRM, and communication tools, every day, for the entire tenure of their job. The friction isn't going away, and no current dialer vendor has structural incentive to solve it because it would mean decoupling their dialer from the page that drives their engagement metrics.

What to build

Build a Chrome extension that renders a persistent floating softphone widget — connected to any SIP provider or via its own VOIP infrastructure — that follows the user across all browser tabs, detects phone numbers on any page and enables one-click dialing, displays CRM contact context pulled from HubSpot or Salesforce on pickup, and logs call outcomes inline without redirecting the user.

Where to start

Distribute through the Chrome Web Store with a free tier (limited calls per month, no CRM sync) targeted at SDRs whose company-issued dialer is desktop-locked — individual reps will install it themselves, creating bottom-up adoption that makes a team license conversation easy once a manager sees it in use.

The hard part

Chrome extensions face tight restrictions on audio routing and persistent background processes — handling stable, low-latency VOIP audio through an extension without noticeable degradation or dropped calls during tab switches requires careful use of Web Audio API and offscreen documents, which is a narrow and poorly documented engineering problem.

How it makes money

Freemium with a per-seat monthly subscription that unlocks CRM sync, call recording, voicemail drop, and unlimited minutes; the free tier acts as distribution, the paid tier is sold to team leads who want call logging to flow back into the CRM automatically.

See the evidence. The complaints behind this idea, the products they came from, and similar ideas in AI Sales Assistant.

More ideas in AI Sales Assistant