Senior Product Manager · London
Mohammed Rashid
I own products end to end — from identifying the problem to shipping the solution to measuring what changes.
Background in engineering (MEng, UCL). Currently Head of Product at Dr Tim Pearce, building AI health products. Previously scaled a clinic from £0 to £1.2M and built a travel SaaS from scratch.
Selected work
Longevity Flywheel
Dr Tim Pearce · 2024–presentProblem: A high-quality longevity clinic with no scalable product layer — every patient interaction was manual, one-to-one, and hard to grow.
What changed: Built the product layer: a B2B2C Flutter app, e-learning academy, and AI companion. Scaled to £100k MRR and £500k/month in e-commerce alongside a £1M+ webinar programme.
Patient AI Companion & Clinician Co-Pilot
Dual-agent systemProblem: Clinicians couldn't monitor patient progress between appointments. Dosage decisions were made on sparse, subjective data — and documentation ate hours of clinical time.
What changed: Two products shipped in parallel. Patients get a companion that tracks mood and wearable data. Clinicians get structured impact insights and automated notes — cutting admin and improving dosage accuracy.
OpenAI Treatment Plan Engine
Twoth · 2022Problem: Dentists at a 6-surgery specialist clinic spent 30–40 minutes per patient manually drafting treatment plans. This bottlenecked capacity and introduced inconsistency.
What changed: Shipped an OpenAI-powered engine that generates personalised plans from intake data. Cut documentation time to under 5 minutes. Patient conversion increased 35%.
TROLLII
FounderProblem: Travel agents had no affordable, API-first way to search and book across multiple hotel inventory sources in one place.
What changed: Architected a B2B2C booking engine on AWS/Node.js connected to 60,000+ hotels via live feeds. Built to handle real-time pricing, availability, and booking at scale.
How I work
Start with the problem, not the solution
I spend more time than most on diagnosis — user interviews, data, stakeholder context — before I let a solution anywhere near a roadmap. The best features I've cut are the ones I was most excited about.
Own the outcome, not the output
Shipped features aren't success. I track what changes for the user after launch and use that to decide what's next. My product decisions are always tied back to a metric I can defend.
Work at the intersection of commercial and technical
I can read a P&L and sit in a sprint planning meeting. That range means I can make faster decisions and translate cleanly between engineering, design, and leadership.
Ship, learn, adjust — fast
I bias toward getting something real in front of users quickly. Prototypes over decks, MVPs over roadmaps. I've scaled products from zero using this approach more than once.
Open to Senior PM roles in London. Get in touch or read my CV.