// legal — msa overview

A structured contracting model
designed for clarity

Arlo operates under a structured engagement model designed to support clarity, flexibility, and long-term collaboration. Engagements are typically governed by a Master Services Agreement (MSA), supported by project-specific Statements of Work (SOW).

// contracting layers

One framework. Layered for every engagement.

Core terms stay stable. Project-specific details and client-required provisions layer on top — without renegotiating the foundation.

~/contracting/layers.conf

  • msageneral framework · terms · ip · liability
  • sowscope · timeline · pricing · acceptance
  • change orderdocumented updates to scope or timeline
  • addendaclient-specific legal, security, or compliance terms
01

How engagements are structured

The MSA establishes the general legal and operational framework for working together, while each SOW defines the specific details of an engagement.

Master Services Agreement (MSA) — covers

  • ·General terms and conditions
  • ·Confidentiality and data handling
  • ·Intellectual property framework
  • ·Payment terms and billing structure
  • ·Liability and risk allocation

Statement of Work (SOW) — defines

  • ·Project scope and deliverables
  • ·Timeline and milestones
  • ·Roles and responsibilities
  • ·Pricing and payment schedule
  • ·Acceptance criteria

This structure allows projects to move quickly without renegotiating core terms for each engagement.

02

Flexibility & alignment

While Arlo maintains a standard MSA framework, we regularly align with client-specific requirements, including enterprise and government procurement processes.

  • 01Reviewing and adapting to client-provided agreements
  • 02Supporting required legal, security, or compliance provisions
  • 03Incorporating organization-specific terms where appropriate

Our goal is to streamline contracting while meeting the requirements of each organization.

03

Key engagement principles

Clarity of scope

  • ·Each engagement is defined through a clear and documented scope to reduce ambiguity and ensure alignment.

Structured delivery

  • ·Work is executed in defined phases with clear checkpoints, approvals, and communication protocols.

Controlled change management

  • ·Changes to scope, timeline, or deliverables are handled through documented updates to maintain transparency.

Long-term maintainability

  • ·Systems and deliverables are structured to support ongoing use, iteration, and ownership.
04

Intellectual property approach

Unless otherwise specified in a written agreement:

  • 01Clients receive rights to project-specific deliverables upon completion and payment
  • 02Arlo retains ownership of underlying frameworks, methodologies, and pre-existing materials

This approach allows us to deliver efficiently while ensuring clients retain control over their systems.

05

Working with Arlo

Arlo engagements are designed to integrate smoothly with internal teams, external partners, and existing workflows.

  • 01Collaborate with internal stakeholders and technical teams
  • 02Operate as an embedded engineering unit or delivery partner
  • 03Support both standalone projects and ongoing engagements

Strategic and experience-layer engagements may be supported in collaboration with Jirehnet, depending on project scope.

06

Availability of full documentation

Full MSA documentation is available upon request and is provided during the contracting process.

07

Contact

For questions regarding engagement structure or contracting:

hello@arlo.eng