So, imagine you're in a crunch, and need to make a quarterly report for your board. Due to nebulous reasons, the only person who is available to do this is an intern with a PhD in statistics, but who started at your company two days ago and doesn't even know how the your office coffee machine turns on.

Due to other nebulous reasons, you have a choice between giving that intern:

Realistically, you will give the intern the PowerBI account. Sure, it would still be nice if they had your company's tribal knowledge, but they will more likely succeed with the task and make less errors if they drag and drop measures in PowerBI rather than blindly writing raw SQL.

The problem is, most Text-to-SQL solutions are the 500-page manual case — they give the an extremely smart but nil-experience agent a ton of documentation of dubious quality, tell it to do its best, and then whether it does a good job is anyone's guess.

We wanted to change that, so we'd like to introduce the 

If you'd like to try it out, you can check out more information in the 

, or reach out to us, and we will help you get set up. Semantic Layer is currently in beta, and we are still ironing over some rough edges, so we'd love to hear what you think about it.

Thanks for reading, and have a great week!

Wobby changelog

Introducing Semantic Layer