From a request to completed work
A request starts a discussion; an agreement makes the shared terms explicit.
Create Intent
Start with a private Project Brief that records the outcome, project type, preferred dates, location, budget guidance, deliverables, usage expectations, creative direction and relevant shortlist. It is a planning record. It does not reserve a date, create an Agreement or start Production.
Keep the brief specific enough to answer and open enough for another creative person to shape. If assisted matching is offered, consent is an explicit choice; it is never assumed from saving a brief or profile.
- Write the outcome and deliverables.
- Add dates, location, usage and budget guidance.
- Name the questions still open.
Accept one exact Agreement version
The provider can propose roles and terms after reviewing the request. Check participant names, responsibilities, schedule, deliverables, revisions, usage, compensation or exchange, expenses and change rules. The meaningful acceptance is tied to the exact version displayed to both people.
An accepted version remains the shared reference. If a material term changes, create a new version or amendment and let both participants review it. Conversation adds context; it does not silently override the accepted record.
Work in linked Production
After the same Agreement version is accepted, Production can hold messages, delivery, issue reporting and completion review in one project context. Keep scope questions beside the record and pause when a material problem cannot be resolved.
Once the requester reviews the final delivery and marks the work complete, eligible reviews and contribution confirmation remain separate choices. A review describes the experience of working together; a confirmed contribution identifies a role in the project. Check the billing status shown in the workspace before expecting any payment action.