I've been using Podio six months to manage accounting clients and various projects. Podio by itself is reasonably priced. It is highly customisable and that is it's greatest feature (and drawback). It's more than a task list... you can really create any online database you want.
What sold me originally was it had relationship fields, so records can be associated to each other like a primary key. The other point was it had recurring tasks built-in. This is a rare feature for online database products (as a native feature).
It does integrate well with it's own family of products under the Citrix label.
Podio's greatest weakness is the flexibility. Very few add-on features are built-in. Yes, there are multiple third parties that offer add-ons, when they work.
I will challenge you to think of this... how will you use the data that you store in Podio? Podio struggles to even provide a "print" feature built-in. The native reports are just widgets, and not pretty ones. They're not designed to print or even share. There's no good backup feature to get data out, other than exporting each view (though there are integrations). I'm just saying it is super-frustrating to actually put the data to use without a decent level of programming knowledge, time, and research into add-on integrations that may not even be in a language you can translate.
I would also challenge Podio to communicate with it's customers. There's no product roadmap, blog is outdated, and really just no communication whatsoever to know what frustrations might later be overcome. I bought a Citrix package at $200/month and then haven't heard a word, other than a couple of survival fixes.
Last, it is not intuitive for team use unless your techie level is at a 7 or 8 our of 10. I failed miserably with two staff members, before I realized I was pushing a difficult interface that frustrated them rather than excited them. There's quirky things, like clicking outside of a certain area on the screen when entering a record -- it saves the record and closes it -- that created tons of errors with my staff. Why not have a "Save and Close" button, rather than a random mouse click perform that function? After that, I would have to go back and dig to see which record they edited and fix it.
There are other random things, like if you use a related field, you can't see it in a table format. Meaning, if Adam Smith has a rental house at 123 Happy Lane, you can't show both of those things a table (at least not easily).
Hope this helps, but I would test it and seriously consider what walls you will hit when it's put to full use. Unfortunately it's caused me to move to a different product.
Please consider what it might no have that you expect to need. If it doesn't have it, you will dearly for the core product plus all the third-party add-ons you'll need just for basic use like displaying the data.