Frezpo turns one client brief into a matched Google Ads and landing page strategy pack — ad architecture, landing page strategy, and design tokens — generated together so the ad’s promise and the page’s headline never drift apart.
This repository has no source code and never will. It exists so the project has a real, indexed page on GitHub. The product runs at frezpo.com — this is a pointer, not a codebase. If you cloned this expecting to run something, there is nothing here to run.
Message match — whether the ad’s promise survives intact to the landing page hero — is usually checked after the fact. The ad gets written by one person or agency, the landing page by another, often weeks apart, and match only gets audited once both artifacts already exist. By the time anyone notices they’ve drifted, the budget is already spent on clicks that bounced.
Frezpo treats message match as a production property instead of a review property. It authors the ad and the landing page from the same brief in the same run, so they agree with each other before anyone builds either one.
A 7-node sequential LangGraph pipeline takes one input — a client brief — and produces the full pack:
Each node reads only the distilled output of the node immediately before it — never the raw brief, never the full run history. That constraint is deliberate: it keeps token cost flat as the pipeline gets deeper and stops prompt drift from accumulating over a long agent chain, which is the usual failure mode once a sequential pipeline grows past three or four steps.
Try it without an account: frezpo.com/stream-demo.
Frezpo publishes three of its internal skills as machine-readable SKILL.md files, each listed with a sha256 in a discovery index any agent can fetch and verify before using:
Index: frezpo.com/.well-known/agent-skills/index.json. Human-facing hub: frezpo.com/skills. Also see llms.txt.
Özer Yılmaztekin, Principal Engineer, 15+ years, İzmir, Türkiye. Built and maintained solo.