Read all the latest musings and news from the Llamas.
In our targeted marketplace, specifically, folks examining trading behavior, results, transactions, and routing, there are two fundamental data tracts.
(1) The trades themselves, and their ancillary touchpoints (quotes, execution benchmarks, etc.).
(2) And process-driven documentation about anything to do with (1).
In the last 10 years, in working with my fully distributed and remote team of engineers, we've leaned heavily on collaborative software for delivering on (1), but in the past, we built specific tools for our clients to handle the same sort of work, in managing (1). It felt weird. We even tried to engage with them in our own collaborative environments, but over time, other factors made this difficult (acquisitions are not 100% spreadsheet affairs).
We've used Flowdock, Slack, Teams, and now Twist and it worked great for ourselves, but the marketplace itself was still clinging to software packages specific to their "thing" (this is industry X version of otherwise ubiquitous functionality), at least up until the last year or so. C19 accelerated the trend, but it was already coming. Our biggest clients have told us this.
Now, at TradeLlama, we focus entirely on (1) for our proprietary efforts, and then we integrate with whatever collaborative tools our clients are leveraging (usually Teams or Slack).
It's a great trend in the marketplace, especially in FinTech, where our clients use these tools. I could spend a lot of time documenting the benefits of this shift, but the main thing is providing an audit trail on information flow, decision trees (and context) around such information, and in aggregate, appropriate dissemination and retrieval of corporate activity.
We even have a Llama bot, called Yama, that gives a CCO the ability to ask, in a thread, "Yama what did Neil Visnapuu trade last month?", and have a cluster map rendered, as well as a link to the appropriate visualizations. (The return set in this case would be crickets chirping).
While most business users of these collaboration tools don't realize this, it's essentially a command-line interface, these frameworks (hence why engineers love them, at least those of us not weaned on Visual Studio and the like). The 10 threads a CCO might be working through on any given day in Teams, for example, reminds me of how most dev screens are a cascade of terminal windows.
It's a big change coming, how you deliver value to clients (in our case, our findings on their trading activity), via integration with these tools. And it is great because service providers can focus on (and charge for) that which they're good at.
If you want to learn more about Yama, please reach out.
"Yama, why do your human handlers prefer Twist?" ...