PRD

Tovali - Community-Based Services Platform

Product Requirements Document (PRD)

Version: 1.0
Date: January 2025
Project: Tovali Community Services Platform
Team: Yarom Cohen (CEO), Tomer Misk (CTO)


1. App Overview and Objectives

Vision Statement

Build a dynamic, accessible, and efficient community platform for everyday services while enabling income opportunities for community members, serving users from ages 3-120 with extreme accessibility focus.

Business Objectives

  • Phase 1 (Q1-Q2 2025): Establish 500 service requesters and 500 service providers in Moshav Dan area
  • Phase 2 (Q3-Q4 2025): Introduce subscription-based monetization and expand geographically
  • Phase 3 (2026): Implement commission-based revenue model and achieve national market presence
  • Long-term: Expand internationally while maintaining first-mover advantage in Israeli market

Value Proposition

For Service Requesters: Find reliable, available help for daily tasks through simple interface with verified community members For Service Providers: Access flexible income opportunities without traditional employment constraints while building community reputation


2. Target Audience

Primary User Segments

Service Requesters

  • Demographics: Ages 3-120, all technical skill levels, Israeli residents
  • Motivations: Prioritize convenience over cost, seek reliable help with daily tasks
  • Behaviors: Currently use neighborhood Facebook groups for service discovery
  • Pain Points: Unorganized service discovery, lack of trust mechanisms, technical barriers

Service Providers

  • Demographics: Freelancers, students, delivery drivers, community members seeking flexible income
  • Motivations: Flexible work opportunities, community connection, reputation building
  • Behaviors: Offer services through social media posts, direct networking
  • Pain Points: Limited visibility, trust-building challenges, payment coordination difficulties

Geographic Targeting

  • Phase 1: Moshav Dan area (local community focus)
  • Phase 2: Adjacent Israeli neighborhoods and communities
  • Phase 3: National Israeli market
  • Future: International expansion

3. Core Features and Functionality

3.1 User Authentication & Verification System

Gmail Authentication Integration

  • OAuth 2.0 implementation using Google Sign-In
  • Automatic profile creation with Google account data
  • Session management with JWT tokens
  • Acceptance Criteria: Users can sign in with Google account, maintain persistent sessions across app restarts

Multi-Step Verification Process

  • Service Providers: Required to upload profile photo and government ID document
  • Service Requesters: Encouraged but not required for basic verification
  • Background Checks: Criminal history verification for service providers
  • Manual Review: Company oversight for initial profile approvals
  • Acceptance Criteria:
    • Service providers cannot offer services until verification complete
    • ID document upload supports common Israeli ID formats
    • Manual review completed within 48 hours of submission

3.2 Service Request and Discovery System

Service Posting Interface

  • Simple form-based service request creation
  • Required Fields: Service type, description, location, preferred timing, budget range
  • Optional Fields: Photos, specific requirements, recurring schedule
  • Voice-to-text input support for accessibility
  • Acceptance Criteria: Users can create service requests in under 3 minutes, support voice input

Service Provider Discovery

  • Location-based matching algorithm prioritizing proximity
  • Service category filtering and search functionality
  • Provider availability calendar integration
  • Acceptance Criteria: Display relevant providers within 5km radius, filter by availability and rating

Service Categories (Initial MVP Focus)

  • Household tasks (cleaning, organization)
  • Delivery and errands
  • Pet care and walking
  • Garden and outdoor maintenance
  • Tech support and setup
  • Future Expansion: Childcare, elderly assistance, professional services

3.3 Communication System

In-App Chat Platform

  • Real-time messaging between requesters and providers
  • Company Oversight: Platform monitoring capability for safety
  • Photo and document sharing capabilities
  • Message history and archival system
  • External Migration: Users can move to WhatsApp/cellular after initial contact
  • Acceptance Criteria:
    • Messages delivered within 2 seconds
    • Photo sharing supports formats up to 10MB
    • Chat history accessible for 6 months

