For solo devs, designers, marketing consultants, translators & architects
By Radim Motycka, Founder and Lead Engineer, ProofSnap · Updated August 15, 2026 · Not legal advice
How to prove scope creep: lock the original SOW with a court-ready qualified timestamp.
52% of projects run into scope creep, up from 43% five years earlier (PMI, Pulse of the Profession 2018). Solo freelancers lose $7,800-$15,600 per year in unbilled hours (our own arithmetic: 2 unbilled hours a week at $75-$150 an hour). When the client says “this was always in scope” six weeks later, a tamper-evident original SOW is the difference between billing the extras and absorbing them.
Drop the signed SOW into ProofSnap File Certifier. SHA-256 is computed locally in your browser, the contract itself never uploads. Receive a sealed evidence ZIP. Bitcoin OpenTimestamps anchoring is always included (US FRE 901 tamper-evidence; built to be certified under FRE 902(13) and 902(14) once a qualified declarant signs the certification). Add an EU qualified timestamp (eIDAS Regulation 910/2014 Art. 41(2): a presumption of accuracy that puts the evidential burden on the other side across 27 EU member states) when the project value justifies it.
Also available for Microsoft Edge · 7-day trial requires a credit card · cancel anytime.
Skip the trial? Buy a SnapPack for $4.99: 3 file certs and 10 captures →
10 seconds per SOW· File never leaves your device· Works for Upwork, Fiverr, direct clients
Sources: PMI Pulse of the Profession 2018 (52% of projects experienced scope creep, up from 43% five years earlier); the $15,600 figure is our own arithmetic, 2 unbilled hours a week × 52 weeks × $75-$150 an hour. Qualified timestamps issued by Disig a.s. QTSP on the EU Trusted List · ETSI EN 319 421/422 compliant.
Quick answer
How do you prove scope creep when the client says “this was always in the SOW”?
Lock the signed SOW the day it is countersigned, and lock every change request the day it arrives. Drop each file into ProofSnap File Certifier and you get a sealed ZIP in about 10 seconds that fixes the exact wording of the SOW at the moment you signed it. The file never leaves your device.
The hash is anchored to the Bitcoin blockchain through OpenTimestamps on every plan, and can be sealed with a Disig eIDAS qualified timestamp, which under Regulation (EU) No 910/2014, Article 41(2) carries a presumption of the accuracy of its date and time across all 27 EU member states. In a US court the package is built to be certified under Federal Rules of Evidence 902(13) and 902(14) once a qualified declarant signs the certification. From about $1.66 per file with the Bitcoin anchor, or $6.99 with the EU qualified timestamp. Anyone can re-verify it with the free ProofSnap Trust Verifier, no account needed.
Already in a dispute right now?
3-minute emergency path
The client just sent the “this was always in scope” email. There is no rush to reply. Lock the original SOW and every change request first. You will then have evidence ready to attach to your response within minutes, before mediation, arbitration or small claims.
Buy SnapPack, $4.99
~60 seconds. Stripe Checkout, credit card. Gives you 3 file certifications + 10 page captures. Credits valid 12 months. No subscription, no auto-renewal.
Certify SOW + change orders
~10 seconds per file. Drag into the File Certifier sidebar. SHA-256 computed locally, the file never uploads. One forensic ZIP per certified file lands in your downloads.
Reply with ZIP + change-order quote
Attach provenance_certificate.pdf to your reply and copy the email template below. Most scope-creep disputes end here, before they escalate.
Email template: “That is outside scope, here is what it would cost”
Subject: [Project name] SOW, change-order #[N] for [feature] Hi [Client name], Thanks for the request to add [feature X]. To confirm scope: the signed SOW dated [date] explicitly covers [list deliverables A, B, C]. [Feature X] sits outside the agreed scope (see SOW § [N], exclusions list). I am happy to add it under the change-order clause (SOW § [change-order section]). My quote: $[Y] for ~[Z] hours, delivered by [date], invoiced on completion. For reference, I have attached the original SOW provenance certificate (ProofSnap, SHA-256 + EU eIDAS qualified timestamp issued by Disig a.s. QTSP on the EU Trusted List). Anyone can re-verify the SOW contents at https://getproofsnap.com/verify/index.html. Drop in the certificate package plus the original SOW PDF, and the verifier returns “File matches certificate”. Under Regulation (EU) No 910/2014 Article 41(2), the qualified timestamp carries a legal presumption of accuracy across all 27 EU member states. Under US Federal Rules of Evidence 902(13) and 902(14), the cryptographic record qualifies as self-authenticating once the attached certification is signed, without expert testimony. Please confirm whether you would like to proceed with the change order. Best, [Your name]
Adapt the tone to your relationship with the client. Keep the three deterrents: SOW section reference + provenance certificate attachment + Trust Verifier URL. The three together remove the ambiguity the "always in scope" argument depends on.
7-day trial requires a credit card · SnapPack is a one-time purchase, no subscription.
Who should lock every SOW, and the specific pain it solves
If your income depends on what was, and was not, in the original scope, this costs about $25 per project. Four kinds of freelancer, four distinct scope-creep patterns.
Solo developers (Upwork, Toptal, direct)
Pain: feature scope drift. “Just add user roles,” “the dashboard should also export to Excel,” “can we move to GraphQL?” Six weeks in, the client claims these were “always in scope.” Without a timestamped original SOW with an explicit out-of-scope list, every Upwork dispute or small claims case is your file vs theirs.
With ProofSnap: certify the SOW the day the Upwork escrow is funded, then certify every change-order PDF the same day it’s countersigned. eIDAS SnapPack 5 ($24.99) covers one SOW + four change orders per project.
Designers (Fiverr, Behance, agency contractors)
Pain: revision-round drift. SOW says “Round 1 includes up to 5 changes. Round 2 includes 3.” By Round 4, the client claims unlimited revisions were “always implied.” A timestamped original SOW with revision caps printed in black and white is the difference between billing the extra rounds and absorbing them.
With ProofSnap: certify the SOW on acceptance. Certify each round’s sign-off PDF. When the client demands a 7th revision, you have a forensic record of every round closed and approved.
Marketing consultants & content writers
Pain: deliverable count drift. “5 articles per month” somehow becomes 5 articles plus 3 social posts plus a newsletter. SEO scope “research and on-page” expands to include backlinks, technical audit, and competitor reports. Per our own arithmetic: at $75-$150/hour, just 2 hours of unbilled work per week, a common amount of drift, costs the freelancer $7,800-$15,600 per year.
With ProofSnap: certify every retainer agreement at signing. Certify any add-on agreement the same day it’s sent. Bill the extras with documented contemporaneous evidence of when scope crossed the line.
Translators, architects & specialized consultants
Pain: high-stakes spec drift, narrow margins. Translators get asked for “a quick proofread” that turns into a full re-translation. Architects field “small tweaks” that re-trigger structural calculations. Consultants extend “a quick call” into a half-day workshop. Original SOW + change orders = the strongest basis for the additional invoice, especially with EU clients, where eIDAS Art. 41(2) puts the evidential burden on the client to disprove the timestamp.
With ProofSnap: certify the SOW + brief + reference materials at project kickoff. Per-project cost under $25 with the eIDAS SnapPack 5.
Platform dispute resolution is blind to off-platform proof
Upwork dispute resolution only considers material visible in Upwork Messages. Conversations on WhatsApp, Slack or email are invisible to the resolution team. Best practice: post the signed SOW to Upwork Messages, certify it with ProofSnap on the same day, and store the ZIP in your project folder. The platform considers the Messages thread; small claims court considers your tamper-evident ZIP. You need both.
Also signed the client’s NDA? Lock both for two-way protection.
Most freelance engagements include a client-issued NDA alongside the SOW. If a dispute escalates, the counterclaim is often “you breached our NDA by referencing the project” or “your work product was always our confidential trade secret per the NDA.” Lock the executed NDA the same day you sign it, same File Certifier, same forensic ZIP. See the dedicated NDA Version Proof page → for the NDA-specific pain (counterparty producing a different signed version six months later) and pricing math for fundraise-scale NDA volume.
From signed SOW to a sealed evidence ZIP in 10 seconds
Drop. Certify. Archive per project. No upload of the SOW itself, no client onboarding, no account required for anyone to re-check your certificate later.
Drop and Certify
Inside the ProofSnap sidebar

