By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.

An exclusive inside look at GPT-5

In this episode, I share my hands-on experience with OpenAI’s GPT-5, the company’s new frontier model.

Claire Vohost

Aug 7, 202540mWatch on YouTube ↗

Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.

CHAPTERS

Jump to publisher timestamps

Chapter summaries

GPT-5’s “engineer-built” personality and who it’s for
Claire shares her first impressions of GPT-5 as a highly technical model optimized for engineering workflows. She frames the episode around a practical question: where GPT-5 fits alongside other models as a specialized teammate rather than a universal upgrade.
- •GPT-5 feels “built by engineers for engineers” in both style and capabilities
- •Strengths: coding, refactoring, technical implementation thinking
- •Potential tradeoff: less business/stakeholder-friendly than GPT-4.1/o3
- •Episode roadmap: product/PRD workflows, coding, ChatGPT Canvas, personal tests
Context: Claire’s model stack and why she tests models like a “team”
She explains her day-to-day model usage across ChatPRD and coding tools, emphasizing deliberate model selection by task. This sets up her evaluation mindset: not “is it better,” but “where does it belong in the workflow.”
- •Uses multiple providers/models (OpenAI, Claude, Gemini) depending on task
- •ChatPRD has extensive prompt/model A/B testing and satisfaction targets
- •Evaluation criteria: output quality, user fit, cost later
- •Models as teammates with distinct personalities and strengths
Switching ChatPRD to GPT-5: side-by-side document generation setup
Claire moves directly into her primary benchmark: PRD/document generation inside ChatPRD. She describes using LaunchDarkly AI Configs to swap models and compare GPT-4.1 vs GPT-5 under identical system prompts and context.
- •ChatPRD’s core workflow: AI-assisted PRDs and feature brainstorming
- •LaunchDarkly AI Configs used for fast model switching in local/production
- •Comparison uses same prompts/context to isolate model behavior differences
- •Early GPT-5 quirk: defaults to markdown bullets and dev-speak
Business lens vs execution lens: how GPT-4.1 and GPT-5 ask questions
The first divergence appears in the questioning and framing. GPT-4.1 pushes on personas, goals, and metrics, while GPT-5 moves quickly toward concrete features and implementation detail—useful for building, riskier for product discovery.
- •GPT-4.1: business impact discovery (who/why, metrics, personas, goals)
- •GPT-5: solution-first behavior (what/how, user stories, numbers, build specs)
- •Implication for PMs: GPT-5 may skip “why” exploration and jump to execution
- •Model behavior reflects broader “coding tool wars” and engineering focus
PRD artifacts and tone: GPT-5’s code-like fingerprints and verbosity
Claire opens the generated PRDs and highlights stylistic artifacts that signal GPT-5’s training bias, like code-block comments and dense structure. She discusses the tradeoff between detail for engineers versus readability for stakeholders.
- •GPT-5 may insert code-adjacent artifacts even in prose docs
- •GPT-5 produces longer, denser, more detailed PRDs overall
- •More detail helps execution; too much can obscure the core message for alignment
- •Personas/use cases: GPT-5 becomes feature-centric vs GPT-4.1 goal-centric
Where GPT-5 clearly wins: functional requirements, UX specificity, tech considerations
The strongest difference shows up in the “how it works” sections. GPT-5 generates notably stronger functional requirements and technical considerations, making it compelling for specs, engineering handoff, and documentation-heavy teams.
- •Functional requirements: more complete, prioritized, and edge-case aware
- •UX descriptions: more concrete prose that can improve downstream prototyping
- •Technical considerations: detailed, engineer-native language and analysis
- •Possible workflow split: PMs may not need to author deep technical sections
From PRDs to prototypes: how model detail changes v0 outputs
Claire tests whether the different PRDs lead to better prototypes. She finds GPT-4.1 yields cleaner, more colorful visuals, while GPT-5’s verbosity produces richer component ideas—even if the aesthetic is less vibrant by default.
- •Prototype quality depends on the PRD as an input artifact
- •GPT-4.1 prototype: simpler, clearer, more colorful/pleasant visual style
- •GPT-5 prototype: more components/upsell mechanics to choose from (abundance)
- •Insight: GPT-5’s detail can improve ideation breadth for prototyping tools
Homepage critique test: surprising differences in “mean vs nice” feedback
Claire compares how each model critiques her homepage. GPT-4.1 is more blunt and harsh, while GPT-5 is more diplomatic—even when prompted to be more critical—highlighting differences in steerability and feedback style.
- •GPT-4.1 delivers sharper, more negative critique (“not up to standard”)
- •GPT-5 gives balanced feedback and a gentler tone by default
- •Re-prompting shows limits/differences in how easily each model is tuned
- •Takeaway: app builders must test promptability and tone control per model
OpenAI ecosystem advantage: API design and developer tooling
Before deeper coding demos, Claire credits OpenAI’s platform strengths beyond raw model quality. She emphasizes API ergonomics, primitives, and controls as decisive factors for building LLM-backed software.
- •OpenAI’s edge: API design, developer tools, ecosystem primitives
- •Model choice in products often hinges on integration simplicity and controls
- •Notes improvements around tool calling, reasoning, and parameters
- •Encourages developers to review the updated documentation
GPT-5 as a coding assistant: fast, thoughtful, and extremely tool-hungry
In Cursor and real shipping work, Claire finds GPT-5 strong at producing and refactoring production code. The standout behavioral trait is aggressive tool usage—often hitting tool-call limits—plus a strong preference for bullet-point communication.
- •Becomes her daily driver while shipping a major feature
- •Strengths: speed, code quality, refactoring, “thoughtful” engineering partner
- •Behavior: heavy tool calling (can hit Cursor tool-call limits)
- •Communication style: persistent bullet points; may feel inefficient at times
GPT-5 inside ChatGPT: Canvas prototyping and front-end design taste
Switching to ChatGPT, Claire tests GPT-5 Thinking with Canvas to generate a blog design matching her brand. She’s impressed by its polish and taste, though she flags recurring contrast/readability issues in generated UI styling.
- •GPT-5 vs GPT-5 Thinking options; uses Thinking for design/prototyping
- •Canvas workflow: reference image + prompt → code/UI output
- •Perceived improvement: more “classy” and polished design than past defaults
- •Issue: text/background contrast problems; likely CSS/model behavior to fix
Personal benchmark: bathroom remodel planning and spatial reasoning
Claire applies GPT-5 to a real consumer workflow: planning a bathroom remodel with layout constraints and visual outputs. She reports improved interpretation of spatial instructions compared with earlier experiences.
- •Uses AI for layout feasibility, visualization, and contractor communication
- •GPT-5 better at left/right/back-wall interpretation and room layout prompts
- •Requires some re-dos but produces more accurate spatial results
- •Positions spatial awareness as a differentiator across both code and images
GPT-5 vs GPT-4o for interior design visualization: paint matching and mockups
In a side-by-side test, GPT-5 generates paint recommendations with names and codes, then produces more faithful mockups to her tile/paint placement instructions. Compared to GPT-4 outputs, GPT-5’s renderings look more coherent and instruction-following.
- •Uploads tile photos; asks for Benjamin Moore paint matches
- •GPT-5 returns specific color names and paint codes; crisp, readable text
- •Mockups follow instructions more closely (half-wall tile, floor, wall materials)
- •GPT-4 comparison appears less sensical and less aligned to constraints
Final takeaways: choose GPT-5 for engineering execution, use others for stakeholder clarity
Claire concludes that GPT-5 is exceptional for engineering tasks: coding, technical writing, and detailed specs. For business storytelling and stakeholder alignment, GPT-4.1/4o/o3 may still be preferable, while GPT-5 meaningfully upgrades ChatGPT’s Canvas and image workflows.
- •Core identity: “for engineers, by engineers” (technical thinker/writer/coder)
- •PM impact: delivers more what/how than who/why—choose based on artifact purpose
- •Coding: few complaints beyond bullet-point style and tool-call intensity
- •ChatGPT upgrades: stronger Canvas/front-end design + improved image spatial awareness

Publisher timestamps

Get more out of YouTube videos.

Read along on your phone, search it beside the video, or ask your favorite AI app what was said.