Evolution of ARR:
1. Subscription revenue for the last 12 months
2. Projected subscription revenue for the next 12 months
3. Multiply your best month by 12
4. Multiply your best week by 52
5. Give out huge discounts but still count it as full revenue, do #4 or #5 to arrive at the final ARR, whichever is the highest. Celebrate like you did #1
@javitoshi@0xhirugohan There are quite a few guardrails you can put in place that restricts the actions that LLMs can take when interfacing with your DB.
The best way we've found to do this at Fluent is by introducing a semantic layer.
@deedydas Would disagree that this is a fair measure of text-to-SQL - Spider 2.0 is more about testing GUI control/how data agents can work across a number of tasks. Wouldn't use it to evaluate accuracy in this context.
5/5 The evolution of the BI role should prioritise high-impact work: spotting growth trends, focusing on data quality, and empowering teams to self-serve.
#Data team's impact will exponentially increase as a result of the shift too.
Read an interesting Reddit thread this week on the evolution of the BI analyst role - it's not getting any easier for them, even with all the BI tools on offer.
Feels like it's time the role evolved from data 'firefighting' to more insight enablement and governance.
A thread ⬇️
4/5 Here’s where AI can actually help. The idea isn’t to replace BI analysts but to automate repetitive tasks so they can focus on real insights. With natural language tools, non-tech teams could answer their own questions, and turn BI from a bottleneck to an enabler.
“I can't answer this” is Fluent’s most popular response.
In our early days, we lost a 9-month deal in 15 minutes, after a senior stakeholder got a few wrong answers.
Now, Fluent flags missing info so admins can intervene. Sometimes, “no” is the smartest answer AI can give.