Reda.
Available

Venture Capital Analyst internship · available from December 2026

Reda Tagmouti

I turn ideas into working products, test them in the real world, and help turn what we learn into the next decision.

I've taken three tech projects to a real decision: a B2B sale, a shutdown driven by unit economics, and a delivered client product. I want to bring that technical and economic read to early-stage investing.

What I'm intoAI and technology, entrepreneurship, product strategy, and early-stage companies.

Off the clockValorant, pool, chess, film.

01

How I work

I like to understand the bigger picture while being hands-on in the details. When I work on a project, I enjoy exploring the problem, looking at it from different perspectives, testing ideas and figuring out what should be done next. I also like switching between different topics and learning quickly when I don't know something yet. For me, the most interesting part is turning an ambiguous problem into something concrete and making it happen.

Build

Build prototypes and systems that work in real conditions: computer vision, data pipelines, and deployment.

Run

Turn an open-ended problem into a concrete plan, priorities, and next steps.

Go-to-market

Talk to early users and customers, test the offer, and bring what we learn back into the product.

02

Selected work

Three projects, at three different stages of maturity.

Case 01 — Field-tested prototype, then shut down

AI Coach Sportif

Role
Founder — product, ML, and market validation
Stack
MediaPipe / MLKit · YOLO11s · WebRTC · Docker · Gemini API · AWS
Status
Prototype — stopped when the economics didn't hold

A computer-vision system that analyzes strength-training movements and gives real-time form feedback. I built it, tested it with users, and stopped when the technical and unit economics didn't hold.

From idea to decision

  1. 01The hypothesis: use computer vision to detect exercise form and give feedback during the movement.
  2. 02I first built for gyms, where cameras could monitor multiple users. I trained models for squats, push-ups, pull-ups and dips. The system worked, but three constraints emerged: the pipeline scaled to only around 10 simultaneous users, installing the required setup was too expensive for a gym, and the legal side was a blocker. Tracking each person individually on the gym's cameras without their consent wasn't possible under GDPR. In a place open to the public, people can't exercise their right to object, and the CNIL only accepts this for anonymised statistical uses.
  3. 03I pivoted to mobile to reduce deployment friction. I took the prototype to Delta Festival (Marseille), where visitors could test live pull-up and dip counting using a camera and a laptop. The stand stayed busy throughout the weekend, with 2,000+ visitors at the stand over the weekend, giving me an initial signal of user interest.
  4. 04I then built the backend for video streaming and rep detection, followed by a second prototype using the Gemini API to analyze frames at the key moment of each rep.
  5. 05The market study changed the decision. Users were willing to pay around €5, while estimated operating costs were around €10 per user under the tested assumptions. I tried to close the gap by replacing the API with a cheaper CPU-based model, using the API only to collect training data. The resulting on-device pose accuracy wasn't reliable enough for real-time feedback. I stopped the project.

This project mostly shows how I work: I run the full loop — build, test in the field, price the real cost — and I own the call to stop when the economics don't work.

What I learned

Demand alone wasn't enough. The product needed to work technically, scale at an acceptable cost, and support a viable price point at the same time.

Case 02 — Deployed and sold to an industrial client, then stopped

Sentinelle AI

Computer vision for industrial production counting

Period
Feb 2026 – Sep 2026
Role
Founder — need validation, model development, sale
Stack
YOLOE · YOLO26 · YOLO-cls · Grounding DINO · OWLv2 · LocateAnything · SAM · Python
Status
Deployed and sold to an industrial client in Morocco (97% accuracy in real conditions) — stopped in September 2026 after market testing.

Published with the owners' consent.

Excerpt — part of what the algorithm records on a camera feedYouTube ↗

The problem

A Moroccan factory producing ice for fish preservation found an unexplained gap between the volumes it produced and the volumes it sold, by comparing two consecutive years.

What I built

An automated production-counting system based on computer vision, built on the factory's existing cameras with no extra hardware. I developed it on my own from the client's data: detection, tracking, counting and a web console.