Service Coordination Tools

  • Availability calendar sharing
  • Appointment scheduling and confirmation
  • Service progress updates and photo documentation
  • Automated reminder system
  • Acceptance Criteria: Calendar integration works with Google Calendar, automated reminders sent 24 and 2 hours before service

3.4 Rating and Trust System

Dual-Rating Mechanism

  • Service requesters rate providers after service completion
  • Service providers rate requesters for cooperation and payment
  • Rating Scale: 1-5 stars with written feedback option
  • Trust Building: Accumulated ratings build community reputation
  • Acceptance Criteria: Both parties must rate within 48 hours of service completion

Profile Reputation Display

  • Average rating display with total number of reviews
  • Recent feedback highlighting
  • Badge system for highly-rated providers
  • Dispute Resolution: Flagging system for inappropriate behavior
  • Acceptance Criteria: Profile pages display average rating, total reviews, and recent feedback prominently

3.5 Pricing and Payment Coordination

Market-Driven Pricing System

  • Service providers set their own rates
  • Pricing Display: Hourly rates, flat fees, or custom quotes
  • Price Negotiation: Built-in messaging for rate discussion
  • Market Feedback: Platform provides pricing guidance based on category averages
  • Acceptance Criteria: Pricing clearly displayed before service booking, negotiation tracked in chat history

Payment Processing (Phase 3 Implementation)

  • Current State: Direct payment between users outside platform
  • Future State: Integrated payment processing with commission collection
  • Multiple payment methods (credit card, bank transfer, digital wallets)
  • Automatic receipt generation and tax documentation
  • Acceptance Criteria: Payment processing completes within 10 seconds, receipts automatically generated

4. Technical Stack Recommendations

Development Platform

Primary: Base 44 NoCode Platform

  • Justification: Enables rapid development with comprehensive capabilities
  • Mobile App Generation: Native-like performance through NoCode compilation
  • Web Platform: Responsive design for desktop and mobile browsers
  • Integration Capabilities: API connections for third-party services

Backend Infrastructure

Database: Base 44 integrated database system

  • User Profiles: NoSQL document structure for flexibility
  • Service Requests: Relational structure for queries and matching
  • Chat Messages: Time-series optimized storage
  • File Storage: Cloud-based storage for photos and documents

Authentication Services

Google OAuth 2.0: Primary authentication method

  • Implementation: Google Sign-In SDK integration
  • Session Management: JWT token-based with refresh capability
  • Security: HTTPS enforcement, token encryption

Third-Party Integrations

ChatGPT API: Application design guidance and user support Google Maps API: Location services and proximity calculations Cloud Storage: Document and photo upload management Email Services: Notification and verification email delivery


5. Conceptual Data Model

User Entity

Users {
  id: string (primary key)
  google_id: string (unique)
  email: string (unique, indexed)
  name: string
  profile_photo: string (URL)
  phone: string
  location: {
    address: string
    coordinates: [latitude, longitude]
    neighborhood: string
  }
  user_type: enum [requester, provider, both]
  verification_status: enum [unverified, pending, verified, rejected]
  created_at: timestamp
  updated_at: timestamp
}

Service Provider Profile Entity

ServiceProviders {
  user_id: string (foreign key)
  id_document_url: string
  background_check_status: enum [pending, approved, rejected]
  service_categories: array[string]
  hourly_rates: object {
    category: price_range
  }
  availability_calendar: object
  rating_average: decimal
  total_reviews: integer
  verification_documents: array[string]
  created_at: timestamp
}

Service Request Entity

ServiceRequests {
  id: string (primary key)
  requester_id: string (foreign key)
  title: string
  description: text
  category: string (indexed)
  location: {
    address: string
    coordinates: [latitude, longitude]
  }
  budget_range: {
    min: decimal
    max: decimal
  }
  preferred_timing: object {
    start_date: date
    end_date: date
    time_slots: array[time_range]
  }
  status: enum [open, in_progress, completed, cancelled]
  photos: array[string] (URLs)
  recurring: boolean
  created_at: timestamp
}