Open the File Certifier panel. Drag in your signed SOW, or any change-order PDF; any file up to 400 MB works. Toggle EU Qualified Timestamp (eIDAS) if the project warrants it. Click Certify File.
Certificate ready in 10 seconds
SHA-256 + Bitcoin + Disig eIDAS

SHA-256 is computed in your browser; only the 32-byte hash leaves your device. Bitcoin OpenTimestamps anchored. Disig eIDAS qualified timestamp sealed. Click Download Certificate Package.
Anyone can re-verify, anytime
Judge. Mediator. Upwork dispute team.

Hand the ZIP to anyone. They drop it into the free ProofSnap Trust Verifier, add the original SOW next to it, and see “File matches certificate”. No ProofSnap account required.
What’s inside the evidence ZIP: 11 to 15 files depending on plan and options
manifest.json, evidence ID + SHA-256 hashmanifest.sig, RSA-4096 signaturepublickey.pem, verifier public keychain_of_custody.json, ISO 27037 custody recordforensic_log.json, hash-chain event logprovenance_certificate.pdf, human-readable certificatemanifest.json.ots, Bitcoin OpenTimestamps proofmanifest.json.tsr, eIDAS qualified TSR (RFC 3161)eidas_validation.json, LTV validation data[your_SOW].pdf, original file (embedded)Lock the SOW and lock your deliverables: two-way protection
Certify your final build, design, translation or audit report on the day you deliver. When the client claims “this is not what we agreed,” you have both halves of the chain: a SHA-256 fingerprint of the SOW (proving what was scoped) and a SHA-256 fingerprint of the delivered file (proving what was shipped, and exactly when). If acceptance is in question, certify the client’s sign-off email PDF too. Three ZIPs across one project (SOW, delivery, sign-off) answer the “you did not deliver” counterclaim with the record instead of recollection. Same File Certifier, same per-file ~$1.66 with SnapPack or $5 each with eIDAS SnapPack 5.
No vendor lock-in. If ProofSnap disappeared tomorrow, your evidence ZIP would still verify against Bitcoin and Disig with open tools.
Try the File Certifier (7-day trial)Built-in vs premium · recognized across small claims, EU courts, platform disputes
Two layers of proof. Choose the one the project justifies.
Every File Certifier ZIP is anchored to the Bitcoin blockchain, on every plan, including the 7-day trial. Add an EU qualified timestamp for international clients or larger contracts.
“A qualified electronic time stamp shall enjoy the presumption of the accuracy of the date and the time it indicates and the integrity of the data to which the date and time are bound.”
Layer 1: Bitcoin OpenTimestamps
Included on every plan · or standalone via SnapPack $4.99
SHA-256 hash of your signed SOW, anchored to the Bitcoin blockchain via OpenTimestamps. Decentralized, independent, tamper-evident. Once anchored, the hash would require breaking Bitcoin's proof-of-work history to forge.
- Cryptographic proof of existence at time T
- US FRE 901 tamper-evidence + FRE 902(13)/(14) certification path (a declarant signs, no expert witness)
- Corroborates the Messages thread if the dispute escalates beyond the platform
- Verifiable with open tools, no ProofSnap dependency
- No EU legal presumption; the opposing party can still challenge accuracy
Sufficient for: most US small claims, Upwork/Fiverr dispute resolution, internal project archives, projects under $5K.
Layer 2: eIDAS qualified timestamp
Optional · from $6.99 per stamp
Disig a.s. (QTSP on the EU Trusted List) issues a qualified timestamp under RFC 3161 + ETSI EN 319 421. Adds the strongest evidentiary weight eIDAS provides for a timestamp: a legal presumption that puts the evidential burden on the client to disprove the timestamp.
- Everything in Layer 1, plus:
- eIDAS Art. 41(2) legal presumption of accuracy
- Evidential burden shifts: the client has to rebut the timestamp
- Recognized in all 27 EU member states (Art. 4, EU Trusted List), and under UK retained eIDAS
Worth it for: EU clients, cross-border engagements, contracts $5K+, any project where you want to shift the burden of proof onto the other side.
EU · 27 member states
eIDAS Art. 41(2) grants qualified timestamps a legal presumption of accuracy. The client must prove your timestamp is inaccurate, not the other way around. Disig a.s. is QTSP on the EU Trusted List.
US · small claims + federal
FRE 902(13)/(14): cryptographic records produced by a reliable process are self-authenticating once a qualified declarant signs the certification, so no expert witness is required. Most freelance disputes belong in state small claims court (CA limit raised to $12,500 for individuals under SB 71, 2024; tiered fees $30/$50/$75; no lawyer).
Platform disputes · Upwork & Fiverr
Upwork escrow disputes consider only material in Upwork Messages. Pin the signed SOW to the thread, certify it the same day with ProofSnap, and the ZIP corroborates date and integrity if the case escalates.
Why this matters: 57% of agencies lose $1,000-$5,000 monthly to unbilled scope creep (Ignition 2025)
Without a qualified timestamp you must prove the SOW is the one in force using email metadata and screenshots, all of which are challengeable and weak in mediation. With a ProofSnap qualified timestamp the court presumes the accuracy of your date and the integrity of the bound data; the client carries the burden of rebuttal, and once the 902(13)/(14) declaration is signed, no expert witness is needed. A dispute is far cheaper to settle at the demand-letter stage than in mediation or small claims when the freelancer can attach a tamper-evident, independently verifiable proof of the original version. Bitcoin OpenTimestamps alone is usually enough for a $2,000 Upwork build; add eIDAS for a $20,000 corporate retainer or a German, French or Spanish agency engagement where the Art. 41(2) presumption carries weight.
ProofSnap is not a law firm and does not provide legal advice. Qualified timestamps are issued by Disig a.s. (QTSP on the EU Trusted List). Consult a qualified lawyer for advice on your specific dispute.
Pay per project or subscribe
Every plan includes Bitcoin OpenTimestamps anchoring. Add eIDAS qualified timestamps for international clients or larger contracts.
Not sure which to pick? Pick by project value & volume.
One small project
Under $1,000, 3 file certs + 10 page captures.
~$1.66/cert · no EU presumption.
SnapPack, $4.99 ↓One $1K-$12.5K SOW
An EU client, or a contract within the small-claims range.
eIDAS Art. 41(2) presumption.
eIDAS SnapPack 1, $6.99 ↓SOW + 4 change orders
Typical 3-month engagement, full audit trail.
EU qualified, $5/cert.
eIDAS SnapPack 5, $24.99 ↓Multiple active projects
Agency owner, busy solo, 5+ SOWs/mo.
Monthly file-cert quota.
Subscribe, Professional $16.99/mo ↓eIDAS SnapPack: pay per SOW
Buy credits, certify when you need to. Credits valid 12 months.
10 stamps
$5.00/stamp · covers a full quarter of projects.
Buy 10 stampsvia ProofSnap extension
Or subscribe (for multiple active projects)
For agency owners, busy solo freelancers, retainer-based consultants. Every plan ships Bitcoin OpenTimestamps anchoring by default. eIDAS qualified stamps are an optional premium layer: included on Enterprise, available via eIDAS SnapPack on Professional.
Professional
or $160/year (20% savings)
- 15 file certifications / month
- Bitcoin OpenTimestamps on every cert
- eIDAS optional, add eIDAS SnapPack
- Unlimited page captures + forensic ZIP with chain of custody
For: solo freelancers with 3-5 active projects, mostly US clients
Enterprise
or $280/year (20% savings)
- 50 file certifications / month
- Bitcoin OpenTimestamps on every cert
- 10 eIDAS qualified stamps / month
- Unlimited page captures + forensic ZIP with chain of custody
For: agency owners, EU-client-heavy freelancers, retainer-based consultants
7-day trial requires a credit card. Cancel anytime within the trial, no charge.
Need only 5 certs/month? Essential $8.99/month also includes Bitcoin OpenTimestamps anchoring.
SnapPack
Bitcoin proof only, no eIDAS$4.99 for 10 page captures + 3 bonus file certifications. Effective ~$1.66 per file cert if you use all three, with 10 page captures on top. Bitcoin OpenTimestamps anchored (US FRE 901 tamper-evidence; FRE 902(13)/(14) certification template included). No eIDAS qualified timestamp: for the EU Art. 41(2) presumption, use an eIDAS SnapPack above.
Typical scenarios
Six weeks into a $14K Upwork build, the client started asking for two integrations they swore were in the original brief. They weren’t. I had the signed SOW with the exclusions list. The difference was that I’d certified the SOW with ProofSnap on day one and stored the ZIP next to the project. When I sent the change-order quote with a screenshot of the verified provenance certificate, the “always in scope” argument disappeared in one reply. I billed the extras instead of absorbing them.
Solo backend developer (typical scenario)
I run a small branding studio. Round-cap drift used to cost me at least one absorbed revision per project. Now I send the SOW with the revision cap printed in bold, certify it the day it’s signed, and certify the sign-off PDF at the end of each round. When a client pushed for a 6th revision on a 4-round contract last quarter, I attached the ZIP of the round 4 acceptance to my change-order email. They paid the extra invoice the next day without a single objection.
Brand designer, solo (typical scenario)
These are typical use-case scenarios written by ProofSnap to illustrate fit, not customer testimonials.
vs DocuSign, Bonsai, time trackers
DocuSign proves who signed. Time trackers prove what you did. ProofSnap proves what the signed document said, and exactly when it existed. They are complementary, not substitutes.
| Feature | ProofSnap | DocuSign Personal | Bonsai / HelloBonsai | Time-tracker (Toggl, Clockify) |
|---|---|---|---|---|
| Tamper-evident original SOW timestamp | Signature audit log | Internal database, no cryptographic seal | Hours only, not contract | |
| eIDAS qualified timestamp | Enterprise add-on only | No | No | |
| Bitcoin OpenTimestamps dual seal | No | No | No | |
| FRE 902(13)/(14) certification template included | Requires witness | Requires witness | Requires witness | |
| File never uploaded | No (cloud-hosted) | No (cloud-hosted) | n/a | |
| Pay-per-use option | $4.99 SnapPack · $6.99 eIDAS stamp | Subscription only | From $25/mo | Free tier, paid from $9/mo |
| Entry price for scope-creep evidence | $4.99 SnapPack = 3 SOWs/change orders | $15/seat/month | $25/month minimum | Time logs, no contract proof |
Comparison reflects publicly available 2026 pricing. Bonsai/Time-tracker terms may differ by plan and region.
Frequently asked questions
provenance_certificate.pdf from the evidence ZIP and bring the original signed SOW. The judge can re-verify the SHA-256 hash on the spot.Lock the next SOW you sign.
Solo freelancers lose $7,800-$15,600 per year to scope creep (our own arithmetic: 2 unbilled hours a week at $75-$150 an hour). One $24.99 eIDAS SnapPack 5 covers a full quarter of SOWs and change orders. A single recovered dispute pays for years of credits.
Lock my SOW (7-day free trial)7-day trial requires a credit card. Cancel anytime within the trial, no charge.