Why Most Mobile CRM Fails (And How Resco Fixed It)

One million syncs a week sounds like a brag, until you realize it’s a promise. Field teams don’t care about features…they care that their mobile CRM works fast, offline, and under pressure.In this episode, we sit down with Ivan Stano, a personal friend and CEO of Resco, to break down what it really takes to build a mobility platform that can handle massive data volumes, device constraints, and the messy reality of field service.We also mix in a little personality, because what’s a great conversation without some rivalry? Ivan (loyal Boston Red Sox fan) and I (unapologetic New York Yankees fan) go back and forth a bit…including a friendly wager on this year’s head-to-head matchups. Let’s just say…one of us will be enjoying that win a little more than the other.Ivan shares his journey from Slovakia to Boston, from joining Resco as a student to becoming CEO, and the mindset that shaped the product: treat failure as feedback, stay lean, and keep learning.From there, we get into the real stuff:What “offline-first” actually means (and why most get it wrong)Synchronization at scale and what a million weekly syncs really looks likeWhy tools like Woodford are powerful… but not exactly plug-and-play (and yes, the whiskey story is real)Then we cut through the AI noise. No hype just reality:Prompt-based configuration to speed up adminsVoice and assistant-style experiences for techniciansThe hard blockers: custom data models, offline constraints, and cost per userWe also dig into inspections, questionnaires, Resco Forms across Microsoft Power Platform, and why your reporting strategy lives or dies by your data model.If you’re building anything for the field this is one of those episodes where theory meets reality.👉 Subscribe for more real-world CRM and field service conversations 👉 Share this with someone trying to make mobile actually work 👉 And drop your take: what should AI simplify first for your teams?Send us Fan Mail