1. FIVE-SECOND VERDICT First line read: "Relay - Ship faster, break less." An engineering manager arriving from a CI comparison would believe this is a general-purpose CI/CD product competing on speed. That is roughly what it is, but the page never names what it replaces, and a reader in the middle of a comparison is looking for exactly that. 2. MESSAGE MATCH - Arrived wanting: a like-for-like comparison against the tool they already run, and one concrete reason to switch. - Page leads with: a speed claim and a joke about hating pipelines. - Gap: the page argues that pipelines are unpleasant. This reader accepted that years ago; they are choosing between vendors, not deciding whether to have CI at all. Match: Partial - decided by "The deploy pipeline for teams that hate deploy pipelines", which positions against having a pipeline rather than against a competitor. 3. FRICTION INVENTORY 1. "Trusted by fast-moving teams everywhere" - unproven - name three customers or cut the line; an unnamed trust claim reads as no customers. 2. "Automated builds. Parallel test sharding. One-click rollback." - unclear - every competitor on the comparison page lists these; add the number that makes yours different or say which one you are best at. 3. "Starts at $49/month" - unclear - per seat, per repo, per build minute? A manager cannot take this into a budget conversation. 4. "Contact us for enterprise" - effortful - this reader is evaluating, not buying, and it is a second ask on a page that has not earned the first. 5. "Most teams are running within a day" - unproven - "most" and "a day" are the two words a migration-averse reader will not believe without a named example. 4. OBJECTION COVERAGE - "What will migrating cost me in engineer-days?" - Half-answered: "Most teams are running within a day" asserts the answer without showing a migration path. - "Does it fit our stack?" - Half-answered: "Do you support monorepos? Yes" covers one case out of many. - "What happens when it breaks at 2am?" - Absent. No support terms, no status page, no on-call story anywhere on the page. - "Why switch from what we already run?" - Absent. The page never names an alternative. - "What does this cost at our size?" - Absent. The pricing line stops well short of this reader's team. 5. CTA DIAGNOSIS The button says "Get Started". The reader believes it opens a signup form of unknown length that probably wants a card. By this point the page has earned little: no named customer, no comparison, no pricing clarity. And the free trial - the offer the page is actually built to sell - is never mentioned in the copy at all, so the thing behind the button is invisible until after the click. Highest-cost word: "Started". It names work the reader has to do rather than the thing they get, and it hides the two facts that would move them: fourteen days, no card. 6. FIX LIST 1. Put the trial terms into the button itself - CTA - removes the "what am I committing to" risk. 2. Replace the trust line with three named customers or a customer count - Friction 1 - removes the unproven claim. 3. Add a one-line comparison against the two tools this traffic arrives from - Message match - closes the gap between what they wanted and what the page leads with. 4. Break pricing into per-seat cost at 20, 50 and 100 engineers - Friction 3 - answers the budget objection this reader must clear internally. 5. Add a support and incident line beside the FAQ - Objection 3 - answers the 2am question. 6. Move "Contact us for enterprise" off the main flow - Friction 4 - removes the competing ask. Rewritten, top two: Button: Start a 14-day trial - no credit card Trust line: Running in production at Vector, Halfpipe and Northbound - 40 to 300 engineers each.