Full-Stack + AI Engineer: Build a Regulatory Compliance SaaS from Scratch (PH-based)

We're building a regulatory compliance platform for businesses and the public. It will be built from scratch to our functional spec, which we'll share under NDA. SCOPE -Automated monitoring and scraping of government websites, with document capture - An AI first-pass review layer: AI-assisted document processing with human review. Must support a locally hosted model” - A public searchable regulatory library (high traffic, SEO) - User sign-up and paid subscription workspaces (individual and organization accounts) - Role-based access (admin, curator, reviewer, org users) and a full audit trail - An admin dashboard, including scraper health and AI processing logs REQUIREMENTS - Proven experience shipping production SaaS: authentication, permissions, background jobs, databases, deployment - Hands-on experience with web scraping, LLM integration or RAG, and PostgreSQL - A standard, portable stack (you recommend it). No proprietary or low-code platforms - Work happens in accounts we own (repo, hosting, database, AI infrastructure) - An NDA and a full IP assignment before the spec is shared - Fixed price by milestone, with payment released when each milestone passes acceptance tests HOW WE'LL START: A SMALL PAID TRIAL You build one scraper for one government regulator's issuances page. Definition of done for the trial: 1. The scraper collects every issuance listed on the target page: title, issuance number, date, category, and source URL 2. It downloads and stores the full source document (PDF/HTML), not just a link 3. All records land in a PostgreSQL table with a documented schema 4. Re-running it adds only new issuances, with no duplicates 5. Failures (site down, layout changed) are logged clearly, not silently skipped 6. The code is in our GitHub repo with a README covering setup and how to run it The best trial leads to the full build. IN YOUR PROPOSAL, INCLUDE: 1. A SaaS product you built that is closest to this, and what you personally did on it 2. Your recommended stack and why 3. Your recommended locally hosted model and the hardware it needs 4. A rough range and timeline for the full build 5. Whether you work solo or with a team, and who would actually work on this Start your proposal with the word "SOURCE" so we know you read this far.