Mobile-first interface for AI sales assistant workflows

A field sales rep or SDR working between meetings pulls out their phone to log a call or check a sequence status, and what they find is a desktop interface squeezed into a mobile browser — buttons misplaced, navigation menus that require precise tapping, and core actions buried three levels deep. The complaint 'it's a bit hard to use from mobile — some things that seem like they should be intuitive, aren't' is a polite way of saying the mobile experience was clearly never tested by anyone who actually does sales on a phone.

This gap persists because mobile is a secondary priority for B2B SaaS vendors almost universally. Their design teams optimize for the demo, which happens on a desktop, and for the power user who configures the system, not the rep who consumes it in short bursts between calls. The buyer — a VP of Sales or RevOps director — evaluates the product from a desktop in a conference room. The people suffering on mobile have no purchasing influence, so their friction never gets prioritized.

The specific failure isn't just visual responsiveness — it's that the information architecture of these tools is built for people who are configuring processes, not people who are executing them. A rep on mobile doesn't need to 'implement changes in my process'; they need to log an outcome, see their next three tasks, and fire off a follow-up. Those three actions currently require navigating a system designed for someone doing quarterly planning.

This is a business because it requires rebuilding the interaction model from the ground up for the execution context, not just resizing a desktop UI. That's a different product decision than a vendor can make with a responsive CSS update, and it means any AI sales tool vendor would have to re-architect how their mobile experience works — which conflicts with their desktop roadmap priorities. A standalone product that connects to these tools via API and presents only the rep-execution layer on mobile sidesteps that entirely.

What to build

Build a native iOS and Android app that connects to Aircall, Aloware, and Amplemarket via their APIs and presents only the rep-facing execution layer — today's tasks, call logging, sequence status, and quick follow-up actions — in a touch-first interface designed around one-handed use between calls.

Where to start

Launch exclusively for Aircall first, where the API is documented and the user base is large enough to find early customers through community forums and the Aircall marketplace listing — a marketplace listing gives you organic distribution from people already searching for Aircall add-ons.

The hard part

API access across multiple underlying sales tools means you're dependent on vendor API stability and completeness — if Aloware changes their API or limits third-party access, a core integration breaks, and you're renegotiating with a vendor who now sees you as a competitor to their own mobile app.

How it makes money

Per-seat monthly subscription paid by the sales manager or ops team, with a 14-day free trial — the rep uses it free, the manager pays to unlock team-wide deployment and activity reporting.