[stephensonsco]

This is a seriously fertile area where you get to "define the new interface".

It's a big problem though, since few buyers know they want those things. Around 95% of customers come into it with "give me the transcripts" and discover over time they want these other things too (some graphical, some technical). They just didn't know it was available.

New GUIs and data representations is a big part of it. Getting accuracy and scale in place is a big part. Building awareness and distribution of what's possible now is another big part.

Re: JSON Error; We fixed that doc link error you saw (it was pointing in the wrong place since we _just_ updated it).

The real docs link is: https://brain.deepgram.com/docs

[btown]

Tableau (and the general business analytics space) have done a good job at reframing the problem as: "don't think about what you want as a leader at a company; instead, democratize data access so your team can decide what it wants, and pay for democratization not for your own features." See for instance: https://www.forbes.com/sites/briansolomon/2016/05/04/how-tab...

Arguably Elastic is a success story about bridging the worlds of an API-first technical stack with a democratized non-technical analytics framework. And they started by just powering excellent search, and building value-add layers over time. But they built into a then-vacuum of API offerings, whereas there are many other (potentially inferior, but well-funded) speech-to-text APIs. I'll be avidly following you guys as you navigate the space, and hopefully you're able to find some good "hooks" or uniquely-easy-to-roll-out integration stories that strike a balance between focus on technical excellence and driving awareness in a super-linear way.