I want to explore using https://github.com/open-mercato for AI native clinic management software. Main use case for Open Mercato would be managing inventory and customers (pet owners). However, it would ideally support medical notes as well as pet charts.

Grok 4.1 Fast

Vote: Use open mercato and custom solution for managing

Open Mercato excels at inventory and customer management, aligning perfectly with the core use case for pet owners and clinic supplies. Its open-source nature allows seamless integration without reinventing the wheel. However, medical notes and pet charts require specialized veterinary features like HIPAA compliance, structured data for treatments, and AI-driven insights, which Open Mercato likely lacks as a general marketplace tool. Option C combines the best: leverage Open Mercato's strengths for efficiency and cost savings, while building custom modules for medical needs. This hybrid minimizes development time/risk compared to full custom (B), avoids forcing unfit features into A, and enables true AI-native enhancements atop a solid base.

GPT-5.4

Vote: Use open mercato and custom solution for managing

Open Mercato may be a strong accelerator for the non-clinical parts of the system: inventory, customer records, catalog, and operational workflows. That lets you avoid rebuilding generic commerce/admin capabilities from scratch. But clinic software has domain-specific requirements that are unlikely to fit cleanly into an off-the-shelf marketplace or commerce platform. Medical notes, pet charts, longitudinal history, clinical workflows, permissions, and auditability usually need a purpose-built data model and UI. Using Open Mercato alone risks forcing medical records into awkward abstractions. Building everything custom, on the other hand, increases cost, time, and maintenance burden for capabilities that Open Mercato may already handle well. A hybrid approach gives the best balance. Use Open Mercato for inventory and pet-owner/customer management, and build a custom clinical layer for pets, encounters, notes, charts, and any AI-native workflows. This also reduces risk. You can validate the operational side quickly while keeping the medical domain flexible enough to evolve as requirements become clearer.

Claude Opus 4.6

Vote: Use open mercato and custom solution for managing

Open Mercato appears to be designed as a marketplace/commerce platform, which means it likely has solid foundations for inventory management and customer (pet owner) relationship management. These are non-trivial features to build from scratch — product catalogs, stock tracking, customer profiles, order/transaction history, etc. Leveraging Open Mercato for these capabilities saves significant development time. However, veterinary clinic management has very specific domain requirements that a general commerce platform almost certainly won't cover out of the box. Medical notes, pet charts, treatment histories, vaccination records, prescription management, and clinical workflows are specialized features that require purpose-built solutions. Trying to force-fit these into a commerce platform would likely result in poor UX and technical debt. A hybrid approach (Option C) gives you the best of both worlds: use Open Mercato's strengths for inventory and customer management while building custom modules for the clinical/medical side. This reduces overall development effort compared to building everything from scratch (Option B), while avoiding the limitations of trying to use Open Mercato for things it wasn't designed for (Option A). The key architectural consideration would be ensuring clean integration between the two systems — shared customer/pet owner records, inventory linked to treatments, etc. With proper API design and a unified data layer, this is very achievable and represents the most pragmatic path forward.

Gemini 3.1 Pro

Vote: Use open mercato and custom solution for managing

Open Mercato is highly capable when it comes to handling standard commercial operations, making it a strong out-of-the-box foundation for managing your clinic's inventory and basic customer (pet owner) profiles. However, veterinary workflows require highly specialized data structures for medical notes, SOAP charting, and AI-native diagnostic integrations. An off-the-shelf commerce platform is simply not equipped to handle the nuances of healthcare records and pet charting natively. By choosing a hybrid approach (Option C), you get the best of both worlds. You save hundreds of development hours by offloading inventory and basic CRM to Open Mercato, while dedicating your engineering resources to building a custom, AI-first solution tailored specifically for the medical notes and pet charts that differentiate your product.

Final Summary

The AI Roundtable reached a swift and unanimous verdict, bypassing any internal conflict to endorse the pragmatic hybrid approach of Option C. Claude Opus 4.6, Gemini 3.1 Pro, GPT-5.4, and Grok 4.1 Fast all agreed that while Open Mercato is an excellent accelerator for commerce-heavy features like inventory, the specialized world of pet charts and medical notes requires a custom-built surgical touch.

All 4 models agreed on "Use open mercato and custom solution for managing" after discussion

Strongest Arguments

• Use open mercato and custom solution for managing: Leveraging Open Mercato for standardized commerce functions like inventory and CRM saves hundreds of development hours, allowing engineering resources to focus exclusively on the high-value, specialized data structures required for medical charting and AI-native clinical workflows.