The subheadline calls MotherDuck "the cloud data warehouse built for answers," but the body copy pivots to architecture: per-user tenancy, isolated DuckDB instances, five compute tiers named Pulse through Giga, Hypertenancy, vertical scaling models. The visitor who arrived because they want fast answers to data questions is now reading a distributed systems explainer. The page is selling the mechanism when the buyer came for the outcome. The fix is structural: the body sections need to stay in the "answers" frame — what the user gets, how fast, from what data — and push the architecture detail to a dedicated technical docs page or a secondary section below the proof. Right now the hero makes a promise the body never keeps.

Software engineers with a big data problem, data scientists doing data engineering, and data engineers with slow pipelines are named in the same sentence, as if they share a problem. They don't — they have different pain, different success criteria, and different reasons to switch. A data engineer evaluating whether to replace a brittle pipeline needs different proof than a software engineer trying to add customer-facing analytics to a product. The page gives all three the same CTA, the same feature list, and the same architecture diagram. The move is to either pick the one buyer this page is built to convert first and build the page around their specific situation, or create distinct entry paths — a nav split, a segmentation question, or separate landing pages — so each buyer lands in a page that speaks to them, not a page that speaks at everyone.

" There is no named first moment — no "connect your first data source in 5 minutes," no "run your first query in under a minute," no concrete picture of what the trial actually delivers. The five compute tier names (Pulse, Standard, Jumbo, Mega, Giga) appear in the body copy without any guidance on which one a new user starts with or why. For a buyer who is already evaluating Snowflake or BigQuery, the absence of a clear time-to-value signal is a reason to default to the incumbent they already understand. Add a single sentence below the CTA that names the specific first thing the user will do and how long it takes — this is the highest-trust sentence the page is currently missing.

A logo without attribution is decoration. The comparison pages on the domain (DuckDB vs. Postgres, multi-tenant analytics, modern data warehouse use cases) suggest MotherDuck has enough technical depth to earn credibility with a skeptical buyer — but that credibility never surfaces on the homepage. Move at least one named customer with a specific outcome above the first scroll: not a logo, a sentence. "Together.ai runs customer-facing analytics on MotherDuck at sub-second latency across X users" is the kind of sentence that makes a data engineer stop scrolling.