Build Modern Pushpay-Integrated Church Platform

Project Title: Developer Needed for Modern Mega-Church Web Platform (Pushpay Integration & Zero-Cost Architecture) Project Overview: Our goal is to build a contemporary, engaging platform that communicates our vision, welcomes first-time visitors, showcases our ministries, and gives easy access to sermons and church activities, with the overarching purpose of pointing everyone who visits to Jesus. We are looking for an experienced developer who can build a high-performance, mobile-first web platform while adhering strictly to our architectural, security, and integration requirements. Key Requirements & Scope of Work 1. Pushpay as Our Central Repository Pushpay ChMS must remain the authoritative source for all church-management information to avoid creating separate databases or duplicating information locally on the website. Specifically: Calendar & Groups: Church calendar and public group listings must pull directly from Pushpay via API or approved embeds. Forms & Registrations: Connection cards, event registrations, and other forms must utilize secure Pushpay forms so information stays in the central repository. Children’s Pre-Registration: Must use a secure, approved Pushpay form process so children’s sensitive information is never stored locally on the platform. Prayer Requests: Must utilize a confidential submission process with clear permission rules. Online Giving: Must link seamlessly to our existing Pushpay giving platform rather than a custom payment portal. Note on API: Please specify your technical approach for connecting the platform to Pushpay, which APIs or embeds you intend to use, and how data caching/refresh rates will be managed. 2. Design and User Experience The platform must feature: A video-enhanced homepage hero section. A dedicated "Plan a Visit" feature for first-time guests. A church history timeline and member testimonials ("Why I choose and love this church"). A dedicated livestream page and a searchable, filterable sermon library. Modern, visually appealing, mobile-friendly design with lightning-fast load times. Clear organization for essential information: mission, vision, beliefs, leadership, ministries, service times, and physical location. 3. Content Management and Ownership The backend must be structured so our administrative staff can easily update text, photographs, ministry information, and announcements on their own without needing developer assistance for routine changes. 4. Chatbot and Ongoing Costs We are open to introducing a chatbot to act as a digital usher, but it must be a 100% free-tier or open-source implementation with zero recurring monthly subscription costs for hosting, usage, or maintenance. Please outline your approach for keeping all third-party tool costs at $0. 5. Security and Maintenance Please detail your proposed approach to: Data security and protection of personal information. Secure storage and protection of Pushpay API credentials (e.g., using environment variables). Role-based access permissions for staff and volunteers. Automated backups and ongoing maintenance/updates. Disaster recovery if the platform or a connected service goes down. 6. Additional Considerations Emergency Alert Banner: Staff must have an intuitive toggle in the backend to quickly post a site-wide notice when services are canceled or changed because of severe weather or other emergencies. To Apply, Please Provide: Links to 2-3 recent modern web platforms you have built from scratch (church or non-profit projects are preferred). Your technical approach to integrating Pushpay forms/embeds and handling data securely without local storage. Your proposed milestone structure, timeline, and cost estimate.