When it comes to product roadmap prioritization for your early stage product: If it's worth doing, it's worth doing.
Factoring in "level of engineering effort" and other random data is typically just noise.
Focus on one question: "What is the #1 reason why more people are not getting more value from my app more often?"
Once you've identified the top problem and the key feature ideas for addressing the problem - DO it.
Don't overcomplicate it.
The only reason you need to concern yourself the level of effort is to a) estimate when key features will ship (and therefore when GTM activities and business metrics might change) and b) understand if you might want to slice the iteration into even thinner slices so you can deliver value more quickly (WITHOUT compromising on the final requirements). c) hold your engineering team accountable.