.svg)
The team that designed your product app is usually the wrong team to build your marketing website. Product design optimizes for unconstrained UI inside a logged-in app. A marketing site lives or dies on page speed, SEO, AI visibility, CMS scale, and conversion structure. Those are a different craft, and asking one team to do both is how you end up with a beautiful site that ranks nowhere and converts no one.
This is not a knock on product designers. The best ones are exceptional at what they do. But "great at product" and "great at a public site that has to be found and has to sell" are two separate skill sets that happen to look similar from the outside.
Why does a founder trust the product agency with the website in the first place?
Because the work looks adjacent. You already have a relationship. They know your brand, they know your team, and they just shipped an app you love. When they say "we can do the website too," it feels efficient. One vendor, one aesthetic, no new onboarding.
We watched this play out with a funded B2B SaaS. Their product design agency, excellent at the app, wanted the marketing site too and was pushing a Framer build to go with it. The founder had a physical reaction to the idea. A past project with the same pattern had gone badly, and he could feel the same movie starting again. He was right to trust that instinct.
The efficiency is real on paper. The problem is that a marketing site has jobs a product app never has to worry about.
What does a marketing site have to do that a product app doesn't?
A logged-in app answers to one metric: can the user complete the task. Nobody Googles their way into your dashboard. Nobody asks ChatGPT to recommend your settings page.
A marketing site answers to a longer list:
- It has to load fast enough to pass Core Web Vitals, because Google and users both punish slow pages.
- It has to be crawlable and structured so search engines and AI answer engines can read it.
- It has to carry schema markup so machines understand what each page is.
- It has to scale as a content system, not a handful of hand-built screens.
- It has to convert cold visitors who owe you nothing, with copy and layout built around a hypothesis.
Product design training points in a different direction. It rewards custom interaction, rich motion, and pixel control inside a controlled environment. Point that skill set at a public site and the same instincts that make a great app quietly work against you.
How do product design instincts wreck a marketing site?
Four failure modes show up again and again.
Heavy animation kills your Core Web Vitals. Scroll-jacking, parallax, and full-screen video reels look incredible in a portfolio. On a live site they inflate load time, block the main thread, and tank the metrics Google uses for ranking. We have seen sites where the hero animation alone pushed Largest Contentful Paint into failing territory. A visitor on a mid-tier phone waits, then leaves.
CMS scale gets ignored. Product designers build screens. Marketing sites need systems. If your blog, your case studies, and your comparison pages are hand-coded one at a time, you cannot publish at the volume modern search and AEO demand. Content is the engine now. On one migration we bulk-loaded 223 schema articles, 110,000 words, into Webflow with Python and the Webflow API. You cannot do that on a site built as a set of static art pieces.
No schema means no AI visibility. Answer engines lean on structured data to understand and cite a page. Skip it and you are invisible to the tools your buyers increasingly use. For one healthcare client, adding structured data moved their AI visibility almost overnight. That lever does not exist if nobody built the foundation. If you want the reasoning, we wrote it up in why schema is the foundation of AEO.
No conversion structure means no leads. A pretty page is not a converting page. Conversion comes from a deliberate structure: a liftable value proposition above the fold, proof, objection handling, and a clear next step, tested against real behavior. Product aesthetics without CRO thinking produce sites that win design awards and lose pipeline.
That last point is where the "Framer build" detail matters. The tool is fine. But when the pitch is "we'll make it look like the app in Framer," the conversation is about visuals, not about the jobs the site actually has to do. If you want the platform tradeoffs specifically, we covered them in Framer vs Webflow.
Isn't this just a Webflow agency talking its own book?
Fair question, so here is the honest version. Yes, we build on Webflow, and yes, we want the work. But the split we are describing is real regardless of who you hire, and we will tell you when a product agency is the right call.
If you need an internal tool, a complex logged-in flow, or a design system for your app, a product design agency is very likely your best partner. That is their craft and they will beat us at it. There are also genuine limits to what a marketing platform can do, which we lay out plainly in what Webflow cannot do.
The mistake is treating the marketing site as an extension of the product work. It is a different discipline with different success metrics. The proof is in what happens when you get it right. A merge-two-domains migration we ran took a site from 600 to 25,000 monthly visits. A site rebuilt around answers and conversion, not just aesthetics, drove real outcomes: dYdX saw +3,722% organic growth after a 600-plus post migration, and a homepage A/B program for a healthcare client lifted final signup completions 144%. None of that comes from a prettier hero.
What should a founder do instead?
Split the work by the job, not by the relationship.
Keep your product design agency close for the product. For the marketing site, hire the team whose craft is performance, findability, and conversion, and who treats content as infrastructure. If they lead with animation and aesthetics before they mention Core Web Vitals, crawlability, schema, or conversion tests, that is your signal.
Ask three questions before you sign anyone up for the site. Can you show me the Core Web Vitals on sites you have shipped. How will content scale in the CMS as we publish. How will this site get found and cited by AI, and how will you test that it converts. A product agency will often struggle with all three, not because they are bad, but because it was never their job.
Where to go from here
If you inherited a beautiful site that ranks nowhere and converts no one, the fix is rarely a redesign. It is usually structure: speed, schema, a real CMS, and a conversion hypothesis you can test. That is the work we do. If you want a straight read on whether your current site is built for the jobs it actually has, our migration and web team is happy to take a look and tell you honestly.
Frequently asked questions
Can a product design agency build a good marketing website?
Sometimes, but it is the exception. The skills overlap on the surface and diverge underneath. Product design optimizes unconstrained UI in a logged-in app; a marketing site has to pass Core Web Vitals, be crawlable, carry schema, scale as a CMS, and convert cold traffic. Ask for evidence on those specific jobs before you assume the overlap holds.
Why do heavy animations hurt SEO?
Because they slow the page down. Scroll-jacking, parallax, and autoplay video inflate load time and block the main thread, which pushes Largest Contentful Paint and Interaction to Next Paint into failing ranges. Google uses Core Web Vitals as a ranking input, and slow pages lose both rankings and visitors who bounce before the animation finishes.
Does my marketing site really need schema markup?
Yes, if you want to be found by AI. Answer engines like ChatGPT, Perplexity, and Google's AI Overviews rely on structured data to understand and cite a page. Adding schema moved one healthcare client's AI visibility almost overnight. Sites built as static design pieces usually ship without it, which makes them invisible to the tools buyers now use. Our AEO guide walks through the setup.
Should I fire my product design agency then?
No. Keep them for the product, where they are strong. The point is to match the craft to the job. Use a product design team for your app and interfaces, and a team built around performance, SEO, AEO, and conversion for your public site.
.avif)
