TVL Platform - Product Roadmap

Last Updated: 2025-10-25 Planning Horizon: 24 months

---

Product Version Timeline

Month  1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
       |------MVP.0-----|--MVP.1--|--MVP.2--|-----V1.0--------|-V2.0-----|--V3.0----|

MVP.0  [========================================]
MVP.1                    [===================]
MVP.2                                 [===================]
V1.0                                           [=============================]
V2.0                                                          [=====================]
V3.0                                                                         [=======]

---

Version Overview

Version	Timeline	Key Deliverable	Business Value
MVP.0	Weeks 1-10	Foundation + Hostaway distribution	Single source of truth
MVP.1	Weeks 11-16	Two-way sync + booking awareness	Unified booking visibility
MVP.2	Weeks 17-24	Multi-channel distribution	Prevent double-bookings
V1.0	Month 7-12	Direct booking engine	No OTA commissions
V2.0	Month 13-18	Events & experiences	Increase booking value
V3.0	Month 19-24	Multi-vendor marketplace	Global scale

---

Capability Matrix

Capability	MVP.0	MVP.1	MVP.2	V1.0	V2.0	V3.0
Authentication
Google SSO	✅	✅	✅	✅	✅	✅
Email/Password	❌	❌	❌	✅	✅	✅
SSO (SAML)	❌	❌	❌	❌	❌	✅
Multi-factor Auth	❌	❌	❌	✅	✅	✅
Supply Management
Space CRUD	✅	✅	✅	✅	✅	✅
Unit CRUD	✅	✅	✅	✅	✅	✅
Media Management	🟡 URLs	🟡 URLs	🟡 URLs	✅ Upload	✅ DAM	✅ DAM
Amenities	✅	✅	✅	✅	✅	✅
Multi-language	❌	❌	❌	✅	✅	✅
Channel Distribution
Hostaway (one-way)	✅	✅	✅	✅	✅	✅
Hostaway (two-way)	❌	✅	✅	✅	✅	✅
Airbnb	❌	❌	✅	✅	✅	✅
VRBO	❌	❌	✅	✅	✅	✅
Booking.com	❌	❌	❌	✅	✅	✅
Custom channels	❌	❌	❌	❌	✅	✅
Availability
Calendar view	❌	🟡 Read	✅	✅	✅	✅
Block management	❌	❌	✅	✅	✅	✅
iCal sync	❌	❌	✅	✅	✅	✅
Conflict prevention	❌	❌	✅	✅	✅	✅
Pricing
Display pricing	❌	🟡 Basic	✅	✅	✅	✅
Seasonal rates	❌	❌	❌	✅	✅	✅
Dynamic pricing	❌	❌	❌	✅	✅	✅
Tax calculation	❌	❌	❌	✅	✅	✅
Multi-currency	❌	❌	❌	❌	❌	✅
Bookings
View external bookings	❌	✅	✅	✅	✅	✅
Direct bookings	❌	❌	❌	✅	✅	✅
Quote engine	❌	❌	❌	✅	✅	✅
Hold mechanism	❌	❌	❌	✅	✅	✅
Guest portal	❌	❌	❌	✅	✅	✅
Payments
Payment processing	❌	❌	❌	✅	✅	✅
Stripe Connect	❌	❌	❌	✅	✅	✅
Automated payouts	❌	❌	❌	✅	✅	✅
Revenue splits	❌	❌	❌	✅	✅	✅
Refunds	❌	❌	❌	✅	✅	✅
Communication
Unified inbox	❌	❌	❌	✅	✅	✅
Templates	❌	❌	❌	✅	✅	✅
Guest messaging	❌	❌	❌	✅	✅	✅
Operations
Task automation	❌	❌	❌	✅	✅	✅
Staff management	❌	❌	❌	✅	✅	✅
Owner portal	❌	❌	❌	✅	✅	✅
Events
Event management	❌	❌	❌	❌	✅	✅
Ticketing	❌	❌	❌	❌	✅	✅
Packages	❌	❌	❌	❌	✅	✅
Marketplace
Multi-vendor	❌	❌	❌	❌	❌	✅
White-label	❌	❌	❌	❌	❌	✅
Partner program	❌	❌	❌	❌	❌	✅

