"Can we add this feature?" is every agency's most common question. The problem? Every client thinks their request is urgent. Every stakeholder thinks their feature is critical. Here's how to prioritize objectively.
The Problem with Gut-Feel Prioritization
Most agencies prioritize features based on:
- •Who asked first (FIFO queue)
- •Who yells loudest (squeaky wheel)
- •Who pays most (highest bidder)
- •What sounds cool (shiny object syndrome)
The result? Agencies build the wrong features, miss strategic opportunities, and frustrate their best clients because they're busy building vanity features for their loudest clients.
The Klientele Scoring System
We use a weighted scoring formula that removes emotion from prioritization:
Total Score = (Value × 3) + (User Reach × 2) + (Strategic Fit × 2) - Effort - RiskEach factor is scored 1-5, then weighted based on importance:
Value (3x weight): How much impact will this have?
- •5: Critical revenue impact or major cost savings
- •4: Significant efficiency gain or competitive advantage
- •3: Noticeable improvement
- •2: Nice to have
- •1: Minimal impact
User Reach (2x weight): How many users does this affect?
- •5: All users, multiple times daily
- •4: Most users, regularly
- •3: Half of users
- •2: Small segment
- •1: Single user or edge case
Strategic Fit (2x weight): Does this align with product vision?
- •5: Core to product strategy
- •4: Strongly aligned
- •3: Neutral
- •2: Slight misalignment
- •1: Off-strategy
Effort (1x weight, subtracted): How much work is this?
- •5: 40+ hours, multiple sprints
- •4: 16-40 hours
- •3: 8-16 hours
- •2: 4-8 hours
- •1: < 4 hours
Risk (1x weight, subtracted): What could go wrong?
- •5: High technical risk, could break core features
- •4: Moderate risk, significant testing needed
- •3: Some risk
- •2: Low risk
- •1: Minimal risk
Automatic Priority Assignment
Based on the total score, Klientele auto-assigns priority:
- •P0 (Critical): Score 15+ → Build this sprint
- •P1 (High): Score 10-14 → Build next sprint
- •P2 (Medium): Score 5-9 → Build this quarter
- •P3 (Low): Score 0-4 → Backlog, revisit later
- •Backlog: Score < 0 → Probably don't build
This removes the politics. The math determines priority, not the loudest voice in the room.
Real Example: Comparing Two Feature Requests
Feature A: Dark Mode
- •Value: 2 (nice cosmetic improvement)
- •User Reach: 5 (all users)
- •Strategic Fit: 2 (not core to product)
- •Effort: 4 (need to update many components)
- •Risk: 3 (could break existing styling)
- •Score: (2×3) + (5×2) + (2×2) - 4 - 3 = 13 → P1
Feature B: Bulk Import from CSV
- •Value: 5 (saves hours of manual entry)
- •User Reach: 3 (only onboarding users)
- •Strategic Fit: 4 (critical for enterprise customers)
- •Effort: 3 (8-16 hours)
- •Risk: 2 (low risk)
- •Score: (5×3) + (3×2) + (4×2) - 3 - 2 = 24 → P0
Dark mode has broader reach, but bulk import scores higher because of its massive value to the users who need it. The formula caught what gut-feel might miss.
Communicating Priorities to Clients
When a client asks "Why isn't my feature being built?" you can show them the math:
"Your feature scored a 7, which puts it in P2 (Medium priority). Here's why:
- •Value: 3 (good efficiency improvement)
- •User Reach: 2 (affects about 20% of users)
- •Strategic Fit: 3 (aligned but not core)
- •Effort: 4 (significant work)
- •Risk: 2 (moderate risk)
This transforms "I decided not to build it" into "the data shows we should prioritize these other features first." Much easier conversation.
Tips for Using the Scoring System
1. Score with stakeholders: Don't score alone. Get input from sales, support, and engineering. The discussion is as valuable as the score.
2. Revisit scores quarterly: Priorities change. A P3 feature might become P0 if market conditions shift.
3. Don't override the scores (often): If you're constantly overriding the formula, your weights are wrong. Adjust the formula, don't ignore it.
4. Break down large features: A huge feature might score low because of effort. Break it into phases—the MVP phase might score higher.
5. Document the why: For each score, write a one-sentence justification. Future you will thank current you.
6. Be honest about effort: Engineers often underestimate. Use your estimation multipliers (see our estimation article) before scoring effort.
Prioritization doesn't have to be political or emotional. Use a scoring system, show your work, and let the data drive decisions. Your clients will understand, your team will focus on what matters, and you'll build better products.