The lesson
In a competitor comparison, give the switcher a low-risk first step so they can adopt you for one job before committing to a full migration.
The hero reads "A Neon alternative for branching at scale" and offers two paths: run production on Xata, or adopt it for branching while keeping production where it is. It also gives a Markdown version of the comparison for readers weighing options with an AI agent. "Why choose Xata over Neon" makes four cards (no fixed per-branch fee, scale-to-zero, Cloud/BYOC/self-hosted, vanilla PostgreSQL), and "How Xata compares with Neon" runs a feature table with written cells such as "No fixed per-branch fee" against "$1.50 per extra branch-month." A "Calculate Your Savings" tool with sliders for builders, agents, branch lifespan and data size shows itemized monthly costs for both vendors at published list rates. The page then lays out "Adopt Xata for branching. Move production later." in three steps and ends with "Evaluate Xata with your Neon workload."
Don't copy the vendor lock-in row about Neon's acquisition or the Markdown-for-AI-agents link unless your claims are current and checkable. Keep the order: one-line positioning with a partial-adoption path, four reasons, a table with written cells, a cost calculator, then staged adoption steps.
Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.