Business Plan Summary
Presentation-style summary of the Zenvee business, operations model, workforce direction, and launch plan. This page now matches the founder portal navigation and visual language used across the other founder pages.
Zenvee
Verified Nail Services Marketplace and Operations Platform
Mobile Application for iOS & Android
May 14, 2026
Executive Summary
Zenvee is a verified nail services marketplace and operations platform that connects customers with certified, vetted technicians and grows in phases. The business starts as an asset-light marketplace, adds Zenvee Events as a catered group-service offering, expands into salon seat partnerships, and later develops into branded Zenvee destinations for customers who prefer a more professional environment.
Founders: Michael Tran, Phillip Ho, and Long Nguyen
Legal structure: LLC established
Year 1 operating budget: $100,000
Legal structure: LLC established
Year 1 operating budget: $100,000
$8B+
US Nail Services TAM
6 Mo
MVP Timeline
Core business: Build the trusted marketplace where customers and technicians meet first, launch catered Zenvee Events for group bookings, then scale supply and customer choice through salon partnerships and Zenvee-operated destinations.
Supply-side moat: Win technicians first on pay with a 70/30 baseline payout versus the common 60/40 salon split, then keep top performers through progression, premium access, and higher-value platform opportunities.
Supply-side moat: Win technicians first on pay with a 70/30 baseline payout versus the common 60/40 salon split, then keep top performers through progression, premium access, and higher-value platform opportunities.
MVP planning note: The marketplace MVP should be modeled as a six-month build ending in a limited-city beta, not a compressed 3-4 month full release.
Technician Join Logic
- ✓ Reason 1: Better starting pay than traditional salon economics
- ✓ Reason 2: Access to customer demand and repeat bookings
- ✓ Reason 3: Safer operating model with verified customers and mutual acceptance
- ✓ Reason 4: The full opportunity path is visible up front, including better payout tiers, stronger visibility, and seat access as technicians qualify
- ✓ Reason 5: Over time, the platform can offer both contractor flexibility and more structured employee-style opportunities for technicians who want stability and benefits
Workforce strategy: Zenvee should start contractor-first for MVP speed, but it should not assume every technician wants to remain a contractor forever. A stronger long-term supply strategy is to preserve room for a mixed workforce model, because many technicians are attracted to salon employment for scheduling stability, simpler taxes, and benefits like healthcare.
Technician Progression Ladder
| Tier | Payout | Qualification Signal | What Improves |
|---|---|---|---|
| Starter | 70/30 | Verified and approved on-platform | Immediate earnings advantage and core marketplace access |
| Proven | 75/25 | Strong ratings, reliable completion, repeat demand | Higher earnings, better visibility, and earlier access to premium opportunities |
| Elite / Loyalty | 80/20 | High trust, consistent demand, strong retention | Best payouts, premium placement, and priority for scarce seat inventory |
Key Differentiators
- Rigorous Verification: License validation, identity verification, background checks
- Technician-First Economics: Better payout structure than common salon 60/40 arrangements
- Flexible Workforce Direction: Start contractor-first while preserving a future path to structured employee-style roles as the platform grows
- Reputation System: AI-powered trust scores with visible badges and certifications
- Regulatory Compliance: State-by-state legal requirement management
- Phased Fulfillment Strategy: Marketplace first, Zenvee Events second, salon partners third, Zenvee destinations fourth
- Real-Time Features: Live tracking, instant messaging, automatic notifications
Financial operations direction: QuickBooks Online should remain the accounting core, while the customer- and technician-facing payment rail should stay separate and be handled by a dedicated in-app payments platform. Stripe is the current default candidate, but equivalent payment platforms should still be evaluated before the final decision is locked.
Competitive Positioning
- ✓ Better pay than traditional salons through a 70/30 starting point and clear upside tiers
- ✓ More trust and operating discipline than Instagram, referrals, and informal booking channels
- ✓ More technician upside than a flat booking marketplace because progression is built into the model
- ✓ More flexible fulfillment than salons because service can move from home to seats to destinations
Market Opportunity
Market Size & Growth
US Beauty Services Market: $64+ billion annually
On-Demand Services Growth: 15-20% YoY
Nail Services TAM: $8+ billion
Estimated SAM: ~$1.2B-$1.6B
Estimated SOM: ~$0.45M-$0.9M GMV in Year 1-2
Untapped Market: ~60% services booked offline
On-Demand Services Growth: 15-20% YoY
Nail Services TAM: $8+ billion
Estimated SAM: ~$1.2B-$1.6B
Estimated SOM: ~$0.45M-$0.9M GMV in Year 1-2
Untapped Market: ~60% services booked offline
TAM / SAM / SOM
| Metric | Meaning | Zenvee View |
|---|---|---|
| TAM | Total addressable market | Full U.S. nail services category, about $8B+ |
| SAM | Serviceable available market | Launchable urban and mobile-friendly segment, about $1.2B-$1.6B |
| SOM | Serviceable obtainable market | About $0.45M-$0.9M GMV in the first 1-2 years based on actual booking targets |
Assumption logic: TAM reflects total category spend. SAM assumes roughly 15-20% of that spend sits inside the dense, launchable markets and service formats Zenvee can realistically serve first. SOM is then tied to practical execution, such as 750-1,500 monthly bookings at a $50 average booking value.
Why This Market?
Market Strengths
- Large addressable market
- High repeat frequency (every 2-4 weeks)
- Strong unit economics
- Lower complexity than ride-sharing
- Growing consumer preference for convenience
Competitive Moat
- Network effects (2-sided market)
- Quality verification (hard to replicate)
- Regional dominance (local execution)
- Reputation system (customer reviews)
- Regulatory compliance expertise
Product Vision & Value Proposition
For Customers
- ✓ Choice of Setting: Book at home first, then at partner salons or Zenvee destinations as the network grows
- ✓ Service Tier Choice: Choose standard services or Luxury service in approved physical salon environments
- ✓ Safety: Verified, licensed, background-checked professionals
- ✓ Transparency: Real-time tracking, upfront pricing, verified reviews, and detailed technician profiles
- ✓ Flexibility: Customer preference is matched with technician-supported environments before a booking is confirmed
Luxury Service Tier
Luxury service: A premium service tier available only in approved physical salon environments such as partner salons or Zenvee destinations. This tier can include alcohol beverages only where legally permitted and only at appropriately licensed or compliant venues, along with massage add-ons and elevated hospitality amenities.
For Technicians
- ✓ Income Flexibility: Work your own schedule
- ✓ Lead Generation: Consistent customer flow
- ✓ Better Payouts: Baseline 70/30 model vs. common 60/40 salon split
- ✓ 100% Tip Pass-Through: Customer tips go fully to technicians with no platform take
- ✓ Reputation Building: Earn badges and improve visibility
- ✓ Growth-Based Earnings: Top technicians can move to 75/25 or 80/20
- ✓ Safety Controls: Verified customers, trust profiles, mutual acceptance, and approved work-location choices
- ✓ Simplified Payments: Automatic weekly/monthly payouts
For Platform
- ✓ Revenue: Technician-first revenue share with channel-based margins
- ✓ Phased Expansion: Asset-light marketplace first, venue-backed growth second
- ✓ Scalability: Single codebase for iOS + Android
- ✓ Data Advantage: Rich insights into supply, demand, and trends
Phased Service Model
| Phase | Model | Why It Matters |
|---|---|---|
| Phase 1 | Marketplace bookings | Validates demand, trust, technician supply, and repeat behavior |
| Phase 2 | Zenvee Events (catering service) | Adds high-value group bookings, social acquisition, and a differentiated "bring your nail shop home" offer |
| Phase 3 | Salon seat partnerships | Adds professional environments without full real estate risk |
| Phase 4 | Zenvee destinations | Creates brand control, recurring venue income, and premium service delivery |
Two-Sided Safety Principle
Zenvee should protect both sides of the marketplace. Customers express their preferred service environment, technicians retain control over which environments they accept, and the platform confirms a booking only when both sides match on the same destination.
Technician Verification & Compliance
Multi-Layer Verification Workflow
Phase 1
Initial Application
Tech uploads: license, government ID, selfie, portfolio, bank details
Tech uploads: license, government ID, selfie, portfolio, bank details
Phase 2
Automated Verification
OCR extraction → Liveness detection → License validation → Background check → Risk scoring
OCR extraction → Liveness detection → License validation → Background check → Risk scoring
Phase 3
Manual Review (Admin)
Score 85-100: Auto-approved | 60-84: Manual review | <60: Rejected
Score 85-100: Auto-approved | 60-84: Manual review | <60: Rejected
Phase 4
Ongoing Monitoring
License expiry checks, performance monitoring, complaint escalation
License expiry checks, performance monitoring, complaint escalation
Trust & Reputation Score (1-100)
| Component | Points | Factor |
|---|---|---|
| License Verified | 25 | Primary verification |
| Background Check Clean | 20 | Safety assurance |
| Booking Completion Rate | 15 | Reliability |
| Average Customer Rating | 20 | Quality of work |
| Repeat Customer Rate | 10 | Satisfaction |
| Response Time Excellence | 5 | Responsiveness |
| Platform Violations (penalty) | -5 per violation | Compliance |
Trust Badges (Customer-Facing)
PLATINUM
95-100 score
500+ bookings, 4.8+ rating
95-100 score
500+ bookings, 4.8+ rating
GOLD
85-94 score
200+ bookings, 4.6+ rating
85-94 score
200+ bookings, 4.6+ rating
SILVER
75-84 score
50+ bookings, 4.5+ rating
75-84 score
50+ bookings, 4.5+ rating
NEW
60-74 score
Building reputation
60-74 score
Building reputation
Technical Architecture
Three-Tier System
Tier 1 - Mobile: .NET MAUI apps (iOS + Android)
Tier 2 - Backend: ASP.NET Core 8 APIs
Tier 3 - Data & Services: PostgreSQL, Redis, Cloud Storage
Tier 2 - Backend: ASP.NET Core 8 APIs
Tier 3 - Data & Services: PostgreSQL, Redis, Cloud Storage
Core Components
| Component | Purpose | Technology |
|---|---|---|
| Authentication | User login, JWT tokens, roles | Identity Server |
| Booking Engine | Create, match, track bookings | C# + Background Jobs |
| Real-Time | Live tracking, chat, notifications | SignalR WebSockets |
| Payments | Process payments, handle splits | Stripe API |
| Verification | License checks, background screening | Third-party APIs |
Technology Stack Summary
Mobile
- .NET MAUI 8
- XAML UI Framework
- Native iOS/Android
- Offline support
Backend & Data
- ASP.NET Core 8
- PostgreSQL Database
- Redis Cache
- Entity Framework ORM
External Services
- Stripe (Payments)
- Google Maps (Geolocation)
- Firebase (Push Notifications)
- Twilio (SMS)
DevOps & Hosting
- Azure or AWS
- GitHub Actions CI/CD
- Blue-Green Deployment
- Application Insights
MVP Features (Phase 1)
Customer App
- ✓ Browse services and technicians
- ✓ Choose standard or Luxury service tiers based on environment availability
- ✓ View technician schedule transparency with blocked times, open slots, queue position, and estimated wait
- ✓ View rich technician profiles with badges, specialties, ratings, and location support
- ✓ Choose direct-service booking mode
- ✓ Complete ID verification and payment verification before booking activation
- ✓ Follow guided identity verification with document upload, selfie, and review status
- ✓ Book appointments in real-time
- ✓ Live technician tracking on map
- ✓ Secure payment checkout
- ✓ In-app messaging
- ✓ Rate and review
- ✓ Booking history and receipts
Technician App
- ✓ Profile and verification setup
- ✓ Availability calendar
- ✓ Accept multiple customers into a real scheduled queue without overlapping blocked times
- ✓ Booking acceptance/rejection with customer and location review
- ✓ View customer trust profile with verification badges, rating, and prior booking behavior
- ✓ Real-time earnings dashboard
- ✓ Transparent tier and payout visibility
- ✓ Destination-of-work preferences and unsafe-address reporting
- ✓ Customer communication
- ✓ Service completion and photos
- ✓ Ratings and feedback
Two-Sided Safety
- ✓ Mutual acceptance before in-home bookings are confirmed
- ✓ Customer verification tiers tied to booking risk
- ✓ Approved location policy for where services can happen
- ✓ Technician safety check-in, SOS, and incident escalation flows
Admin Dashboard
- ✓ Technician verification queue
- ✓ License and credential verification
- ✓ Technician payout tier management
- ✓ Safety incident review and unsafe customer/address management
- ✓ Complaint management
- ✓ User suspension/ban controls
- ✓ Basic analytics and reporting
Expansion Roadmap
Phase 2: Salon Partnerships
- ✓ Partner with existing salons and reserve seats for Zenvee bookings
- ✓ Give customers a professional meeting environment without full ownership cost
- ✓ Let eligible technicians rent seats without committing to a full salon lease
- ✓ Extend the same marketplace into venue-backed fulfillment
Phase 3: Zenvee Destinations
- ✓ Launch branded Zenvee locations for premium service delivery
- ✓ Allow technicians to rent seats or stations directly when preferred
- ✓ Build long-term brand control and recurring venue revenue
Two-Sided Safety Model
Core Policy
Technicians should never be forced into unsafe or unknown appointments. Customers can state a preferred location, but technicians control which environments they support. A booking should only lock once both sides align on the same destination and the technician accepts the customer.
Preference Matching Rule
The marketplace should route requests toward technicians who already support the customer's preferred environment. If a technician does not accept that environment, they may decline or suggest another supported option. If there is no agreement, the request should continue through the network until a technician matches the customer's preference or the customer accepts an alternative.
Luxury rule: Luxury bookings should only route into approved physical salon environments. They should not be offered for in-home or uncontrolled appointment settings.
Schedule transparency rule: If a technician has already accepted other customers, those bookings should appear as blocked time on the technician's schedule. Customers should only be able to choose open slots after environment alignment, and confirmed bookings should be inserted into the technician's visible queue. Queue position and estimated wait can also be shown so the customer can decide whether the remaining schedule works for them.
Customer Credibility Model
The app should establish credibility for customers as well as technicians. Every active customer profile should carry an ID Verified status once identity checks are completed. Technicians should see trust-relevant customer profile data such as ID verification, payment verification, rating history, prior completed bookings, and preferred environments. Raw sensitive documents should stay private; the platform should expose verification status, trust score, and booking behavior instead.
ID Verified Policy
| Step | Requirement |
|---|---|
| 1 | Customer uploads a government-issued ID |
| 2 | Customer completes selfie and liveness verification |
| 3 | System validates document authenticity and readability |
| 4 | System checks that identity name aligns with payment profile details |
| 5 | If automation is inconclusive, route to manual review instead of silent rejection |
Operational rule: Customers can register before verification is complete, but protected booking types should require ID Verified status before activation. Failed or suspicious checks should move the account into review or restriction.
Safety Controls
| Control | Purpose |
|---|---|
| Customer verification tiers | Start with ID Verified as the baseline trust requirement, then add more controls for higher-risk bookings |
| Customer trust profile | Gives technicians enough verified detail to make an informed acceptance decision |
| Mutual acceptance | Lets technicians review customers and confirm only when both sides agree on the environment |
| Location-mode preferences | Lets customers request and technicians accept or suggest customer home, approved site, salon, or destination |
| Unsafe address and incident reporting | Flags risky customers, homes, or interactions for review |
| SOS and live safety tooling | Provides check-in, emergency contact sharing, and escalation options |
Matching Rules
| Rule | Purpose |
|---|---|
| Environment match first | Prioritize technicians who already support the customer's preferred setting |
| Availability and schedule fit | Only present technicians who can actually fulfill the requested slot |
| Geographic and venue fit | Rank technicians and venues that reduce travel friction |
| Service compatibility | Ensure the technician offers the requested service type |
| Trust and quality ranking | Boost reliable technicians with strong ratings and completion history |
| Safety filters | Exclude blocked, unsafe, or unsupported customer/location combinations |
Booking States
| State | Meaning |
|---|---|
| draft | Customer is preparing the booking request |
| requested | Request submitted with preferred environment |
| candidate_selected | Customer selected a technician candidate |
| pending_technician_response | Technician is reviewing the request |
| counter_offered | Technician proposed a different supported environment |
| pending_customer_response | Customer is reviewing the counter-offer |
| confirmed | Both sides agreed and payment is authorized |
| rerouting | System is moving the request to another technician |
| in_progress | Service has started |
| completed | Service finished successfully |
| cancelled | Booking was cancelled |
| expired | Request timed out without agreement |
| no_match | No eligible technician could accept current criteria |
Acceptance and Counter-Offer Flow
The customer chooses a technician from ranked matches. The technician then reviews the request and either accepts it as-is, declines it, or counter-offers with another supported environment. The booking only becomes confirmed once both sides agree on the same setting and payment is successfully authorized.
Edge Cases
- Timeout: If the technician does not respond within the response window, the request expires for that technician and reroutes.
- Reroute: The system should try the next best eligible technician while preserving the customer's original preference when possible.
- No Match: If no technician fits the request, the app should propose alternate times, environments, or venue types.
- Payment Failure: No booking should move to confirmed without payment authorization.
- Safety Block: Unsafe addresses, customers, or unsupported risk levels should stop or restrict routing.
Development Timeline (13 Weeks)
| Phase | Timeline | Key Deliverables |
|---|---|---|
| Phase 0 Setup |
Weeks 1-2 | Infrastructure, DB schema, API specs, CI/CD |
| Phase 1 API & Auth |
Weeks 3-5 | Authentication, user profiles, service catalog |
| Phase 2 Booking Engine |
Weeks 6-8 | Booking creation, matching algorithm, mutual acceptance, real-time updates |
| Phase 3 Customer App |
Weeks 6-9 | Booking UI, tracking, profiles (parallel with Phase 2) |
| Phase 4 Tech App |
Weeks 8-10 | Verification, availability, earnings dashboard |
| Phase 5 Payments |
Weeks 8-9 | Stripe integration, payouts, technician tiers, payout rules |
| Phase 6 Verification |
Weeks 10-11 | Admin dashboard, verification queue, compliance |
| Phase 7 Ratings & Reputation |
Week 11 | Review system, trust scores, badges |
| Phase 8 Notifications |
Weeks 11-12 | Push notifications, SMS, in-app messaging, safety alerts |
| Phase 9 Testing & QA |
Week 12 | Unit tests, integration tests, security audit |
| Phase 10 App Store Launch |
Week 13 | iOS App Store & Google Play submission |
| Phase 11 Salon Partnerships |
Months 4-8 | Partner salon onboarding, seat inventory, venue-aware booking |
| Phase 12 Destinations |
Months 8+ | Branded locations, station rentals, destination operations |
Financial Model
Revenue Model
- Primary: Technician-first payout model with blended platform share by service channel
- Secondary: Premium technician tier, advertising, subscriptions
Cash Payment Policy
Cash bookings: Customers can pay cash, but the technician collects that money directly at service time. Zenvee still records the booking amount, tip, and cash method, and still tracks the platform commission owed on that booking.
- Technician keeps collected cash: No platform disbursement is needed for the service amount
- Platform still earns its share: Commission is reconciled through future payouts or technician settlement
- Safer rollout: Cash should be limited to technicians in good standing until reconciliation controls are proven
Seat Rental Strategy
| Model | Use Case | Why It Matters |
|---|---|---|
| Partner salon seats | Phase 2 expansion | Tests demand for professional environments without heavy fixed real estate risk |
| Zenvee-owned seats | Phase 3 destinations | Adds brand control, recurring rental income, and premium service capacity |
Technician Seat Access Rules
- Eligibility: Verified technicians in good standing with strong trust and completion history
- Pricing options: Per-use, day-rate, monthly seat rental, or blended rent-plus-commission
- Capacity logic: Prioritize technicians whose booking volume and quality justify scarce seats
Technician Payout Strategy
| Channel | Technician Share | Platform Share | Purpose |
|---|---|---|---|
| Marketplace baseline | 70% | 30% | Primary recruiting advantage over salons |
| Top-rated technicians | 75% | 25% | Reward retention, service quality, and demand |
| Recurring / relationship-based clients | 80% | 20% | Protect loyalty and keep clients on-platform |
| Salon partnership services | 65-70% | 30-35% | Supports venue costs without reverting to 60/40 |
Tip policy: Customers can tip at checkout or after service, and 100% of that tip goes to the technician. Zenvee does not take commission on tips, so tip income strengthens technician incentives without being counted as platform revenue.
Cash handling note: If a booking is paid in cash, the technician collects the money directly. Zenvee should still log the service amount and platform share, then reconcile the platform commission through future payouts or scheduled settlement.
Progression model: Technicians see the full ladder up front. They start at 70/30, can move to 75/25 by proving quality and repeat demand, and can reach 80/20 when they become high-trust, high-retention supply on the platform.
Unit Economics Example
Customer Books: $30 Manicure
Traditional salon 60/40:
Technician earns: $18
Salon keeps: $12
Zenvee marketplace 70/30:
Technician earns: $21
Platform keeps: $9
Technician gain vs. salon: +$3 per booking
CAC: $2-5 | LTV: $200-400 | Payback: 1-2 months
Traditional salon 60/40:
Technician earns: $18
Salon keeps: $12
Zenvee marketplace 70/30:
Technician earns: $21
Platform keeps: $9
Technician gain vs. salon: +$3 per booking
CAC: $2-5 | LTV: $200-400 | Payback: 1-2 months
$50 Service Example
Marketplace baseline:
Technician payout (70%): $35
Platform share (30%): $15
Expert / loyalty tier:
Technician payout (75-80%): $37.50-$40
Platform share (20-25%): $10-$12.50
Technician payout (70%): $35
Platform share (30%): $15
Expert / loyalty tier:
Technician payout (75-80%): $37.50-$40
Platform share (20-25%): $10-$12.50
$50 service with $10 tip:
Technician service payout: $35
Technician tip payout: $10
Platform share: $15
Tip money is fully technician-owned and excluded from platform revenue.
Technician service payout: $35
Technician tip payout: $10
Platform share: $15
Tip money is fully technician-owned and excluded from platform revenue.
Founder-Led Year 1 Budget
| Category | Budget |
|---|---|
| Product development and contractor support | $35K |
| Cloud, software, and third-party tools | $12K |
| Marketing and launch acquisition | $28K |
| Legal, insurance, and business admin | $10K |
| Support and operations buffer | $8K |
| Contingency reserve | $7K |
| Total | $100K |
Scaled Operating Costs (Monthly, Estimated)
| Cost Category | Range |
|---|---|
| Cloud Infrastructure (AWS/Azure) | $1.5K-4K |
| Third-Party Services (combined vendor stack) | $500-3K |
| Development Team | $15K-25K |
| Marketing & User Acquisition | $5K-10K |
| Total Monthly | $24K-42K |
Third-party cost note: Stripe is generally usage-based, not a flat monthly charge. Payment processing costs usually scale as a percentage of each customer payment plus a fixed fee per transaction. Higher monthly third-party totals only make sense when payment fees are combined with verification vendors, maps, SMS, fraud tools, and software subscriptions.
Break-Even Projection
Year 1 assumption: $50 average booking, 27% average platform share, and ~$8,333 monthly burn from a $100K annual budget.
Gross revenue per booking: $13.50
Mathematical break-even: ~618 bookings/month
Practical target: 700-800 bookings/month
Recommended operating goal: ~750 bookings/month to absorb normal variance
Gross revenue per booking: $13.50
Mathematical break-even: ~618 bookings/month
Practical target: 700-800 bookings/month
Recommended operating goal: ~750 bookings/month to absorb normal variance
Marketplace target at ~750 bookings/month:
~1,500 active monthly customers if each books 0.5 times/month
~25 active technicians at 30 bookings/month each
Safer staffing target: 30-35 active technicians
Estimated app acquisition target: 7,500-10,000 customer downloads and 60-100 technician downloads/applications
~1,500 active monthly customers if each books 0.5 times/month
~25 active technicians at 30 bookings/month each
Safer staffing target: 30-35 active technicians
Estimated app acquisition target: 7,500-10,000 customer downloads and 60-100 technician downloads/applications
Seat-rental note: Partner and destination seat revenue can improve unit economics once usage is proven, but seat inventory should be added carefully after marketplace demand is validated.
Risk Mitigation & Success Factors
Key Risks & Mitigation Strategies
| Risk | Impact | Mitigation |
|---|---|---|
| Quality Control | Customer dissatisfaction | Rigorous verification, rating system, support |
| Regulatory Changes | Legal liability | Monitor regulations, build compliance flexibility |
| Tech Onboarding | Slow network growth | Streamlined verification, clear incentives |
| Payment Fraud | Financial loss | Stripe fraud detection, transaction monitoring |
| Data Breach | Privacy violation | Encryption, SOC 2 compliance, audits |
| Technician Churn | Network depletion | Competitive payouts, transparent tiers, support, reputation system |
Critical Success Factors
- Quality Technician Network: Rigorous onboarding and continuous quality monitoring
- Customer Satisfaction: Reliable service delivery, responsive support
- Regulatory Compliance: Proactive legal management across regions
- Financial Discipline: Monitor unit economics closely, achieve profitability quickly
- Technology Excellence: Reliable platform with minimal downtime
- Brand Reputation: Strong reviews and word-of-mouth growth
Success Metrics & KPIs
User Acquisition & Engagement
| Metric | Target (6 months) |
|---|---|
| Monthly Active Users (MAU) | 5,000-10,000 |
| Technicians on Platform | 500-1,000 |
| Monthly Bookings | 2,000-5,000 |
| Customer Repeat Rate | 35-40% |
| App Store Rating | 4.5+ stars |
Quality & Satisfaction
| Metric | Target |
|---|---|
| Average Booking Rating | 4.5/5.0 |
| Booking Completion Rate | 95%+ |
| Customer NPS Score | 50+ |
| Technician NPS Score | 45+ |
Financial Performance
| Metric | Target (12 months) |
|---|---|
| Monthly Revenue | $50K-100K |
| Customer Acquisition Cost | $3-5 |
| Platform Take Rate | 20-30% |
| Path to Profitability | 6-9 months |
Next Steps & Recommendations
Immediate Actions (This Month)
Week 1
Secure funding/resources, hire core team (2-3 backend, 2-3 mobile devs)
Week 1-2
Finalize technical architecture, set up development infrastructure
Week 2-3
Begin database schema and API development
Monthly Milestones
- Month 1-2: Core backend, mobile app shells, verification system
- Month 3-4: Complete mobile features, payment integration, real-time workflows, and testing
- Month 5: Closed beta testing, App Store preparation, and soft launch planning
- Month 6: Limited-city beta launch, feedback collection, and operating refinement