LYTMS
Your sharpest claim — sub-second cold starts — appears once, then disappears while four other promises take over.
“AI infrastructure that developers love”
Pull one of the concrete differentiators from your subheadline up into the headline itself. Sub-second cold starts or the Python-decorator angle would both do more work than 'developers love' — your own testimonials show those are the things people actually remember.
Get the ship-ready rewrite →Your headline names the category and adds a vanity sentiment. 'Developers love' is something AWS could print on a t-shirt. The sentence directly below it — sub-second cold starts, instant autoscaling, feels local — is your actual wedge,...
Not five scoring areas. Five questions, asked in sequence. The page is judged on how many it answers before the visitor gives up.
The page has no single differentiation claim it commits to.
▸ Read the full takeCollapseThe hero says "AI infrastructure that developers love," the feature section says "designed to help AI teams deploy faster," the platform section says "build robust, scalable data applications," and the footer CTA says "ship your first app in minutes." Each of these is a different promise — developer affinity, speed, robustness, ease of onboarding — and none of them is the same promise. The buyer who lands here can't answer the question "why Modal instead of Replicate or RunPod" because the page never answers it. Modal's actual defensible claim is buried in the subheadline ("sub-second cold starts, 100x faster than Docker") and never repeated or defended anywhere else on the page. Pick one claim — the cold start and speed story is the sharpest and most falsifiable — and make every section on the page a proof point for that one claim.
The testimonials are doing the wrong job.
▸ Read the full takeCollapseThe page has more than twenty pieces of social proof, which is a significant asset, but almost all of them are individual engineers expressing enthusiasm ("brings me joy," "magical," "sooo nice") rather than named teams describing a specific outcome at scale. The four named testimonials at the top — Brian Ichter, Mike Cohen, Aakash Sabharwal, Anton Osika — are the strongest signals on the page, but they're formatted identically to the Twitter ticker below them, so the buyer's eye treats them as the same category of evidence. The buyer evaluating Modal against Lambda Labs or Anyscale isn't looking for joy; they're looking for a team like theirs that ran a workload like theirs and got a specific result. Separate the four named testimonials into a dedicated proof section above the product grid, give each one a one-line outcome summary ("reduced inference latency from X to Y," "scaled to 10,000 containers without ops overhead"), and cut the Twitter ticker to five of the most outcome-specific quotes.
“Inference, Training, Sandboxes, Batch, and Notebooks are listed in a flat grid under 'Powering any ML workload' with identical visual treatment. No product is marked as primary, recommended, or most popular. No copy guides the buyer toward a starting point based on their job-to-be-done.”
“AI infrastructure that developers love”
“Multiple testimonials reference Lambda and Docker by name ('If you are still using AWS Lambda instead of @modal you're not moving fast enough'; 'DX is sooo nice compared to Docker, Cloud Run, Lambda'). The page itself never makes this comparison explicitly — no comparison table, no head-to-head claim, no 'vs Lambda' fr”
Every finding named, quoted, and paired with the rewrite — that’s how Lytms reads a page. Run it on your own site to see all of yours, free.
Hero value, conversion-killing sentences, cliché density, awareness fit, buyer-language gap, competitive differentiation.
Call-to-action clarity, visual weight, offer strength, form friction, CTA-to-page match.
A live feed of what the category is moving toward, with a drafted response for the moves worth responding to.
Pick one competitor on Pro. Same scoring this page is held to. Same-day alert when they ship a homepage change.
Mine reviews, transcripts, support, social. Ranked, attributed, matched against the homepage.
Accept, edit, ship. An action queue tied to a CMS or copied straight to clipboard.
Lytms reads any B2B homepage the same way — verdict, five scores, every line that costs the visit. Free to run. Full report and drafted rewrites on Pro.
The page presents five distinct products — Inference, Training, Sandboxes, Batch, Notebooks — without telling the buyer which one to start with or which one is the core.
A buyer who arrived from a search for "serverless GPU inference" lands on a page that immediately asks them to also consider training, sandboxes, batch jobs, and notebooks. This is a navigation problem disguised as a product problem: the page is structured as a product catalog, not a conversion surface. The buyer who came for inference doesn't need to know about Notebooks on the first visit; they need to know that Modal solves their inference problem better than the alternative they're currently using. Restructure the product section to lead with the primary use case (inference, given the market and the ICP), treat the other products as "also available when you're ready," and add a single outcome-specific CTA after the inference description rather than a generic "Learn more" on each card.
The page never names what the buyer is switching from.
▸ Read the full takeCollapseEvery testimonial that mentions a comparison — "compared to Docker, Cloud Run, Lambda," "if you are still using AWS Lambda instead of Modal," "similar to using Vercel for the first time" — is buried in the Twitter ticker where it's easy to miss. The buyer evaluating Modal almost certainly came from one of three places: they're running on Lambda and hitting cold start limits, they're managing Kubernetes and drowning in ops overhead, or they're on Replicate and hitting pricing or flexibility walls. The page never speaks to any of these situations directly. Add a short section — three columns, each naming a specific prior state and the specific Modal outcome — that makes the switching case explicit. "Running on Lambda? Modal cold starts are under a second. Managing Kubernetes? Define your infra in Python, no YAML." This is the highest-trust move the page isn't making.