Eliminating Menu Fragmentation at the Operational Core.

Chris Istvan’s connection to computing didn't begin in a computer science lecture hall—it began in preschool seated in front of an Apple IIe. Even in those earliest years, technology wasn't merely a curiosity; it was an interactive environment meant to be unlocked. Rather than keeping it to himself, Chris spent his preschool hours eagerly teaching other students how to navigate the system and play games, discovering a natural instinct for breaking down digital interfaces and making technology intuitive for others.

That early spark ignited into real engineering when his family acquired his first personal machine: a Canon Computer powered by an Intel Pentium 100 processor. On that desktop tower, Chris pushed far past basic hobby computing. He began architecting full-fledged websites, engineering custom 2D games in Java, coding secure login authentication portals, and building functional e-commerce platforms from the ground up. Crafting these systems in an era before modern drag-and-drop frameworks taught him the foundational mechanics of software engineering: robust database relational schemas, secure session management, and the discipline of writing resilient, high-performance code.

At the same time, his appreciation for enterprise software was taking shape through real-world observation. Growing up across both Southern California and Utah, Chris spent formative years waiting for his mother's work shifts to conclude and commuting to and from school. In those everyday intervals, he closely observed how diverse businesses operated behind the counter. From medical and administrative offices to retail storefronts, service providers, and dispatch operations, he watched managers and staff run their organizations on a patchwork of platforms over the years. Seeing firsthand how mission-critical enterprises relied on early POS networks, mainframe terminals, and accounting databases gave him an early, intuitive masterclass in enterprise software design principles: the absolute paramountcy of data integrity, the fragility of siloed information, and the necessity of building software that withstands relentless operational pressure.

When Chris entered the hospitality industry in Park City, Utah, those lifelong technical instincts collided with the fast-paced realities of kitchen life. Over years of hands-on work spanning local mom-and-pop sandwich shops, fine dining bistros, and high-volume franchises—along with building enduring friendships with independent chefs and restaurant owners—he experienced the unfiltered operational pressures of the trade. Restaurant operators aren't software companies; they are culinary artisans and hospitality providers who live and die by ticket times, razor-thin margins, and guest trust.

As third-party delivery networks expanded, Chris experienced the grueling administrative nightmare they introduced. Both before and after the internet boom, keeping menus synchronized was an agonizing manual exercise. When the dinner rush hit, busy managers had to juggle an entire counter of proprietary tablets, repeatedly re-entering item prices, daily modifications, and sold-out ingredients across four or five isolated systems. A single missed adjustment or delayed 86'd item triggered angry customer reviews, stressed line cooks, and costly order cancellations.

During the COVID-19 pandemic, when delivery became an indispensable lifeline for survival, the systemic friction reached a breaking point. Predatory third-party apps extracted up to 30% in commissions, complex modifier trees were stripped down or dropped entirely, and desynchronized menus plagued kitchens with constant refund disputes. Watching friends in the industry fight for their livelihoods, Chris recognized that restaurants didn't need another aggregator app or an expensive manual service—they needed a clean, unified synchronization pipeline built like enterprise infrastructure.

“We didn't need another middleman extracting hefty fees from hardworking cooks. We needed an enterprise-grade synchronization pipeline that honors the kitchen's authentic POS as the single source of truth.”

Chris Istvan • Founder, CEO & CTO Pronounce (East-vahn)

Former Senior Software Engineer, Enterprise Integrations Specialist, and CTO.

Bringing together decades of experience as a Senior Software Engineer, Enterprise Integrations Specialist, and CTO with the systems principles he absorbed growing up between California and Utah, Chris engineered Dishfuls POS Sync. By integrating natively and bi-directionally with Toast POS, Square, and Clover, Dishfuls POS Sync establishes the kitchen's Point of Sale as the master source of truth. Real-time menu edits, automated channel markups, nested modifier trees, and sub-second 86ing broadcasts deploy across delivery platforms and consumer channels simultaneously—eliminating double-entry, protecting profit margins, and giving restaurant operators their time back.