The Thinker
and the Maker
Why the best strategists now need to do both
years I spent in advertising before I built my first product.
The deck is not the product
Strategy decks are beautiful. They're persuasive, polished, and completely inert. They sit in inboxes. They get forwarded once. They don't DO anything. The best thinking in the world is worthless if it stays in a PDF.
The gap between idea and URL
There used to be a long chain between a strategic insight and something real. Research to brief to concept to build to launch. That chain is collapsing. The strategist who can go from observation to working prototype in a night has an unfair advantage over the one who writes a 40-page recommendation.
The gap between the deck and the product
I founded Burst Communications and discovered something uncomfortable: I was great at selling the vision but had no idea how to build the thing. Strategy decks don't ship products. That gap between the pitch and the prototype is where most ideas go to die. Founding taught me that the person who can do both, think it and make it, has an unfair advantage over the person who can only do one.
The waterfall is over
The old process was brief, concept, pitch, approval, build, launch. That's a six-month relay race for something nobody's tested. The new process is observation, prototype, test, iterate. You can go from noticing a problem to having a working solution in a single evening. The competitive advantage isn't budget or headcount anymore. It's clock speed.
hours to build a working pub guide. From idea to live URL. That's not a flex. That's what's possible when thinking and making happen in the same brain.
products I've shipped since September 2025. Without writing a single line of code.
AI didn't replace me. It promoted me.
I went from being the person who recommends things to the person who makes things. AI tools like Claude Code didn't take my job. They gave me a bigger one. The thinking still matters. But now I can prove the thinking works by building it.
Learn to build, not to code
There's an important distinction between learning to code and learning to build. Coding is syntax. Building is decision-making. Which tool for which problem. When to use a database versus a spreadsheet. When to ship versus when to polish. AI handles the syntax. You handle the judgement. The skill isn't writing JavaScript. It's knowing what to make and when it's done.
The prototype is the new deck
When I have a strategic point to make, I don't write a brief anymore. I build a working version of the idea and send the URL. The conversation changes completely when you can say "here, try it" instead of "imagine if."
Version one should embarrass you
If your first version is polished, you waited too long to ship. The point is to get it out, learn from real usage, and improve. Every product I've built started ugly. The discipline is shipping before it's ready and improving in public. Perfection is the enemy of proof.
The things that didn't ship
Not everything I built was good. Some products launched to silence. Some ideas turned out to be solutions looking for problems. One project I spent three weeks on got zero users. That's the point. Building teaches you what strategy decks never could. Real failure, not hypothetical risk analysis. Every product that flopped sharpened the instinct for the next one.
The client meeting that changes
I used to walk into rooms with a 60-slide deck and a recommendation. Now I walk in with a URL and say try it. The energy in the room shifts completely. Skepticism turns to curiosity. Hypothetical turns to tangible. Feedback goes from "interesting concept" to "can we change the header?" That's a fundamentally different conversation. That's the conversation builders get to have.
Building changes how you collaborate
People assume building solo means working alone. It's the opposite. When you can build, every conversation becomes more productive. Engineers explain constraints and you understand them. Designers share references and you can implement them. Product managers describe features and you can prototype them overnight. Building doesn't replace collaboration. It removes the translation layer.
Nobody asked me to build any of this
Every product I've shipped started with a problem I had personally. Not a client brief. Not a market gap analysis. A genuine itch. Building for yourself first is the most honest form of strategy because you can't lie to yourself about whether it's useful.
to midnight. The hours when everything gets built. Constraints make better work.
The feedback loop changes everything
When you build the thing yourself, feedback becomes instant. You don't wait for a research debrief or a post-campaign report. You watch real people use it. You see what they click, what they ignore, where they get stuck. The learning is immediate and the iteration is same-day.
Builders are replacing recommenders
The industry is splitting into two camps. People who advise on what should be built, and people who build it. The second group is winning because they can show proof, not just promise. The most hireable person in the room is no longer the best presenter. It's the one with a portfolio of shipped work.
Agencies used to separate thinking and doing into different departments. The future is one person who does both.
The strategist's new toolkit
Taste. That's the toolkit. AI can generate anything, which means the hard part is no longer making things. It's deciding what's worth making, how it should feel, and when to stop. Strategy was always about choices. Now you get to make those choices AND see them through.
in Web3 revenue I generated at MediaMonks. Not from a strategy deck. From understanding culture, building prototypes, and proving concepts worked before asking for budget. Thinking and making, together.
The portfolio is the new CV
Nobody reads CVs anymore. They Google you. They look at what you've shipped. A live URL that works is worth more than a line on a resume. When you can show 20+ products instead of describing 20+ projects, the conversation changes.
You don't need permission to build
The biggest lesson from shipping 20+ products: nobody gave me a brief. Nobody approved a budget. Nobody said go. You don't need permission. You need a laptop, an idea, and three hours after your kid goes to bed. The barrier was never technical. It was psychological.
The external proof
I published a book on Web3 and emerging technology through BCS in 2024. I was named a BIMA 100 Tech Pioneer. Not for being a coder. For understanding how technology, culture, and strategy intersect. For building things that proved the thinking worked. External recognition matters because it tells you the building isn't just a hobby. It's a practice that others can see and validate.
What changes when you ship
Your relationship with ideas changes permanently. You stop falling in love with concepts and start falling in love with execution. You learn that version one should embarrass you and version two should surprise you. You discover that the best feedback comes from a live URL, not a research debrief.
The agency that builds
The agencies that will win the next decade aren't the ones with the best strategists or the best creatives. They're the ones where strategy and execution live in the same person or the same room. Where the time between insight and prototype is hours, not months. Where the output isn't a recommendation. It's a working product. The agencies that can't build will consult. The ones that can build will lead.
Strategy is a verb now. The best strategists don't just think about what should exist. They make it exist.
I stopped presenting ideas and started sending URLs. Everything changed.