Legend:

• ✅ Full implementation
• 🟡 Partial/Limited implementation
• ❌ Not available

---

Team Size Recommendations

Phase	Recommended Team	Roles
MVP.0	4-6 people	2 Backend, 1 Frontend, 1 DevOps, 1 Product/Design
MVP.1	4-6 people	2 Backend, 1 Frontend, 1 DevOps, 1 Product
MVP.2	6-8 people	3 Backend, 2 Frontend, 1 DevOps, 1 QA, 1 Product
V1.0	8-12 people	4 Backend, 3 Frontend, 1 DevOps, 2 QA, 1 Product, 1 Design
V2.0	10-15 people	5 Backend, 4 Frontend, 2 DevOps, 2 QA, 1 Product, 1 Design
V3.0	15-20 people	6 Backend, 5 Frontend, 2 DevOps, 3 QA, 2 Product, 1 Design, 1 Data

---

Dependencies Between Versions

MVP.0 → MVP.1

Blocking Requirements:

• MVP.0 must have stable one-way sync
• Channel API integration patterns established
• Audit trail system operational

Data Migration:

• Add booking-related tables
• Add availability calendar tables
• No breaking changes to existing entities

MVP.1 → MVP.2

Blocking Requirements:

• Two-way sync working for Hostaway
• Conflict detection mechanism validated
• Field mapping system extensible

Data Migration:

• Add channel-specific configuration
• Extend channel_listings for multi-channel
• No breaking changes

MVP.2 → V1.0

Blocking Requirements:

• Multi-channel sync stable
• User auth system production-ready
• Database performance validated at scale

Data Migration:

• Add payment tables
• Add pricing rule tables
• Add guest/owner portal tables
• May require account_id backfill

V1.0 → V2.0

Blocking Requirements:

• Payment processing live
• Booking engine stable
• Financial reporting operational

Data Migration:

• Add event/ticket tables
• Add package tables
• No breaking changes to existing bookings

V2.0 → V3.0

Blocking Requirements:

• Events system stable
• Multi-tenant architecture validated
• Analytics infrastructure scalable

Data Migration:

• Add vendor tables
• Add white-label configuration
• Add multi-currency support
• May require org restructuring

---

Risk Mitigation

Risk	Impact	Mitigation	Version
Hostaway API rate limits	HIGH	Per-target limiters, jitter backoff	MVP.0
Double-booking on multi-channel	CRITICAL	GIST constraints, conflict detection	MVP.2
Payment processing failures	HIGH	Idempotent payments, retry logic	V1.0
Tax compliance complexity	HIGH	Avalara integration, jurisdiction DB	V1.0
Event capacity overselling	MEDIUM	Real-time inventory locks	V2.0
Multi-vendor data isolation	CRITICAL	RLS policies, account_id enforcement	V3.0

---

Success Criteria by Version

MVP.0 Success

• 10+ properties managed
• 100% sync success to Hostaway
• Zero data loss in sync
• <1 min sync latency

MVP.1 Success

• 50+ properties across channels
• All Hostaway bookings ingested
• Availability calendar accurate
• Zero sync conflicts

MVP.2 Success

• 100+ properties distributed to 3+ channels
• Zero double-bookings
• <5 min cross-channel sync
• 99%+ sync reliability

V1.0 Success

• 500+ properties
• 1,000+ monthly direct bookings
• $5M+ monthly booking value
• 99.9% uptime
• <200ms API latency (p95)

V2.0 Success

• 1,000+ events listed
• 50+ event organizers
• 5,000+ event bookings/month
• 30%+ guests book events with villas

V3.0 Success

• 100+ vendors
• 10+ white-label agencies
• 10,000+ properties globally
• $50M+ annual booking value
• 20+ countries

---

Related Documents

• MVP Overview
• V1 Product Specification
• V2 Product Specification
• V3 Product Specification
• Master Index