Community Platform MVP Full-Stack Developer Needed

Cliente Freelancer · Remoto · Remoto · freelance · mid · 10.000–20.000 USD

Publicada el 2026-07-20

Descripción de la oferta

Have A Seat – Web-First Community Platform MVP / Full-Stack Developer & Architect Needed Have A Seat – Web-First Community Platform MVP I am looking for an experienced full-stack developer/software architect to help build the Phase 1-3 MVP of Have A Seat, a privacy-first community platform focused on belonging, trusted relationships, family connection, learning spaces, creator communities, clubs, and legacy preservation. The current priority is a web-first, mobile-friendly community platform with reusable systems and configurable spaces. The MVP should be built as one shared platform, not separate custom builds for each community. Core Phase 1 MVP Features 1. User Accounts & Authentication - Sign up / login - Basic profile/account settings - Membership level access - Role-based permissions 2. Front Door / Arrival Experience - Users should feel like they are arriving somewhere meaningful, not just landing in an empty feed - Warm welcome experience - “Find Your Seat” onboarding flow - Ava – Your Guide / AI-assisted welcome experience, if feasible for MVP 3. My Seat Home - Personal home/dashboard space - User’s main arrival area - Command board / welcome panel - Access to Bubbles, Tables, Commons, events, messages, and memberships 4. Bubbles Bubbles are a core feature. A Bubble is a user-managed relationship and permission layer. Users can create Bubbles for family, friends, creator members, students, clubs, or private groups. Bubble features should include: - Create/edit Bubble - Add/remove members - Per-person permissions - View/comment/post/invite permissions - Share content to selected Bubbles - Exclude specific people when sharing - Host moderation controls 5. Tables Tables are small intentional conversation/gathering spaces. MVP table features may include: - Create/join table - Table type/category - Member list - Basic chat/discussion - Host controls - Connection to Bubbles or Commons 6. Commons The Commons is the shared discovery/gathering area. MVP Commons features may include: - Public or semi-public gathering area - Interest-based tables - Community discovery - Simple navigation to example spaces 7. Creator / Learning / Club Space Foundation The MVP should support configurable Seat types rather than separate backend systems. Examples: - CreatorSeat - LearningSeat - ClubSeat - BusinessSeat - CommunitySeat These should share the same core backend foundation: - users - seats - roles - permissions - resources - tables - events - messages - memberships 8. Events / Basic Scheduling - Create events - View upcoming events - Connect events to Seats, Bubbles, Tables, or Commons 9. Admin / Owner Dashboard - Manage users - Manage communities/seats - Review reported content - Manage basic settings - View basic activity 10. Example Communities for Testing The platform should allow example communities to be configured using the core Seat system, such as: - Have A Seat Community Club - PTI LearningSeat example - Roots, Routes & Regiments example - Fantasy Football Club example These should be configurations of the shared system, not separate custom software builds. Important Architecture Requirement I do not want separate backend systems for each Seat type. The correct approach should be one unified backend with category-based configuration, shared data models, shared permissions, and different UI/feature toggles depending on the Seat type. For example: - CreatorSeat = category + permissions + UI - LearningSeat = category + permissions + UI - ClubSeat = category + permissions + UI - BusinessSeat = category + permissions + UI Technical Expectations Please recommend the best technology stack, but I am expecting something appropriate for a modern web platform, such as: - React / Next.js or similar frontend - Node.js / NestJS / Laravel / similar backend - PostgreSQL or equivalent database - Role-based access control - Secure authentication - Scalable cloud hosting - Mobile-responsive design - Clean API structure - Secure file/media handling What I Need First Before full development begins, I want an MVP Technical Blueprint based on my existing Master Blueprint. I do NOT need my full vision document rewritten. I need the developer/architect to translate my existing blueprint into: - Final Phase 1-3 MVP scope - Features to postpone - Technical architecture - Database structure - Permissions model - Development milestones - Testing plan - Timeline estimate - Revised build estimate Ideal Freelancer Please apply if you have experience with: - SaaS platforms - Community platforms - Membership/subscription systems - Role-based permissions - Social/community features - Real-time or semi-real-time chat/discussion tools - Creator platforms - Learning platforms - AI-assisted onboarding or AI integrations - Privacy-sensitive applications Please include: - Relevant portfolio - Similar projects - Suggested tech stack - Estimated Phase 1 timeline - Whether you prefer working independently or with another developer - What you would include in Phase 1 versus Phase 2 I am considering a phased approach. Target Phase 1 MVP budget: approximately $10k, depending on scope. Future phases may include: - Commons Passport - Seat Shopper - advanced Bookshelf / Memory Archive - Watch & Play Together - Root Routes & Regiments - advanced creator tools - advanced AI features - business memberships and storefront tools The goal is to build a strong Phase 1 foundation first, test with real users, and then expand based on feedback. The total is 3 Phases Goal Prove that people enjoy the Have A Seat experience and will return. Features Front Door Experience Ava Welcome Guide User Registration/Login Membership Plans My Seat Home Personal Dashboard Bubbles Tables Commons Events Notifications Basic Messaging CreatorSeat Foundation LearningSeat Foundation ClubSeat Foundation BusinessSeat Foundation Role-Based Permissions Admin Dashboard Mobile Responsive Design Beta Communities Have A Seat Community Club PTI Beta Community Roots, Routes & Regiments Beta Fantasy Football Club Beta Launch Goal Founders Circle Beta Launch Phase 2 – Community Growth & Engagement Goal Increase engagement and discovery. Features Commons Passport Expanded Commons Discovery Advanced Table Types Watch Together Spaces Stay While Spaces Enhanced Events Community Directories Interest Matching Creator Dashboards Learning Progress Tracking Bookshelf Phase 1 Shared Albums Shared Resource Libraries Improved Search Communities PTI Expansion Creator Communities Learning Communities Genealogy Communities Launch Goal Public Beta Phase 3 – Legacy, Business & Commerce Goal Expand into long-term sustainability and community ownership. Features Root Routes & Regiments Migration Trails Genealogy Workspaces Advanced Bookshelf Memory Archive Collaborative Family Books Seat Shopper Commons Storefronts Business Memberships Creator Monetization Tools Sponsored Access Programs AI Buddy AI Storytelling Assistance Advanced Analytics Community Templates Launch Goal Full Version 1.0 Architecture Across All Phases The key thing developers need to understand: One Platform Not: PTI software Genealogy software Football software Classroom software Creator software Instead: 1 One Platform 2 ├── Personal Seat 3 ├── Creator Seat 4 ├── Learning Seat 5 ├── Club Seat 6 ├── Business Seat 7 └── Community Seat Shared Systems: Users Memberships Roles Permissions Bubbles Tables Commons Events Resources Messaging Notifications Bookshelf Show more lines Different experiences are created through: Membership Levels Permissions Layouts Feature Toggles Community Configuration f you're posting for a Lead Architect / Full-Stack Developer, I would ask for these 10 core skills: 1. Software Architecture Ability to design scalable systems, databases, APIs, and platform structure. 2. Full-Stack Development Experience building both frontend and backend applications. 3. React / Next.js For the Have A Seat web interface, dashboards, Seat Home, Commons, and admin tools. 4. Node.js / NestJS (or equivalent backend) For APIs, permissions, memberships, events, and platform services. 5. PostgreSQL Database Design Strong relational database design for: Users Seats Bubbles Tables Events Memberships Permissions 6. Authentication & Security Experience with: Login systems User roles Access control Privacy-focused applications 7. SaaS Platform Development Have A Seat is essentially a SaaS community platform, so experience building subscription-based applications is important. 8. Community / Social Platform Experience Platforms involving: Communities Groups Forums Memberships Creator platforms Learning platforms 9. Cloud & Deployment Experience with: AWS Azure Vercel Cloudflare CI/CD pipelines Production deployments 10. AI Integrations Not advanced AI development necessarily, but experience integrating: OpenAI Azure OpenAI AI assistants Guided onboarding experiences Bonus Skills (Nice to Have) Stripe subscriptions Real-time chat WebSockets Video integrations (Zoom, Google Meet, YouTube) Learning Management Systems (LMS) Creator platform development Moderation tools Analytics dashboards

Skills

Fuente original: freelancer

Análisis JobHunter