Building a Technical Marketing Portfolio

Originally, I was going to coded a static HTML resume. An NPC move. A simple site with a simple case study.

But if I want to escape mediocrity and position myself as an in-house Technical Marketing Strategist, I can’t just tell people what I do. I have to build a system that proves it. I need to document the why.

Over the last five years, I’ve operated in the trenches of DTC e-commerce. But the game is chaotic, and entropy is a constant. My ad accounts for TOANDME and PRIMEXMPLE vanished. The data proof went poof. It’s like losing a corrupted save file after a 100-hour playthrough. All the dashboard proof of the infrastructure I built…gone.

When you hit a glitch like this, you have two choices: stagnate, or find a new channel.

I had to audit the inventory I had left. I asked myself: Is it realistic to apply for a Growth Marketing position without medium or enterprise-level case studies? Probably not. But I still have the reps. I still have the skill tree unlocked.

Take my recent project, Kevora. It was a highly specific product: a bionic-hand massager mimicking a therapist's grip. I walked away from it without the granular Shopify data, but I kept the media assets. More importantly, I kept the mental framework. I know exactly how I leveraged AI, structured the email flows, tested social ads, and pivoted to find new audiences. It generated $0 to $10k in a month. It wasn't an enterprise-level flex, but it proved I can engineer cash flow from scratch.

I know how to think. I know how to learn. And with the extension of AI, my ability to adapt has become hyper-lethal.

So, I’m making a strategic pivot. I am aiming for a Technical Marketing Specialist role. Very few people actually love the backend work. It’s complex, it’s messy, and it demands systems thinking. That means there is a massive demand.

The Level 3 Portfolio System

I initially started vibe-coding a static HTML site. I quickly realized that was a Level 1 approach. If employers want to see the technicality I bring to the table, the portfolio is the case study. I archived the static code. I am rebuilding this with a clean, functional aesthetic to show the absolute fullness of my strength.

Here is the technical architecture we are deploying:

1. The Foundation (Next.js & Sanity CMS) We are moving from a static front to a dynamic Next.js application, integrated with Sanity for the CMS backend. I’ve killed the pop-up modal layouts for blog posts. Instead, I’m building dynamic routes (/app/blog/[slug]/page.tsx). This is a non-negotiable for proper backlinking and SEO structure.

2. The Automation Engine (n8n & AI Integration) I am setting up a VPS to run n8n, ensuring the automation hub operates even when my local machine is asleep. This is where we plug in the AI. We are testing Claude Design for automated email and website asset creation, and exploring the LumaLabs API to see if an internal product can further efficientize the workflow. The goal is a fully automated pipeline that generates weekly content for my blog and newsletter.

3. The Capture Pipeline (Loops.so & GTM) Traffic is a vanity metric. It means nothing if you don't constrain the chaos and capture the data. I’ve integrated loops.so at the end of the blog layout. This CTA prompts readers to join my inner circle. To track this, Google Tag Manager (GTM) is being deployed across the board.

The Final Synthesis: The icing on the cake is the webhook architecture. We are pointing the webhook from the Sanity backend to a Zapier or n8n URL.

The command is simple: Every time a document with type 'post' is published, send the JSON data to this endpoint.

Our automation hub captures that data, runs it through a custom AI prompt to extract the highest-leverage ideas, and drafts a short-form newsletter in our capture tool, pushing the audience back to the full post.

This isn't just a resume. It’s a self-sustaining ecosystem.

More documentation to follow.