← Legal Center

Effective and last updated October 4, 2026

Project & Statement of Work Terms

Default rules for project scope, dependencies, changes, acceptance, and handover.

Applies to: Customers and professionals on scoped projects

Required project details

  • Parties, project name, deliverables, and explicit exclusions.
  • Platforms, environments, integrations, dependencies, price, taxes, deposit, and milestones.
  • Client materials, access, dates, revisions, acceptance tests, and review period.
  • Change-order procedure, third-party costs, licenses, ownership, confidentiality, and security scope.
  • Hosting, maintenance, support, warranty if any, termination economics, and authorized approvers.

Change orders

A Change Order should identify the requested change, added or removed deliverables, price impact, schedule impact, and assumptions. No material change binds either party until accepted by authorized representatives through the designated workflow.

Dependencies and delays

Schedules pause or adjust when a required dependency is late. If delay materially affects reserved capacity, Pyramad may reschedule resources and reasonably revise timing or price after notice.

Handover

After final payment and subject to the Project Agreement, Pyramad will provide agreed handover materials, which may include source code, design files, deployment instructions, transferable credentials, or documentation. Internal tools, security-sensitive materials, proprietary systems, and items not listed as deliverables are excluded.

Legal contact: legal@pyramad.com

These policies should be read together. A signed project agreement controls where it expressly says so.

THE NEXT THING STARTS HERE

What will you
bring to life?

Start building for free
PYRAMAD®   /   MAKE WHAT MATTERS