← Reddit

Our website redesign won a preference test because of a hero animation Claude built

Reddit · redlikecherries · July 24, 2026
A two-person team conducted a preference test on their redesigned homepage by recording users thinking aloud while reviewing both versions. Users predominantly chose the redesign due to its animated hero component, though testing also revealed that users ignored body copy, were confused by terminology like "artifacts," and preferred combining elements from both versions rather than choosing a single winner. The team launched a hybrid version incorporating the new animation and revised messaging based on the feedback, which they analyzed using Claude's transcription and analysis capabilities.

Detailed Analysis

A two-person team's account of using Claude to run and analyze a website preference test offers a granular look at how AI agents are being folded into everyday product and design workflows, not just as code generators but as research assistants. The non-technical founder describes a process where Claude transcribed recorded user sessions, synthesized qualitative feedback across three participants, and published a side-by-side comparison of the old and new homepage designs. The most striking outcome wasn't a straightforward win for the redesign—it was a nuanced set of findings: users skimmed headlines rather than body copy, gravitated to an animated hero element (also built with Claude, via the Fable tool), stumbled over internal jargon like "artifacts," and spontaneously suggested a hybrid of both designs that the team ultimately shipped instead of either original version.

What makes this case notable is the division of labor it illustrates: a person with no engineering background directed the qualitative research process end-to-end, while an AI agent handled the labor-intensive parts—transcription, thematic analysis, and publishing a readable report—that would normally require either specialized UX research skills or significant time investment. This reflects a broader shift in how small teams and solo founders are using conversational AI agents not as autocomplete for code, but as a substitute for entire job functions like research analyst or copywriter. The detail about Claude changing "artifacts" to "Publish your agent's work" based on user confusion shows the agent being used for interpretive, judgment-based work—translating raw user sentiment into concrete product decisions—rather than purely mechanical tasks.

The example also underscores a recurring theme in Anthropic's positioning of Claude: agentic workflows that chain together multiple capabilities (video/animation generation, transcription, qualitative synthesis, and web publishing) in service of a single business outcome. Rather than using Claude as a single-turn assistant, the team treated it as a persistent collaborator across the entire redesign lifecycle—from building the hero animation to analyzing why that animation resonated with test subjects. This mirrors Anthropic's broader push toward Claude as an "agent" capable of multi-step, tool-using workflows rather than a chatbot confined to text generation, a positioning reinforced by recent product releases like Claude's coding and computer-use capabilities.

More broadly, the anecdote fits into a growing body of user-reported case studies where AI models are credited with democratizing skills once gated behind specialized expertise—UX research, video production, technical writing—for non-technical operators running lean teams. It also implicitly validates a design philosophy increasingly common in AI-adjacent product circles: rapid, cheap, AI-assisted user testing that surfaces qualitative insights (like jargon confusion or emotional resonance with an animation) that pure A/B testing or analytics dashboards might miss entirely. As more solo founders and small teams share similar workflows publicly, these stories serve as informal case studies that shape perceptions of what AI agents like Claude are capable of in real-world, non-technical business contexts, reinforcing the narrative that large language models are becoming general-purpose collaborators across disciplines rather than narrow coding tools.

Read original article →