Frezpo is one campaign strategy pipeline, one engineer, no agency behind it.

I'm Özer Yılmaztekin, and I built Frezpo because I kept watching campaign strategy fall apart at the handoff between the ad and the page. You give Frezpo one client brief; a 7-node pipeline turns it into ad architecture, landing page strategy and design tokens, authored together, so the promise the ad makes is still standing when someone builds the page. No agency, no team. I designed, built and deployed the whole thing myself.

Why this exists

Message match — the ad's promise surviving all the way to the landing page headline — is usually treated as a review step. Someone checks the page against the ad after both are already built, often by different people, sometimes weeks apart. By the time anyone notices the drift, the campaign has already spent budget on clicks that bounced.

Frezpo treats message match as a production property instead of a review property. The ad hooks, the landing page hero, the conversion path and the design tokens all come out of the same brief in the same pipeline run, authored to agree with each other before anyone builds anything. There is no separate ad person and separate landing page person to lose the thread between them.

Who builds it

Özer Yılmaztekin is a Principal Engineer & Technical Customer Success Manager with 15+ years of hands-on frontend and DevOps experience, based in İzmir, Türkiye. The work below is the checkable part — named employers, measured outcomes.

Build pipeline, Akbank

Refactored a hybrid React Native project into a standalone AAR package, cutting build times from 50 minutes to 10 — an 80% reduction — and removing the Java team's Node.js dependency.

Release quality, Appcircle

Built AI-integrated reporting tooling over Jenkins and internal APIs, driving weekly bug tickets from 26 down to 8 through feature/bug ratio analysis.

Render performance, eBay

Cut first render time on a high-traffic commerce platform from 1.5s to 600ms by attacking virtual-DOM CPU load in SSR and moving the critical path to Node.js/EJS.

Delivery at scale, Microsoft & Innovance

Standardised React and React Native build and release strategy on Azure across 15 development teams, through UAT and production.

Across those years the employers have been Appcircle, Akbank, Microsoft, eBay, n11, Takasbank — working in React, TypeScript, Node.js and Azure. Frezpo is his first product built and shipped entirely solo: a Next.js front end, Python and LangGraph orchestration, Supabase persistence and Polar billing, deployed end to end by one person.

How Frezpo is built

Frezpo runs as a 7-node sequential LangGraph pipeline — Marketing Strategist, Search Intent Mapper, Conversion Architect, Hook Generator, Copywriter, UX Strategist and Frontend Developer — each simulating a role on a marketing team. The nodes carry strict context isolation: each one reads only the distilled output of the node before it, never the raw brief or the full conversation history. That holds token cost flat as the pipeline gets deeper and stops prompt drift creeping in over a long agent chain.