Full-Stack Developer Needed to Complete and Launch Existing SaaS Application

Project Overview I am looking for an experienced full-stack developer to take an existing SaaS application called **TherapistOS** through final development, functional testing, and production launch. TherapistOS is an application I have been developing independently using Cursor, with Lovable used as a visual and component reference. The product concept, branding, navigation, feature structure, pricing model, and much of the user interface have already been established. I have reached the point where I need an experienced developer to take over the technical completion process, review the existing codebase, finish incomplete functionality, implement integrations, thoroughly test the application, and prepare it for public launch. **This is an existing application. I am not looking to have it rebuilt from scratch or redesigned.** I want to preserve the existing work and have a developer build on what is already there. I am looking for someone who can work independently, make sound technical decisions, communicate clearly, and take responsibility for getting the application production-ready. About TherapistOS **TherapistOS** *Your professional life, organized.* TherapistOS is a professional workspace designed for therapists and other behavioral health professionals. The purpose is to help users organize their professional responsibilities, tasks, projects, professional relationships, continuing education, business initiatives, and career development. It is not an EHR, practice management system, client CRM, or clinical documentation platform. It is not intended to store protected health information (PHI). Existing Application Structure The application has six main sections: **1. Home** - Professional workspace overview. - Priorities and upcoming activities. - Access to important areas of the application. **2. Plan** - Tasks and recurring tasks. - Priorities and due dates. - Projects and goals. - Categories and custom categories. - Today, This Week, Upcoming, Overdue, and All task views. - Calendar planning. **3. Connect** - Professional relationship tracking. - Referral sources and professional contacts. - Organizations, practices, collaborators, and networking contacts. - Contact details and relationship status. - Last contact and next follow-up. - Ability to create follow-up tasks. **4. Develop** - Continuing education organization. - Courses, trainings, conferences, books, and podcasts. - Certifications and license renewal dates. - Professional development goals. **5. Build** - Professional project management. - Business ideas and initiatives. - Workshops, websites, podcasts, courses, digital products, and marketing projects. - Project statuses and task breakdowns. **6. Explore** - Career exploration and professional development. - Alternative career directions. - Employment and entrepreneurship options. - Skills, interests, income goals, and work preferences. - Exploring opportunities while potentially retaining some clinical work. The intended Explore progression is: Explore → Compare → Investigate → Prepare → Test → Move. The application also includes an AI Planning Assistant that uses information from the user's workspace to help prioritize work, break down projects, and identify practical next steps. Current Development Status The application has been developed primarily in Cursor. Lovable has been used as a visual/component reference. The existing codebase is the source of truth. The application already has an established product direction, visual identity, navigation, page structure, and feature architecture. Some functionality may need completion, troubleshooting, or further implementation. The developer will need to review the actual repository to determine the current state of the backend, database, authentication, API functionality, and integrations. I can provide the existing source code, GitHub access, and access to the relevant development environments and services. Scope of Work Phase 1: Codebase Audit and Technical Assessment Begin by reviewing the existing application before making substantial changes. - Review the full codebase and existing architecture. - Identify the frontend and backend technologies. - Review database structure and data persistence. - Review authentication and account management. - Review existing API integrations. - Assess the current Stripe implementation. - Identify incomplete features, bugs, and security concerns. - Identify functionality that already works and should be preserved. - Identify anything preventing a reliable production launch. Provide a written technical assessment with prioritized launch blockers, recommended fixes, and an estimate of the remaining work. Do not rebuild or replace existing functionality without explaining why it is necessary and receiving approval. Phase 2: Complete Application Functionality Review and complete the existing application functionality. This includes: - User registration and authentication. - Login, logout, and password/account management. - Database persistence. - Creating, editing, completing, and deleting tasks. - Recurring tasks and due dates. - Projects and project statuses. - Goals and progress tracking. - Professional contact management. - Relationship statuses and follow-up tracking. - Professional development records. - Career exploration functionality. - User settings and preferences. - AI Planning Assistant. - Calendar functionality. - Appropriate loading, empty, success, and error states. Verify that information persists correctly between sessions and that users can only access their own account data. The AI Planning Assistant should be tested for its ability to use relevant workspace information, generate practical recommendations, break down projects, and allow users to review and edit suggested actions before adding them. Phase 3: Calendar Integrations Calendar functionality is an important part of TherapistOS. I want Google Calendar and Apple Calendar integrations fully implemented for launch. **Google Calendar** - Secure Google OAuth authentication. - Connect and disconnect Google accounts. - Request appropriate calendar permissions. - Retrieve and display relevant calendar events. - Allow users to add TherapistOS tasks and planning blocks to Google Calendar. - Handle authorization token storage and refresh. - Handle errors, expired connections, and revoked permissions. - Prevent duplicate event creation. - Ensure users can manage their calendar connection. **Apple Calendar** Evaluate and implement the appropriate integration approach for Apple Calendar users. This may involve CalDAV, calendar subscriptions, or another technically appropriate approach. Requirements include: - Allow users to get TherapistOS planning items into Apple Calendar. - Support the intended calendar connection workflow. - Clearly communicate any limitations. - Handle calendar updates and disconnections appropriately. Assess whether genuine two-way synchronization is technically feasible and appropriate for each provider. Clearly distinguish two-way synchronization from one-way calendar export or subscription. The goal is a usable calendar integration, not simply retaining the existing .ics download functionality. Calendar functionality is for professional planning, not patient scheduling. Phase 4: Free and Premium Subscription Functionality TherapistOS will have two subscription levels. **Free** - 3 active projects. - 25 active tasks. - 5 active goals. - Professional relationship tracking. - Unlimited affiliations. - Calendar export. - Core planning tools. **Premium** - Unlimited projects. - Unlimited tasks. - Unlimited goals. - Unlimited professional relationship tracking. - Unlimited affiliations. - Calendar planning. - AI Planning Assistant. Planned pricing: - $9.99/month. - $99/year. I need the developer to review and complete the Stripe integration. This includes: - Subscription checkout. - Successful and failed payment handling. - Subscription status management. - Subscription upgrades and downgrades. - Cancellation. - Subscription expiration. - Webhook processing. - Premium entitlement enforcement. - Return to Free plan when appropriate. - Accurate subscription status within the application. Premium restrictions must be enforced through the backend/API, not just by hiding frontend buttons. Test the complete subscription lifecycle using Stripe test mode before production. Phase 5: Mobile and Desktop Responsiveness The application needs to function well on mobile, tablet, and desktop. Specific mobile requirements: - All six navigation items must be visible simultaneously in the bottom navigation. - Bottom navigation must not horizontally scroll. - Top filter rows may swipe horizontally on mobile, with scrollbars hidden. - The page itself must never horizontally scroll. - Proper spacing and sizing at narrow mobile widths. - Appropriate mobile safe-area spacing. - Forms, menus, dialogs, and modals must work on smaller screens. - No clipped text, buttons, or controls. Test at approximately 320px, 360px, 390px, tablet, and desktop widths. The visual identity should be preserved. TherapistOS has an established warm, editorial design direction. Avoid generic SaaS redesigns, unnecessary gradients, excessive rounded cards, heavy shadows, or wholesale changes to the existing interface. Phase 6: Security, Privacy, and Account Management Review: - Authentication and authorization. - User data isolation. - Database access policies. - API security. - Server-side entitlement enforcement. - Secure handling of OAuth tokens. - Administrative permissions, if implemented. - Account deletion. - Data deletion behavior. - Appropriate handling of user-generated content. TherapistOS is not intended to store client information or PHI. Ensure the application does not introduce clinical documentation or client data functionality. Do not make claims of HIPAA compliance unless specifically implemented and independently verified. Phase 7: Production Preparation and Launch Once functionality and testing are complete: - Configure production environment variables. - Configure production database and services. - Configure production authentication. - Set up the custom domain and SSL. - Configure production Stripe credentials and webhooks. - Configure Google OAuth production settings. - Configure Apple Calendar integration as applicable. - Verify production email and notification functionality, if implemented. - Configure deployment and hosting. - Test account creation and login in production. - Test actual subscription checkout. - Verify calendar connections in production. - Resolve deployment issues. - Confirm the application is ready for public users. The intended public domain is TherapistOS's custom domain, rather than a Lovable subdomain. The exact domain configuration will be provided. Phase 8: Final Handoff I want to retain ownership and control of the application. The developer should provide: - Updated source code in my GitHub repository. - Database schema and migration documentation. - Environment variable documentation. - Deployment instructions. - Integration setup documentation. - Instructions for managing Stripe and subscriptions. - Instructions for maintaining and updating the application. - A summary of completed work and any remaining limitations. All code and development work must be committed to my repository. Features Deliberately Deferred The Affiliate Program is planned as a future feature. For launch, it should display: **Affiliate Program – Coming Soon** Do not build affiliate tracking, commissions, referral payouts, tax reporting, or affiliate financial infrastructure. Do not add unrelated features or expand the product scope. The priority is completing and launching the existing application. Required Technical Experience Applicants should have demonstrated experience with: - Full-stack SaaS application development. - React and TypeScript. - The existing project's backend and database technology. - Authentication and authorization. - API development. - Stripe subscriptions and webhooks. - Google Calendar API and OAuth. - Apple Calendar integration, CalDAV, or equivalent approaches. - Responsive mobile application development. - Application testing and debugging. - Production deployment and hosting. - Application security. Experience taking an existing application developed with Cursor, Lovable, or similar AI-assisted development tools into production is a plus. Working Arrangement and Milestones I prefer a milestone-based contract with individual deliverables and approval at each stage. **Milestone 1: Technical audit and completion plan** Review the existing repository and provide a written assessment, launch blockers, technical recommendations, and a fixed-price estimate for the remaining work. **Milestone 2: Application functionality** Complete the existing application functionality, fix bugs, and resolve backend and persistence issues. **Milestone 3: Integrations** Complete Google Calendar, Apple Calendar, Stripe, and related account functionality. **Milestone 4: Testing and security** Perform end-to-end testing, responsive testing, and security review. Resolve identified issues. **Milestone 5: Production launch** Configure production services, domain, integrations, and deployment. Test the live application. **Milestone 6: Final handoff** Provide documentation, updated repository, and instructions for ongoing maintenance. The remaining milestones and budgets will be finalized after the initial codebase assessment. Questions for Applicants Please answer the following when applying: 1. Describe your experience taking an existing SaaS application from development to production. 2. What experience do you have with Stripe subscription management and webhook implementation? 3. Have you implemented Google Calendar API integrations and Apple Calendar or CalDAV integrations? Please describe the functionality you built. 4. Are you comfortable taking over an existing codebase developed using Cursor and Lovable without rebuilding it? 5. How do you approach testing an existing application before launch? 6. Can you work through a GitHub repository owned by the client and commit all changes directly to it? 7. Please provide examples of SaaS applications you have developed or helped launch. What Success Looks Like The finished deliverable is a fully functional, tested, production-ready TherapistOS application. A user should be able to create an account, organize their professional life, manage projects and relationships, use the planning assistant, connect their calendar, choose a subscription, and use the application reliably on mobile and desktop. I want to move from independently developing the product to having a technically sound application that is ready for real customers. I am looking for a developer who can take ownership of the technical completion while respecting the existing product decisions and work already invested in the application.