It's hard to be sure that that's all you need. Maybe you'll be fine, maybe you'll get stuck between keeping a slow DB or rewriting everything. Doesn't cost much to go proper relational from the start. And if you're really sure you want objects, there are NoSQL solutions that are designed for that.
I'm kind of on the side of avoiding ORM unless you have a clear need for it. But I've seen projects where they are very valuable. If you mainly want to register, update and delete a bunch of structured data, it's not a bad idea to put it in a dabatase. And if you do those operations a lot in some part of the application, it's not a bad idea to use an ORM there. For analysis and reports and such I would probably suggest just writing SQL directly though.