# The PM’s New First Draft Is an AI Prototype

*By PM Daily Digest • August 20, 2026*

Across prototyping, agentic products, and AI-first teams, the strongest signal is that PMs must provide context, stage trust, and defend judgment while execution accelerates.

## Big Ideas

**AI prototyping is becoming the PM’s first draft.** Product Compass reports that Meta PMs now vibe-code prototypes for Zuckerberg and that product-sense interviews include a live prototyping round; a Productboard survey cited in the piece says 60% of enterprise product teams already use two AI tools for prototyping. [^1] The shift is from “complete spec” to context plus iteration: define users, problems, jobs-to-be-done, evidence, and out-of-scope in `CLAUDE.md`/`AGENTS.md`, ask the agent to propose the interface and alternatives, and ask up to five questions before it starts. [^1] Cheap, reversible ideas can be feature-flagged and measured in production, while high-risk or hard-to-reverse ideas still merit experiments. [^1] The PM edge is therefore the quality of the context and the judgment about what to learn, not prompt-to-screen speed. [^1]

**Model choice is product design.** A local-model essay argues that the right model is the one that clears the quality bar for a specific job: coding needs reasoning and context, while inline writing needs latency, voice, and timing. [^2] Local inference fits small, frequent, personal or offline work; cloud fits hard reasoning, shared work, and large context. [^2] Use that split as an architecture question before choosing a vendor or model.

## Tactical Playbook

**Find the automation boundary manually.** A founder with roughly 10 prospective pilot users asked whether to run the process manually or build a light MVP. The advice: ask each person for one real case and a review date, run the first three manually, and only build the step that repeats across all three. [^3][^4] For agentic workflows, this tests repeatable value before automating a whole system.

**Treat AI-generated prototypes as real software.** In the workshop, a Lovable CRM’s contacts policy was `USING true`, so any signed-in user could see the data; an outside attendee confirmed the exposure 62 seconds after the link was shared. The fix was per-user isolation, and the article’s rule is to inspect Cloud policies before publishing. [^1] Make data isolation a demo gate, not a post-launch cleanup.

## Case Studies & Lessons

**Owner’s pivot was an outcome redesign, not a chatbot add-on.** At Pizza Expo, restaurant-owner enthusiasm for an AI concept contradicted the company’s earlier expert and discovery signal; Owner then changed onboarding so a restaurant name triggers web, competitor, Google-profile, review, and photo analysis, followed by a new site in under five minutes. [^5] Owner says more than 83% of new customers now start with Gradar, growth was faster in 2025 than 2024, and it is approaching $100M ARR. [^5] The lesson is to encode a best-practice path that drives an outcome: in agentic products, repeated manual logins are a failure signal, so low-touch success matters more than DAU. [^5]

**Square stages delegation behind trust.** William Ave describes the DRRI/DRI model as one empowered owner carrying a decision from ideation through go-to-market and scale, cutting silent vetoes and alignment problems. [^6] ManagerBot starts with ideas and rich artifacts such as menu engineering and labor forecasts; only after investigation and trust does the user delegate bulk actions such as campaigns or price changes. [^6] A reusable agent UX is: insight → artifact → reviewed action → delegated execution.

## Career Corner

**AI-first teams still need juniors, but managers must defend the learning loop.** Opus 2’s CPTO says juniors are part of its diversity strategy and receive the same 30/60/90 onboarding and first-year value expectations as more senior hires. Managers are expected to spot LLM slop and make juniors present their own thinking, not just submit fast output. [^7] The team also compares AI adoption with PR size and DX/DORA scores, retaining small, well-planned customer value as the quality bar. [^7] For PMs, use AI but keep reasoning visible; for leaders, measure quality and learning alongside speed.

## Tools & Resources

**Lennybot is a focused retrieval tool for PM work.** Lenny Rachitsky’s new Grok Bot is trained on 500+ podcast episodes and newsletter posts; prompts cover first 1,000 users, promotion, PM interviews, growth ideas, and hard feedback, via a custom MCP connector. [^8] Use it to generate starting hypotheses and questions, then validate them against current users and data.

---

### Sources

[^1]: [AI Prototyping in 2026: Lovable vs. Google AI Studio vs. Claude Design vs. Claude Code](https://www.productcompass.pm/p/ai-prototyping-lovable-ai-studio-claude)
[^2]: [𝕏 article by @hnshah](https://x.com/i/article/2089938520031031296)
[^3]: [r/startups post by u/IndependenceOne4743](https://www.reddit.com/r/startups/comments/1vsr6zd/)
[^4]: [r/startups comment by u/RocketSeven](https://www.reddit.com/r/startups/comments/1vsr6zd/comment/p4pbmig/)
[^5]: [From 0% to 83% AI-First Customers in 2 Years: How Owner's CEO Rebuilt a $100M Vertical B2B Company](https://www.youtube.com/watch?v=sJM9BrgpxwI)
[^6]: [Square Global Head of Product on How to Build AI Agents People Actually Use | Willem Avé](https://www.youtube.com/watch?v=s0XqhUFhOjo)
[^7]: [How to hire and develop juniors in an AI-first product org](https://www.youtube.com/watch?v=E92tSzhMqkw)
[^8]: [𝕏 post by @lennysan](https://x.com/lennysan/status/2090177314630029679)