# Launch Readiness Decision Matrix

*Go/No-Go criteria with specific metrics*  
*February 16, 2026*

---

## EXECUTIVE SUMMARY

**Current Status: NOT READY FOR PUBLIC LAUNCH**

- **Critical Blockers:** 3 Category A issues (cannot launch without)
- **Risk Level:** HIGH (competitive threat, product gaps, market confusion)
- **Recommended Action:** DELAY launch 2-4 weeks, focus on fundamental issues
- **Alternative:** Limited beta launch with Michael's network only

---

## DECISION MATRIX

### CATEGORY A: CRITICAL BLOCKERS (Must Fix to Launch)

| Issue | Current Status | Fix Required | ETA | Impact if Not Fixed |
|-------|---------------|--------------|-----|-------------------|
| **Zero Real Jobs** | 5 seed jobs | 20+ real contractor jobs | 2-4 weeks | Immediate worker churn, bad first impressions |
| **Payment Flow Broken** | Charge before work | Completion-based charging | 1-2 weeks | Customer dissatisfaction, high refunds |
| **Browse Workers Missing** | Workers can only apply | Contractors can browse/invite | 1 week | 50% of hiring use cases broken |

**GO CRITERIA:** All 3 Category A issues resolved
**NO-GO CRITERIA:** Any Category A issue remains unresolved

### CATEGORY B: SIGNIFICANT RISKS (Should Fix to Launch)

| Issue | Current Status | Risk Level | Mitigation |
|-------|---------------|------------|------------|
| **Competitive Positioning** | Fighting Yakka Labour directly | HIGH | Pivot messaging to "operating system" |
| **Domain Migration** | rivet.rateright.com.au | MEDIUM | Move to rateright.com.au |
| **SMS Infrastructure** | All sequences deactivated | MEDIUM | Reactivate with Michael approval |
| **Email Deliverability** | Untested support@ inbox | LOW | 30-minute verification test |

**RISK TOLERANCE:** Can launch with 1-2 Category B issues if Category A is resolved

### CATEGORY C: POLISH ISSUES (Nice to Fix)

| Issue | Impact | Effort | Priority |
|-------|--------|--------|----------|
| Stale match data display | UX annoyance | Low | Later |
| Signup name verification | Minor bug | Low | Later |
| PWA icon incorrect | Branding issue | Low | Later |

**LAUNCH IMPACT:** Category C issues don't block launch

---

## DETAILED ASSESSMENT

### Critical Blocker #1: Zero Real Jobs Problem

**The Issue:**
- Platform has 5 seed jobs with fake data
- Real workers will sign up, see nothing relevant, churn immediately
- Bad first impressions are impossible to recover from

**Current Metrics:**
- Real jobs: 0
- Seed jobs: 5
- Worker signups without jobs: 100% churn rate expected

**Go Criteria:**
- ✅ 20+ real, current jobs from verified contractors
- ✅ Geographic spread across Sydney suburbs
- ✅ Trade variety (5+ different trades)
- ✅ Reasonable pay rates ($30-50/hr)
- ✅ Responsive job posters (reply to applications)

**Fix Strategy:** Michael's network activation plan (see separate document)
**Timeline:** 2-4 weeks of personal outreach
**Risk:** If network response is poor, delay launch further

### Critical Blocker #2: Payment Flow Broken

**The Issue:**
- Currently charge $50 before work happens
- No recourse if worker no-shows or job cancelled
- No completion confirmation system
- High refund risk, poor user experience

**Current State:**
- Payment timing: Before work (wrong)
- Completion tracking: None
- Dispute resolution: None  
- Refund policy: Undefined

**Go Criteria:**
- ✅ Completion-based charging system
- ✅ 48-hour confirmation window
- ✅ Basic dispute resolution process
- ✅ Clear refund policy published
- ✅ Technical implementation complete

**Fix Strategy:** Hybrid completion confirmation model (see payment flow spec)
**Timeline:** 1-2 weeks technical development
**Risk:** Complex to implement, may introduce new bugs

### Critical Blocker #3: Browse Workers Missing

**The Issue:**
- Contractors can only see workers who apply to their jobs
- No proactive worker discovery
- Misses 50% of how real hiring works
- Bug #10 from Michael's QA session

**Current State:**
- Contractor workflow: Post job → wait for applications
- Worker discovery: None
- Proactive hiring: Impossible

**Go Criteria:**
- ✅ Browse workers page for contractors
- ✅ Filter by trade, location, experience, availability
- ✅ Contact/invite workers to apply
- ✅ Worker profiles optimized for browsing

**Fix Strategy:** Builder implements browse workers feature
**Timeline:** 1 week (Builder estimated 4-6 hours)
**Risk:** Low technical risk, straightforward implementation

---

## COMPETITIVE THREAT ASSESSMENT

### Yakka Labour Threat Level: HIGH

**Market Position:**
- Established leader in our exact category
- "Modern, app-based construction labour hire platform built specifically for Australia"
- Strong SEO presence, content marketing, brand recognition

