Solo founder here, same pattern on a smaller scale. I can draft a launch post or a support reply in seconds, but verifying every link, version number, and pricing claim before it goes out eats more time than writing ever did.
Same pattern in my classroom. I used to spend grading time rewriting feedback comments; now I spend it verifying that the lesson plans the tool generated actually cite real standards and not fabricated ones. Net time saved is maybe 20 percent, not the 70 the vendor promised.
Same thing happened with student essays. I used to spend prep time finding sources to recommend, now I spend it verifying that the three citations in a six-paragraph essay actually exist and say what the student claims. Curious whether anyone in a non-academic setting has found a workflow that catches fabricated quotes faster than just opening each link.
Same pattern on our analytics team of 6. The model drafts a stakeholder memo with five plausible-looking metric references in 30 seconds, and I spend 40 minutes confirming each one actually matches what's in dbt. Net win is real but smaller than the demo suggests, and the failure mode is silent which is what worries me most.
Same pattern here, except the citation checking expanded to include checking that the cited case actually says what the draft claims it says. About 40% of the time it doesn't, or the quote is from a dissent. Drafting time dropped maybe 60%, verification time roughly doubled, so net win is smaller than partners think.
Same pattern in our lab. Three of us used to spend a week each on lit reviews; now drafting takes a day but verifying every citation still eats most of the week because the models hallucinate plausible DOIs and reassign findings to the wrong authors. Has anyone found a workflow that catches the subtle ones, like a real paper cited for a claim it doesn't actually make?
Same pattern in our lab. Three of us spend most of a manuscript week now verifying that the model didn't hallucinate a citation or misattribute a finding, which used to be a fifteen minute task at the end. Has anyone found a tool that actually checks claim-to-source fidelity, not just whether the DOI resolves?
Same pattern on our team of six. I used to spend half my PR time writing the code and half waiting on review, now I spend most of it verifying that the AI's cited functions and line numbers actually exist before anyone else looks at it. Genuinely unsure if that's a better use of a junior or just a different flavor of grunt work.
Same pattern on my team of nine. Drafting a PR description or RFC went from an hour to ten minutes, but I now spend forty minutes verifying that the linked functions, line numbers, and "as documented in X" claims actually exist. Net win is maybe 20%, nowhere near the 5x the vendor deck promised.
Same in my classroom but inverted: drafting feedback on 90 essays takes minutes now, verifying the model didn't hallucinate a quote from the student's actual paper takes the whole prep period. Net time saved is maybe 20%, not the 80% the vendor pitch promised.
Same on our team of 6. I spend more time verifying that the cited functions/lines actually exist than I do writing patches, and half my PR comments now are "this reference is hallucinated." Is anyone actually getting useful mileage out of the cite-checker tools, or do you still end up doing it by hand?
Same shift on the design side. Critique used to be about whether the mock was any good; now half the time is spent verifying that the "research insights" the PM pasted in actually trace back to the interview transcripts.
Same pattern hit our design team. The Figma to spec handoff used to take two days of writing, now it's two days of verifying that the AI didn't invent a component name or reference a deprecated token from our old library.
Saw this firsthand with a comms team I helped last quarter. Drafting dropped from two days to twenty minutes, but the senior editor now spends her afternoons opening footnotes one by one because the model confidently cited a 2019 report that doesn't exist. The net time saved is real but maybe half what leadership thinks it is.
Same pattern in my 9th grade class. The kids generate essays fine but spend twice as long verifying the sources the model invented, and half still turn in fabricated citations because checking is boring and writing felt done.
Same pattern on my team. PR drafts went from 40 minutes to 10, but reviewers now spend most of their time verifying that the linked issues, prior PRs, and doc references the model cited actually say what the description claims they say. Net win is real but smaller than the drafting speedup suggested.
Same pattern across three of my clients now. The drafts land in an hour but I spend half a day per deliverable opening every cited source to confirm it actually says what the draft claims, and roughly one in five doesn't. Started billing citation verification as a separate line item because clients kept assuming it was instant.
Same pattern at two of my clients last quarter. We cut first-draft time by maybe 70% but legal review actually got slower because every claim now needs a source trace, and the model hallucinates citations confidently enough that the reviewers stopped trusting the bibliography wholesale. Anyone found tooling that surfaces the actual passage behind a citation inline, or are people still doing this in spreadsheets.
Same pattern showed up in my 9th grade English class once I let students use AI for first drafts. The drafting time collapsed but I now spend most of my feedback window verifying that the quotes they cite actually appear in the text, and roughly a third don't. Has anyone found a workflow where the tool flags its own fabricated citations before the student submits?
Citation checking being the new bottleneck assumes the citations are the only thing worth verifying. On the three PRs I reviewed yesterday, the references were fine and the control flow was quietly wrong in two of them. Moving the bottleneck from drafting to citations isn't a win, it's a tell that reviewers stopped reading the logic.