Chat System Entity

Conversations {
  id: string (primary key)
  service_request_id: string (foreign key)
  participants: array[user_id]
  created_at: timestamp
}

Messages {
  id: string (primary key)
  conversation_id: string (foreign key)
  sender_id: string (foreign key)
  message_text: text
  attachments: array[string] (URLs)
  message_type: enum [text, photo, system]
  timestamp: timestamp
}

Rating System Entity

Reviews {
  id: string (primary key)
  service_request_id: string (foreign key)
  reviewer_id: string (foreign key)
  reviewee_id: string (foreign key)
  rating: integer (1-5)
  feedback: text
  review_type: enum [requester_to_provider, provider_to_requester]
  created_at: timestamp
}

6. UI Design Principles

Accessibility-First Design

Age Range 3-120 Support

  • Font Sizes: Minimum 16px with scalable options up to 24px
  • High Contrast Mode: WCAG 2.1 AAA compliance
  • Simple Navigation: Maximum 3 taps to reach any feature
  • Voice Input: Speech-to-text for all text input fields
  • Visual Indicators: Clear icons with text labels

Mobile-First Responsive Design

Screen Size Optimization

  • Primary: Mobile screens 375px-414px width
  • Secondary: Tablet and desktop responsiveness
  • Touch Targets: Minimum 44px for all interactive elements
  • Thumb-Friendly: Important actions within thumb reach zones

Language Support

Multi-Language Interface

  • Primary: Hebrew (right-to-left layout support)
  • Secondary: Arabic, English
  • Dynamic Switching: Language selection without app restart
  • Cultural Adaptation: Date formats, currency display

Screen Flow Design

Service Requester Flow

  1. Home Screen: Service categories and recent requests
  2. Request Creation: Step-by-step form with progress indicator
  3. Provider Discovery: List view with filtering options
  4. Communication: Integrated chat with service details sidebar
  5. Service Tracking: Progress updates and completion confirmation

Service Provider Flow

  1. Dashboard: Available requests and earnings summary
  2. Request Browse: Location-based list with filtering
  3. Profile Management: Verification status and service categories
  4. Calendar Management: Availability and scheduled services
  5. Communication: Chat with request details and navigation

7. Security Considerations

Data Protection Framework

Privacy Compliance

  • GDPR Compliance: EU citizen data protection
  • Israeli Privacy Law: Local regulatory compliance
  • Data Minimization: Collect only necessary information
  • User Consent: Explicit consent for data collection and usage

Platform Safety Measures

User Verification Security

  • Document Encryption: ID documents encrypted at rest and in transit
  • Background Checks: Integration with Israeli criminal history databases
  • Manual Review Process: Human verification for initial profiles
  • Fraud Detection: Automated flagging of suspicious activity patterns

Communication Security

Chat System Protection

  • Message Encryption: End-to-end encryption for sensitive communications
  • Content Moderation: AI-powered inappropriate content detection
  • Reporting Mechanisms: Easy reporting for harassment or misconduct
  • Company Oversight: Platform monitoring capability for safety investigations

Payment Security (Phase 3)

Financial Transaction Protection

  • PCI DSS Compliance: Credit card data handling standards
  • Secure Payment Processing: Third-party payment processor integration
  • Fraud Prevention: Machine learning-based transaction monitoring
  • Dispute Resolution: Automated and manual dispute handling processes

8. Development Phases and Milestones

Phase 1: Foundation & Trust Building (Q1-Q2 2025)

Milestone 1.1: Core Platform Development (Month 1-2)

  • User registration and Gmail authentication
  • Basic service request creation and browsing
  • Simple chat system implementation
  • Manual verification process setup
  • Acceptance Criteria: Users can register, create requests, and communicate

