# Scope change requests for agencies and freelancers

Scope change requests for agencies and freelancers is a SaaS idea for web, design and marketing agencies and freelancers working on fixed-price projects, priced to test at $29 a month per agency. Clients ask for small extras in calls and chats, and the team just does them. With it, agencies turn a client’s extra asks into priced change requests the client approves before any extra work starts.

_Published 19 Oct 2026. A starting point we wrote, not market research: run the 7-day test before you build._

## What problem does it solve?

Clients ask for small extras in calls and chats, and the team just does them. By the end the project has grown, and nobody can show what was agreed or billed.

**Why now:** Clients now talk to agencies across chat, calls and shared docs, so small asks slip through without anyone pricing them.

## What do they use today?

Most agencies handle extras with a quick yes in a meeting or message, and sometimes a line in a shared project note. Few send a priced quote for small asks, so billing them later feels awkward.

## How does it work?

A client asks for an extra page on a call, so the project lead writes a change request with a price and the time it adds. The client approves or declines from an emailed link, and the answer goes into a signed log. The team starts the extra work only after approval, and approved extras are exported for the next invoice.

## What goes in the first version?

- Change request with description, price and time impact
- Client approves or declines from an emailed link
- Running total of approved extras per project
- Signed log of every request and decision
- Export approved extras for the next invoice

## Who pays, and how much?

- **Who pays:** Web, design and marketing agencies and freelancers working on fixed-price projects
- **Price to test:** $29 a month per agency

A flat price per agency suits a business where several project leads send change requests, so nobody has to count seats. It replaces the shared notes and long email threads that hold the record now.

## How to test it in 7 days

1. Ask ten agency owners how much unbilled extra work their last project had.
2. Help one agency send a real change request through a simple form and see how the client responds.
3. Post about scope creep in freelancing subreddits and count replies asking for the tool.

## Where to find the first customers

- Agency owner communities on LinkedIn and Slack
- Freelancing and web design subreddits
- Accountants and coaches who work with agency owners

## What are the risks?

- Some agencies fear upsetting clients; position it as clear, friendly paperwork.
- Proposal and project tools may add change orders, so keep it fast.

## How to build it on shipanysaas

4 of the parts it needs are already in the kit. Get the kit, open it in Claude Code, Codex or Cursor, and paste the starting prompt.

**Already in the kit:** Teams and roles, Billing, Emails, In-app notifications

**You build:**

- Change request form with price and timing
- Client approval link with signed log
- Approved extras export for invoicing

[Get the kit](https://www.shipanysaas.com/pricing)

### The starting prompt

```text
You are in a fresh copy of the shipanysaas starter kit, a pnpm and Turborepo monorepo: the Next.js web app is in apps/web and the Supabase database, with its migrations, in apps/web/supabase. Help me build the first version of Scope change requests for agencies and freelancers.

Read AGENTS.md first, then the AGENTS.md in every folder you work in: the kit's rules there win over your defaults. When a skill in .agents/skills (also in .claude/skills and .cursor/skills) matches a task, use it.

## The product
- What it does: Agencies turn a client’s extra asks into priced change requests the client approves before any extra work starts.
- Who pays: Web, design and marketing agencies and freelancers working on fixed-price projects
- Their problem: Clients ask for small extras in calls and chats, and the team just does them. By the end the project has grown, and nobody can show what was agreed or billed.
- Price to test: $29 a month per agency (a plan in apps/web/config/billing.config.ts)

## Build only this first version
1. Change request with description, price and time impact
2. Client approves or declines from an emailed link
3. Running total of approved extras per project
4. Signed log of every request and decision
5. Export approved extras for the next invoice

## Already in the kit: reuse it, never rebuild it
- Teams and roles: team accounts with members, roles and invitations
- Billing: Stripe or Lemon Squeezy subscriptions, per seat or usage-based, and one-off payments
- Emails: transactional email through Resend or Nodemailer
- In-app notifications: a notifications bell in the web app

## New code it needs
- Change request form with price and timing
- Client approval link with signed log
- Approved extras export for invoicing

## How to work
1. Plan first: list the database tables (with row-level security, so each team only sees its own rows), the pages and the server actions for the first feature. Then stop and wait for my OK.
2. Build one feature at a time with the kit's own UI and form components, with a migration for every schema change and user-facing text in the translation files.
3. After each feature, run the verification steps in AGENTS.md, fix what they find, and tell me what you built and what comes next.

## Rules
- Ask me before you add a dependency, delete a file, or change sign-in, billing or the admin panel.
- Leave the parts of the kit this product doesn't use as they are.

Done when every first-version feature works for a signed-in team and the AGENTS.md checks pass.
```

### Guides for the parts it uses

- [How to add Resend email to a Next.js + Supabase app](https://www.shipanysaas.com/blog/nextjs-supabase-resend-email)
- [How to add Stripe embedded checkout to a Next.js + Supabase app](https://www.shipanysaas.com/blog/nextjs-supabase-stripe-embedded-checkout)
- [Multi-tenant SaaS architecture: teams, roles and invitations done right](https://www.shipanysaas.com/blog/multi-tenant-saas-teams-roles-invitations)

## More ideas: Agencies

- [Client feedback and testimonials for agency projects](https://www.shipanysaas.com/saas-ideas/agency-client-feedback-testimonials): Agencies send a short survey at each project milestone, catch unhappy clients early, and turn happy answers into approved testimonials.
- [Client approvals for small design and video studios](https://www.shipanysaas.com/saas-ideas/studio-client-approvals): Studios share drafts, clients comment on the exact spot, and every approval is on record.
- [Monthly Search Console reports for freelance SEOs](https://www.shipanysaas.com/saas-ideas/seo-client-reports): Freelancers connect each client’s Search Console once and send a clear monthly report with their own notes.

- [All SaaS ideas](https://www.shipanysaas.com/saas-ideas)
- [Try the free generator](https://www.shipanysaas.com/saas-ideas#generator)