By all means, trying to write nowadays seems useless. If the goal was to scale, the two platforms that would help the most for career and business would be LinkedIn and YouTube—the algorithms pretty much guarantee it.

You go on LinkedIn and people unapologetically seem fine either A) copy-pasting a thought rewritten in a new way, or B) outright copying the person who used AI, who probably stole the idea from someone else online anyway. I'm not against the concept of stealing—all artists steal. But in order to strengthen my critical thinking skills and truly display my strengths, I think very long blog posts will help. I'll have the ability to refine and craft unique perspectives in my field of marketing science, and honestly, that's more valuable to me than engagement metrics.

So here's what I'm doing instead:

Intelligence Briefings

This is where I break down marketing papers I've read and show how I was able—or could be able—to use them for actual campaigns. Whether it's a new theorem in multi-mix modeling or a forecasting paper to improve PMAX advertising, the goal isn't to be groundbreaking. It's to document applied research. How does academic theory translate into a working system? What happens when you try to implement something that only exists in a whitepaper?

Not meant to be revolutionary, but it forces me to think critically about what actually works versus what sounds good in a case study.

System Blueprints

Not everyone plays by the same set of rules when it comes to scaling. The goal here is to create blueprints for marketing systems that would normally be built by external consulting companies like Deloitte or Accenture.

As a freelancer and tech consultant, I get hired to build these systems because of my wide variety of skills. For example: How do you build first-party cookies that can track user activity and send it to Google Ads without breaking HIPAA? Or how do you build a data-driven PMAX engine for a Shopify brand with an AOV of $70-80? These are the types of problems that companies either pay six figures for or fumble through themselves.

I'm documenting them instead. Step-by-step. The technical architecture, the implementation gotchas, the actual code if it's relevant. Not abstract frameworks—actual blueprints you can follow.

If you find any of this useful, reach out to me on LinkedIn. I don't expect many people to read this, so I'll be more than happy to respond.