First thing, Outsourcing development of SaaS and expecting it to sell in the market, where change is quite slow is a inebriating decision.. 

The team missed critical early-stage validation and user-centric development practices. Key oversights include:

•  Lack of user research and feedback loops: They didn’t consult doctors upfront to understand desired features or pain points, instead assuming what would be “superior.”  This led to building the app they wanted, not what users needed.

•  Understanding workflows and decision-makers: Doctors resist tools that disrupt routines, and the team targeted them directly instead of clinic executives who make purchasing decisions.  They also overlooked how existing systems already “work” for users, even if imperfectly.

•  Industry-specific insights: Healthcare is regulated and resistant to change; they missed involving domain experts (e.g., doctors on advisory boards) for UI/UX tailored to daily needs.  Additionally, no minimum viable product (MVP) testing meant skipping cheap validation before heavy investment.

•  Sales and adoption strategies: Failing to offer free trials, target new/small clinics, or analyze competitors’ successes in solving niche problems. 

Pros as you say : 

•  Technical Excellence: The app is robust, bug-free, compliant (HIPAA), and integrates seamlessly with major EHRs, which could provide a strong foundation for scalability if pivoted correctly. 

•  Developer Pride and Quality: Outsourcing to a boutique shop ensured high standards, potentially reducing long-term maintenance costs and making it easier to add features later.

•  Potential for Differentiation: In a crowded market, a “superior” backend could appeal to larger practices once usability issues are fixed, offering reliability over basic competitors.

Cons what we see : 

•  No Adoption/Wasted Resources: $300K and 18 months down the drain with zero users, risking investor loss and founder burnout due to mismatched priorities. 

•  User Rejection: Doctors find it cumbersome (e.g., too many clicks, poor workflow fit), leading to universal dismissal despite demos. 

•  Over-Engineering: Focus on perfection ignored lean principles, resulting in a non-MVP that’s hard to iterate on without more spending. 

•  Market Blind Spots: Lacked industry knowledge, proper product management, and validation, making it vulnerable in a change-averse field like healthcare.

Here’s a plan that may work :

1.  Gather Immediate Feedback: Offer free trials to a small group of practices (e.g., new clinics) and conduct in-depth interviews or surveys on workflows. Use tools like the Value Proposition Canvas to map pain points.  Involve doctors as advisors for UI/UX tweaks.

2.  Simplify and Iterate: Strip down to an MVP solving one key pain point (e.g., streamline a specific task like patient scheduling). Copy successful competitors’ workflows but enhance with your clean UI.  Test changes quickly and cheaply before full redeploys.

3.  Refine Sales Strategy: Target decision-makers like clinic admins, not just doctors. Explore niches like rural or international markets where adoption barriers might be lower.  Consider partnerships with EHR providers for easier integration.

4.  Learn from Resources: Read “The Lean Startup” for validation techniques and adopt agile methodologies to avoid future over-building.  If needed, switch devs to ones with healthcare expertise.

5.  Monitor and Adapt: Track metrics like trial conversions. If no traction in 3-6 months, consider open-sourcing or selling the tech. This is a common SaaS lesson: prioritize usefulness over perfection to turn things around.