TRANSPARENT ITERATIONS • SCOPE CLARITY • ZERO SURPRISE CHARGES

Revision & Scope Change Policy

We want you to be 100% thrilled with your digital product. This policy defines our collaborative revision process, ensures projects stay on schedule, and protects both parties from scope creep.

Policy Version: 2.1 Effective Date: October 2026 Scope Governance: Agile Checkpoints

1. Included Revision Cycles by Discipline

Brand Identity

3 initial conceptual directions followed by unlimited refinement rounds on the chosen direction.

UI / UX Prototyping

2 full interactive review cycles per screen/flow prior to coding lock-in.

Custom Software

Sprint-based user acceptance testing (UAT) with continuous bug and UI polish.

2. The Consolidated Feedback Process

To keep your project moving swiftly, revisions should be consolidated into structured review batches (e.g. via Figma comments, centralized Google Docs, or Loom video walkthroughs) rather than piecemeal ad-hoc requests. This ensures our design and engineering leads can address all feedback cohesively in a single sprint.

3. Revision vs. Scope Change (The Distinction)

✓ INCLUDED REVISION (FREE)
  • Adjusting typography, colors, or visual hierarchy.
  • Re-aligning layout blocks within the approved brief.
  • Replacing photography, placeholder icons, or copy.
  • Refining animations, button hover states, or padding.
⚡ SCOPE CHANGE (ADDENDUM)
  • Requesting new pages or screens not in the SOW.
  • Adding third-party integrations (e.g. ERP, CRM).
  • Changing database architecture after backend completion.
  • Rebuilding approved wireframes after coding has begun.

4. Scope Change Addendum Procedure

When a feature request falls outside the original contract scope, your project manager will provide a transparent, written Change Order Addendum stating the exact scope, timeline adjustment, and fixed cost. We never proceed with out-of-scope work without your prior written authorization.

5. Milestone Sign-Off & Architectural Lock-In

Our process is sequential. Once a milestone is signed off (e.g. wireframing), that phase is "locked." This architectural lock-in protects your budget: backtracking to rebuild structural foundations after frontend code has been engineered significantly inflates engineering hours and costs.

6. Cancellation & Milestone Refund Criteria

If you decide to cancel a project prior to completion:

  • Completed Milestones: Non-refundable, as work has already been delivered, reviewed, and accepted.
  • Work in Progress: Billed proportionally up to the formal cancellation date.
  • Unstarted Future Milestones: 100% refunded immediately to your original payment method.

7. Project Dormancy & Reactivation

To reserve dedicated engineering capacity, projects require active client participation. If a project remains unresponsive or stalled for more than thirty (30) consecutive calendar days without prior arrangement, it may be placed on dormant status.

Dormant projects can be reactivated with five (5) business days notice, subject to current team scheduling availability.