Milestone 1.2: Trust & Safety Implementation (Month 2-3)

  • ID document upload and verification system
  • Rating and review system
  • Background check integration
  • Community guidelines and reporting features
  • Acceptance Criteria: Verification process operational, safety measures active

Milestone 1.3: MVP Launch and Testing (Month 3-4)

  • Beta testing with 50 early adopters
  • Performance optimization and bug fixes
  • Legal compliance finalization
  • Local community partnership establishment
  • Acceptance Criteria: Stable platform supporting 100 concurrent users

Phase 1 Success Metrics:

  • 500 registered service requesters
  • 500 registered service providers
  • 80% user verification completion rate
  • 4.5+ average platform rating

Phase 2: Scale & Monetization (Q3-Q4 2025)

Milestone 2.1: Subscription System Development (Month 5-6)

  • Payment processing integration
  • Tiered subscription plans for service providers
  • Premium feature access controls
  • Subscription management dashboard
  • Acceptance Criteria: Service providers can subscribe and access premium features

Milestone 2.2: Geographic Expansion (Month 6-7)

  • Multi-region service categorization
  • Location-based matching optimization
  • Regional community management tools
  • Localized marketing campaign support
  • Acceptance Criteria: Platform operates in 3+ geographic regions

Milestone 2.3: Advanced Features Implementation (Month 7-8)

  • AI-powered provider recommendations
  • Recurring service scheduling
  • Enhanced communication tools
  • Performance analytics dashboard
  • Acceptance Criteria: Advanced features increase user engagement by 40%

Phase 2 Success Metrics:

  • 25% service provider subscription rate
  • 3x geographic market expansion
  • 90% user retention rate
  • Break-even on operational costs

Phase 3: Commission Model & National Expansion (2026)

Milestone 3.1: Transaction Processing System (Month 9-10)

  • Commission-based payment implementation
  • Multi-payment method support
  • Automatic fee calculation and collection
  • Financial reporting and tax documentation
  • Acceptance Criteria: Platform processes payments with <1% error rate

Milestone 3.2: National Scale Infrastructure (Month 11-12)

  • High-availability server architecture
  • Advanced security and fraud prevention
  • National marketing and brand presence
  • Enterprise customer acquisition
  • Acceptance Criteria: Platform supports 10,000+ concurrent users nationally

Phase 3 Success Metrics:

  • National market presence across major Israeli cities
  • Sustainable commission-based revenue model
  • Market leadership position in non-professional services
  • International expansion readiness

9. Potential Challenges and Solutions

Technical Challenges

Challenge: NoCode Platform Limitations

  • Risk: Advanced features may require custom development
  • Solution: Plan hybrid approach with custom integrations where necessary
  • Mitigation: Regular platform capability assessment and backup development options

Challenge: Scalability Bottlenecks

  • Risk: Manual verification processes limit growth
  • Solution: Implement automated verification stages with manual review for edge cases
  • Mitigation: Build scalable verification workflow from Phase 1

Challenge: Real-Time Communication Reliability

  • Risk: Chat system performance under load
  • Solution: Implement message queuing and redundancy systems
  • Mitigation: Load testing throughout development phases

Market Challenges

Challenge: Dual-Sided Marketplace Dynamics

  • Risk: Chicken-and-egg problem for user acquisition
  • Solution: Focus on service provider recruitment first, then drive requester demand
  • Mitigation: Community-based marketing leveraging existing social networks

Challenge: Trust Building in New Platform

  • Risk: Users prefer established social media connections
  • Solution: Comprehensive verification system and community reputation building
  • Mitigation: Partnership with local community leaders and existing groups

Challenge: Competition from Free Alternatives

  • Risk: Facebook groups and direct networking remain popular
  • Solution: Demonstrate clear value through convenience, safety, and organization
  • Mitigation: Focus on unique value propositions that free alternatives cannot provide

Business Challenges

Challenge: Monetization Timing

  • Risk: Delayed revenue generation affects sustainability
  • Solution: Conservative cash flow planning and milestone-based investor updates
  • Mitigation: Multiple revenue stream development and flexible pricing strategies

