We've built a tool to reduce meetings, how do we validate it?

Hi Indie Hackers!
My co-founder and I built a platform that we think can reduce meetings. We based it on our experience in the industry and the many hours spent in meetings; we've created something that we find value in ourselves and use every day already, but it's been a struggle to get customers on board.

A bit of background, the software is an automated audio-centric asynchronous communications platform focused on simplicity. Basically, it lets people schedule, write and listen to (or read) status updates. In particular, it helps with coordinating distributed workforces, and we strongly feel that it reduces redundant meetings while making any remaining ones much more productive. Ideally, it's most useful in large companies with multiple teams where it could fill in gaps with existing tools, but we've had a chicken-and-egg problem where folks want to see other customers having success with it before trying us out.

At this point we're considering piloting with startups or maybe specific department or team types in companies as a niche (open to suggestions!). Are there any other ideas for how we can try validating this?