[tomnipotent]

> You tell us what you want the destination to look like

Implicit mapping between SQL to target is great, but how does the SQL author know what SQL to write in the first place?

I've done no shortage of integrations like this, and there is no avoiding reading the target SaaS documentation to know what their schema looks like so I can shape data accordingly. Without that step, I can't even start writing SQL.

[tejasmanohar]

Not implicit but - declarative! Our goal is to provide enough context in our docs, app (e.g. autocomplete, automatic schema discovery, etc.), and resources to guide users through this and then recipes on top for common workflows!

We do a lot of validation upfront (at both the schema & data layer), and I think it's still early days there... this is a big opportunity IMO. Great callout.

We find people start with a simple SQL model + sync and then bounce back and forth and edit their queries as they explore our columns.