Company · About ScopeDue
About ScopeDue
ScopeDue exists to help freelancers turn client changes into clear business records before work continues. When a client asks for extra work, a priced approval link can show what changed, what it costs, whether payment is required, whether payment was confirmed, and what proof exists later.
Last reviewed: May 26, 2026 · Built for freelancers, solo studios, and small service providers in the United States.
Mission
Why ScopeDue exists
Freelancers often lose money after they already won the client. The problem is rarely one dramatic dispute. It is usually a chain of small moments: a casual message, a quick revision, a source file request, a late payment, or a final handoff that happens before the payment is confirmed.
ScopeDue is built for that middle layer between proposal, invoice, and delivery. Its mission is to make every client change calm, priced, approved, payment-aware, and documented without forcing a solo freelancer into a heavy operations system.
Product belief: a freelancer should not have to choose between sounding difficult and doing unpaid work. A clear record can make the conversation more professional for both sides.
The problem
Client changes should not live only in scattered messages
A client change may begin in email, text, Slack, a video call, a project comment, or a casual “can you also add this?” message. That can be fine for a conversation, but it is weak as the only business record.
| Common freelancer moment | What often gets missed | How ScopeDue frames it |
|---|---|---|
| Client asks for extra work in chat | Price, timeline impact, and whether the work is inside the original scope | A priced change request approval with a client approval link |
| Client says “I paid” | Whether the freelancer actually received the money | A payment ledger where the client can mark paid and the freelancer confirms received |
| Final or source files are ready | Whether payment is required before handoff | A handoff record that can stay locked until payment is confirmed |
| Project closes after several changes | A clean timeline of approvals, payment events, and handoff decisions | A Proof Pack for business records and project closeout |
Audience
Who ScopeDue serves
ScopeDue is for freelancers and small service providers who already have client work and need a cleaner way to handle changes, revisions, payments, and handoff decisions.
Creative freelancers
Graphic designers, brand designers, video editors, and photographers who need to handle extra revisions, alternate formats, final files, and source file release requests.
Web and technical freelancers
Web designers, freelance developers, SEO freelancers, and marketing consultants who need to price extra pages, integrations, reports, edits, and launch changes.
Solo studios and small providers
Small teams that do custom client work and need a lightweight approval trail without adopting a full CRM, project management suite, or accounting platform.
What ScopeDue is and is not
A focused approval, payment, and proof layer
ScopeDue is for
- Creating priced change requests before extra work starts.
- Sending a client approval link that makes the change, price, and timeline impact clear.
- Tracking payment requested, client marked paid, proof uploaded, and freelancer confirmed received.
- Keeping final handoff or source file release tied to confirmed payment when needed.
- Exporting a Proof Pack as a clean business record.
ScopeDue is not for
- Replacing a contract, lawyer, accountant, tax advisor, or payment processor.
- Managing every sales lead, task, message, invoice, and bookkeeping workflow in one place.
- Guaranteeing payment, guaranteeing dispute outcomes, or claiming legal protection.
- Publishing private client approval pages or user-specific Proof Packs as public SEO pages.
- Turning client boundaries into conflict. The goal is calm, clear professionalism.
Principles
Product principles behind ScopeDue
Calm professionalism
ScopeDue should help a freelancer say, “Yes, I can do that. Here is the approval link,” instead of writing an awkward message from scratch every time.
Clear boundaries
The product should make scope, price, timeline impact, payment condition, approval, and handoff status visible before work continues.
Client-friendly links
A client should not need to learn a complex portal just to approve a change, ask a question, or mark payment as sent.
Business records
Approvals, payment events, handoff events, and exported Proof Packs should give freelancers a cleaner record than scattered screenshots.
Freelancer confirmation
A client can mark paid or upload proof, but final payment status belongs to the freelancer once money is actually received.
No legal overclaiming
ScopeDue helps document business events. It does not promise legal outcomes or replace professional advice.
Workflow
The core workflow ScopeDue is built around
- Create the record. The freelancer records what changed, why it is outside the current scope, what it costs, and how it affects the timeline.
- Send the client link. The client reviews a clear approval page instead of approving from a scattered chat message.
- Get a response. The client can approve, decline, or ask a question before the freelancer starts the extra work.
- Track payment status. If payment is required before work or handoff, the ledger records payment requested, client marked paid, proof uploaded, and freelancer confirmed received.
- Save the proof record. Approval, payment, and handoff events can be included in a Proof Pack for business records and project closeout.
Trust boundaries
Records are useful because they stay specific
The product is intentionally narrow. ScopeDue focuses on the moments where a freelancer needs a clear approval trail, payment status history, handoff record, and Proof Pack. That focus keeps the product lighter than a broad freelancer CRM and more specific than a generic template library.
- Approval trail
- A record of what the client reviewed and how they responded, including approve, decline, or question events when available.
- Payment status history
- A timeline of payment events such as requested, client marked paid, proof uploaded, pending confirmation, freelancer confirmed received, overdue, disputed, waived, or refunded.
- Handoff record
- A record showing whether final files, source files, or project handoff were released only after the required condition was met.
- Proof Pack
- A clean export of the project or change request timeline, including scope, approvals, payment events, receipt references, notes, and handoff history where available.
Important: ScopeDue helps freelancers create a clear business record of approvals, payments, and handoff events. It is not a substitute for legal, tax, or accounting advice. For professional questions about contracts, taxes, accounting, disputes, or collection rights, contact the appropriate professional advisor.
Who built ScopeDue
Robert Frank — creator of ScopeDue
ScopeDue was created by Robert Frank, a freelancer and product builder based in Des Moines, Iowa. The product grew from firsthand experience with freelance client disputes — scope creep, informal approvals, late payment confusion, and handoff disagreements that could have been avoided with a clear business record.
ScopeDue is not a venture-funded startup or a marketplace. It is a focused tool Robert built to solve one specific problem: the moment between "the client asked for something extra" and "work continues." The goal is to make that moment calm, documented, and clear for both sides of the project.
ScopeDue is built for freelancers in the United States — web designers, developers, copywriters, social media managers, graphic designers, video editors, and SEO consultants who do custom client work and need a lightweight approval and payment record without a full operations platform.
For questions about the product, contact Robert at support@scopedue.com. For product changes and updates, see the product changelog.
Start here
Helpful places to understand the product
See the product features
Explore how ScopeDue handles approval links, payment status, Proof Packs, and handoff locks.
Try the workflow idea
Use a free tool to turn a client’s extra request into a priced approval record.
Review the trust pages
Read the product limits, security approach, privacy policy, and terms before using ScopeDue for client records.
Clear record before work continues
Learn why ScopeDue exists by seeing the workflow.
The next time a client asks for “one quick change,” do not rely only on a vague chat thread. Create a priced approval link, clarify the payment condition, and keep a record of what happened.