folioStart with the outcome.
Give the project a name that both parties recognize. Then describe what will be handed over: the files, access, work product or other output. A project title is a useful label, but it is not a complete scope.
The current builder provides a title and three short deliverable fields. Use the downloaded draft as a starting point for a fuller conversation, especially when the work has dependencies or several rounds of review.
Write down the boundaries.
- Name the deliverables and the format in which they will be provided.
- Identify anything the client needs to supply before work can start.
- Agree on included revisions and how additional work will be requested.
- Record acceptance criteria so that “done” means the same thing to both sides.
Give the timeline a starting point.
The workspace offers a 14, 30, 60 or 90-day delivery window. This is a proposed duration, not an automatically calculated due date. The downloaded draft describes it as running from the agreed start.
Before using an agreement, the parties still need to establish the start date and how late inputs, revisions or pauses affect delivery. A date passing is not the same as a client approving the work.
What a downloaded draft contains.
| Included by the builder | Still to be agreed |
|---|---|
| Project title and proposed USDC value | The identities and roles of both parties |
| Delivery window | Start date and milestone deadlines |
| Three deliverables and their amounts | Approval criteria and revision process |
| Unsigned draft notice | Cancellation and dispute terms |
Treat a change as a new agreement.
When the scope changes, revisit the amount and timeline rather than assuming the original terms cover the new work. Keep both parties aligned on the revised version.
The current site does not collect signatures, track versions or store shared agreements. Editing a field only changes the draft in your open page. Download it before leaving if you want to keep a copy.