Tony Arad Felik | Not Just Surviving AI — How to Thrive in It
Tony Arad Felik
Key takeaway: When AI takes over IQ and execution tasks, a manager's value shifts to strategy, people, culture and managerial courage — not delivery.
How AI is changing the way products, teams and careers are built
Eyal David · Updated:
AI on Product Builder covers how AI changes the way products get built: both the work itself and the products that come out of it. In these conversations, founders, product leaders and engineers explain why a product manager's value is moving from execution to judgment, why context and planning matter more than any single prompt, how to move fast without giving up ownership of quality, what makes customers trust and pay for an AI product, and where a real moat comes from when the model belongs to someone else.
“AI can give you five great solutions in a second. My place is to understand which four I kill and what's good.”
“My next bottleneck is going to be product managers who can't produce precise requirements fast enough.”
“AI is an amazing thing, but it's not a substitute for ownership, it's not a substitute for your responsibility for what you put in.”
“If the code is written so fast, sometimes by people who can't read it — then who will read it, who will understand it, who will care about its engineering quality?”
“If at your company you notice you're stopping talking to users, that's the red flag of a lifetime.”
“Don't be a people pleaser, give me pushback.”
“So basically the shift that developers are going to go through is becoming more orchestrators and reviewers of the agents' work.”
“One of the skills AI demands is, necessarily, critical thinking.”
“I wrote one big, magnificent prompt and hoped for the best... very quickly I got to spaghetti.”
“In my view, a good developer in the new world is one who knows how to identify problems among their customers and solve them, rather than one who writes code.”
“Nobody today will buy a chatbot or an app and pay for it at scale, even if it's a few dollars a month.”
“There's no AI without data — take the data out of the AI, there's nothing, there's no air there.”
“It doesn't make people redundant, it makes redundant the people who don't use this technology.”
“The gap that bothers me most today is the huge difference between what management in organizations believes can be done with AI, and what the people on the ground actually know can be done.”
“We're not trying to build AI in order to build Artificial General Intelligence; we want to create AI that solves real problems today and brings a lot of value.”
According to Shira Moyal, a PM's value lies in sense: the ability to ask the right questions, understand the business, customers and strategy, and make decisions quickly. Execution, like tracking timelines and writing tickets, keeps shrinking. Go to the episode
According to Nadav, the hardest problem when working with LLMs is context — how much information to expose, where, and at what cost (tokens and accuracy). Whoever knows how to build and preserve the right pieces of context (e.g. saving decisions in markdown files and referencing them) gets the strongest power in vibe coding. Go to the episode
AI slop is an insufficiently-vetted AI output passed along as if it's finished. Galit explains it "costs you twice": someone else on the team has to fix both your work and what the machine did poorly, and it also signals you're still at a basic usage level. It happens mainly when the machine isn't given enough context. Go to the episode
A language model predicts the next word token by token, so it struggles to plan, execute, correct itself along the way, and know how deep to search. An agentic system wraps the LLM, uses it as one tool out of a broad set, and enables controlled autonomy that breaks down a complex, multi-step problem in a way that provides guarantees an enterprise can rely on. Go to the episode
Vertical AI companies have teams with deep knowledge of a specific industry, and usually unique data that is very hard to obtain. Even when they use off-the-shelf models, that knowledge and data create value that is hard to copy. Examples from the episode: Aidoc in medicine and Eleos in psychological therapy. Go to the episode
Tony Arad Felik
Key takeaway: When AI takes over IQ and execution tasks, a manager's value shifts to strategy, people, culture and managerial courage — not delivery.
Ilan Peleg
Key takeaway: Code has become cheap, so a good developer is one who can identify customers' problems and solve them, not one who just writes code.
Amir Frankel
Key takeaway: Fast is slow, and slow is fast: AI speeds up the first step, but if you don't measure the whole cycle (quality, QA bugs, reviewer load) you pay for the shortcut for years.
Lior Frenkel
Key takeaway: There's a huge gap between what management believes AI can do (10x promises) and what actually happens on the ground (roughly 1.5x-2x) — creating constant pressure and a sense of failure on teams.
Shira Moyal
Key takeaway: A product manager's value has moved from execution to sense: AI gives you five good solutions in a second, and the PM's job is to know which four to kill. AI won't do that for you.
Daniel Marcous
Key takeaway: When AI raises engineering velocity, the bottleneck moves to product managers. That's why Daniel plans to hire fewer engineers and more product managers and designers in 2026, changing the 1-to-10 ratio he used to run with.
Itai Horn
Key takeaway: A mattress is a rare 'event' purchase with a high AOV and a lot of upfront research — so the whole decision rests on trust (365-day returns), a strong brand (Nectar, DreamCloud) and explaining the offering as clearly as possible.
Ori Katz
Key takeaway: Every hardware company is really a software company: Hailo has ~30-40 hardware engineers versus 100-150 software engineers, because the people who buy the chips are software developers who want to run AI on them — not to fiddle with the silicon.
Galit Galperin
Key takeaway: AI doesn't start with tools, it starts with mindset: the question isn't "which tool", but whether you have the head to work differently.
Nadav Abrahami
Key takeaway: AI writes code fast, but someone still has to understand what was built — the new challenge is understanding, ownership and engineering quality, not the writing itself.
Rani Bar Hama
Key takeaway: When building with AI, planning beats intuition: one big prompt plus spot fixes leads to spaghetti. Write a PRD, convert it into a set of prompts in a logical order, and define for each prompt what you expect to get and its acceptance criteria.
Ela Hatzav
Key takeaway: מעבר קריירה לא שגרתי משתלם: מפסיכולוגיה ותיירות, דרך עשור ב-non-profit (תגלית), ועד Product Management ב-Wix — הצטיינות בכל תחום (לאו דווקא אקדמי) היא מנבא חזק להצלחה בפרודקט.
Yaniv Golan
Key takeaway: A moat in the AI era doesn't come from the model: even if 99% of the value is the model, your 1% is only worth something if it rests on industry-specific knowledge or data that is very hard to obtain.
Rami Segal
Key takeaway: In a giant organization like Salesforce there's no problem reaching customers — the real challenge is visibility, relevance, and the fight over internal prioritization against competing solutions within the same company.
Dedy Kredo
Key takeaway: The developer's role is shifting from writing code to orchestrating and reviewing agents; strong developers who adopt these working methods become several X more productive.
Dedy Kredo
Key takeaway: In a GenAI startup the game is win big or fail big: you need a strong point of view, an insight people aren't paying attention to today, and to go with it through a big bet.
Zeevi Arnovitz
Key takeaway: A good copilot rests on three pillars: general knowledge (onboarding, like a new hire), personal instructions (custom instructions), and context specific to each project.
Zeevi Arnovitz
Key takeaway: A product copilot is like a genius intern: without context it returns generic outputs. Build it as a project with knowledge (what you'd give a new hire in onboarding), custom instructions that ask for pushback rather than people-pleasing, and a separate chat for each product project.
Tse'ela Mida
Key takeaway: da Vinci doesn't operate on its own — the surgeon sits at a console and controls four robotic arms; the robot doesn't tire or tremble and adds degrees of freedom and 3D vision, which translates into fewer complications, shorter hospital stays and lower costs.
Jonathan Gur-Zeev
Key takeaway: AI won't enter professional production on speed alone. Weavy's goal isn't working twice as fast but building a "design machine" that produces a thousand times more output without giving up control and professional integrity.
Lior Sassy
Key takeaway: With AI products the solution comes before the problem: LTX Studio started from text-to-image technology and an internal tool, and the real work was breaking down what filmmakers and ad creators need and finding where the product truly gives them value.
Alex Frenkel
Key takeaway: People won't pay for a mental-health chatbot, but organizations pay for a hybrid service: Kai cracked its business model only when it added a human clinical team for intake and plan tailoring, with the AI accompanying users day to day.
Roy Feig
Key takeaway: When an entire industry underwrites categorically and exits whole regions, there's an opening for whoever can assess risk at the level of a single property. Honeycomb built its IP exactly there: spotting the good buildings everyone else gives up on.
Amnon Morag
Key takeaway: The biggest value from AI in the coming years will come from autonomous systems that wrap the LLM — 'controllable, reliable and efficient' — and not necessarily from improving the model itself.
Shay Shitrit
Key takeaway: AI at the discovery stage makes it possible to distill insights from an enormous volume of sources (transcripts from Gong, Slack conversations, CSM/RSM summaries, presentations) within hours instead of weeks — Shay says he won't do discovery anymore without this tool.
Eilon Reshef
Key takeaway: A product manager's number-one skill at Gong: sit with the customer, look them in the eye and understand what they need, why, and what they'll get from it, not just what they ask for. Otherwise you become a paper shuffler.
Ohad Peri
Key takeaway: Bllink's first feature (onboarding a building through an AI chat instead of a human rep) failed — not technically, but psychologically: building-committee managers who entrust money want to see there's a human behind the process. But the failure produced the AI infrastructure that today powers the automation of customer support.
Uri Fen
Key takeaway: A product manager's real focus is on the problems, not the solutions — solutions are easy; the hard part is understanding whether the problem is even worth solving for the user and the business.