Challenge: Regulatory Compliance

  • Risk: Changing regulations for marketplace platforms
  • Solution: Proactive legal consultation and compliance framework development
  • Mitigation: Regular legal review and adaptable platform architecture

10. Future Expansion Possibilities

Feature Enhancement Roadmap

Advanced AI Integration

  • Service Matching: Machine learning algorithms for optimal provider-requester matching
  • Dynamic Pricing: AI-powered pricing recommendations based on demand and supply
  • Predictive Analytics: Service demand forecasting and provider scheduling optimization
  • Customer Support: Chatbot integration for common questions and issue resolution

Enterprise Services

  • Corporate Accounts: Business customer management for recurring services
  • Bulk Service Coordination: Multiple service request management
  • Integration APIs: Connection with property management and facility services
  • Corporate Reporting: Service utilization and cost analysis dashboards

Social Features

  • Community Forums: Knowledge sharing and discussion spaces
  • Service Provider Networking: Professional development and collaboration tools
  • Local Event Integration: Community event service coordination
  • Social Impact Tracking: Community benefit measurement and reporting

Geographic Expansion Strategy

Phase 1 - Israeli Market Domination

  • Target Cities: Tel Aviv, Jerusalem, Haifa, Beer Sheva
  • Market Penetration: 70%+ market share in non-professional services
  • Local Partnerships: Integration with municipal services and community organizations

Phase 2 - Regional Expansion

  • Target Markets: Similar demographic regions in Eastern Mediterranean
  • Cultural Adaptation: Platform localization for different cultural contexts
  • Regulatory Navigation: Country-specific compliance and partnership strategies

Phase 3 - Global Platform

  • International Markets: English-speaking countries with similar service demands
  • Franchise Model: Local operator partnerships with platform licensing
  • Technology Export: White-label platform solutions for other markets

Technology Evolution

Mobile App Store Distribution

  • Native App Development: iOS and Android store-optimized applications
  • Offline Capabilities: Core features accessible without internet connection
  • Push Notifications: Real-time service updates and communication alerts
  • Device Integration: Camera, GPS, and calendar native integrations

Blockchain Integration

  • Trust Verification: Decentralized reputation and verification systems
  • Smart Contracts: Automated service agreements and payment processing
  • Token Economy: Platform token rewards for high-quality service providers
  • Data Ownership: User control over personal data and service history

Development Handoff Notes

Critical Implementation Considerations

NoCode Platform Optimization

  • Leverage Base 44's built-in mobile app generation capabilities
  • Implement custom CSS for accessibility requirements (font scaling, high contrast)
  • Use platform's API integration features for Google OAuth and third-party services
  • Plan for custom code injections where NoCode limitations exist

Database Design Priorities

  • Index frequently queried fields (location coordinates, service categories, user ratings)
  • Implement soft delete patterns for user data compliance
  • Design for horizontal scaling from Phase 1 to support future growth
  • Create proper foreign key relationships to maintain data integrity

Performance Benchmarks

  • Page load times under 3 seconds on 3G connection
  • Chat message delivery under 2 seconds
  • Search results rendering under 1 second
  • Image uploads processing under 10 seconds

Testing Requirements

  • Cross-browser compatibility testing (Chrome, Safari, Firefox)
  • Mobile device testing across iOS and Android versions
  • Load testing for concurrent user scenarios
  • Accessibility testing with screen readers and keyboard navigation
  • Security penetration testing for user data protection

API Documentation Requirements

  • Comprehensive endpoint documentation for future integrations
  • Rate limiting specifications for external API usage
  • Error handling and response code standardization
  • Version control strategy for API updates
  • Webhook implementation for real-time updates

This PRD serves as the comprehensive blueprint for Tovali's development, providing clear technical specifications while maintaining focus on user needs and business objectives. The phased approach allows for iterative development and validation while building toward the long-term vision of community-based service marketplace leadership.