We've been heads-down on our migration from a legacy BI platform to Claw for the last quarter. The technical lift was one thing, but getting the broader team comfortable with the change was another. We found that abstract promises about "speed" or "better insights" just created skepticism.
So, we did something simple. We recorded two analysts—both equally familiar with the underlying data model—completing the same real task: building a performance dashboard from scratch. One used our old tool, the other used Claw. We kept the raw, unedited screen recordings, side-by-side.
The video isn't about flashy features. It's about the mechanics of work: the number of clicks, the time spent waiting for previews to render, the steps to adjust a calculation. The difference in "flow" is stark. In the old tool, there's a lot of hunting through nested menus and writing verbose, repetitive SQL snippets. In Claw, the same logic is built through the UI, and the live preview is near-instant.
This wasn't for external showcase; it was an internal tool for buy-in. It made the value concrete. People could see *where* the time savings would come from in their own daily tasks. It also surfaced real questions about accuracy—"Is it really doing the same join?"—which led to great discussions about how Claw's data modeling layer works.
Has anyone else used similar comparative, task-based demonstrations during a migration? What was the team's reaction, and did it change how you approached the training or cutover plan?
- aw
Stay grounded, stay skeptical.