Legal · Pod changes

Addendum to Master Service Agreement

Last updated · June 2026
This is a draft template of our standard Addendum for K15 Labs managed pods. The exact Addendum is filled in when Client adds a pod member to the pod.

Adding a pod member to your pod uses this short, predictable addendum: the added role, member type, allocation, code-producer status, start date, added monthly price, and updated monthly plan. Fields in brackets are filled in at signing.

01

Parties and structure

This Addendum (“Addendum”) is entered into between K15 Labs, LLC (“K15 Labs”) and [Client legal name] (“Client”).

This Addendum modifies the Master Service Agreement between the parties dated [MSA date] (“Agreement”). See /legal/msa.

Once signed, this Addendum forms part of the Agreement. All terms of the Agreement remain in effect unless this Addendum expressly changes them.

Document type: Pod change.

02

Purpose

Client wishes to add one or more pod members to the existing K15 Labs managed pod.

This Addendum confirms:

  • the added role;
  • the member type;
  • the allocation;
  • whether the member counts as a code-producer;
  • the start date;
  • the added monthly price;
  • the updated monthly plan;
  • any changed operational terms.
03

Added pod member

  • Role: [AI-native developer / designer / QA / cloud/DevOps engineer / other specialist]
  • Specialty or focus: [Full-stack / frontend / backend / DevOps / QA automation / manual QA / design / data integrations / AI workflows / other]
  • Pod: [Existing pod name]
  • Allocation: [Full-time / part-time / percentage allocation]
  • Required skills or context: [As agreed]
  • Start date: [Confirmed start date]

The added member joins the pod as an ongoing part of the managed team, not as a short-term contractor rented directly by Client.

04

Code-producer status

The added member:

  • ☐ Counts as a code-producer.
  • ☐ Does not count as a code-producer.

A member counts as a code-producer if their role includes shipping code, including AI-native developers and code-producing specialists such as cloud/DevOps engineers or QA engineers writing test automation.

A member does not count as a code-producer if their role does not include shipping code, such as designers or manual-only QA.

Code-producers in the pod after this Addendum: [N] of 5.

If code-producers exceed 5, an additional pod is required. Any additional pod, Technical Lead coverage, Pod Owner coverage, and related pricing must be confirmed in writing.

05

Work and priorities

The added member will work under the same engagement framework as the rest of the pod.

Client’s Product Owner continues to decide what gets built, in what order, and what “done” means.

K15 Labs continues to manage staffing, coordination, delivery cadence, replacement logistics, and Technical Lead review under the Agreement.

Day-to-day priorities are coordinated through the Pod Owner and handled under the agreed process of record.

06

Intellectual property

All Work Product created by the added member for Client is owned by Client on the same terms as the Agreement (see /legal/msa#ip).

Client ownership applies from the moment the Work Product is created.

The added member does not change the Agreement’s intellectual property, confidentiality, security, or replacement terms.

07

Added monthly price

Added monthly price: [Added monthly amount]

Pricing basis:

  • ☐ Additional code-producer, starting from $6,490 per month, pro-rated to the allocation actually used.
  • ☐ Additional non-code-producing specialist, starting from $6,490 per month, pro-rated to the allocation actually used.
  • ☐ Specialist role with custom pricing: [Amount and basis]
  • ☐ Additional pod required because code-producers exceed 5: from $7,500 per month, Pod Owner and Technical Lead included [pod details].

Billing currency: USD.

Billing for the added member begins on [billing start date], unless otherwise agreed in writing.

If the added member starts mid-billing cycle, the first invoice for the added member will be pro-rated unless otherwise agreed.

08

Updated monthly plan

  • Previous monthly plan: [Previous monthly amount]
  • Added monthly amount: [Added monthly amount]
  • New total monthly plan: [New monthly amount]
  • Pass-through costs, if any: [None / describe]
09

Changed operational terms

Unless listed below, there are no changes to tools, reporting cadence, availability, process of record, AI tooling, security requirements, or engagement scope.

Changes: [None / list changes]

10

Replacement and continuity

The added member is covered by the Agreement’s replacement and continuity terms.

K15 Labs may replace the added member under the Agreement.

Client may request a replacement for reasonable cause through the Pod Owner.

Where practical, K15 Labs will use a continuity process so that open tickets, pull requests, context, and current priorities are handed over before rolloff.

11

No direct employment relationship

The added member remains assigned and managed by K15 Labs.

This Addendum does not create an employment relationship, contractor relationship, agency relationship, or direct staffing relationship between Client and the added member.

K15 Labs remains responsible for hiring, management, supervision, compensation, replacement, and performance management of its personnel.

12

Confirmation

Except as expressly modified by this Addendum, the Agreement remains unchanged and in full effect.

13

Signatures

Signatory
K15 Labs, LLC
Name
[Authorized signer]
Title
[Title]
Signature
 
Date
 
Signatory
[Client legal name]
Name
[Signer name]
Title
[Signer title]
Signature
 
Date