Most marketing teams build the product video first and then try to figure out social later. That's the order that creates the "can we just crop this to 9x16" conversation, and by that point you're already working backwards. Here's what usually happens. The team puts real effort into a product video for the website. It's well produced, clearly explains the product, and does exactly what it needs to do on a landing page. Then someone on the team says "we should use this on social too" and the scramble starts. Crop it vertical, trim it to 30 seconds, maybe add captions. The issue is that no amount of reformatting changes the underlying structure of the video. A product video is built to explain something to a person who already showed up wanting to learn. The pacing assumes intent. The opening assumes context. Those assumptions are baked into every edit, and they don't disappear when you change the aspect ratio. What I've started doing with teams is planning the social version during the product video process, not after it. You're already in the same creative world, working with the same footage and the same messaging. The cost of building a social cut alongside the product video is significantly lower than coming back to it weeks later and trying to reverse engineer something that was never designed for a feed. Think of it as two outputs from one production window instead of one video you try to stretch into two jobs.

So true.

Gelée — Replo Build (Concept)

A self-initiated concept: redesigned a fictional collagen-jelly-stick CPG brand into a tight, 2-product Replo store.

I wanted to test how far a page builder like Replo could go without leaning on generic templates or default sections — so I mapped out a full 7-section flow (hero, product education, reviews, shop, comparison, trust/FAQ, close) and built each section from scratch, studying category leaders like Jolie and Grüns for what actually converts before writing a single line of copy.

What went into the build: — Custom PDP with tiered pricing, subscribe-vs-one-time toggle, and a benefit checklist pulled from category research — Accordion FAQ restructured from a flat list into scannable categories — Comparison module (Gelée vs. traditional powders/pills) built as a responsive table, not a static image — No-plugin interactions throughout — hover states, accordion behavior, and quantity selectors handled natively in Replo instead of embedded scripts

Concept project, not client work yet but to built to sharpen my Replo skill set and show how I think about DTC wellness UX end to end.