Every engagement follows the same sequence: written scope — HTML preview — preview approval — payment — milestone build — delivery — handover. The order is deliberate: quality is demonstrated before payment, and payment discipline protects the final handover.

This policy defines what "delivery" means, when it has occurred, and how revisions work. Your signed scope of work may add engagement-specific gates, and prevails where it differs.

Before the first payment request, we deliver a working HTML preview of the core solution generated from your approved scope. The preview is clickable, reflects the agreed structure, and is sent with a review period stated in writing.

You may approve the preview or request revisions. Revisions requested at preview stage — while the work is within the approved scope — are included at no cost. The preview becomes a permanent reference for the engagement: what is delivered at completion must match what was previewed, as amended by agreed scope changes.

Payment begins only after your written preview approval. This is the first gate of the delivery model.

Timeline commitments are stated in the Final Scope of Work and begin from the later of: scope approval, or receipt of required client materials and access. Each milestone carries its own acceptance date.

The following events are timeline gates that pause or extend the schedule and are communicated in writing: pending client feedback beyond the stated review period; pending client materials, content or credentials; approved scope changes; and third-party dependencies outside our control (for example, payment gateway or API approvals).

We commit to informing you of any gate event within one business day of it arising — not at the deadline.

Included with every engagement: two revision rounds within the approved scope. A revision round is a consolidated set of change requests submitted together. Piecemeal requests received separately are grouped into the current round.

Preview-stage revisions (before payment) are free and do not count against the two rounds.

Requests outside the approved scope are not revisions — they are scope changes handled under the Client Approval Policy with a new written quote and timeline before work begins.

Delivery occurs when the solution is deployed or handed over in the manner the scope defines (for example: live on your hosting, or package handover), passes the agreed quality checklist, and you have confirmed delivery in writing.

If you do not respond to a delivery notice within the review period stated in the scope (default: five business days), the delivery is considered accepted unless defects are reported. This prevents indefinite open states, and we will remind you before the period closes.

Defects reported at delivery are fixed at no cost where they reflect non-conformity with the approved scope. This obligation is the warranty for the engagement and continues for 30 days after delivery acceptance.