1. A proposal comes first
Posting a project request does not create a contract or payment obligation. Work begins only after both parties accept a written proposal, statement of work, or equivalent agreement. That signed project document controls if it differs from this general page.
2. Scope, milestones, and schedule
The project document should identify deliverables, exclusions, milestones, acceptance points, dependencies, estimated timing, and the delivery approach. Dates depend on timely access, content, decisions, and feedback from both sides.
3. Client inputs and access
The client is responsible for providing accurate requirements, lawful content, authorized access, a decision-maker, and timely feedback. Domains, production accounts, payment-provider accounts, and other business-critical services should normally remain in the client's control.
4. Fees and payment
The accepted proposal defines currency, taxes, deposit or first milestone, later payment stages, invoicing, due dates, and third-party costs. All public prices and budget ranges are negotiable starting guides, not binding quotes. The final agreed amount is recorded in the accepted proposal before work begins.
5. Change control
Material work outside the accepted scope is explained before it is built. The parties should agree any effect on cost, schedule, or milestones in writing. Small clarifications that do not materially change the work can be handled within normal delivery communication.
6. Intellectual property and third-party tools
The project document records ownership and handover. Unless agreed otherwise, project-specific deliverables are transferred after the related fees are paid. Pre-existing tools, reusable know-how, open-source software, fonts, themes, APIs, and third-party services remain subject to their own ownership and license terms.
7. Confidentiality and NDA
Both sides should use non-public project information only for evaluating or delivering the work. A reasonable mutual or client NDA can be reviewed before sensitive details are shared. Credentials and private keys should be exchanged through an agreed secure channel, not the public form.
8. Review, acceptance, and support
Milestones should include a practical review or acceptance period. Defects against the accepted scope are handled under the proposal's correction terms. Enhancements, changing requirements, third-party failures, and ongoing maintenance are separate unless explicitly included.
9. Pausing or ending a project
The accepted proposal should explain notice, payment for completed work, treatment of deposits, handover of completed deliverables, and access removal. Governing law, liability limits, warranties, and dispute terms are also set in that signed document.