AI Developer for Telemedicine Brand

Rise AI Growth Operating System Project Objective: Build a scalable AI-enabled growth operating system that unifies marketing, attribution, intake, communication, analytics, and Docible integration while minimizing disruption to the existing funnel. 1. Executive Summary The objective of this project is to transform Rise's current collection of disconnected tools into a unified growth platform that provides: • Full ownership of website and funnel infrastructure • End-to-end attribution visibility • AI-assisted marketing and lifecycle automation • Advanced intake analytics and abandonment recovery • Seamless GoHighLevel synchronization • Reliable Docible integration • Continuous optimization through analytics and AI insights To minimize risk and preserve current revenue-generating workflows, implementation will follow a phased migration strategy. Existing systems (Webflow, Embeddables, GoHighLevel, Docible) will remain operational while new infrastructure is introduced incrementally. The initial focus will be on establishing owned infrastructure and implementing AI-powered abandonment recovery, which offers the fastest path to measurable revenue impact. 2. Proposed Technology Architecture Frontend • Next.js 15 (App Router) • TypeScript • Tailwind CSS • ShadCN UI Backend • Node.js • Next.js API Routes / Server Actions • PostgreSQL Infrastructure • AWS o Amplify or ECS/Fargate o Route53 o CloudFront o S3 o ACM o RDS PostgreSQL CMS Recommended: • Payload CMS Alternative: • Builder.io • Sanity AI Layer • OpenAI API • Prompt Templates • Approval Workflow Integrations • GoHighLevel • Mobi Attribution • Embeddables (temporary) • Docible Analytics • PostgreSQL Event Store • Metabase / QuickSight 3. Phase 1 – Foundation & Infrastructure Objective: Establish owned infrastructure without disrupting current funnel performance. Deliverables: - AWS Environment • Production environment • Staging environment • Domain configuration • SSL certificates • Deployment pipeline - Core Application • Next.js application setup • Authentication system • Admin portal foundation • Environment management - Database Design Implementation of: • campaigns • creative_assets • ads • pages • page_variants • intake_flows • intake_questions • orders • docible_records • ghl_contacts • communication_events • events • ai_generations • approval_reviews - Event Tracking Framework Unified event model for: • Page views • CTA clicks • Intake progression • Checkout progression • Orders • Communication events Required Client Access: - AWS • AWS Account access • IAM user • Domain ownership - Existing Systems • Webflow access • GoHighLevel access • Mobi access • Embeddables access • Docible documentation Success Criteria: • Infrastructure deployed • Database operational • Authentication working • Event schema documented • Staging and production environments live 4. Phase 2 – Website & CMS Migration Objective: Replace Webflow with a scalable, editable website architecture. Deliverables: - CMS Setup • Payload CMS implementation • User roles • Draft/publish workflow - Website Migration • Homepage • Core marketing pages • Blog/resources (if applicable) - Landing Page Builder Reusable modules: • Hero sections • Testimonials • Offer sections • CTA blocks • FAQ sections - Advertorial Builder Reusable templates: • Long-form advertorials • Campaign-specific pages • SEO-friendly structures - Publishing Workflow • Preview mode • Draft mode • Publish mode • Version history Required Client Inputs: • Brand assets • Design guidelines • Existing Webflow content • Landing page inventory • Advertorial inventory Success Criteria: • Website fully hosted on AWS • CMS editing enabled • Content migration completed • No SEO degradation 5. Phase 3 – GoHighLevel Lifecycle Automation Objective: Create the first revenue-generating automation layer through lifecycle tracking and abandonment recovery. Deliverables: - GoHighLevel Integration Sync: • Contacts • Tags • Opportunities • Pipelines • Custom fields - Event Synchronization Implement: • lead_created • intake_started • intake_abandoned • intake_completed • checkout_abandoned • order_completed • refill_due • inactive_customer • docible_status_updated - Attribution Sync Pass: • UTM parameters • Campaign IDs • Creative IDs • Landing page identifiers • Mobi session IDs - Abandonment Recovery Automated workflows for: • Landing page abandonment • Advertorial abandonment • Intake abandonment • Checkout abandonment AI Features: Generate: • SMS drafts • Email drafts • Recovery messaging All AI-generated content requires human approval before activation. Success Criteria: • Real-time lifecycle updates • Accurate segmentation • Recovery campaigns operational • Attribution preserved 6. Phase 4 – AI Workbench Objective: Create internal AI tools that accelerate campaign production while maintaining human approval controls. Deliverables: - Campaign Generator Generate: • Campaign concepts • Audience targeting • Hooks • Offers - Creative Generator Generate: • Ad copy • Headlines • Video prompts • Creative briefs - Landing Page Generator Generate: • Landing page drafts • Campaign page drafts - Advertorial Generator Generate: • Long-form advertorial drafts • Editorial content structures - Communication Generator Generate: • SMS sequences • Email sequences • Onboarding campaigns • Winback campaigns - Approval Workflow • Review queue • Version tracking • Approval history • Publish controls Success Criteria: • AI drafts generated successfully • Approval system functioning • No automatic publishing 7. Phase 5 – Custom Intake Platform Objective: Replace Embeddables with a fully owned intake experience. Deliverables: - Intake Builder Support: • Multi-step forms • Conditional logic • Dynamic branching - Analytics Layer Track: • Viewed questions • Answered questions • Changed answers • Abandonment points • Completion rates - User Experience Features • Resume progress • Mobile optimization • Session persistence • Performance optimization - Security • Server-side validation • Secure storage • Compliance-ready architecture - Integrations • GoHighLevel • Checkout • Docible Migration Strategy: 1. Keep Embeddables active 2. Run custom intake in staging 3. Validate conversion parity 4. Gradually migrate traffic 5. Fully replace Embeddables Success Criteria: • Conversion rates maintained or improved • Question-level analytics available • Embeddables retired 8. Phase 6 – Docible Integration Objective Automate order and patient handoff processes while improving operational visibility. Deliverables: - Integration Layer Implement: • Patient creation • Order creation • Status synchronization - Webhook Processing Handle: • Status updates • Fulfillment updates • Order changes - Retry Framework Automatic recovery for: • API failures • Timeout failures • Network failures - Operations Dashboard Visibility into: • Sync status • Failed records • Retry queues • Processing history Required Client Inputs: • Docible API documentation • API credentials • Field mapping requirements • Clinical workflow requirements Success Criteria: • Successful patient/order sync • Reliable webhook processing • Operational dashboard available 9. Phase 7 – Analytics & Optimization Engine Objective: Create continuous improvement systems powered by analytics and AI insights. Deliverables: - Dashboard Suite Marketing Dashboard • Campaign performance • Creative performance • Attribution Funnel Dashboard • Landing pages • Advertorials • Intake analytics • Conversion tracking Recovery Dashboard • Recovery performance • Revenue attribution • Workflow performance Operations Dashboard • Docible status • Sync health • Order lifecycle - AI Insights Engine Weekly recommendations for: • Funnel improvements • Drop-off reduction • Campaign opportunities • Recovery optimization Success Criteria: • Executive reporting available • Optimization recommendations generated • End-to-end visibility established 10. Compliance & Security Considerations HIPAA / Privacy Review Required: Before launch: • PHI handling review • Vendor agreement verification • Data retention review • Security review AI Restrictions: AI systems must never: • Automatically publish patient-facing content • Store unnecessary PHI • Send clinical information to unauthorized systems Data Separation: Only lifecycle metadata should be synced to: • GoHighLevel • AI generation systems Unless compliance approval is explicitly provided. 11. Testing & Validation Strategy Development Testing: • Unit testing • Integration testing • API testing QA Testing: • Funnel testing • Attribution validation • Event validation • Form testing UAT: Client validation of: • Website editing • AI generation • GoHighLevel workflows • Intake flows • Docible handoff Production Rollout: Each phase follows: Development → Staging → QA → UAT → Production No direct deployment to production. 12. Risks & Assumptions Risks: - Third-Party API Limitations Potential impact: • Docible capabilities • GoHighLevel limitations • Mobi integration constraints - Compliance Requirements HIPAA requirements may affect: • AI workflows • Data storage • Communication automation - Existing Funnel Complexity Unknown customizations in: • Webflow • Embeddables • GoHighLevel may require additional discovery. Assumptions: • AWS account will be provided. • GoHighLevel API access is available. • Mobi supports session-level attribution identifiers. • Docible provides API and/or webhook access. • Client will approve AI-generated content prior to publishing.