No. 01
Verbal re-scoping
"We also need X, Y, Z: just add those in." Three weeks later, it's "we never asked for those." Seal the ask the moment it lands.
For freelancers & consultants
Prove you delivered it. And that they accepted it.
When a client says the work wasn't what they agreed, the argument is your word against theirs. Pactbound makes it the record's: sealed, identity-verified sign-offs on every agreement and deliverable, tamper-evident and verifiable by anyone.
Arguments you’ve had to swallow
All of these end when both sides have a sealed, acknowledged record.
No. 02
Deliverable disputes
You sent the final files. They claim they never received them, never approved them, or want endless revisions outside scope. A sealed acknowledgment ends the guessing.
No. 03
"This isn't what we agreed"
The work ships, then the story changes about what was promised. Without a record, you're arguing from memory. With one, you point to the scope they acknowledged and the date they did it.
No. 04
Revision rounds that never end
Scope said 2 rounds of revisions. They're on round 6, denying the original agreement. Point to exactly what was signed off, and when.
A real freelance dispute
What do I do when a client says the final deliverable wasn't what we agreed?
Kira delivered a complete mobile app redesign for a small e-commerce client: high-fidelity screens, a component library, and a dev-ready spec in Figma. The client came back saying the deliverable wasn't what they expected. They wanted an interactive prototype they could test with real users before handing to developers.
An interactive prototype wasn't in the original scope. Kira had sealed the kickoff brief with Pactbound: 'high-fidelity screens for 12 user flows and a component library.' She'd also sealed a scope addition from week 4 when the client asked for three extra checkout screens, captured and acknowledged the same day they asked.
The client said they had 'assumed' the prototype was included. Kira sent two links: the sealed kickoff scope and the sealed delivery of the exact files described in that scope. There was nothing in either record about a prototype.
The final invoice got paid. The prototype was quoted separately. The client signed off on the add-on and hired Kira for the next sprint.
The deal felt solid in the room. Put it on the recordbefore it isn’t.
A handshake and a friendly email feel like enough, until the relationship sours. Sealing the agreement costs you 60 seconds and changes every conversation that follows.
What you seal
Every point a client could later walk back.
- The kickoff scope and statement of work
- Every verbal or Slack re-scope, the moment it lands
- Revision-round limits and what counts as a round
- Milestone deliverables and the client's acceptance
- Final files plus the sign-off that closes the project
- The credentials and assets you hand over at the end
The workflow
How freelancers use Pactbound.
- I
Seal the initial scope
After the kickoff call, draft the scope in Pactbound, attach the agreement, send for acknowledgment. Client clicks once. Sealed.
- II
Seal every change
Every time scope shifts (verbal add-on, revision request, timeline change), create a new seal. 30 seconds per change.
- III
Seal the delivery
When work is delivered, attach the final files and request acknowledgment. The client confirms. Now there's a sealed, identity-verified record of what they accepted.
- IV
Covered, whatever comes next
If a dispute ever lands (a chargeback, a bad-faith review, a legal threat), you have a tamper-evident chain of exactly what was agreed and delivered, structured the way decision-makers expect to read it.
Where the receipt does the work
One artifact, three places it pays off.
Small-claims ready
Identity-verified acknowledgments with an external timestamp are the kind of contemporaneous record a small-claims judge accepts: not Slack screenshots reconstructed after the fact.
Chargeback evidence
Export a bundle as PDF and drop it straight into a Stripe, PayPal, or Square dispute: proof of delivery and proof of acceptance in one file.
Outlives the project
The receipt is verifiable by anyone with an open-source script, even if Pactbound disappears. It still checks out years later, because the proof doesn't depend on us being around.
Before your next kickoff call
The next scope-creep conversation ends differently.
Free to start: 5 sign-offs a month, no credit card. 60 seconds to seal your first agreement.
Seal your first agreement No card Works in minutes