Lead Developer for Nonprofit Mobile-Responsive Web Platform - 45 Day Sprint

We are a nonprofit organization that connects volunteers with elderly and disabled homeowners who need help with lawn care. We operate on a "labor of love" model and are making a significant investment to automate our backend operations.
We are looking for a Technical Project Manager + Developer (or a small, tight-knit agency) to build our new volunteer management web platform. We have an existing WordPress website that serves as our public-facing marketing and intake site, and an existing SQL database on our VPS that contains all our current volunteer, homeowner, and request data. We are building a custom mobile-responsive web application to handle the complex logistics of volunteering.
Note on Infrastructure: We are NOT using Supabase. Our backend already exists—we have a production SQL database with live data. The new platform will connect to this existing database via a Node.js/Express API layer on our VPS. If you see Supabase mentioned in older planning documents, please disregard. We need someone comfortable building custom API endpoints, not setting up a new BaaS platform.
Note: This is NOT a native iOS/Android app project. This is a mobile-first React web application that must work flawlessly on mobile browsers.
The Context:

We are not starting from zero. We have a comprehensive 20-page "Master Technical Blueprint" (Technical Spec) that defines every table, user flow, and SMS template.
The Tech: We are using Lovable.app for the frontend (React/Vite) and a custom Node.js API connecting to our existing SQL database on the backend. You must be comfortable working in this environment.
Timeline: This is a 45-day sprint. We must be "Code Complete" by February 28th for our Spring Launch.
Current Site: Attached Screenshot. (See attached screenshots for the new platform vision).

The Tech Stack

Frontend: Lovable.app (React/Vite) - Mobile-First Design.
Backend/Database: Existing SQL Database on VPS + Node.js/Express API layer (NOT Supabase).
Communication: Email & Twilio (SMS/Voice Masking).
Maps: OpenStreetMap / Leaflet.

Scope of Work
You will be executing a strict "Definition of Done" checklist provided in our specs.
The build is broken into 4 core modules:
1. Core Automation (The "Uber" for Lawn Care)

Migrate our "Wishlist" of features into a functional web app.
Rebuild existing Volunteer Dashboard with geolocation (Job Feed).
Implement a "3-Stage Commitment Flow" (Address is hidden until the volunteer commits).

2. The "Community" Layer (New Features)

Group Events: A module for corporate/civic groups to "Pledge a Service Day" (B2B2C model).
Volunteer Rosters: A rotation system where multiple volunteers support one homeowner (preventing burnout).
Privacy Guard: Strict logic to ensure addresses are never shown on public feeds.

3. Grant Compliance & Admin

Equipment Tracking: An improved system (to what we have already) to track usage of equipment used.
Impact Reporting: Auto-generate reports on "Fines Saved" and "Hours Volunteered" for our auditors.

4. Immediate Fixes

We have a minor login/auth issue on the current build that needs an immediate fix to start the engagement.

Ideal Candidate Profile

Mobile-Responsive Expert: You know how to make complex forms feel simple on a smartphone browser.
You Speak "Grant": You understand that if the "Impact Report" doesn't work, we lose funding.
You are a Builder: You are comfortable with Lovable.app for rapid UI development AND can write custom Node.js/Express endpoints to connect to our existing database when needed.

Budget & Terms

Budget: This is a fixed-price contract funded by a grant. We have a set budget and a set scope.
Timeline: Kickoff immediately. Delivery by Feb 28th.
Status: We are a 501(c)(3) nonprofit.

How to Apply (Please Read Carefully)
We will not respond to generic copy-paste proposals. To be considered, please reply with:

The "Password": Start your proposal with the phrase "I am ready to Mow."
Your Stack Experience: Confirm your specific experience with Node.js/Express APIs, SQL databases (MySQL or PostgreSQL), and Twilio API.
Approach: Briefly explain how you would handle "Group Event" privacy—specifically, how you ensure a homeowner's address is visible to the group lead but hidden from the public feed.

Upon selection of a shortlist, we will share the full "Master Technical Blueprint" for a final accurate quote. Show More