When deciding on modules, you'll primarily want to set them up with your product owners and customers in mind.
Whether you have two or 200 product owners, you'll want modules set up so that when each product owner goes into Receptive, they can see the product area(s) they're responsible for, and filter out the rest using the module filter. Each time they login, those filters will still be applied, so it will make their life very easy!
At the same time, you'll need the modules to be clear to customers so when they submit a new request, they understand which module their request relates to.
Read more about how to set up your modules here.
As for tags, here's the full list of ideas.
The way you use tags will evolve over time, so for now think about what you need to answer this question:
What segments of feedback do we want to analyze in our first roadmapping meeting with Receptive?
Do you want to look at dealbreakers for prospects? Or maybe issues that were potential bugs, or quick wins, or items that are stopping our customers from moving forward with our product?
We use tags for each of these (in addition to the effort vs value report) in Customer Success at Receptive so when our dev team wants to go in and plan their next project for customers, they have cues from CS on which items are the highest priority. Then within those filtered items, the SmartList will prioritize based on the value of the request.
Maybe you want to build for another team or user group, so you'll just think through what could be high priority items to segment out, and work backwards.