Clinical & Research Statistics
- ·Study design & power analysis
- ·Bayesian & frequentist modeling
- ·Interim monitoring & adaptive designs
- ·Manuscript-ready results & interpretation
I partner with clinical researchers, medical teams, and labs to blend statistical methodology with production-quality software. Decisions that hold up under scrutiny. Systems that scale.
Who I work with
Services
About
Statistician, software builder, and advisor. I move between R/Python notebooks, registrational study plans, and production codebases without handing anything off to chance. The job is to uncover the signal, package it so people can act on it, and leave teams with systems they can evolve.
I partner directly with founders, principal investigators, and R&D leaders. No bloated teams—just thoughtful work and fast loops.
Principles
Tooling
R · Python · Stan · Next.js · Supabase · Postgres · DuckDB · Airflow · AWS · Vercel
Portals
Each portal routes to a dedicated property
Engagements, proposals, secure data rooms, and project dashboards for active clients.
Enter portalCustom tools, model sandboxes, and private documentation for ongoing build-outs.
Enter portalCollaboration space for partner labs, grant workstreams, and reproducible pipelines.
Enter portalCourses, workshops, and cohort support for students and research teams.
Enter portalSnapshots
Neuro device trial
Rebuilt the statistical analysis plan, automated interim checks, and gave sponsors realtime dashboards.
Health analytics platform
Designed the modeling approach, built the orchestration layer, and handed off runbooks to the product team.
Population study
Tuned the models, codified QA, and deployed a reproducible pipeline the team now owns.
How it works
Audit what you have, surface constraints, and select the statistical or software approach that fits reality — not the textbook.
Prototype quickly, lock down governance, and deliver analyses or tooling that stakeholders can trust and verify.
Hand off documentation, dashboards, and runbooks so your team extends the work without ongoing dependency.
FAQ
Yes. Most partnerships blend fixed-scope builds with an ongoing cadence for questions, audits, or roadmap support.
Absolutely. The best outcomes happen when we share the same repo, dashboards, and delivery rhythm.
R, Python, Stan, Next.js/React, Postgres, DuckDB, Airflow, Supabase, and whatever your team already runs.
Get in touch
Send a brief with your hypotheses, timelines, and constraints. I'll come back with a concrete path—statistical design, a custom tool, or a hybrid.