Peter Goetz
Peter Goetz has a total of 9 co-authors. Here are the top co-authors by number of shared publications:
- Frédéric Pattyn
Department of Business Informatics, Ghent University, Tweekerkenstraat 2, 9000 Ghent, Belgium
8 shared publications - Khandakar Rabbi Ahmed
Miyan Research Institute, International University of Business Agriculture and Technology, Dhaka 1230, Bangladesh
2 shared publications - Yannick Dillen
Vlerick Business School, Ghent University, 9000 Ghent, Belgium
2 shared publications - Afnan Aldhahri
Department of Software Engineering, College of Computing, Umm Al-Qura University, Makkah, Saudi Arabia
1 shared publication - Aqsa
Department of Computer Science, Wuhan University, Wuhan, China
1 shared publication - Geert Poels
Faculty of Economics and Business Administration, Department of Business Informatics and Operations Management, Ghent University, Ghent, Belgium
1 shared publication
Latest Publications
- Open Access
Validate Before You Build: Exploring Pre-MVP Evidence Levels—Not Quantity—And Startup Performance in Early-Stage Software Ventures
Software startups operate in environments characterized by rapid change, high uncertainty, and limited resources, resulting in high failure rates and challenges such as premature scaling and cash flow mismanagement. Prior research on pre-MVP validation has largely measured activity by volume rather than by the strength of evidence produced, leaving open whether evidence type, rather than quantity, is associated with startup performance. This study addresses that gap by investigating how early-stage software startups validate their initial idea before building their first Minimum Viable Product (MVP). Through 29 semi-structured interviews with founders from 16 software startups, pre-MVP validation activities were extracted and inductively coded into a six-level Validation Canvas spanning three validation stages identified in the literature: problem validation, problem-solution fit, and product-market fit. Startup performance was assessed through a composite ranking across funding, revenue, profitability, and runway indicators, and validation activities were analyzed thematically to derive the six evidence levels. No clear relationship was observed between the number of validation events and startup performance. Instead, stronger-performing startups tended to reach higher levels of evidence—particularly securing contingent investment commitments (Level 5) or paying customers (Level 6) before full MVP development. Level 6—paying customers before the full product exists—is identified as the strongest form of pre-MVP market evidence, as it directly validates willingness-to-pay without relying on investor confidence. In this study, product-market fit is operationalised as demonstrated commercial viability through external financial commitments rather than interest signals or free sign-ups alone. Based on these exploratory findings, the study proposes the Hierarchy of Validation: a staged, bidirectional process model in which bottom-up traversal from informal interest signals (L1) toward paying customers (L6) emerged as the primary pattern among stronger-performing startups. A top-down direction, in which experienced founders begin at higher evidence levels and work downward, is proposed as a hypothesis for future research. To our knowledge, this is among the first accounts of pre-MVP validation that differentiates strength of evidence rather than volume of activity, contributing the Hierarchy of Validation as an original, exploratory framework for early-stage software startups. These findings remain exploratory and require validation in larger and more diverse samples.
Open AccessValidate Before You Build: Exploring Pre-MVP Evidence Levels—Not Quantity—And Startup Performance in Early-Stage Software Ventures
Software startups operate in environments characterized by rapid change, high uncertainty, and limited resources, resulting in high failure rates and challenges such as premature scaling and cash flow mismanagement. Prior research on pre-MVP validation has largely measured activity by volume rather than by the strength of evidence produced, leaving open whether evidence type, rather than quantity, is associated with startup performance. This study addresses that gap by investigating how early-stage software startups validate their initial idea before building their first Minimum Viable Product (MVP). Through 29 semi-structured interviews with founders from 16 software startups, pre-MVP validation activities were extracted and inductively coded into a six-level Validation Canvas spanning three validation stages identified in the literature: problem validation, problem-solution fit, and product-market fit. Startup performance was assessed through a composite ranking across funding, revenue, profitability, and runway indicators, and validation activities were analyzed thematically to derive the six evidence levels. No clear relationship was observed between the number of validation events and startup performance. Instead, stronger-performing startups tended to reach higher levels of evidence—particularly securing contingent investment commitments (Level 5) or paying customers (Level 6) before full MVP development. Level 6—paying customers before the full product exists—is identified as the strongest form of pre-MVP market evidence, as it directly validates willingness-to-pay without relying on investor confidence. In this study, product-market fit is operationalised as demonstrated commercial viability through external financial commitments rather than interest signals or free sign-ups alone. Based on these exploratory findings, the study proposes the Hierarchy of Validation: a staged, bidirectional process model in which bottom-up traversal from informal interest signals (L1) toward paying customers (L6) emerged as the primary pattern among stronger-performing startups. A top-down direction, in which experienced founders begin at higher evidence levels and work downward, is proposed as a hypothesis for future research. To our knowledge, this is among the first accounts of pre-MVP validation that differentiates strength of evidence rather than volume of activity, contributing the Hierarchy of Validation as an original, exploratory framework for early-stage software startups. These findings remain exploratory and require validation in larger and more diverse samples.
- Open Access
A Deep Learning Framework for Predictive Feature Prioritization in Early-Stage Software Startups: Integrating Historical Delivery Data and Market Signals
Feature prioritization in early-stage software startups is a critical yet poorly structured challenge, as prevailing frameworks rely predominantly on expert intuition and fail to exploit patterns latent in historical delivery data and labor market dynamics. This study proposes a deep learning framework that explores labor-market signals as a reproducible proxy for market-driven feature prioritization. The framework encodes two complementary information sources: internal sprint delivery history processed by a Bidirectional Long Short-Term Memory network with attention, and external market signals from LinkedIn job postings processed by a Convolutional Neural Network encoder; the resulting representations are fused via a cross-modal layer to classify job postings as proxies for High or Low feature-priority market demand. The model is evaluated on the publicly accessible LinkedIn Job Postings dataset (2023–2024, approximately 124,000 records) and achieves an Area Under the Receiver Operating Characteristic Curve of 0.961 on the proxy classification task, outperforming classical baselines including gradient Boosted Trees, Random Forest, Support Vector Machine, and Logistic Regression. SHapley Additive exPlanations analysis identifies industry sector and geographic location as the two most influential market-signal predictors. These results suggest that jointly encoding internal delivery dynamics and external market signals offers a promising, scalable decision-support tool to assist startup product teams in data-driven roadmap prioritization, subject to further validation against direct expert priority labels.
Open AccessA Deep Learning Framework for Predictive Feature Prioritization in Early-Stage Software Startups: Integrating Historical Delivery Data and Market Signals
Feature prioritization in early-stage software startups is a critical yet poorly structured challenge, as prevailing frameworks rely predominantly on expert intuition and fail to exploit patterns latent in historical delivery data and labor market dynamics. This study proposes a deep learning framework that explores labor-market signals as a reproducible proxy for market-driven feature prioritization. The framework encodes two complementary information sources: internal sprint delivery history processed by a Bidirectional Long Short-Term Memory network with attention, and external market signals from LinkedIn job postings processed by a Convolutional Neural Network encoder; the resulting representations are fused via a cross-modal layer to classify job postings as proxies for High or Low feature-priority market demand. The model is evaluated on the publicly accessible LinkedIn Job Postings dataset (2023–2024, approximately 124,000 records) and achieves an Area Under the Receiver Operating Characteristic Curve of 0.961 on the proxy classification task, outperforming classical baselines including gradient Boosted Trees, Random Forest, Support Vector Machine, and Logistic Regression. SHapley Additive exPlanations analysis identifies industry sector and geographic location as the two most influential market-signal predictors. These results suggest that jointly encoding internal delivery dynamics and external market signals offers a promising, scalable decision-support tool to assist startup product teams in data-driven roadmap prioritization, subject to further validation against direct expert priority labels.
- Open Access
Automated Product Feature Prioritization in Software Startups Using Natural Language Processing and Multi-Criteria Machine Learning
Prioritizing product features is a crucial task for software startups due to scarce resources and rapidly changing markets. Existing prioritization approaches (for example, MoSCoW, Kano) are subjective and struggle to handle large sets of user feedback, resulting in inefficient product strategies and longer time to market. This paper bridges this gap by developing an automated feature prioritization approach based on a combined Natural Language Processing (NLP) and Multi-Criteria Machine Learning (MCML) system. The framework uses transformer-based sentence embeddings (specifically, a fine-tuned BERT model) to capture natural language semantics from user reviews and applies k-means clustering—with K selected via silhouette analysis—to discover latent product features. A sentiment-informed scoring system captures user feedback polarity; multiple criteria (sentiment, frequency, linguistic intensity, and user impact) are evaluated to generate a feature vector. An ensemble model combining Gradient Boosting and Random Forest (with tuned via grid search on the validation set) is then used to predict a feature priority class and produce a ranked list. The model is applied to a real Google Play Store review dataset; the results show accuracy 0.94, precision 0.94, recall 0.94, and F1-Score 0.93, with a macro-averaged F1 of 0.90 and balanced accuracy of 0.90. The results demonstrate the potential of NLP and multi-criteria learning for automated feature prioritization at scale. Our research offers an automated approach that addresses the challenges faced by software startups and may help enhance product–market fit and accelerate time to market.Open AccessAutomated Product Feature Prioritization in Software Startups Using Natural Language Processing and Multi-Criteria Machine Learning
Prioritizing product features is a crucial task for software startups due to scarce resources and rapidly changing markets. Existing prioritization approaches (for example, MoSCoW, Kano) are subjective and struggle to handle large sets of user feedback, resulting in inefficient product strategies and longer time to market. This paper bridges this gap by developing an automated feature prioritization approach based on a combined Natural Language Processing (NLP) and Multi-Criteria Machine Learning (MCML) system. The framework uses transformer-based sentence embeddings (specifically, a fine-tuned BERT model) to capture natural language semantics from user reviews and applies k-means clustering—with K selected via silhouette analysis—to discover latent product features. A sentiment-informed scoring system captures user feedback polarity; multiple criteria (sentiment, frequency, linguistic intensity, and user impact) are evaluated to generate a feature vector. An ensemble model combining Gradient Boosting and Random Forest (with tuned via grid search on the validation set) is then used to predict a feature priority class and produce a ranked list. The model is applied to a real Google Play Store review dataset; the results show accuracy 0.94, precision 0.94, recall 0.94, and F1-Score 0.93, with a macro-averaged F1 of 0.90 and balanced accuracy of 0.90. The results demonstrate the potential of NLP and multi-criteria learning for automated feature prioritization at scale. Our research offers an automated approach that addresses the challenges faced by software startups and may help enhance product–market fit and accelerate time to market. - Open Access
- 12 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 51-57
Perceived Product Management Priorities in Software Startups.
- 12 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 51-57
Open AccessPerceived Product Management Priorities in Software Startups.
- Open Access
VECTR: A Lightweight Requirements Prioritization Method for Software Startups Grounded in ROI, Time-to-Value, and Confidence
Startups face critical challenges in prioritizing requirements under severe resource constraints. Although methods such as RICE and ICE are known, prior studies show that decisions often default to ad hoc judgments and stakeholder opinions. This paper introduces and validates VECTR, a lightweight prioritization framework that integrates three criteria highly relevant to startups: return on investment (ROI), Time-to-Value (TtV), and confidence. Rather than presenting these criteria as conceptually new, VECTR’s contribution lies in their explicit operationalization for startup contexts and their integration into a single lightweight visualization. Seventeen practitioners—including founders, product managers, and technical leads—participated in semi-structured interviews. They first described their current prioritization practices and then evaluated VECTR through explanatory material and a proof-of-concept visualization. Results show that ROI, TtV, and confidence are already considered in practice, but inconsistently. Practitioners found VECTR intuitive, visually clear, and useful for structuring discussions, while noting limitations related to estimation effort and subjective assumptions. Most reported that it could support better data-driven decisions, though concerns remained around input estimation and assumptions made by biased humans. This study contributes a financially grounded, software-startup-suitable prioritization method and offers practitioners a practical way to allocate scarce resources toward requirements with the greatest impact, while acknowledging that the validation demonstrates perceived usefulness rather than measurable performance gains.
Open AccessVECTR: A Lightweight Requirements Prioritization Method for Software Startups Grounded in ROI, Time-to-Value, and Confidence
Startups face critical challenges in prioritizing requirements under severe resource constraints. Although methods such as RICE and ICE are known, prior studies show that decisions often default to ad hoc judgments and stakeholder opinions. This paper introduces and validates VECTR, a lightweight prioritization framework that integrates three criteria highly relevant to startups: return on investment (ROI), Time-to-Value (TtV), and confidence. Rather than presenting these criteria as conceptually new, VECTR’s contribution lies in their explicit operationalization for startup contexts and their integration into a single lightweight visualization. Seventeen practitioners—including founders, product managers, and technical leads—participated in semi-structured interviews. They first described their current prioritization practices and then evaluated VECTR through explanatory material and a proof-of-concept visualization. Results show that ROI, TtV, and confidence are already considered in practice, but inconsistently. Practitioners found VECTR intuitive, visually clear, and useful for structuring discussions, while noting limitations related to estimation effort and subjective assumptions. Most reported that it could support better data-driven decisions, though concerns remained around input estimation and assumptions made by biased humans. This study contributes a financially grounded, software-startup-suitable prioritization method and offers practitioners a practical way to allocate scarce resources toward requirements with the greatest impact, while acknowledging that the validation demonstrates perceived usefulness rather than measurable performance gains.
- 13 August 2025
- Published by Springer Nature
- p. 173-191
Product Feature Prioritization Practices in Software Startups: A Survey Study
- 13 August 2025
- Published by Springer Nature
- p. 173-191
Product Feature Prioritization Practices in Software Startups: A Survey Study
- Open Access
- 16 July 2025
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Access
- Vol. 13, 142546-142560
RECTV: Enhancing Agile Decision-Making in Startups Through Value-Driven Requirements Prioritization
Effective requirements prioritization is a success factor for software development. Models of prioritization that are traditionally used like MoSCoW, RICE, AHP and the Kano Model are deficient in responding to what is essential for startups in terms of speed and delivery of value, efficiency in cost, and mitigation of risk. In this paper, we introduce RECTV, a new startup requirements prioritization framework. Essential decision making components including Cost, Risk, Technical Feasibility, Confidence Level (C), and Time to Value (TtV) are integrated as key pieces of the RECTV tool to help startups prioritize based on informed, data based decision making. In contrast to traditional models, RECTV validates the outcomes of the features while delivering business value in a way where startups can adapt to market feedback and uncertainty rapidly. This work positions RECTV as a practical alternative to traditional models, offering startups a structured and responsive approach to prioritize features under real-world constraints. By conducting a comparative analysis with other models, the framework is evaluated and proved to be superior at tackling the startup glitches such as low funds, unspecified features, and the necessity of fast market adjustment. For startups, RECTV helps them to make better use of resources and develop features that avoid unnecessary risks.
- 16 July 2025
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Access
- Vol. 13, 142546-142560
Open AccessRECTV: Enhancing Agile Decision-Making in Startups Through Value-Driven Requirements Prioritization
Effective requirements prioritization is a success factor for software development. Models of prioritization that are traditionally used like MoSCoW, RICE, AHP and the Kano Model are deficient in responding to what is essential for startups in terms of speed and delivery of value, efficiency in cost, and mitigation of risk. In this paper, we introduce RECTV, a new startup requirements prioritization framework. Essential decision making components including Cost, Risk, Technical Feasibility, Confidence Level (C), and Time to Value (TtV) are integrated as key pieces of the RECTV tool to help startups prioritize based on informed, data based decision making. In contrast to traditional models, RECTV validates the outcomes of the features while delivering business value in a way where startups can adapt to market feedback and uncertainty rapidly. This work positions RECTV as a practical alternative to traditional models, offering startups a structured and responsive approach to prioritize features under real-world constraints. By conducting a comparative analysis with other models, the framework is evaluated and proved to be superior at tackling the startup glitches such as low funds, unspecified features, and the necessity of fast market adjustment. For startups, RECTV helps them to make better use of resources and develop features that avoid unnecessary risks.
- Open Access
- 17 January 2025
- Published by Science Publishing Group in International Journal of Sustainability Management and Information Technologies
- Vol. 11 (1) , 45-66
Time to Value (TtV) as a Missing Requirements Prioritization Criterion for Startup Survival: Insights from Founders vs. Systematic Literature Review
Software startups operate under extreme uncertainty and financial pressure, making Requirements Prioritization (RP) a critical activity for improving survival prospects. This study investigates which prioritization criteria are most relevant to early-stage ventures by conducting a systematic literature review (SLR) of 40 studies and analyzing 358 RP references encompassing 82 distinct criteria across 10 categories. Additionally, we conducted 34 semi-structured interviews with founders from 19 software startups to compare academic insights with real-world practices. The analysis reveals a substantial gap between scholarly emphasis and practitioner needs: while "expected cost" is the most frequently cited criterion in the literature, criteria related to financial impact—such as return on investment, cash flow, and time to value—are underrepresented despite being consistently cited by the most successful startups in our sample. Notably, the criterion "Time to Value," absent from all reviewed literature, emerged as a key factor among practitioners. These findings highlight the need for a more financially grounded and context-sensitive approach to RP in startup environments. The study concludes with a call for greater alignment between academic frameworks and the realities faced by early-stage software ventures, especially in economically challenging conditions.
- 17 January 2025
- Published by Science Publishing Group in International Journal of Sustainability Management and Information Technologies
- Vol. 11 (1) , 45-66
Open AccessTime to Value (TtV) as a Missing Requirements Prioritization Criterion for Startup Survival: Insights from Founders vs. Systematic Literature Review
Software startups operate under extreme uncertainty and financial pressure, making Requirements Prioritization (RP) a critical activity for improving survival prospects. This study investigates which prioritization criteria are most relevant to early-stage ventures by conducting a systematic literature review (SLR) of 40 studies and analyzing 358 RP references encompassing 82 distinct criteria across 10 categories. Additionally, we conducted 34 semi-structured interviews with founders from 19 software startups to compare academic insights with real-world practices. The analysis reveals a substantial gap between scholarly emphasis and practitioner needs: while "expected cost" is the most frequently cited criterion in the literature, criteria related to financial impact—such as return on investment, cash flow, and time to value—are underrepresented despite being consistently cited by the most successful startups in our sample. Notably, the criterion "Time to Value," absent from all reviewed literature, emerged as a key factor among practitioners. These findings highlight the need for a more financially grounded and context-sensitive approach to RP in startup environments. The study concludes with a call for greater alignment between academic frameworks and the realities faced by early-stage software ventures, especially in economically challenging conditions.