The lesson
Open a competitor comparison by naming the one frustration buyers already have with the rival, then organize every later section around that frustration.
The hero, under "Understand the difference," says i2c's transaction decisioning "exist[s] in a black box clients can't access" and offers "Read the Docs" and "Talk to Sales." "Compare key capabilities" follows as a table with four rows: Developer Experience, Authorization Intelligence, Reconciliation and Program Support. Each row has a short written cell for each side, and the Lithic column is highlighted. "Why clients choose Lithic over i2c" then runs three numbered cards that each start with a condition, such as "If your developers want a first-class experience." The page ends with quotes from Mercury, Atlas and Order.co and a close under "Still deciding between Lithic and i2c?" with "Explore Sandbox" and "Contact us."
Don't copy the pointed claims about i2c's overseas support or thousand-page PDFs unless you can stand behind equivalent claims about your own competitor. Keep the structure: a one-line problem frame, a short table with written cells, conditional reason cards, named customer quotes, then a closing prompt with a self-serve and a sales option.
Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.