Qentoros

The challenge

Qentoros is a Blacksburg biotech developing platelet-derived biologics for horses, and it needed one product to serve three audiences that could not be more different: the public discovering the brand, veterinary clinics ordering the flagship treatment, and clinical investigators running FDA-regulated drug trials. Most companies would build three separate systems. Qentoros needed them to feel like one product, while keeping each surface sealed off from the others.

Three products in one app

We built the entire React application: a single installable web app with three independently gated surfaces. The public marketing site establishes the brand and captures leads, with an animated landing page, a full BIO-PLY™ orthobiologic deep-dive and clinical-stage tracker, a pipeline overview of biologics still in development, a team directory, and a contact page with an embedded map. Every form segments its lead into a PostgreSQL database and fires a transactional email.

The storefront is invite-and-approval: licensed clinics enroll with their billing details, professional license, and liability agreement; staff review and grant access; approved clinics order the product and see their own order history, with enrollment, approval, decline, and confirmation emails all sent server-side. Behind both sits the clinical trials system, the technical centerpiece: a regulated electronic data capture tool for the veterinarians running equine drug studies.

Software that holds up to the FDA

The trials system is built to 21 CFR Part 11 and FDA CVM expectations, not just to work. Each enrolled horse moves through a long, resumable workflow: a four-step onboarding wizard, structured Day 0 through Day 6 dosing, scheduled 30/60/90/180-day follow-ups, and end-of-study disposition, alongside safety forms for adverse events, protocol deviations, and early exits, every entry timestamped and attributable.

An append-only audit log records every data action, and a one-click export assembles a complete CVM submission package as XML, ready for filing. An operations dashboard tracks deadlines, tasks, and per-patient schedules across the whole study, with an admin console for access requests, orders, leads, and support.

Architecture built for the field

One codebase, three isolated experiences: two independent permission flags (shop access versus trials access) plus admin roles, enforced by dedicated route guards, so the same app safely serves a public brochure, a private storefront, and regulated data capture. Clinical data runs on a hybrid data layer, with local storage as an instant cache and a hosted PostgreSQL database as the durable source of truth, upserted in the background, so a veterinarian in a barn with spotty signal never loses a form.

Security is a first-class concern: invite-only authentication, a 30-minute cross-tab inactivity timeout, CAPTCHA on entry, and a full local-storage wipe on logout so nothing leaks on a shared clinic workstation. Enrollment decisions, order confirmations, and notifications all run server-side in serverless edge functions against the SQL database, so there is no bespoke API server to maintain, and the whole thing ships as an installable PWA on Vercel.

Accessible by design

Veterinarians capture trial data on whatever device is in the truck, often one-handed and in a hurry. The app is built WCAG-conformant: semantic structure, keyboard navigation, visible focus states, and long clinical forms that stay clearly labeled and legible under real conditions.