In the short term, the main priorities include some UX polish, [adding support for dividing the address book into multiple sections][sections], [automatic import of address book entries from URLs][URL-import] specified by the user, [integration with Rotki][rotki], and tackling a few rough edges.

Longer-term, working on [creating a standardized address book format][format] for [interoperability between address books across the whole ecosystem][interoperability] (including wallets and other apps) seems very worthwhile.

The full roadmap is listed at <https://github.com/users/aspiers/projects/2/views/2>.

Funds would go mainly towards development of new features as mentioned above, and perhaps a bit towards getting assistance from professional designers and marketers.

The original hope was to achieve viral growth from word of mouth, by making rolod0x so useful and easy to use that it becomes a complete no-brainer for everyone to use it.  However there are so many web3 projects competing for everyone's attention that kickstarting adoption via some grassroots marketing may make sense.

There are no plans to monetize rolod0x.  It was built as a public good to improve web3 UX and therefore help scale web3 adoption.

[sections]: https://github.com/rolod0x/rolod0x/issues/16
[URL-import]: https://github.com/rolod0x/rolod0x/issues/24
[rotki]: https://github.com/rolod0x/rolod0x/issues/81
[format]: https://github.com/rolod0x/rolod0x/issues/244
[interoperability]: https://github.com/rolod0x/rolod0x/issues?q=label%3Ainteroperability