Skip to content
View Benyoumen's full-sized avatar
🎯
Focusing
🎯
Focusing

Block or report Benyoumen

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
Benyoumen/README.md

Benjamin Tayar, Forward Deployed PM building AI products and agents

Hi, I'm Ben 👋

Forward Deployed PM in São Paulo. I find the problem worth solving, decide what to build first, and build it with AI, without the slop.

About me

I have 17 years of experience building digital products, as VP Product & Growth, CEO and founder. I scaled a B2B SaaS platform used by thousands of real estate businesses.

Since 2023, I build AI products and AI agents. I also teach product, executive and engineering teams how to work with them.

Most of my energy goes into two things: finding the right problem, and putting the work in the right order.

Recent work: an AI sales assistant

I built a multi-agent system that supports salespeople from prospecting to forecast. It researches and qualifies accounts, finds similar customers to prospect, and prepares sellers for meetings. It also keeps the CRM up to date and flags risks in the pipeline.

  • From 2 days to 30 minutes to prepare an account.
  • 90% adoption across the teams using it.
  • 1 to 2 hours saved per salesperson, every day.

Three rules shaped the design:

  1. Use fixed rules where the process is known. Use AI only where judgment adds value.
  2. A person approves before the agent writes to the CRM, until the agent earns more autonomy.
  3. Agree on the business KPI and its baseline before building anything.

Forward Deployed PM

I work as a Forward Deployed PM: inside the client's operation, next to the people who do the job. I learn their workflow in detail. Then I build the agent where they already work: their CRM, their spreadsheet or their chat tool.

Nobody relays the problem through a chain of handoffs. I hear it directly from the people who have it, so the solution fits the real constraint.

Four rules keep this work from turning into one-off consulting:

  • Outcome first, then scale. First, a result the client can measure. Then, a version we can repeat.
  • Build once, reuse often. A piece built for one client is designed so the next client can use it too.
  • Function over form. If people don't use what we built, we change it, even if we liked it.
  • Value that stays. The client's team runs and corrects the agent with its own evals. The value should not leave when I do.

How I work

The 4D product loop: 1 Discover, 2 Design, 3 Develop, 4 Deploy, then the next loop

I follow the 4D method: Discover, Design, Develop and Deploy. Each phase ends with a clear check. If the check fails, the work goes back one phase. The loop is the same for a client's operation and for a product with many customers.

Prioritization gets as much care as discovery. I rank work by user value, KPI impact, expected ROI, effort and dependencies. Sometimes a small feature goes first because a bigger one depends on it.

How an AI agent earns autonomy: 1 Suggest, 2 Recommend, 3 Approve, 4 Veto window, 5 Act and report

The levels follow Sheridan's scale of automation, the model Product Faculty uses to design AI features. An agent gets a level per type of action, not one level overall. For example, it may log a note on its own but still need approval to send an email. To move up, it needs evidence: a pass rate on real test cases, a trial run next to the team, a working undo, and the process owner's sign-off.

How I evaluate AI agents

Two eval loops. Offline decides if a change may ship. Online finds what the agent gets wrong. Each new failure becomes a test case.

I treat evals as product work. Before a change ships, it must pass a fixed dataset with code checks and a validated LLM judge, in repeated runs. After it ships, every run is traced, users rate the output, and each new failure becomes a test case.

  • Code before judges. Anything a rule can check goes in code. A judge covers only what needs interpretation.
  • One judge, one failure. Pass or Fail, never a 1 to 5 score, and no trust before it agrees with human labels.
  • Honest numbers. Zero failures in 10 cases does not mean 100% accuracy. I state the margin.
  • Watch it after launch. A nine-step production loop with alerts and a 30-minute weekly review of the worst runs.

The full version of the method: AI evals workflow · Production monitoring · RAG evals · LLM-as-a-Judge · the backlog workflow · the agent principles.

What you'll find here

Backlog Writing System

Backlog Writing System. My method from problem to weekly delivery: a Now / Next / Later roadmap, readable specs, a capacity simulator, and evals for AI behavior. 21 skills and a worked example.
Field guide · Capacity simulator

No-slop design

No-slop design. How to spot screens that look generic and AI-made, and how to fix them. Each live mockup sits next to its generic version.
Mockup gallery · The 16 tells

AI Evals Method

AI Evals Method. How I measure, improve and ship an agent: traces, datasets, experiments, a validated judge and a six-point release gate. Built and tested with Arize AX.
The workflow · Monitoring · RAG evals · Lessons

LLM-as-a-Judge

LLM-as-a-Judge. How to write a judge that can be trusted, and what the PM should decide. Includes a ready-to-adapt judge prompt.
The method · Example judge

NextStone concept

NextStone. A full product concept: a marketplace where real estate developers meet investment funds. Four roles, each with its own dashboard.
Live demo · Case study

Agent Design Principles

Agent Design Principles. How an agent earns autonomy, how it writes safely to a system of record, and how to design screens people use all day.
Read the principles

PM Deck and Writing Skills

PM Deck and Writing Skills. Rules and a QA pipeline for decks and project messages that read as professional, not AI-generated. The sample deck follows its own rules.
Live deck

The backlog document

The backlog document. One page to review a whole backlog before it goes to Jira or Azure DevOps. Set owners and story points, and see each person's load against their capacity.
Open the document · Spec preview

Every example uses a fictional product and fictional data. Nothing comes from a customer or an employer.

Teaching

I co-designed and delivered AI adoption programs for about 3,000 leaders, product managers and developers. Partners include FGV, Secovi-SP and LARES. The programs teach teams to find high-value AI use cases, link them to KPIs and ROI, and redesign their workflows.

Certifications

Product Faculty, AI Product Management Certificate

AI Product Management. Product Faculty. Verify the certificate. Taught by Rohan Varma (Product, Codex at OpenAI) and Shubham Saboo (Senior AI Product Manager, Google).

Le Wagon, Data Science and AI

Data Science and AI. Le Wagon bootcamp. Python, machine learning, deep learning and models in production.

Le Wagon, Web Development

Web Development. Le Wagon bootcamp. Full-stack web apps, from database to interface.

Background

  • 17 years in product, B2B SaaS, growth and digital platforms. Former VP Product & Growth, CEO and founder.
  • Two master's degrees in law and an MBA in real estate management (ESSEC).
  • Trained in Paris, based in São Paulo, working internationally.
  • Native French, fluent English and Portuguese.

Open to

Forward Deployed PM · Head of AI Product · Director of Product · Group PM · Senior AI PM

Remote roles across the US, Europe and Latin America.

Pinned Loading

  1. nextstone-concept nextstone-concept Public

    Concept MVP: a marketplace connecting real estate developers with investment funds. Four roles, demo mode, no backend needed.

    TypeScript

  2. agent-design-principles agent-design-principles Public

    UX principles for AI agents that act for a person: autonomy earned tier by tier on evals, the write contract with the system of record, dense operator screens. 4 skills, 2 diagrams.

    Mermaid

  3. backlog-writing-system backlog-writing-system Public

    A backlog is a set of decisions. Seven stages with a gate each, twelve principles, 18 skills, 14 templates, a worked example, evals as acceptance criteria for AI behavior.

    HTML

  4. no-slop-design no-slop-design Public

    Visual AI slop is manageable: the 16 tells of generated screens and what to do instead, the mockup-first validation workflow, 4 skills, and a live mockup gallery built on fictional data.

    HTML

  5. pm-deck-and-writing-skills pm-deck-and-writing-skills Public

    Editorial rules and a QA pipeline for decks and project messages, plus an anti-AI-slop rewrite guide

    CSS