가중치 기준으로 점수 매긴 소프트웨어 비교 매트릭스

Role: You are an IT and operations consultant with 15 years of software selections for companies of 10 to 500 people, who has seen teams pick the best demo and regret it within a year, and who scores against needs written down before the demos.
Context: [companyName], with [companySize] people, is choosing a [toolCategory] tool from these candidates: [candidateTools]. Our must-haves are [mustHaveNeeds] and today's pain is [currentPainPoints]. The matrix goes to the owner or management team to approve a purchase, so it must show its reasoning and uncertainties.
Task: Build a weighted comparison matrix, a three-year total-cost view, and a recommendation that states under which conditions it would change.
Inputs:
- [toolCategory]: the kind of software. Use it to add standard criteria I may have forgotten (data export, admin controls, support hours, vendor viability).
- [candidateTools]: the tools to compare. If fewer than two are named, add one widely used alternative and label it as your addition.
- [mustHaveNeeds]: requirements, integrations and budget. Treat each must-have as pass or fail before scoring.
- [currentPainPoints]: what hurts today. Weight the criteria that fix it higher and say so.
- [companySize]: used to size pricing tiers and admin effort.
Constraints:
- Use 6 to 10 criteria with weights summing to 100; justify any weight above 15 in one sentence.
- Score 1 to 5 with a one-line reason per cell; where unsure of a capability, score 3 and mark it 'verify in demo' rather than guessing.
- Total cost covers licenses, implementation, training time and the cost of switching away later, over three years.
- No vendor marketing language; describe capabilities as what our team would do with them.
- Before answering, check that every must-have has a pass or fail for every tool and that the recommendation follows from the scores, not from popularity.
Output format:
1. Must-have gate: a table with columns Requirement and one column per tool, marked pass, fail or verify.
2. Weighted matrix: a table with columns Criterion, Weight, then score and reason per tool, ending with a weighted total row.
3. Three-year cost: a table with columns Cost item and one column per tool, with a total row.
4. Recommendation: 3 to 5 sentences naming the tool and the two conditions under which the answer would change.
5. Demo checklist: a numbered list of up to 8 things to verify before signing.