Freelance Developer for Contract Intelligence Tool

# Freelance Support Developer — SaaS Platform (Ongoing, Reactive)

**Project type:** Ongoing / as-needed
**Start:** Pre-launch (testing phase), continuing post-launch

## About the role

We're looking for a freelance developer to join an existing SaaS platform (contract risk intelligence tool for the construction industry) in a support capacity.

**Phase 1 — Pre-launch (paid testing/familiarization):**
Run through the platform's modules and workflows to get hands-on familiarity with the system before it goes live. This includes functional testing, identifying bugs, and flagging issues across core flows (authentication, payments, contract analysis workflows, notifications).

**Phase 2 — Post-launch (ongoing, reactive support):**
Once live, be the developer we call on when bugs or issues are reported. This is reactive, not a monitoring/on-call role — you'll pick up issues as they're flagged, diagnose them, and fix them. Frequency will vary depending on volume.

## What you'll be working with

- Supabase (backend, database, edge functions)
- Lovable (frontend build tool)
- Stripe (payments/subscriptions)
- Standard web app auth, notifications, and error handling flows

## Scope boundaries (important)

This role does **not** include access to or changes on:
- The AI/analysis engine, its system prompt, or edge functions calling the model API
- The clause knowledge base / retrieval logic

Those are owned by a separate specialist. Your scope is frontend, general backend/infrastructure, bug fixes, and QA.

## What we're looking for

- Full-stack or backend-leaning developer comfortable with Supabase and modern web stacks
- Comfortable working reactively — picking up and diagnosing issues without hand-holding
- Available on an ongoing, as-needed basis (not full-time)
- Prior SaaS support/maintenance experience preferred

## How to apply

Please include:
1. A short note on relevant experience with Supabase and SaaS support/maintenance
2. Your rate (hourly or day-rate) for both the pre-launch testing phase and ongoing reactive support
3. Availability / turnaround time you'd typically commit to once live