Policy

Software Terms of Service

By commissioning COWebs.lb for software builds, you agree to the terms below. These keep both parties aligned throughout discovery, build, and support.

01

Scope of Services

COWebs.lb provides bespoke desktop software, automation pipelines, internal dashboards, and related consulting. Deliverables are controlled by the approved proposal or statement of work (SOW). Any work requested outside that scope is treated as a formal change request and quoted separately.

  • Deliverables may include source code, installer packages, documentation, and training only when explicitly listed in writing.
  • Timeline dates are best-effort estimates, not guaranteed delivery deadlines.
  • Third-party licenses, APIs, hosting, and SaaS fees are billed to the client unless stated otherwise.
  • Client is responsible for providing accurate content, timely approvals, and lawful use of delivered systems.
02

Feedback & Revisions

  • Each milestone includes up to two revision rounds focused on the functionality delivered.
  • Feedback windows last five business days. Missing a window may shift the launch timeline and resource allocation.
  • Milestone approval can be provided by email, WhatsApp confirmation, or signed acceptance notes.
  • Major directional changes after approval are considered new scope and require a change order.
03

Payments

Milestone terms follow the Payment Policy. Work may be paused automatically when invoices are overdue, and delivery access may be restricted until balances are cleared.

  • Deposits are non-refundable once discovery assets are handed over.
  • Retainers renew monthly until either party gives 30 days written notice.
  • All invoices are payable in USD unless explicitly agreed otherwise in writing.
04

Intellectual Property

  • Ownership of project-specific deliverables transfers only after full and cleared final payment.
  • Reusable internal libraries, templates, frameworks, and tooling remain property of COWebs.lb, with a perpetual project-use license granted to the client.
  • Third-party components remain subject to their original license terms and restrictions.
  • COWebs.lb may showcase non-confidential screenshots in portfolios unless prohibited by NDA.
05

Confidentiality & Security

All shared data, databases, credentials, business records, and technical documents are treated as confidential information.

  • Confidentiality obligations apply to both parties and survive project completion or termination.
  • Credentials are stored in encrypted vaults and rotated after project completion.
  • Unless otherwise agreed, project data and credentials are deleted from active environments within 30 days after handoff.
  • Security audits or penetration testing can be arranged for an additional fee.
06

Support & Warranty

  • Bug fixes within 30 days of launch are complimentary.
  • Operational issues caused by external vendors, API outages, or infrastructure are billed hourly.
  • After the warranty period, services are provided on a retainer or time-and-material basis.
  • COWebs.lb commits to commercially reasonable efforts to deliver stable and functional systems throughout the agreed scope.
  • Software is provided as delivered for the agreed scope; uninterrupted or error-free operation is not guaranteed.
  • Retainer clients receive priority support per their SLA.
07

Termination

  • Either party may terminate with written notice if the other materially breaches the agreement and fails to cure within 10 days.
  • On termination, all unpaid work becomes due immediately and deliverables produced to date are handed over.
  • COWebs.lb may suspend work immediately for non-payment, abusive or unprofessional conduct, or unlawful use requests.
  • Clauses on payment, IP, confidentiality, liability, and dispute resolution survive termination.
08

Liability, Law & Disputes

  • To the maximum extent permitted by law, COWebs.lb is not liable for indirect, incidental, or consequential damages.
  • Total liability is capped at fees paid for the affected milestone or the previous three months of retainer fees, whichever is lower.
  • Both parties agree to attempt good-faith resolution within 15 business days before formal proceedings.
  • These terms are governed by Lebanese law. Disputes fall under the competent courts of Beirut unless both parties agree to arbitration.

Questions about these terms

Send an email to cowebs.lb@gmail.com or message on WhatsApp. Custom agreements and NDAs are welcome.

Contact Christian

Scope Control and Service Accountability

Strong terms of service protect both execution quality and project clarity. We define scope expectations, acceptance criteria, delivery boundaries, and communication responsibilities so implementation decisions can be managed with consistent accountability.

This framework reduces ambiguity when requirements evolve and helps teams assess change requests with transparent effort impact. Clear contractual structure also supports smoother handoff, predictable maintenance planning, and more reliable collaboration across stakeholders.

For long-term engagements, terms alignment ensures continuity as systems grow in complexity. It establishes a stable operating baseline for feature expansion, integration updates, and support governance without compromising delivery discipline.

Contractual Clarity for Sustainable Delivery

Software execution quality depends on clear assumptions, realistic sequencing, and accountable handoff. We treat implementation as an operational system, not just feature delivery, so each milestone is validated against business impact, dependency readiness, and maintainability constraints.

This approach helps teams avoid common failure points: unclear scope boundaries, rushed integration decisions, incomplete documentation, and unstable rollout plans. It also improves budgeting discipline by aligning effort with outcome-critical priorities rather than broad, low-impact work bundles.

For Lebanese businesses building internal capability, this structure supports durable adoption: better process reliability, lower manual error rates, stronger reporting confidence, and consistent performance through growth stages.