The environmental footprint of a software service development may be impacted by several factors, spanning human factors to infrastructure choices. To the best of our knowledge, the state of the art in the domain of environmental footprint fails i) to address the full spectrum of software services life cycle, from design to operation and maintenance and ii) to cover different categories of impacts. In this paper, we therefore introduce a methodology and the associated model to guide the software development ecosystem and their stakeholders in estimating the environmental footprint of their projects along multiple impact categories. This holistic approach delivers actionable insights to identify potential shifting between phases, such as development and usage, but also hotspots among resources consumed to produce and operate software services. We report on a sample case study that emphasizes the importance of development impact on a software life cycle and shows the relative importance of phases, as well as resources consumed.