Well, instead of having to explicitly fill each field in a form, you can just say "Fill the personal details form" or "Fill the credit card form" and we'll work out what each field is and fill it with sensible inputs - either dummy data or data supplied by the test author. Since you aren't hard-coding each locator, and we determine what fields are present and how to deal with them at runtime, unstable ids, classes, & xpaths, and even adding/removing form fields can be handled gracefully (as long as the user journey doesn't change semantically).

We can also handle other common actions like "Login", "Search for ipsum", "Select the first search result" (or "Select the first product/hotel/flight/etc" - that one's really impressive), "Add to cart", "Checkout". When writing the tests, we give you the list of imperative actions than we think your declarative commands map to, and you can correct us if (when) we get it wrong.

We also have some value-adds. Apart from the usual assertions (checking the page loads, looking for certain text or elements, et cetera), you can write assertions checking for the presence and correctness of 200+ advertising and analytics tags, and can included computed assertions (assertions that are computed from the context of the test). We also have natural language date handling, so you can write evergreen tests with commands like "Search for a flight next Monday" and we'll resolve that to the actual date to input into the datepicker. We're also working on malware detection (basically checking all loaded resources and outbounds like on every page we load for suspicious markers).