Start a project
Tell me what you are building and where it is stuck. I take on a small number of engagements at a time, so the fastest way to find out whether we are a fit is to describe the actual problem.
Common questions
What kind of work do you take on?
AI and LLM systems, cloud infrastructure, and production applications — work that has to ship and then stay up. Recent contracts: a computer vision mobility assessment app, and an AI-native operational layer for a staffing agency.
How do you price engagements?
Fixed price against a written scope wherever the work can be defined up front, so you know the number before I start. Open-ended and advisory work runs on a retainer or hourly. Either way the scope is written down first.
Will you work with an existing codebase?
Often that is the job. My last two contracts both began with inherited code that needed assessment before anything could be built on it. You will get an honest read on what is salvageable and what is not.
Do you work in regulated or clinical settings?
Yes. I have built medical device software for continuous patient monitoring, and a research-grade assessment app handling participant data where privacy design was a contractual requirement rather than an afterthought.
Do you offer advisory work without building?
Yes — architecture review, technical due diligence on a codebase you are inheriting or acquiring, and advice for teams adding AI to an existing product. A short review is often the most useful first engagement.
What about research collaborations?
I take these on. I am a published researcher with computational biology and bioinformatics experience, so grant-funded projects and academic timelines are familiar rather than novel.