Work Agreement

This agreement outlines how engagements work: what is included, how delivery progresses, payment structure, and post-launch support. Work is remote. Quality and clarity are non-negotiable. Please read before kickoff.

Scope is whatever is explicitly agreed in the proposal, email, or written brief. Typical engagements include:

• Full-stack development (front-end and back-end)
• Responsive layouts across modern devices
• Compatibility with current major browsers
• Implementation of approved designs, logic, and APIs

Work outside the agreed scope is scoped and priced separately before it begins.

Projects move through a clear sequence so progress stays visible:

1. 01

   Discovery

   Goals, constraints, content, and success criteria.

2. 02

   Planning

   Structure, UX decisions, or adoption of provided designs.

3. 03

   Development

   Build, integrate, and refine against the agreed brief.

4. 04

   Review

   Shared preview, feedback, and revisions within policy.

5. 05

   Handoff

   Delivery or launch after payment milestones and sign-off.

Each project timeline is set by size and complexity and confirmed in the proposal or written correspondence. Meeting dates depends on timely content, feedback, and approvals from the client.

Two revision rounds are included for in-scope changes — copy, color, spacing, and layout adjustments. Material changes that expand scope or require redesign are quoted before work continues.

Engagements typically begin with an upfront portion of the total fee. Remaining balance is due by stage or on delivery, as stated in the proposal or invoice. Amounts, methods, and due dates are confirmed in writing before work starts.

To keep the schedule intact, the client agrees to:

• Provide copy, images, and brand assets by agreed dates
• Respond to questions within a reasonable window
• Give clear written feedback and approvals during review

Repeated delays in assets or approvals may shift the delivery date; coordination will be offered in good faith.

Upon full payment and delivery, ownership of the delivered project files and code transfers to the client. The provider may include the work in a personal portfolio unless otherwise agreed in writing.

A limited support window (typically 14–30 days from delivery) covers bugs or defects from the original build at no extra cost. New features or substantial changes after that window are scoped and priced separately.

Either party may request cancellation by mutual written notice. Work completed through the cancellation date remains payable for the stage delivered. Disputes are handled directly and in good faith.

Confirming a proposal, making the initial payment, or sending written go-ahead constitutes acceptance of these terms. Request any amendments before kickoff so both parties start aligned.