Full-Stack Developer Needed to Build Pest Management SaaS Platform & Customer Portal from Prototype

Project Overview I own a pest management business in Australia and have developed the concept and working front-end prototype for a new pest-management software platform called Pest Vantage. I am looking for an experienced full-stack software developer to take the existing prototype and turn it into a secure, professional, production-ready web application. This is not simply a website build. The software will be used internally by pest-control technicians and externally by customers through their own property dashboard. I already have: The business concept and workflow UI/dashboard designs Desktop and mobile layouts A working HTML/CSS/JavaScript prototype An initial Pest Risk Score system Technician inspection workflow Customer dashboard concept Property Pest Passport concept Branding and logo Example reports and scoring structure The developer will therefore not be starting from a blank page. The objective is to turn the prototype into a scalable web application. The Software Has Two Main Sides 1. Technician / Administration Portal This is used by the pest-control business. It should allow technicians/admin users to: Log in securely Create customers Create properties Search and manage existing properties Start a new inspection Complete inspection checklists on mobile Score individual pest/risk categories Automatically calculate a 0–100 Pest Risk Score Add findings and recommendations Take/upload property photos Attach photos to specific findings Record treatments performed Record technician notes Set the next inspection date Generate customer reports View previous inspections View property score history Manage ongoing PestWatch memberships Track properties requiring follow-up Eventually support multiple technicians/users The system needs to work extremely well on a mobile phone, as technicians will use it while walking around customer properties. 2. Customer Portal / Pest Passport Each customer should have a secure login where they can only access their own property/properties. The customer dashboard should show: Property address/details Current Pest Risk Score out of 100 Excellent / Good / Moderate / High Risk / Critical status Change since previous inspection Pest-specific risk categories Termite conditions Cockroach conditions Rodent conditions Ant conditions Spider conditions Mosquito activity Fly activity Moisture conditions Building entry points Recommendations Inspection photographs Previous reports Next inspection date PestWatch membership status Score history graph Complete property inspection history A major feature is the Property Pest Passport, which creates an ongoing history for the property rather than simply storing individual PDF reports. For example: August 2025 – Score 60 ↓ November 2025 – Score 68 ↓ February 2026 – Score 75 ↓ August 2026 – Score 82 Customers should be able to see how the condition/risk profile of their property has improved over time. Pest Risk Scoring Engine The application needs a configurable scoring system. Individual inspection questions and conditions contribute differently to the final score. For example, termite conditions and moisture may have significantly more influence on the final property score than lower-risk categories. The scoring rules/weights should ideally be configurable through an admin interface rather than permanently hard-coded. The software should also eventually be capable of showing why a score changed. Example: Previous Score: 75 Current Score: 82 +7 improvement Reasons: Entry point sealed: +3 Vegetation removed: +2 Moisture issue corrected: +2 The scoring engine is an important part of this project. Inspection Findings During an inspection, the technician should be able to quickly create findings such as: Category: Moisture Location: Rear wall Risk: High Finding: Excess moisture detected Photo: Upload/take photo Recommendation: Investigate drainage/leak source The system should make this process extremely fast on mobile. Where possible, common findings should generate predefined recommendations that the technician can accept or edit instead of repeatedly typing the same information. Automatic Reports After completing an inspection, the technician should be able to press: Generate Report The application should create a professional Pest Vantage report containing: Customer information Property information Inspection date Pest Risk Score Previous score Score improvement/decline Risk summary Individual findings Technician notes Recommendations Inspection photographs Next inspection date PestWatch membership status Reports should preferably be available as both: Online customer reports Downloadable/printable PDF reports Technology / Backend Requirements I am open to recommendations regarding the technology stack. The production application will need: Secure cloud database User authentication Admin/technician accounts Customer accounts Role-based permissions Secure password management Database backups Photo/document storage API/backend Mobile-responsive interface Desktop interface Customer-specific access controls HTTPS Production deployment Source-code repository Proper environment/configuration management Possible technologies could include React/Next.js, Vue, Node.js, Python, Supabase, PostgreSQL, Firebase, AWS, etc., but I am open to the developer recommending the most suitable architecture. I care more about security, reliability, maintainability and future scalability than using a particular programming language. Future Features The system should be designed so we can later add features such as: Automated email notifications SMS notifications Appointment scheduling Recurring PestWatch memberships Subscription/payment processing Technician scheduling Business analytics Property risk mapping QR-code access to Pest Passports Multiple technicians Multiple business locations Pest activity analytics by suburb/region Integrations with my existing Squarespace website Potential mobile app/PWA More advanced property/pest intelligence features These do not necessarily all need to be included in the first development milestone, but the architecture should not prevent us from adding them later. Squarespace Integration My public-facing business website currently uses Squarespace. The software can be hosted separately, but customers should eventually be able to access the platform through buttons/links such as: Customer Login View My Pest Passport Get My Pest Risk Score from the Squarespace website. Existing Prototype I will provide the selected developer with the existing prototype, including: HTML/CSS/JavaScript files Current dashboard Mobile layout Technician interface Customer interface Initial scoring logic Pest Passport concept Branding assets Logo Example property data The prototype is intended to demonstrate the workflow and visual direction. I understand that parts of the application may need to be rebuilt properly for production. Developer I Am Looking For I am particularly interested in developers who have experience building: SaaS applications CRM/field-service software Inspection software Property management platforms Customer portals Field technician applications Dashboard-based software Reporting systems Experience with mobile-first field software would be highly valuable. I do not want someone who will simply convert the HTML into another framework. I want a developer who can understand the business workflow and help create a well-architected product that can grow over time. Important – Ownership & Confidentiality This project contains proprietary business concepts, workflows, scoring methodologies and branding. The successful developer must be comfortable agreeing that: All custom source code created for the project will belong to me upon payment. All designs, database structures and project-specific intellectual property created for the project will belong to me. Project information will remain confidential. The software may not be resold or reused as a competing pest-management product. Source code must be maintained in a repository/account that I can access. I must retain full administrative access to hosting, database and other production services. An NDA may be required before detailed proprietary information is provided. How I Would Like the Project Developed I would prefer to work in milestones rather than one enormous fixed project. An example structure could be: Milestone 1 – Architecture & database design Milestone 2 – Authentication + customer/property database Milestone 3 – Technician mobile inspection system Milestone 4 – Pest Risk scoring engine Milestone 5 – Customer dashboard/Pest Passport Milestone 6 – Reports + photo system Milestone 7 – Testing/security/production deployment There is potential for substantial ongoing development after the initial system is completed.