Vague Mock Contracts — AI Prompts for Adobe Acrobat

The moments that lead here

If one of these is your afternoon, you are in the right place.

we lose time renegotiating scope because our mock contracts are vague.

1 ready prompt

Written for the moment this actually comes up.

Become — change the pattern

Across several client conversations, scope expands because our preliminary contracts don’t make…

Across several client conversations, scope expands because our preliminary contracts don’t make change costs visible. Diagnose the pattern and recommend one drafting habit for negotiable mock contracts that clarifies deliverables, change control, and non-negotiables. Include one concession that consistently closes deals without increasing hours materially.

Who does this, and with what

The same task is different work inside a different job.

Web DesignerAdobe Acrobat

Next to this one

Other negotiate work people do in Adobe Acrobat.

Unexpected Freelancer File Types Unfavorable Standard Terms Unstandardized Counter‑drafts Urgent Scope Change Decision Urgent Vendor Packet Assembly Wrong Canonical Procedure

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.

The rest of the map

Same library, five ways in.

Work Atlasthe whole map, interactive Careers1,949 jobs and their real tasks Soft skillsthe human part of the work Activities500 things people do Prompt Librarybrowse every prompt