Services
I work with a small number of clients at a time, which is the only way each one gets real attention. The work falls into three groups: what people see and use, the systems underneath it, and the fields where I already know the constraints.
Web & mobile
What people actually see and use — and whether they can find it.
Full-stack web and mobile, taken to something you can maintain after I leave.
- Next.js and React front ends; React Native across iOS and Android
- Python, FastAPI, and Node back ends with the data model thought through first
- Inherited codebases: assessment, then a plan, then the work
- Handover that includes documentation, not just repository access
Fast, accessible marketing sites that your team can update without calling me.
- Marketing sites, landing pages, and campaign pages
- Bilingual and multi-language builds where the second language is not an afterthought
- Migrations off WordPress and shared hosting, including the DNS move
- Content workflows that fit how the organisation already works, not a CMS licence
The technical half of search — the part that is engineering rather than copywriting.
- Site architecture: pages that target what people actually search for
- Structured data, canonicals, sitemaps, and robots policy
- Core Web Vitals and the render path that decides them
- Migrations and redesigns that keep the rankings you already have
Native iOS where the platform matters, React Native where one codebase is the point.
- Native iOS in SwiftUI, including camera, Vision, and SceneKit work
- On-device inference where the cloud is too slow, too costly, or not permitted
- StoreKit 2 subscriptions and paywalls
- React Native and Expo for teams that need iOS and Android from one codebase
AI & infrastructure
The systems underneath: what the product can do, and what keeps it up.
Agentic systems and retrieval pipelines that hold up outside a demo.
- Agentic architectures and multi-step tool-using workflows
- Retrieval: chunking, embeddings, vector stores, and the quality of what comes back
- On-device and power-efficient models where the cloud is not an option
- Evaluation harnesses, so a change can be shown to be an improvement
Infrastructure defined in code, so environments are reproducible and deploys are dull.
- AWS and GCP architecture, provisioned with Terraform
- CI/CD pipelines and environment parity across dev, staging, and production
- Secrets handling, key rotation, and least-privilege access
- Cost review — the line items nobody has opened in a year
Specialist domains
Fields where I already know the constraints, so you are not paying me to learn them.
Software for clinical and care settings, where the constraints are real and I have met them before.
- Medical device software and continuous patient monitoring
- Local-first and privacy-by-design architectures for participant data
- Accessibility and WCAG treated as a requirement rather than an audit
- Clinical research tooling, capture workflows, and reporting
Analysis pipelines and research tooling, from someone who has also been the researcher.
- Bioinformatics pipelines and gene expression analysis
- Image analysis software for laboratory workflows
- Statistical modelling, visualisation, and reproducible analysis
- Grant-funded timelines and academic collaboration
How engagements work
Three structures. Which one fits depends on how well-defined the outcome is at the point we start talking.
Fixed-scope delivery
A defined piece of work, written down, at a price agreed before I start. You know the number and the deliverables in advance, and anything deferred is recorded as deferred so there is no argument later about what was included.
Ongoing retainer
A recurring block of time each month for teams that need continuity — feature work, infrastructure, and whatever surfaces. Priced monthly and cancellable.
Review & advisory
A short, bounded engagement: architecture review, technical due diligence on a codebase you are inheriting or acquiring, or advice on adding AI to a product that already exists.
Rates depend on scope and timeline, so there is no price list here. Describe what you need and you will get a number in writing before any work starts.
How a project runs
Scoping call
Free, usually half an hour. What you are building, what is already there, what is actually blocking you. If I am not the right person, you hear it here.
Written scope
Phases, deliverables, and a price. Everything in scope is listed; everything deferred is listed as deferred.
Build
Work lands in your repository in reviewable pieces. You watch it arrive rather than waiting for a reveal at the end.
Handover
Documentation, an operator guide where one is needed, and a walkthrough. You own the code and can maintain it without me.
Have something in mind?
Describe the problem and you will get an honest answer about whether I am the right person for it.