Analytics at the speed of code" — a category claim that requires the visitor to already know what agentic BI means and why it matters. The subheadline adds "AI-native BI platform" and "modern data teams" without naming the specific person this page is built to convert or the specific problem they walked in with. The result is that a data engineer migrating off Looker, an analytics engineer evaluating dbt-native tooling, and a data team lead trying to eliminate SQL tickets all land on the same page and none of them see their situation named in the first five seconds. The page has at least three distinct buyers — developers who want BI-as-code, business users who want AI-powered answers, and team leads who want to kill the Looker bill — and it tries to serve all three simultaneously, which means it converts none of them cleanly. Pick the first buyer this page is built to close, name their situation in the hero, and let the other segments find their path through secondary navigation or dedicated landing pages.

"No more Looker pricing" appears as a single line in a feature grid near the bottom, after the user has already scrolled through agentic AI explanations, a developer workflow section, a code-shipping section, and an integration section. But for any team currently paying Looker's per-seat licensing, that line is the reason to switch — it's not a feature, it's the financial case. The testimonial from Yu Ishikawa at Ubie ("Traditional BI tools sit on top of your warehouse and create chaos. Lightdash's semantic layer scales without breaking") and the fake Slack thread mocking "We ran out of Viewer Licenses" both gesture at the same pain, but neither appears until the user is already deep into the page. Move the pricing pain — specifically the Looker seat cost comparison — into the hero or the first scroll position, because that's the objection that makes the buyer stop evaluating and start converting.

The top half sells "Agentic BI" — AI builds your dashboards, agents answer questions, the future is automated. The bottom half sells "BI-as-code" — version control, CI/CD, CLI tools, preview environments, developer workflows. These are not the same product promise. Agentic BI says the AI does the work so your team doesn't have to. BI-as-code says your developers get better tools to do the work themselves. A buyer who came for the first promise will read the second half and wonder if the product is actually for them. The page needs one primary axis — either Lightdash is the tool where AI builds and operates your analytics layer, or it's the developer-first BI platform where you ship analytics like code. Both are defensible positions. Running them in parallel on the same page means neither one lands.

vity" — is the closest thing on the page to a concrete time-to-value claim, but it appears at the very bottom, after the CTA, as a visual graphic attached to a "Book a call" prompt. This is the wrong placement and the wrong frame. The buyer's most practical objection to switching from Looker or Tableau is migration cost and ramp time, and the page never addresses it directly until the user has already decided whether to act. Pull the migration story — specifically "Day 3: Migration Magic" with a link to the migration docs — into the section immediately following the hero, where it can neutralize the switching-cost objection before the buyer has built it up. The current placement treats migration as an onboarding detail; it's actually the deal-breaker filter.