Journal
From request to agreement
The space between an idea and a booked job is where the good questions go.
A request is an invitation
Give enough to decide: what, when, where, deliverables, usage, budget, who else is involved. Short and clear beats long and vague.
Sending a request doesn't book or charge anything. The other person can ask questions or decline.
Accept the exact version
The agreement puts it all in one place: people, roles, dates, deliverables, usage, price, expenses and what happens if plans change. Read it, then accept that version.
- Names and roles.
- Dates, deliverables, usage and money.
- What happens if things change.
No is a fine answer
A quick yes nobody understood is worse than a careful no. If something changes after you agree, send a new version instead of settling it in chat.