What was validated

  • 0197% accuracy in real conditions, measured against manual counts.
  • 02Integration with the existing cameras.
  • 03Sale to the client.

Market test

I then contacted about ten other manufacturers to test whether the sale could be repeated. None of them recognised the need, and none were ready to invest. I stopped the project in September 2026.

What I learned

One paying client doesn't prove a market. Repeatability has to be tested before investing in scale.

The annotation tooling

Labelling was the bottleneck of the project, and off-the-shelf platforms weren't good enough for this dataset — so I built the tool around it.

  • 01Bootstrapped labels with YOLOE: I show it the object on an easy dataset, correct what it misses, train a first model, then use that model to re-annotate the rest.
  • 02SAM fits every box to the object's real shape, so I no longer adjust bounding boxes by hand.
  • 03Duplicate-annotation detection, and propagation of one label across dozens of frames when the object stays put and only the background changes.
  • 04A stream watcher that crops detections straight into the dataset, removing most of the manual work of finding and cutting footage.
  • 05Side-by-side model comparison, a review pass over the labelled set to catch errors, and a separate mode for classification datasets.

For the labelling loop I compared YOLOE against Grounding DINO, OWLv2 and LocateAnything — YOLOE Large came out ahead, and it anchors the loop. I run the same comparison across the models I train myself, to pick the one I re-annotate with.

Case 03 — Client product, first version delivered

Online eyewear store with virtual frame try-on

Designed, built and delivered

Role
Product design and development
Stack
Next.js · MediaPipe FaceLandmarker · WebGL / Canvas · Cloudflare
Status
First version live at lhoptic.com — catalogue images and try-on assets pending from the client

An e-commerce storefront for an independent optician, with browser-based virtual try-on for eyewear.

The client wanted customers to browse and buy eyewear online while reducing the uncertainty of choosing frames without trying them on. I built the full storefront and a browser-based virtual try-on that tracks the user's face through the webcam and aligns frames in real time. The first version is live.

The first version is delivered and online. What is left sits on the client's side: images to fill out the catalogue, and the assets the try-on needs to be accurate — images of the contact lenses, and 3D models of the frames. Until those arrive, the try-on runs on an estimation rather than on the real products.

03

How I look at a startup

What my own projects taught me to check first.

01 · A sale is not a market

One paying client says nothing about repeatability.

Sentinelle AI: one sale, then ~10 manufacturers who didn't recognise the need

02 · Unit economics before traction

A busy stand doesn't fix ~€10 of cost per user against a ~€5 price.

AI Coach

03 · Technical defensibility

A product built on a third-party API leaves its margin with the provider.

AI Coach, Gemini API

04 · Regulation early

GDPR can close a market before the technology does.

AI Coach, cameras in gyms

04

Engineering × Entrepreneurship

MSc CentraleSupélec–ESSEC Entrepreneurs · 2025–2026

Strategy, business models, financing, negotiation, and go-to-market.

First semester: finance, strategy and entrepreneurship courses (accounting, business models, fundraising, go-to-market). Second semester: I chose the Startup Launchpad track. My project was incubated and every course was applied directly to it through assignments. I built the full financial business plans of AI Coach and Sentinelle AI and pitched them to a faculty jury. In the Business Acquisition course, I valued an SME and proposed the price I would pay to buy it.

Engineering degree · ENSEA

Engineering, machine learning, and computer vision.

Technical training in engineering, machine learning, and computer vision. It gives me the foundation to prototype and build the technology myself.

Together, they give me a useful combination: I can understand the technology, but I also care about whether the product makes business sense.

05

A note to the team

I'm looking for an investment team where I can learn to evaluate startups alongside experienced investors. What I bring: I've been on the founder side, and I can judge whether an AI product is technically defensible and what it really costs to run. Happy to walk you through the products, the numbers and the decisions, including the ones that didn't work.

Looking for

  • →Venture Capital Analyst internship · available from December 2026, analysing early-stage startups in AI, deeptech and B2B automation