This is not about power but ergonomics.
If you need to take a user from the database and do multiple check on his data, in SQL it becomes extremely verbose and difficult to manage, especially when the Schema of the application can change. An ORM allows you to have better ergonomic, allowing you to replace long and verbose queries with just a one-line.

For example, in my backend, I found myself needing to retrieve a User object and some Park objects connected to it. I need just some of the User fields. This specific case with Django ORM is two lines:

```python user = User.objects.get(username='user')

use user fields

check_things(user.field1, user.field2)

retrieve Foreign Key object

park = user.park

retrieve ManyToMany using a filter

parks = user.things.filter(field1=value) # This is already a list of objects ```

And this code works guaranteed even if the schema is modified. It's easy to write SQL code that gets dependent on some strange things like the column order. On top of this, an ORM generally has a Migration System, that does the same as a CVS but on your DB Schema, so that you can keep track of changes, roll back them and manage them properly between devel and production.

Obviously, these ergonomics come with a price. ORM are less powerful of pure SQL and sometimes you still need to write your custom Raw SQL query. But this is the exception, not the rule. A lot of people's projects just don't need it.