Development Terms & Conditions

Scope & Estimates

• All project estimates are calculated based on the initial scope and specifications provided by the client at the time of inquiry.
• If additional features, changes in functionality, or new integrations are requested after the estimate is issued, the total development time and cost will be revised accordingly.
• To ensure accurate planning and avoid unexpected delays or costs, clients are strongly encouraged to provide complete and detailed requirements before work begins.

Hourly Adjustments

• Development hours may increase if the project scope evolves, requirements are unclear, or additional technical challenges arise during implementation.
• Issues related to legacy systems, outdated codebases, or third-party plugin conflicts may require extra time for troubleshooting and resolution.
• Any adjustments to the estimated hours will be communicated transparently, and work will proceed only after client approval.

Payment Terms

• Payment is due in full as soon as the project is confirmed. A project is considered confirmed when a member submits their initial request and both parties have reached a written agreement on the scope of work, including what can and cannot be delivered. Work will commence only after payment has been received.
• If, at any point after the project has started, the member requests changes, additions, or new features that fall outside the agreed scope, these will be treated as change requests. Where such changes are billable, a separate invoice will be issued. Work on the requested changes will begin only after the corresponding payment has been received.

Legacy System Compatibility

• Projects involving older PHP or MySQL systems may require additional effort to ensure compatibility with modern development standards and security practices.
• Where possible, we will refactor or isolate legacy code to maintain system stability and reduce future maintenance risks.
• Clients should be aware that legacy integration may impact timelines and require flexible planning.

Change Requests & Scope Management

• All work will be carried out according to the agreed project scope defined at the start of the engagement.
• Any request that alters, expands, or replaces the agreed scope — including new features, design changes, or functional adjustments — will be considered a change request.
• Change requests will be reviewed and, if accepted, estimated for additional time and cost. Work will only proceed once the client has approved the revised estimate in writing.
• To maintain efficiency and avoid delays, clients are encouraged to consolidate feedback and change requests into a single, organized submission per revision round.
• Unapproved or ongoing changes that significantly impact timelines may result in the project being paused until scope and budget are re‑confirmed.

Revisions & Feedback

• Minor revisions, such as layout adjustments or text edits, are typically included within the original estimate.
• Major revisions, such as changes to core logic, database structure, or user flow—will be treated as new tasks and billed separately.
• Timely and specific feedback from the client helps ensure revisions are completed efficiently and accurately.

Code Alteration & Warranty

• The delivered code is tested and verified to function as agreed at the time of deployment.
• Any modifications, edits, or additions made to the codebase by the client or a third party without prior written approval will void any warranty or complimentary support period.
• If issues arise after such unauthorized changes, they will be treated as new, billable work and estimated separately before implementation.
• This policy ensures that the integrity, security, and maintainability of the system are preserved.

Security & Data Integrity

• All user input will be properly validated, escaped, and sanitized to prevent common vulnerabilities such as SQL injection and cross-site scripting (XSS).
• Bizeem follows industry best practices to ensure that the codebase is secure, maintainable, and aligned with modern PHP standards.
• Security is treated as a core priority throughout the development lifecycle, especially in areas involving user authentication, data storage, and form handling.

Delivery & Deployment

• All deliverables will be thoroughly tested in a staging environment to ensure functionality, performance, and compatibility before deployment to production.
• Deployment support is included unless otherwise specified, and we will assist with server configuration, database migration, and final setup as needed.
• Any post-deployment issues directly related to the original scope will be addressed free of charge for up to 7 calendar days after launch.
• Any post-deployment issues or change requests that fall outside the original agreed scope will be treated as additional billable work. Such requests will be estimated and approved before implementation, and may be addressed within 30 calendar days following the launch.

Communication

• Clear and consistent communication is essential for successful project delivery. The designer in charge provides regular updates on progress, milestones, and any blockers encountered.
• Clients are encouraged to respond promptly to questions or requests for clarification to avoid delays.
• All communication will be documented to ensure transparency and accountability throughout the project.

Last Updated: August, 2025