**Strategic Risk:**
- Fighting them head-to-head = David vs Goliath scenario
- Our current positioning plays into their strengths
- They could copy our $50 fee model easily

**Go Criteria for Competitive Response:**
- ✅ Clear differentiation strategy (not just cheaper)
- ✅ "Operating system" messaging vs "hiring app"
- ✅ Voice-first features highlighted as unique
- ✅ Michael's network activated as competitive moat

---

## LAUNCH SCENARIOS

### Scenario A: Full Public Launch (NOT RECOMMENDED)
**Requirements:** All Category A + B issues resolved
**Timeline:** 4-6 weeks minimum
**Risk:** High - competing with established player
**Upside:** Maximum market reach if successful

### Scenario B: Network Beta Launch (RECOMMENDED)
**Requirements:** Category A issues resolved, Michael's network loaded
**Timeline:** 2-3 weeks
**Approach:** Launch only to Michael's construction network
**Benefits:** 
- Test platform with real users who trust Michael
- Generate success stories and case studies  
- Refine product based on real usage
- Build momentum before public launch

### Scenario C: Delayed Launch (CONSERVATIVE)
**Requirements:** All issues resolved + OpsMan integration started
**Timeline:** 6+ weeks
**Benefits:** Launch as "operating system" not just "hiring app"
**Risk:** Market opportunity may shift, momentum lost

### Scenario D: Partnership Launch (STRATEGIC)
**Requirements:** Partnership with Yakka Labour negotiated
**Timeline:** 2-3 months
**Approach:** Complementary services, not competition
**Benefits:** Avoid direct competition, faster path to market

---

## DECISION FRAMEWORK

### GO Decision Criteria (All Must Be True)
1. ✅ **Jobs Loaded:** 20+ real jobs from Michael's network
2. ✅ **Payment Fixed:** Completion-based charging implemented
3. ✅ **Browse Workers:** Contractor discovery feature complete
4. ✅ **Network Committed:** 10+ contractors committed to using platform
5. ✅ **Differentiation Clear:** Positioning distinct from Yakka Labour

### NO-GO Decision Criteria (Any Can Trigger)
1. ❌ **Network Response Poor:** <10 contractors willing to post jobs
2. ❌ **Technical Issues:** Payment system not working reliably
3. ❌ **Competitive Confusion:** Can't articulate difference from Yakka
4. ❌ **Resource Constraints:** Team cannot support launch demands
5. ❌ **Market Timing:** External factors make launch inadvisable

### SOFT LAUNCH Decision Criteria (Middle Path)
1. ✅ **Category A Fixed:** Critical blockers resolved
2. ✅ **Network Ready:** Michael's contacts committed
3. ⚠️ **Category B Issues:** Some remain but manageable
4. ✅ **Feedback Loop:** Ability to iterate based on real usage

---

## MEASUREMENT CRITERIA

### Week 1 Success Metrics (Post-Launch)
- **Job Applications:** 2+ applications per posted job
- **Response Rate:** 80% of contractors respond to applications
- **Technical Stability:** <5% error rate on core flows
- **User Feedback:** 4.0+ stars from early users

### Month 1 Success Metrics
- **Successful Hires:** 10+ completed hires through platform
- **User Retention:** 60% of contractors post second job
- **Word of Mouth:** 3+ organic contractor signups
- **Platform Health:** 90%+ uptime, fast load times

### Month 3 Success Metrics
- **Revenue Run Rate:** $500+/month (10+ hires/month)
- **Market Validation:** Proven demand from construction network
- **Product-Market Fit:** Clear value proposition validated
- **Scale Readiness:** Systems can handle 5x growth

---

## RECOMMENDATIONS

### PRIMARY RECOMMENDATION: Network Beta Launch

**Strategy:**
1. Fix Category A blockers (2-3 weeks)
2. Load jobs from Michael's network (parallel)
3. Launch to network contacts only (soft launch)
4. Gather feedback, refine product (4 weeks)
5. Consider public launch with proven success stories

**Benefits:**
- Lower risk, trusted user base
- Real feedback from construction professionals
- Success stories for broader marketing
- Time to differentiate from Yakka Labour

### ALTERNATIVE: Delayed Strategic Launch

**Strategy:**
1. Fix all issues (4-6 weeks)
2. Start OpsMan integration (parallel)  
3. Launch as "construction business operating system"
4. Lead with complete solution, not just hiring

**Benefits:**
- Better competitive positioning
- Higher value proposition
- Sustainable differentiation
- Premium pricing potential

---

## THE HARD TRUTH

**We are not ready for public launch.** The platform is technically sound but strategically naive. We're solving the wrong problem (matching) instead of the real problem (complete workforce management).

**Best path forward:** Network beta launch with Michael's contacts, use that feedback to refine positioning, then public launch as integrated business solution.

**Timeline:** 6-8 weeks to proper public launch, 2-3 weeks to network beta.

---

*Decision point: Michael must choose between speed (network beta) and strategy (delayed integrated launch). Both are better than competing head-to-head with Yakka Labour as "another construction hiring app."*