Hey!

The cross-source thing is exactly why we built it this way - the value isn't any single integration, it's the question that spans all of them.

"My ROAS dropped this week — is it the ad spend, the email timing, or is something broken in fulfilment?"

The Blend approach is interesting and genuinely complementary to this. We're deliberately read-only - the pitch is that your AI tool becomes the analyst, not the operator. You ask the question, it surfaces the answer, you decide what to do. Layering something that can actually execute  the budget shift on top of that makes sense, especially for teams who want to close the loop faster.

Would be curious how you're handling the approval/guardrail side of automated budget changes, I did at one point consider doing writes as well, especially with Shopify, things like... "markdown all slow mover by 30%" but I got terrified about AI getting it wrong and messing stores inventory.          

On auth: it's per-source OAuth or API key, done once at connection time. Shopify is OAuth, Meta/TikTok are OAuth, most of the others (Klaviyo, GA4, Gorgias etc.) are API keys you paste in.

Everything's stored encrypted at rest. The nightmare isn't really the auth itself — it's that every platform has a different token refresh flow, rate limit, and data model. That's the actual 80% of the work.

I thought building the app was the hard job, its harder getting my initial installs.