- What consumes capacity
- Monthly capacity includes multidisciplinary delivery time: product management, requirement clarification, UX and UI work, software development, technical configuration, QA and testing, standard deployment activities, delivery documentation, scheduled client meetings, internal delivery coordination directly related to the engagement, and delivery and progress reporting. These activities are included within the plan but consume the plan’s allocated capacity.
- Changes and rework
- QA and standard testing are included within monthly capacity. Rework caused by a Primewayz implementation defect should not be double-charged. Rework caused by changed requirements, new scope or delayed client decisions consumes capacity.
- Additional capacity
- Additional capacity must be requested and approved before work is performed. It is subject to delivery-team availability and may be supplied as an additional approved block or through a temporary plan upgrade at the applicable commercial rate from the canonical pricing configuration or an approved proposal.
- Hosting and third-party dependencies
- Hosting, software licences, paid APIs, stock assets, specialist services and other third-party costs are excluded unless explicitly included in a signed proposal.
- Access and client dependencies
- The client is responsible for timely access, content, credentials, approvals and decisions. Capacity reserved for a billing month remains subject to the normal rollover policy when work is delayed by missing client input. Primewayz provides reasonable warning where a client dependency threatens delivery.
- Emergency and out-of-hours work
- Emergency or out-of-hours work is not automatically included. It is subject to availability, explicit approval, and may require additional commercial treatment.