Projects
CRIO — Regulated clinical data integration
Integrating CRIO's eSource platform with Veeva's EDC API
CRIO needed to connect its eSource platform to Veeva's EDC API for a pharmaceutical sponsor's clinical study: a regulated, zero-to-one integration where a wrong assumption about the data model could cost a partner sponsor real time. I owned this from discovery and requirements through sponsor UAT and early release, while running a second CRIO product team at the same time.
I read Veeva's API documentation myself, tested calls in Postman, and worked directly with developers to confirm what the API would actually return before committing to a data model; that produced an immutable-ID subject-linking approach targeting sub-60-second linking for site coordinators. When CRIO's and Veeva's data models didn't reconcile on deleted records, I made the call myself: send empty strings with a distinct change-reason tag, keeping the audit trail intact without stalling engineering on the ambiguity. I also prototyped a "mapping visibility" feature in Lovable so users could see at a glance which data points were mapped, and built a Looker dashboard tracking the integration's health post-launch (time to send, success rate, failures by type).
- Delivered MVP through sponsor UAT and built the early-adopter site and user list
- Ran training webinars ahead of general release
- Designed the subject-linking approach to target sub-60-second linking for site coordinators
AdvancedMD — Telehealth platform rebuild
Rebuilding Telehealth around a build-vs-buy call on Zoom
As PM for AdvancedMD's patient engagement portfolio (Telehealth, Patient Portal, Electronic Payments), I ran a build-vs-buy analysis comparing Zoom's video API against a proprietary calling system — the market read that set the technical direction for a full rebuild of the legacy Telehealth platform.
I paired Pendo and Splunk analytics to combine usage data with direct user feedback, using that combined view to prioritize the rebuild and time a reversal of an earlier switch from Zoom to Twilio. I also added a credit-card-on-file option to the Telehealth intake flow.
- Monthly usage grew 63%, from 27.4M to 44.7M minutes (Jul 2022–Feb 2024)
- $500K in annual savings from a Zoom contract renegotiation driven by usage forecasting
- 41% lift in on-time payments after adding credit-card-on-file
CRIO — AI-augmented product workflows
Automating the product team's manual workflows with AI
As my team's AI Champions representative, I built and rolled out AI-driven workflows for requirements docs, Jira tickets, regulatory updates, and code-change summaries, including a custom AI skill with integrated Python scripts, executed via CoWork tasks, that automated our product release notes.
I also developed a comparative analysis framework to evaluate AI-generated content against human-written content, using iterative prompt engineering to improve it, and built a usage dashboard that tracked Claude adoption and flagged overspending across peers.
- AI content and decision-making accuracy improved from 40% to 80% through iterative prompt engineering
- Saved the product team 5–10 hours a week
- Cut my own Claude spend 46% using the usage dashboard I built
CRIO — Offshore team & infrastructure migration
Standing up CRIO's first successful offshore development team
An earlier attempt to fold India-based developers directly into US teams had caused friction and time loss for tech leads. Instead of repeating that approach, I stood up CRIO's first successful offshore development team and hired an India-based Product Owner to run it independently rather than managing it myself.
That team went on to lead the company's migration off legacy mounted file-share storage onto Google Cloud Storage.
- $30K a month in storage cost savings from the cloud storage migration
- Built a team structure that ran independently, without requiring day-to-day oversight