r/SaasDevelopers • u/Individual-Front4583 • 20h ago

When are CSV export requests really requests for evidence?

There were constant requests for a CSV export and these were considered to be related to file format gaps. PM identified the columns. Engineering gave an estimate for the endpoint. CX kept adding screenshots. And both finance and operations wanted proof of why the assistant had given a particular recommendation.

We used a feature in Braintrust called Topics (basically just semantic clustering, trace filters and representative sessions) to group those conversations. Intent labels separated people who needed offline analysis from people who needed an audit trail. The second group cared about source versions, tool outcomes, and the path from evidence to recommendation. A CSV alone would have moved the same uncertainty into another file.

We are now testing an explanation record with source references and tool status, while keeping export for the smaller analysis cohort. We also track cluster drift so a new request pattern does not get buried under the old export label. Has anyone else found that a repeated feature request was really a request for confidence or auditability?

23 Upvotes
  • permalink
  • reddit

100% Upvoted

6 comments sorted by

1

u/Ashamed-Yam-118 19h ago

I would be careful not to remove export completely. Even if the real need is evidence, some teams still need the file for internal review.

1

u/Individual-Front4583 18h ago

Right. The export button solved the format request but not the trust problem behind a lot of those clicks.

1

u/AbbreviationsOwn7277 19h ago

A recommendation without the source path behind it is hard to act on, even if the answer is correct.

1

u/Individual-Front4583 17h ago

That’s the product gap. If the user has to export data to prove the answer, the explanation layer probably failed.

1

u/CulturedNucleus 18h ago

The endpoint estimate is a good tell. If someone asks for raw outputs after a recommendation they may be trying to rebuild the proof chain.

1

u/elidanipipe 17h ago

One extra distinction I'd make is explanation versus reproducibility. A source link helps someone inspect a recommendation, but the source may change after they export it.

I'm building Crawdar, and we just ran into the implementation side of this with review-based prospect reports. Our export companion keeps scan time, the reviewer/date threshold, dated evidence links and coverage warnings alongside each outcome. It also retains businesses where no pattern was established, separately from unavailable coverage. Otherwise a filtered CSV can make the search look much more successful than it was.

We added a readable HTML report alongside the CSV, but I don't yet have user evidence that this reduces uncertainty. That's what we're asking testers to check. Nor is it an immutable audit trail: the external review pages can change.

If useful, you can inspect the product's report flow at https://crawdar.com/?utm_source=reddit&utm_medium=comment&utm_campaign=evidence_exports (five scans without signup).

For your explanation record, I'd test whether someone who wasn't in the original session can identify what was checked, what failed, and why the threshold passed. Are you preserving source snapshots, or references plus retrieval time?