← Back to homepage

COOPERATION_PROTOCOL_

[ REVISION: 2026.04.03 ]|[ STATUS: OPERATIONAL ]

[ 01 ] SYSTEM_SCOPE_

This Protocol defines the rules for using services provided by DevStudio.it and the terms of cooperation for digital projects. It forms a contractual layer with the Client alongside offers and statements of work or service agreements.

Acceptance (including submitting a brief, signing a contract, or starting work after written confirmation) means the Client has reviewed this Protocol and agrees to its provisions where required by law.

[ 02 ] OPERATIONAL_GLOSSARY_

The following definitions apply throughout the document — individual contracts may extend them unless that conflicts with applicable law.

  • ProviderDevStudio.it — engineering and advisory services in software development and web infrastructure.
  • ClientA natural person conducting business, a legal entity, or an organizational unit using the Provider's services.
  • ProjectWebsite, store, web/mobile app, integration, AI module, or other digital deliverable covered by the Agreement.
  • AgreementSeparate services agreement / work contract / annex, including attachments (e.g. specification, backlog).
  • ProtocolThis document — the cooperation policy published at devstudioit.com.

[ 03 ] REALIZATION_ARCHITECTURE_

ZERO_TEMPLATES_POLICY: for scopes covered by a bespoke engineering agreement, we do not deliver off-the-shelf white-label templates as a substitute for a real build — we design and implement for the Client's goals with full control over code and IP.

The Provider performs services per the Agreement. Operational scope includes:

  • Engineering of e-commerce systems and stores on a custom stack
  • AI models, automation, and data integrations
  • Web performance optimization (Core Web Vitals, frontend/backend architecture)
  • Web & mobile apps, APIs, ERP/CRM/logistics integrations
  • UI/UX design and conversion-path audits
  • Support, maintenance, monitoring, and post-launch partnership modules

[ 04 ] DELIVERY_PIPELINE_

Default workflow (adjustable in the Agreement):

  1. 01.Discovery / consultation and requirements analysis
  2. 02.Proposal, estimate, and schedule
  3. 03.Signing the Agreement and kick-off
  4. 04.UI/UX (if in scope)
  5. 05.Implementation, code review, staging
  6. 06.Testing, optimization, acceptance
  7. 07.Production deployment and handover
  8. 08.Post-sales support per package

[ 05 ] PAYMENT_PROTOCOL_

Invoices, settlements, and payment conditions:

  • Bank transfer or card — per invoice
  • Installments available for larger Projects
  • Advance 30–50% before work starts (default; otherwise per Agreement)
  • Balance after acceptance or per milestone schedule
  • Invoices compliant with VAT and accounting rules

[ 06 ] IP_AND_CODE_OWNERSHIP_

After full payment for a given Project, economic rights to the delivered code and materials handed to the Client transfer to the Client, unless the Agreement states otherwise.

The Provider may reuse general patterns, helper libraries, and technical know-how that are not unique to the Client's Project.

[ 07 ] LIABILITY_SLA_

The Provider is responsible for service quality as defined in the Agreement. Liability is typically limited to the fee for the given Project, excluding damages from intentional misconduct.

The Client provides complete, truthful data and assets required for delivery — Client delays shift the timeline.

[ 08 ] AGREEMENT_EXIT_

Either party may terminate the Agreement observing the notice period in the Agreement (default 14 days unless otherwise agreed). If terminated by the Client, the Provider is entitled to payment for work performed and justified costs.

[ 09 ] DEFAULT_REGULATIONS_

Matters not covered by this Protocol or the Agreement are governed by Polish law. Disputes fall under courts competent for the Provider's seat unless mandatory law provides otherwise.

Effective from 18.09.2024. Last document revision: 2026.04.03.