Full-Stack Developer for Football Analytics Funnel — Next.js, Whop, Discord & Telegram

We are developing STATS, a worldwide consumer-facing football analytics platform for supporters, football enthusiasts and users interested in data-driven match probabilities. Our main analytics and prediction architecture is being developed separately. We are looking for a capable full-stack developer to build the acquisition, conversion, subscription and community-distribution system around it. This is not a bookmaker and will not accept or place bets. The platform will publish football analytics, probability outcomes, visualisations and match information. The successful developer will initially work with mocked JSON match and probability data through an agreed API contract. The system will later connect to the live STATS analytics engine. What We Want to Achieve We want to create a scalable customer journey: Google Search / Instagram / TikTok → Relevant match, team or league landing page → Useful free football analysis → Free account or community registration → Premium subscription offer → Whop checkout → Premium website, Discord and Telegram access The platform should eventually support multiple countries, languages, competitions and football leagues. Main Components 1. Public Acquisition Website Build a responsive public website containing scalable, search-friendly pages such as: - Individual match pages - Team analytics pages - League and competition pages - Tactical-analysis pages - Match probability pages - Educational football analytics content - Campaign-specific landing pages These pages should be generated from structured data while remaining useful, fast and search-engine friendly. Potential technologies include: - Next.js - TypeScript - Vercel - PostgreSQL - Server-side rendering or incremental static regeneration - Structured data - XML sitemaps - Reusable page templates The landing pages must work properly on desktop and mobile. 2. Customer Funnel Visitors should be able to: - Read useful free match information - Explore free charts and probability previews - Follow teams or leagues - Save matches - Request alerts - Create a free account - Join a free Discord or Telegram community - Discover premium features - Upgrade through Whop The funnel must be measurable so we can understand which landing pages, channels and calls to action produce registrations and paid customers. 3. Authenticated Web Platform Free and premium users should have accounts with different permissions. Potential features include: - User registration and authentication - Free and premium access levels - Saved teams, leagues and fixtures - Match dashboards - Probability and analytics displays - Alert preferences - Subscription status - Discord and Telegram connection status - Billing-management link - Secure premium-content protection 4. Whop Subscription Integration Whop will be used for checkout, recurring subscriptions and membership management. The integration should handle: - New memberships - Successful payments - Renewals - Failed payments - Cancellations - Reactivations - Refunds - Disputes - Website entitlement changes - Discord role/access changes - Telegram access changes Webhook handling must be secure and idempotent. Duplicate or out-of-order webhook events must not grant incorrect access or corrupt membership records. Customers should be able to manage their subscription through the appropriate Whop billing page. 5. Discord Integration We want free and premium Discord areas. The Discord system may include: - Automated match and probability posts - Rich embedded messages - Free and premium member roles - League or competition channels - Team-specific channels - Match discussion areas - Automated membership access - Commands such as /match, /probability or /explain - Logging and moderation support Whop may manage paid Discord roles and access. A custom STATS bot would primarily publish analytics, respond to commands and create interactive football experiences. 6. Telegram Integration The Telegram system may include: - Free public channel - Premium private channel - Automated probability updates - Match alerts - Lineup-change alerts - Links back to the full website analysis - Automated premium access - Access revocation when membership becomes inactive - Reliable message delivery and failure logging 7. Analytics and Attribution We need to measure the complete funnel, including: - Traffic source - Landing page visited - Country, language and device - Free-account registration - Team or league follows - Alert requests - Discord and Telegram joins - Premium-offer views - Whop checkout starts - Successful paid conversions - Renewals and cancellations - Retention by acquisition source The system should support controlled experiments with landing-page layouts, messages and calls to action. Any tracking must be implemented securely and with appropriate privacy controls. 8. Future Social Content Automation This may become a later phase rather than part of the first proof of concept. The future system may convert structured match information into short, original animated football videos for Instagram Reels and TikTok. The desired creative direction is an original classic football-comic aesthetic. It must not copy protected characters, artwork or branding belonging to existing football comics. The videos could automatically change: - Teams and colours - Fixture details - Probability figures - Tactical stories - Competition and language - Landing-page link - Call to action Experience with Remotion, programmatic video generation or social publishing APIs would be valuable but is not essential for the initial phase. We want a modular architecture. Probability calculations should happen only in the central STATS system. Discord, Telegram and the website should all receive consistent information from the same source. Suggested Technology We are open to professional recommendations, but experience with the following would be valuable: - TypeScript - Node.js - Next.js - NestJS or a comparable backend framework - PostgreSQL - Redis and BullMQ or comparable queue technology - REST APIs - Webhooks - Discord API - Telegram Bot API - Whop API - Vercel or comparable hosting - Authentication and role-based access - Analytics and conversion tracking - GitHub - Automated testing - Secure secret management You do not need experience with every technology if you can demonstrate strong development fundamentals and explain how you would approach unfamiliar components. Initial Paid Proof of Concept We do not expect one developer to build the complete global platform immediately. The first engagement should be a small paid proof of concept that: 1. Receives a mocked football probability event. 2. Validates and stores it in a database. 3. Displays it on a simple responsive web page. 4. Publishes it to a private Discord test channel. 5. Publishes it to a private Telegram test channel. 6. Simulates or processes a Whop membership event. 7. Changes a test user between free and premium access. 8. Safely handles a duplicate webhook event. 9. Records actions and failures in logs. 10. Includes setup and testing documentation. If the proof of concept is successful, the project can continue through agreed paid milestones. Expected Milestones A possible milestone structure is: Milestone 1: Technical Discovery - Review requirements - Recommend final technology - Define system boundaries - Define the API contract - Produce a short architecture plan - Identify risks, dependencies and assumptions Milestone 2: Proof of Concept - Mock probability feed - Basic database - Test web page - Discord publishing - Telegram publishing - Whop membership test - Logging and duplicate-event protection Milestone 3: Public Website and Landing Pages - Responsive website - Reusable match, team and league templates - Structured-data integration - Sitemap generation - Performance optimisation - Initial funnel analytics Milestone 4: Accounts and Premium Access - Authentication - Free and premium permissions - Whop checkout - Membership synchronization - Billing-management access - Secure premium-content protection Milestone 5: Community Integrations - Production Discord integration - Production Telegram integration - Automated access and revocation - Commands, rich messages and alert preferences - Rate-limit and failure handling Milestone 6: Testing and Deployment - Automated tests - Security checks - Performance testing - Production deployment - Monitoring and alerts - Technical documentation - Complete handover Future milestones may include internationalisation, additional leagues, experimentation tools and automated social-video production. Security and Ownership Requirements This platform will process customer accounts and payment-related membership events. Security is essential. We expect: - Verified webhook signatures - Idempotent event processing - Secure storage of API keys and bot tokens - Role-based access - Appropriate logging without exposing sensitive information - Database backups - Error handling and retry mechanisms - Automated tests for important access-control flows - Documentation of security assumptions - No secrets committed to source code All source code must be stored in company-owned repositories. Company-owned accounts will be used for: - Source-code hosting - Cloud deployment - Databases - Domains - Whop - Discord - Telegram - Analytics and monitoring The developer must provide documentation and a complete handover. Confidentiality and intellectual-property terms will apply. Who We Are Looking For We are open to applicants worldwide. Practical ability matters more than degrees, location or years of experience. Talented self-taught and junior developers are welcome if they can demonstrate that they build reliable software and learn quickly. The ideal person: - Has built working applications, bots or integrations - Can explain technical decisions in plain English - Communicates reliably - Breaks complex projects into manageable stages - Writes clean and understandable code - Thinks about security and failure conditions - Is honest about what they know and do not know - Is comfortable collaborating with another architecture team - Is interested in a longer-term relationship if the initial work succeeds Individuals are preferred, but small specialist teams may apply. What to Include in Your Proposal Please provide: 1. Your location and time zone. 2. Your availability and expected weekly capacity. 3. Your hourly rate or suggested milestone pricing. 4. Your recommended technology stack. 5. Relevant portfolio, GitHub or live-project links. 6. Details of any Next.js, Node.js, database or SaaS work. 7. Details of any Discord or Telegram bot work. 8. Details of any Whop, Stripe or subscription integration work. 9. An explanation of which components you could build personally. 10. Any components for which you would need assistance. 11. Your suggested scope, duration and price for the paid proof of concept. 12. Whether you are interested in ongoing work after the proof of concept. Please also answer these technical questions briefly: - How would you prevent the same payment webhook from granting access twice? - How would you handle webhook events that arrive in the wrong order? - Would you use a Discord webhook or a Discord bot to publish the probability information, and why? - How would you protect premium website content from free users? - How would you allow development to begin before the real STATS prediction API is ready? - How would you protect API keys, payment secrets and bot tokens? - What would you monitor in production to know whether the system is failing? Generic proposals that do not address the project or technical questions are unlikely to be considered. Engagement Structure - Remote and worldwide - Freelance/contract - Small paid proof of concept first - Further work divided into paid milestones - Potential long-term involvement - Budget open to reasonable proposals based on capability and scope We are looking for someone who can help us build the system carefully in stages, beginning with a reliable proof of concept and developing toward a scalable global platform.