How to Build a Copilot for Product Work — Zeevi Arnovitz (Wix) - Product Builder Podcast episode with Eyal David
Updated:

How to Build a Copilot for Product Work — Zeevi Arnovitz (Wix)

Host: · Guest: Zeevi Arnovitz · About the host

In this episode

  • A good copilot rests on three pillars: general knowledge (onboarding, like a new hire), personal instructions (custom instructions), and context specific to each project.
  • Without enough context, even the strongest model returns generic outputs — the real investment is in the context stage, like briefing an intern.
  • Setting custom instructions solves the people-pleaser problem: you ask the model for pushback instead of flowing along with every idea.
  • The practical architecture: one project that holds knowledge + custom instructions, and under it a separate chat for each product project.
  • The copilot accompanies the entire product lifecycle — from discovery, through wireframes and challenges, planning the test, all the way to shipping the product.
  • The tooling landscape moves fast: at Wix they build in Gemini, Zeevi personally prefers ChatGPT, and every few weeks a new model (like Claude) changes the game.

Episode Description

Zeevi Arnovitz from Wix breaks down his method for building a copilot that accompanies product work end to end. Instead of treating AI as a one-off chat, he builds a permanent 'worker' based on three pillars — knowledge, personal instructions, and context — and relates to it like a genius intern who needs a good brief so it doesn't produce generic outputs.

Read the full transcript
Full transcript with speakers and timestamps

Selected quotes

“I really treat this thing like an intern working with me, and like a real intern — even if this intern is the most genius in the world, if you don't give enough context about what we're working on, its outputs will be generic.”
— Zeevi Arnovitz
“The three important pillars of the copilot are general knowledge... I look at it as if you just hired someone new to your team.”
— Zeevi Arnovitz
“Don't be a people pleaser, give me pushback.”
— Zeevi Arnovitz

Questions & answers

What are the three pillars of a product copilot?

General knowledge (everything you'd give a new hire during onboarding), personal/custom instructions (how you want it to respond, including pushback), and setting up a project that centralizes both, with a chat under it for each task.

Why is context so important?

Because even a genius intern, if it doesn't get enough context about what you're working on and what problem you're solving, will return generic outputs. That's why you should invest most of the effort in the context stage.

How do you solve the model's people-pleaser problem?

Through personal/custom instructions — define up front that the model shouldn't flow along with every idea but should instead give pushback and challenge you.

What tools do you build the copilot in?

At Wix they build in Gemini; Zeevi personally likes to use ChatGPT; and he notes that Claude is changing the game too. The landscape refreshes every few weeks.

Across which stages does the copilot accompany you?

Across the whole project — from the discovery level, through the wireframes and the challenges, planning the test, and all the way to how the product ships.

Product AI Copilot Product Management Wix ChatGPT Takhles Episode LLM