About
Technical Product Manager and Product Owner with 5+ years taking AI, SaaS, fintech and marketplace products from ambiguous problem to shipped release. I own the full arc: discovery, PRDs and technical specifications, backlog and acceptance criteria, release planning. I also build working prototypes, so a contested spec gets settled with something clickable instead of another document.
I’m David Olatunji, though almost everyone calls me Avi — online I’m AviOfLagos. Product owner and technical product manager based in Lagos, working with teams across Toronto, New York and Berlin. My background is split down the middle: electrical engineering, then computer science, then four years of shipping products. That split is basically the job description.
In practice that means I can sit in a technical design review and a pricing conversation on the same afternoon, and translate faithfully in both directions. I write the roadmap and the acceptance criteria. I also open Figma and the codebase when a spec is faster to settle with a prototype than a paragraph.
Most of my recent work is AI products: an orchestration platform for marketing teams, a registry that lets agents install new capabilities, a voice AI that runs first-round interviews. Before that, marketplaces, real estate, then solar. The thread is the same: take something people currently do with spreadsheets, phone calls and hope, and make it a product.
Alongside client and venture work I mentor product managers at HNG, Africa’s largest tech internship programme, where I’ve helped shape curriculum and success metrics for thousands of participants and run the community events that go with it. Teaching the fundamentals is the fastest way I know to keep re-checking my own.
How I work.
Settle it with something clickable
A prototype ends an argument that a third document would only extend. If two people read the same spec two ways, I build the smallest version of both and we look at them.
The backlog is the strategy
Everyone agrees with the roadmap deck. What you actually chose is whatever sits at the top of the backlog on Monday, so that is the artefact I guard.
Write the acceptance criteria first
If I cannot say what "done" looks like before work starts, the requirement is not ready. Most scope arguments are really an unwritten criterion surfacing late.
Ship, then look
Research before a release tells you what people say. The week after tells you what they do. I plan for both and weight the second more heavily.
Where I’ve been.
Three of them. The full record lives on the résumé.
- Own the product end to end for an AI marketing platform, from the original pilot through a V2 architecture scoped across 11 milestones and 7 epics.
- Led 6+ client products across AI, fintech, real estate and Web3 from discovery to MVP, owning roadmaps, requirements and go-to-market.
- Led product coordination and mentorship across 30,000+ participants annually in Africa's largest tech internship programme, enforcing agile standards and improving delivery efficiency by ~50%.
Toolkit.
Certifications.
Click one to see the certificate.