Parallel UI mode for SaaS version rollouts

When an AI sales assistant ships a new workspace and reps immediately say 'it would be better to return the old interface,' the vendor faces a painful choice: roll back and lose the new architecture, or hold the line and absorb the churn. Most hold the line. The reps are stuck.

This gap exists because SaaS vendors have no commercial incentive to maintain two UI versions simultaneously — it doubles their QA surface area and slows future development. But the buyer (sales leadership) and the user (the rep) want different things: leadership wants the new features, reps want the familiar navigation. Nobody is building the bridge between those two positions.

What's missing isn't a new UI — it's a configurable skin layer that maps the new underlying data and API to a navigation structure the rep already knows. Think of it as a saved interface configuration that a sales ops admin sets once: which columns are visible by default, in what order, with what density, and which workflows are one click vs. buried in menus. The complaints here are not about missing features — they're about 'the interface takes up too much screen space,' 'some column views could be more efficient,' 'the view seems old and a little outdated' (meaning: the new one is unfamiliar, not that the old one was good). That's a configuration and defaults problem, not a rebuild.

This is a business because the need recurs every major version cycle, and sales ops teams at companies with 100+ reps are already spending hours on change management training every time a tool updates. If they could lock down a UI configuration profile and push it to all reps, they'd pay for that directly — it replaces 3-4 hours of re-training per rep per major release.

What to build

Build a browser extension that lets sales ops admins define and enforce a saved layout profile — column order, panel sizing, default views, nav shortcuts — on top of any web-based sales tool, and push that profile to all reps via a shared team config link that persists across tool version updates.

Where to start

Launch with support for one specific tool (e.g., Aircall or Aloware) where the v1-to-v2 UI complaint volume is highest and loudest on public review sites, so you can acquire early customers through existing frustration communities.

The hard part

Browser extension-based UI overlays break every time the underlying tool updates its DOM structure, which means ongoing maintenance per supported tool is high and churn risk spikes exactly when the customer needs it most — right after a vendor update.

How it makes money

Per-seat monthly subscription billed to the sales ops team account; flat admin fee for configuration management plus a per-rep fee above a 10-rep free tier.