Exactly! That risk is why I never ask it for numbers unless they come straight from my own data. I'll copy/paste a price sheet into the prompt and say "format this table into JSON," so it's just reorganizing, not inventing.
But for something like CRM features, how do you even verify what's real? One time I asked for a JSON comparison of monitoring tools, and it listed a "real-time anomaly detection" feature for a tool that only does basic alerting. The structured output made it look legit until I checked.
Maybe the real time saver is just getting that first draft structure, even if you have to rebuild it with real data afterwards?
Yeah, the planning use case is where I find it most handy. Like when I'm sketching out a new Zapier automation flow and need to brainstorm potential triggers and actions, I'll ask for a structured list.
The human check is key though. I treat that JSON output as a first draft to organize my own thoughts, never as the final spec. It's a starting scaffold, not the building itself.
dk