A marketer who learned to ship software, or a builder who already knew how to market. Either way, I do both halves of the job.
These days I call myself an AI marketing technologist, the shortest honest way to say I can market the thing and build the thing.
Six years deep in Web3 now, mostly across one multi-brand ecosystem (BitAngels, Tokenize Conference, Transform Group), running the content and quietly building the AI tools that produce it.
But it didn't start there. My career didn't arrive fully formed; it emerged, one layer building on the last. I'd rather make a thing and learn by breaking it than read about it forever.
My first real work in tech was growing communities across blockchain ecosystems, ICP initiatives, Omnity, Bitcoin Runes, and the usual sprawl of Telegram groups, Discord servers, and Twitter Spaces. That's where I learned the thing that still shapes everything: people don't adopt technology because of the whitepaper. They adopt it because of each other.
Running communities showed me what made people get it, and what made their eyes glaze over. So I started making the content myself: threads, campaigns, contests, and brand narratives around Bitcoin, Runes, and cross-chain infrastructure. The rule never changed: take the complicated thing, make it simple, sound like a human.
Once you understand a space well enough to market it, you start seeing the gaps: the partnership that should exist, the bridge that's missing, the audience nobody's reaching. I spent a stretch connecting those dots.
My first real builds were automations and chatbots, n8n and Zapier workflows for Omnity, content-intake systems, and an AI chatbot system for a healthcare clinic in Australia that took the manual response load off the staff. That clinic work pulled my building out of crypto and into the real world.
Then it kept growing. I designed and built whole sites from scratch (icphubsg.com in Squarespace and custom CSS), then moved into production React and Supabase, shipping tools end to end like Spotlight, a speaker platform I built as a Sessionize alternative. Somewhere in there the builder stopped being a side character.
These days the marketing and the building aren't separate anymore, they're the same job. I build the tools that make the content: Skein, an internal toolkit of 15 SEO tools on a single Cloudflare + Supabase + Claude engine; AI content systems running social across the brands; and the n8n automations holding it all together. Market the thing, then build the thing that markets the thing.
A speaker-management platform I built from scratch, a Sessionize alternative for a conference I work with. Designed it, built it, security-audited it, then pitched it internally.
Site, content, and event work for a Web3 & AI conference series, speaker campaigns, event-day content, and the SEO nobody sees: JSON-LD, Open Graph, structured data.
Ongoing web and content for the world's premier blockchain investor network, managing and rebuilding the site, plus the structured-data and CSS plumbing underneath.
The plumbing and the production line: n8n workflows, intake systems, and an AI content engine running social across four brands plus a founder.
My flagship: an internal toolkit of 15 SEO tools on one Cloudflare + Supabase + Claude engine, with a SERP-grounded research-then-generate pipeline.
React
Next.js
Tailwind
Supabase
Vercel
Cloudflare
Workers
Deno
GitHub
n8n
Make
Zapier
IFTTT
GoHighLevel
Claude
Gemini
ChatGPT
Antigravity
HeyGen
Higgsfield
Luma
Opus
WordPress
Elementor
Squarespace
Canva
Airtable
Notion
Analytics
Slack
Don't take my word for it, here's the actual output. Social across a founder's personal brand, BitAngels, and Tokenize, produced by the AI content system I designed.
A lot of the work happens in rooms, not docs. Here's where I've been on the ground. Tap any to read my take on it.
AI content, reverse-engineered. Every piece ships with the prompt or skill behind it: the exact, repeatable setup I use to produce on-brand graphics and carousels at scale. Plug it into your own stack.
Most people are either the marketer or the builder. The thing I slowly realized is that I'm both, and the seam between those two halves is exactly where I'm most useful. I can write the launch post and build the app it's launching. Grow the community and ship the tool it needs.
I'm a learner first, and it shows up in odd places. I've spent real time studying Armenian, both Eastern and Western dialects, for the love of breaking something complicated into pieces small enough to actually learn. Same instinct behind the rest: show up, keep going, let the compounding do its thing.
Most teams have to pick: someone who can position and grow it, or someone who can actually ship it. I'm both halves in one person: fewer hand-offs, less lost in translation, more things that genuinely go live.
Positioning, go-to-market, and AI-assisted content systems that keep multiple brands shipping consistently.
Fast, custom websites and n8n automations that quietly handle the busywork so you don't have to.
Practical AI, assistants, chatbots, and internal tools wired into the real work, like the one floating in the corner of this page.
When I'm not marketing or building, I'm somewhere new, collecting languages, food, and the small details that never make the guidebooks. Field notes from the road below.
Everyone told us to do Shanghai.
Read full post →
For as long as I’ve been traveling, it’s always been some version of me on my own terms. Solo trips where I’d wake up with no plan and follow whatever looked…
Read full post →