Thinking on it further, I'm not sure that having re-usable apps a-la Django or perhaps Plone/Zope "Products" is feasible, at least in the sense that they'll work with any Pyramid project.
In order to be useful, these apps or products will have to define views, models/storage, and templates. Each one of these can be configured very differently within each Pyramid project, making it hard to fit all possibly use cases. Granted, Chameleon and Mako templates are bundled with Pyramid, but say someone wants to re-use an app that defines some Chameleon templates in their project that use Jinja2?
So I don't think it's going to be easy to try supporting all Pyramid projects in a self-contained, re-usable application like Django. Because Pyramid itself tries very hard to avoid having an opinion, making components where the opinion (storage backend, templating renderer, view routing mechanism) matters apply to everyone is difficult.