I walked into this problem ready to vibe code it. Seven platforms, seven data sources, one very chaotic 15-minute standup every morning. My instinct was Lovable, something fast, something I could spin up in an afternoon.
Claude Cowork had a different idea.
It told me it knew I liked to vibe code. And then it told me, gently but clearly, that a Google Sheet would be easier for the whole team to use. No app to log into. Already in everyone’s workflow. And by the way — have I heard of Google Apps Script?
I had not.
What followed was one of the most useful builds I have done in a long time. Not because the technology was impressive (though it was), but because the AI wasn’t just executing my request. It was advising me. It steered me toward the right tool before writing a single line of code. Then it wrote the code, built the diagnostic layer, and helped me find three data issues I would not have caught on my own.
One of those catches led to a conversation with Propensity’s customer success team. They are making platform changes based on what we surfaced. That is not something I expected when I started a Google Sheet.
The full case study lives here on the site if you want all the technical detail. The LinkedIn article is the thought leadership version — what this actually means for how we think about AI in modern marketing ops.
Read the full article on LinkedIn →
If you have been waiting to build the thing you keep manually reconciling every week, this one is for you. What would your war room track?
Comments are closed