ScopeLock: open-weight AI that turns freelance scope creep into paid change orders

Description and use

ScopeLock leverages open‑weight Gemma 3 and TabPFN to automatically analyze client requests, label out‑of‑scope items, cite SOW clauses, and generate paid change orders, safeguarding freelancers’ revenue.

Problem

Freelancers and small agencies lose money to scope creep because they cannot easily document and enforce scope boundaries.

Outcome

ScopeLock automates scope analysis, generates enforceable change orders, and provides cost estimates, enabling freelancers to protect revenue from scope creep.

Workflow

• Paste statement of work (SOW) and client thread or import Slack JSON or voice memo
• Index SOW into pgvector (Ollama embeddings)
• Paste client thread
• Analyze scope: LLM returns verdicts, citations, reply draft, change‑order line items
• View side‑hustle cockpit: scope‑creep score, TabPFN‑estimated hours, rush‑fee math
• Export change order as Markdown
• Optional: generate voice reply via ElevenLabs

Evidence

ScopeLock is a side‑hustle tool for freelancers and small agencies who keep losing money to scope creep.

Source

You paste your statement of work and a client thread (or import Slack JSON, or drop a voice memo). ScopeLock: Labels each client ask as in‑scope vs out‑of‑scope, cites language from your SOW, drafts a professional boundary reply, runs a Side hustle cockpit: scope‑creep score, TabPFN‑estimated change‑order hours, rush‑fee math, and a client‑ready change order you can export as Markdown

Source

Open Gemma 3 (google/gemma-3-4b-it) is the reasoning core — on Render it runs via OpenRouter; locally you can point at Ollama instead.

Source

TabPFN 3.5 regression on bundled project history CSV

Source