When JP Rius launched Precision Telemed in 2024, he came prepared with something most telehealth founders do not have: two decades of pharmaceutical commercial experience spanning sales force launches, drug commercialization, and supply chain trade operations. What he was not prepared for was the software.
Precision Telemed was built around a straightforward premise. Physician-led telehealth programs offering compounded semaglutide, compounded tirzepatide, testosterone replacement therapy, sermorelin, and NAD+ therapy at transparent, all-inclusive prices. No insurance games, no inflated clinic overhead. The clinical model was clear. The technology infrastructure to support it was another matter entirely.
When Every Vendor Wants You to Bend to Their Limitations
The telehealth software market offered no shortage of options. EHR platforms, patient intake tools, pharmacy integrations, billing systems. Rius evaluated most of them.
The pattern was consistent. Vendors wanted Precision Telemed to build its practice around their existing capabilities, not the other way around. Customization was cosmetic. The underlying workflows and product roadmap belonged to the vendor. If a required feature was not already built, the answer was a variation of "it's on our roadmap" — which in practice meant never.
For a company aiming to move quickly and build AI-assisted workflows capable of managing a multi-product clinical operation, that was a dead end. Rius decided to build his own platform.
Three Developers and the WordPress Detour
Three separate development teams were hired in sequence. All three led the project in the wrong direction. The most consequential mistake came from a developer who insisted WordPress could serve as the technical foundation for a clinical telehealth operation.
The limitations emerged immediately. WordPress is a content management system stretched through plugins to approximate functions it was never designed to perform. Applied to clinical workflows covering intake, provider assignment, prescription routing, pharmacy integration, and compliance documentation, the technical debt accumulated faster than it could be addressed. By early 2025, Precision Telemed had spent months and significant capital building something functional enough to demonstrate viability but incapable of supporting the scale the business required.
Finding the Right Team and Reaching MVP
In February 2025, Rius finally found his development team. The right one.
Rather than arriving with a predetermined technical solution, they spent time understanding Precision Telemed's specific clinical and operational demands before recommending an approach. The first objective was pragmatic: get the WordPress stack to a minimum viable product stable enough to serve real patients and validate the business model. That milestone was reached. But the foundation remained a constraint on what the company could become. The decision was made to rebuild from scratch.
Building Precision Health Digital 2.0 on Symfony
The rebuild was built on Symfony, an enterprise-grade PHP framework used by organizations that require performance, architectural flexibility, and a codebase that scales without becoming unmanageable. Every lesson from the WordPress build was incorporated from the start.
The practical difference is significant. Adding a new treatment program on the old stack required weeks of development effort and extensive testing. On Precision Health Digital 2.0, new products can be added in a fraction of that time. The architecture is modular by design. Artificial intelligence is also embedded directly into clinical and operational workflows, handling the coordination complexity that multiple treatment programs — each with distinct titration protocols, lab requirements, and pharmacy routing — would otherwise require manually.
What Owning the Stack Actually Means
Most telehealth companies pay per-seat licensing fees to software vendors for every component of their stack. Those fees compress the margin available to hold program prices low.
Precision Telemed eliminated most of that overhead. Owning the platform means controlling the roadmap, building features on internal timelines, and treating the technology as an asset rather than a recurring expense. For patients, the outcome is direct. The testosterone replacement therapy program starts at $199 a month. The compounded tirzepatide program starts at $199 for the first month. Pricing at that level is only sustainable when the technology layer is not generating per-seat vendor fees on every patient served.
Where the Company Stands
Precision Telemed has now served more than 5,000 patients across its GLP-1, TRT, sermorelin, and NAD+ programs. The company is LegitScript-certified and operates across all 50 states.
Precision Health Digital 2.0 is the foundation beneath all of it. The plug-and-play architecture allows new programs to reach patients faster than was possible at any prior point in the company's development. The Symfony foundation means Precision Telemed can scale without the technical debt that nearly derailed it in its first year.
The lesson Rius draws from the experience is straightforward: when the software market cannot provide what a business actually needs, sometimes the right answer is to stop asking it to.
Copyright © 2026 California Business Journal. All Rights Reserved.
For California Business Journal Disclaimers, go to /terms-conditions/.
