2
0 Comments

I'm building a "flight recorder" for business workflows. Is this a real problem

I've been a longtime reader and could really use the community's wisdom on a B2B SaaS tool I'm building.

We've all seen amazing free tools like Microsoft Clarity. They're fantastic for watching session replays to understand how anonymous visitors browse a public website or e-commerce store. They help answer the question: "Why are people dropping off from our homepage?"

But my obsession is with a different, more specific problem I saw in my last job: the internal "black box."

We could see the outcome of an employee's work (an insurance claim was processed, a complex support ticket was closed), but we could never see how they did it. We were blind to the actual workflow inside our core applications.

This got me thinking: what if there was a "flight recorder" specifically for these high-stakes, internal workflows? A tool that lets a manager or QA lead replay how a specific employee handled a specific case ID or ticket number.

The goal isn't to monitor website traffic; it's to solve internal business problems:

Audit Trail: Have an immutable record for compliance when a regulator asks why a certain decision was made.

Training: Capture the exact workflow of your star performers and use it to train new hires effectively.

Process Improvement: Pinpoint where employees get stuck or make repeated errors in the workflow and fix the process itself.

So, my question to you all is:

Does this distinction between public website analytics (Clarity) and internal workflow intelligence make sense?

For those managing teams, do you have this internal visibility gap? If so, how do you currently handle training or quality assurance for complex digital tasks?

What's the biggest reason a tool like this would fail? Is it employee privacy concerns, a lack of perceived need, or something else?

I'm trying to make sure I'm solving a distinct and valuable problem that free tools like Clarity aren't built for.

Thanks for any and all feedback!

on June 27, 2025