We want to better understand what people are TRULY trying to accomplish when it comes to AI so we can make our products better. We know it’s broad and there are so many different lanes, but if you had to pick one of the 2 options below, which one would you choose?

Ask most teams how many drafts exist for their last significant piece of AI-assisted work and you'll usually get a shrug. Somewhere between three and eight, probably, spread across different tools, different conversations, different people's individual sessions. Nobody has a clean record of which version is actually current, what changed between iterations, or why one direction got chosen over another that also looked reasonable at the time. This is the version control problem, and it's one of the least discussed costs of fast AI-assisted iteration. When content generation was slow, there weren't many versions to track because there wasn't time to produce many. Now that generation is nearly free, teams routinely produce far more versions than they used to, and almost nobody has built a system for managing that volume. The result is a growing category of time loss that happens quietly, in the confusion of figuring out where things actually stand. ------------- Context ------------- Version confusion isn't a new problem in professional work. But it used to be naturally bounded, because producing a new version required real effort, which meant versions were relatively few and the history of how a piece of work evolved was usually still fresh enough in someone's memory to reconstruct if needed. AI has removed that natural bound. A single person working on a proposal might generate six or seven distinct drafts in an afternoon, exploring different angles, adjusting tone, trying different structures. Multiply that across a team where several people are independently iterating on related pieces of work, and the total version count for even a single project can climb into the dozens within days. Most of this iteration happens inside individual AI tool conversations that aren't connected to any shared system, which means the history lives in scattered chat threads rather than anywhere a team member could reliably find it later. The cost shows up in specific, recurring moments: someone asks which version is final and nobody's sure. Two people unknowingly work from different drafts and produce conflicting output. A decision gets revisited because the reasoning behind an earlier direction wasn't recorded anywhere and has to be reconstructed from memory, imperfectly. None of these moments individually costs much time. Across a project, across a team, across a year, they add up to a meaningful and largely invisible drain.