if nobody else has the same problem I'm just gonna hack together some scripts, call it a day, and charge them like a contractor.

if the problem is more generalizable then it's worth hunkering down and building something more robust, and charging them like a vendor.

at any rate, part of their problem is people are leaving before they get a chance to talk, and not enough people are talking to them. bit of a catch-22 for them. why not see if the well runs deep?

If you don't mind me asking, when you watch sessions, do you have a better way to prioritize the session you watch than just picking at random?

For example, do you have some way to pull out a bunch of session groups from the data automatically so you only have to watch one session in the group to know what the problems were for all of the sessions in that group?

Just to wrap this back, I suspect there's a way to process these sessions really quickly to figure out what the user trends are in ~real-time. This way you can do the same thing you're already doing, but with much more context.

Adding another two channels, with these channels being: 1. A weighted map of stats for all of the sessions at once. Weighted by heuristics you choose or by good defaults. 2. Reports detailing all the natural problem groups the sessions fall into. With breadcrumb trails available for deep-dives.

Most importantly I think there's a way to do this without having to rely on llms at all; by modeling the whole thing as a set of graph problems.

If this sounds reasonable to you lmk.

Have a good one!