We use cookies.

By clicking “Accept All”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Cookie Policy for more information.

Optahunt

Doctor Project illustration

Jump or climb? Progress has no secret except effort.

Yassine Fatihi: curiosity, the real trigger.

Yassine Fatihi started as a developer in 2015, building intranets, platforms and dashboards. Then came e-commerce: project manager, business analyst, product owner, on Magento, Salesforce Commerce Cloud and order management systems. Since 2021, product data has been at the core of the work.

One question kept coming back along that road: why do good teams, with good tools, still publish products with wrong or missing information? It is not because the tool is bad that the catalog is broken. Most of the time, the data model and the ownership are.

In March 2023 that question became Doctor Project: an independent practice, remote or on site, built on Research, Strategy, Technology and Leadership, with one goal: make product data clear, structured and useful, so customers find the right product and businesses grow with confidence.

Why does Doctor Project exist?

Complexity to clarity, in product data systems.

Across luxury, fashion, petcare, DIY retail and B2B distribution, the same pattern keeps appearing: a catalog modeled on a supplier classification, identifiers nobody owns, several tools and no single source of truth. Teams work hard and still fix the same errors every week.

Efficiency is not only speed. It is how often you have to stop and fix things. Doctor Project exists to reduce those stops: get the model and the ownership right first, then let the tools do their job.

Doctor Project illustrationThe Golden Question

The lesson behind the method

On a global petcare catalog, a barcode reconciliation showed that 67% of products shared a duplicated barcode, caused by product versioning and low GS1 maturity. Fixing it meant warning distributors for about 4,000 references.

Nothing was broken in the tools. The problem was a decision made years earlier, the first time an identifier was assigned. An identifier is a promise to the outside world, and the cheapest moment to get product data right is the first one.

So we start before any configuration: the model, the identifiers, the owners. The tools follow.

Doctor Project illustrationDrive your direction before it drives you

How we work

Every engagement rests on four pillars:

  • Research: facts first. We measure your catalog before we recommend anything.
  • Strategy: a roadmap that business and IT can both sign.
  • Technology: the tool is never the hero, it serves the model.
  • Leadership: decisions, owners and governance that still hold after go-live.

Governance is a daily habit, not a document. That is why every mission ends with teams who can run the catalog on their own. See how a PIM engagement starts.

Clarity over complexity

Small and senior by design, remote or on site. You work directly with the person who designs the solution, in English or French, from the first workshop to go-live. The mission is simple: prove that good product data does not need more complexity. It needs a clear model, clear owners and a little patience.

Doctor Project illustration

Education and certifications

A Master's in Web and Mobile Development and Architecture (EFREI Paris, 2020), a Bachelor's in Computer Science (UPEC, 2018), and certifications in Akeneo, Fluent Commerce and project management. Learning never stops: we test before we recommend.

Training program thumbnail

Professional Bachelor's in Data Security

Sectors we know from the inside

Luxury and jewelry, fashion, petcare and veterinary, DIY retail, confectionery and B2B distribution. Each sector taught us something the next one needed.

Industry illustration

Startup Industry

Where it started: building the product.

Before product data, there was code. As a developer and project manager on SaaS products for invoicing and IP protection, and later as a prompt engineer for a LinkedIn SaaS, we learned how fast a young product grows, and how quickly its data model has to keep up.