The world's best AI Analytics platform, where anyone can ask questions and build with trusted data. Create a free account 👉https://xitter.cf/t.co/ejDVlOl1RP
your data
Joined October 2019
- Tweets1.2K
- Following322
- Followers7.2K
- Likes1.1K
Pinned Tweet
Today we announced that Greenflash is joining Hex.
Excited to welcome the Greenflash team, and have them join us on building the best platform for data work in the AI era.
Hear more from our CEO, @barrald → hex.tech/blog/hex-greenflash…
Building is the easy part in today's age but the real question is whether you want to own one long term.
Ask yourself (and your team) these few questions first:
👉 Is the workflow truly unique to your business?
👉 Will you have engineering time to keep investing after the prototype?
👉 Are you comfortable with part of your data team becoming the team that maintains it?
If most of those answers are no, the parts worth owning are your metric definitions, business logic, and the institutional knowledge that makes an agent useful. Not all the infrastructure around it.
New on the blog from Nick Pasquinzo - link in the comments!
Every data team has a story about this one. What's the most common ad hoc request you get? đź‘€
50%Can you pull this quick?
25%Why don’t these match?
25%Can i get this in excel?
0%Is this dashboard right?
4 votes • Final results"Should I replace my BI tool with an agent?"
Not exactly.
Here are 5 🔑 takeaways from our new guide that explain why:
1. Analytics has split in two: AI tools nobody governs, and BI tools nobody uses.
2. A two-week wait for an answer is now a 30-second expectation.
3. The new BI test: can more people self-serve, can you trust the answer, and does it work where your team already works?
4. Good answers depend on context that stays current.
5. Bolting an agent onto your BI tool just means maintaining logic in two places.
Grab the guide from the comments 👇
Huge congrats to our friends at @modal on their $750M raise. Proud to be part of the journey 🚀
Today we're announcing that Modal has crossed $1B in annualized run rate, as well as raised a $750M Series D at a $15.75B valuation, led by @Accel.
Since our Series C, usage has tripled and we’ve grown more than 15x year-over-year.
We are deeply grateful to the developers and companies building on Modal. There's still so much more to build, and we can't think of a better time to be building software.
T-minus 2 weeks!
One day in SF with the sharpest data people we know, then a party in the Mint’s vaults. (Yes, the haunted ones 👀).
Pack your bags and your chargers, we'll see you on October 27th at Prompt!
For last minute tix, email us at [email protected] 🤝
ICYMI: @claudeai Dashboards connect directly to Hex.
With this connection, you can ask your data a question in Claude, get an answer, and send it to Hex, while leveraging all of our rich context, collaboration, and governance capabilities.
Read more: claude.com/resources/article…
Our very own @daviddbwilson just wrote this 🔥 blog on his learnings about using eval-driven development when building Quick Edits in Hex.
Check it out!
Ten months ago, Account 360 felt like the future.
Our customer team built it so anyone could check on any account, any time. Then the way the team worked with data changed, and the bar for "good" moved with it.
Every new question became another tab, and the answers often showed up after the call they were needed for. Now the team asks Threads directly, and all the data behind Account 360 is what powers those answers.
Nisha Dwivedi on what changed, and what she'd tell any customer team building something similar 👇
🤖 Made with AI
Hex retweeted
Ran four @hexanalytics searches live in a call yesterday, sending data nearly instantly while we're discussing something is wildly powerful. So glad our data team set us up with Hex. (This is a Hex fan account now.)
Hex retweeted
The @hexanalytics agent is divine. Crazy leverage compared to the old world of hand rolling SQL. Bravo to the team.
Spark was everywhere. @databricks was making less than $1M a year.
@pwendell, co-founder and VP of Engineering at Databricks, says the company had a few rough years where the open source project was taking off and the business wasn't.
So they built something you could only get from Databricks. A managed service is, by definition, something you can't open source. And by the time it existed, Spark had already done the hard part of getting people to care.
Open source wasn't the product. It was the top of the funnel.
Full episode of Friends of Data on YouTube, link in the comments 👇