π€ We've built real-time martech stacks. Then bottlenecked them with human-time decisions.
Every marketer knows this pain. You've got real-time personalization, identity resolution, clean rooms, orchestration engines, and a dozen other sophisticated tools. Your martech stack is a marvel of modern engineering. But how do you actually use it? Through educated guesses, periodic reviews, and 'strategic adjustments.'
π’ It's like steering an ocean liner with janky controls in fog.
The truth is that we're running complex, real-time marketing infrastructure with human decision-making that's anything but real-time. We make slow decisions with incomplete data, wait weeks/months to see results, then make more slow decisions.
π We're the bottleneck in our own operation.
The shift isn't just about adding AI - it's about fundamentally changing how we operate. Moving from:
β‘οΈ Human-in-critical-path β Human-in-loop
β‘οΈ Quarterly optimization β Continuous learning
β‘οΈ Segmentation guesswork β Scale experimentation
β‘οΈ Perfect control β Directional correctness
Here's what this means practically:
π― Focus on the unsexy: Invest heavily in high-quality customer signals, context and the infra to support it
π― Define the experience we want for our customers declaratively - what we want instead of imperatively (step-by-step how to do it)
π― Let the model understand our customers deeply and execute the experience for them
π― Monitor and shape strategy vs micromanaging execution The question is whether we're ready to let go of the illusion of control and let the model navigate. π€
#martech #AI #marketing
the collapse is not needed. merging authentication and authorization is not trivial.
authentication is binary (you are who you say you are).
authorization is often bespoke (discounts, account types, team entitlements, how to handle updates to payment methods and ownership etc.).
@kimmonismus the fork happens when a model realizes it needs to make a tool (human?) call.
that determination: i've hit a wall, is not a trivial problem to solve.
@samuel_spitz prob not. the cost complexity of reconciliation/testing is too much.
R&D is a very different motion from operations. unless you want to be a just tapping away at the slot machine, then yes, 10, 20..... who's counting
@icanvardar no it's fine, in fact doing better than ever. not saying i like it or anything. but linkedin is objectively doing fine as a business.
yea, its a totally different vibe than x.
tbh, i can't say X is not slop either. just depends on what flavor of slop works for you.
@MatthewBerman jury's out. models will get better, but they won't get cheaper (not this gen anyways). plus, a ton of token burn happens on vertical domain nuance, and at some point, it will just make more sense to call an api
@archiexzzz perhaps this will age poorly, but consumer vibe coding has negative margins. it will never be a business (although a good acquisition strategy)
@catboosted makes sense. but i would bet vibe coding is negative value, coz negative margins. if anything, companies like @databricks stand to make the most from vibe coding in the enterprise.