Custom Enterprise BCP Encoding

Who this SOW is between.

Formal notices under Section 10(j) of the Agreement require personal or overnight-courier delivery. Operational approvals and invoices may go by email, effective one business day after sending.

What this engagement is for.

Encoded Brands will support the creation, composition, and integration of a Brand Context Protocol (BCP) file for each brand in scope, encoding Rumble, RUM Group, and Quake.ai, verifying each domain, and rolling out MCP access across each brand's authorized AI tools, phased to match how ready each brand actually is. Rumble goes first since it's established and ready now; RUM Group and Quake.ai follow once each confirms readiness.

What's covered.

Brands in scope

Out of scope: content creation, tool procurement, ongoing agency management, and any brands beyond the three listed above.

RUM Group Inc. authorizes Encoded Brands to retrieve and process content from the domains, files, and sources it submits, and to draw on open-web research of publicly available material, to create and maintain each BCP.

What "Deliverables" means for this SOW.

Work Product under this SOW means the structured brand content compiled into each brand's BCP file (Rumble, RUM Group, Quake.ai), and is work made for hire per Section 4(a) of the Agreement, assigned to Client on payment of the applicable Fees.

Consultant Materials means the Encoder, the Brand Context Protocol (BCP) format and methodology, the Registry platform, and related templates used to produce and host the BCP files, per Section 4(c) of the Agreement. Client receives the license described there to use Consultant Materials as integrated into each BCP file, for that file's intended purpose.

Registry hosting is a Service, not a Deliverable. It is the ongoing hosting, signing, and domain verification of each Verified BCP endpoint, billed as the recurring fee in section 06 and running for as long as the applicable Registry subscription is active. If this SOW or the Agreement ends, the hosting service stops and each endpoint is taken down, but ownership of the underlying Work Product already assigned to Client is unaffected — Client may export each BCP file per the Agreement's ownership terms.

Phases and duration.

Phase 1 runs the full 6-week standard duration because it builds the things Phases 2 and 3 reuse: the discovery framework, the interview question set, the claims-review process, and the working rhythm between our teams, developed through Encoded Brands' prior work with these brands under Bruiser. RUM Group and Quake.ai compress to 3 weeks each because they skip that setup — discovery for each is scoped against the framework Phase 1 already validated, and the encoding and claims-review cycle runs on a proven template rather than being designed from scratch. The fee credit in section 06 reflects the same relationship and the same reuse, not a lower quality bar — each brand's published BCP file meets the same standard.

Phase 1 begins within 5 business days of signature. Phases 2 and 3 may run concurrently with Phase 1 if RUM Group or Quake.ai are ready sooner; total elapsed time is 6 weeks if only Rumble proceeds, up to roughly 12 weeks if all three phases run sequentially. Delays caused by client dependencies extend the affected phase day for day.

Engagement fee and schedule.

Custom Enterprise BCP Encoding — standard package

The standard charge for a Custom Enterprise BCP Encoding is $50,000 per brand. This includes: up to 8 stakeholder interviews, one consolidated round of legal review of the claims set, domain verification, Registry publication, BCP integration, a team enablement session, and a BCP ownership transfer session, delivered over a 6-week duration. Work beyond this standard scope — additional stakeholder interviews, additional legal review rounds, expanded workstreams, or a compressed timeline — is scoped and priced as needed under Section 3 of the Agreement (change control).

Project fees

If only Rumble proceeds, total project fees are $50,000 plus travel and expenses. RUM Group's and Quake.ai's phases are priced and locked in this SOW now, but only invoiced once each brand confirms readiness in writing — that activation is not a change order under Section 3 of the Agreement, just a scheduled trigger for scope already agreed here.

Registry subscription

Ongoing hosting fee, billed monthly per brand from that brand's publication date. Includes unlimited teammates, no per-seat charges, up to 100 AI-assisted re-encodes annually per brand (additional re-encodes $49 each), unlimited Registry reads, and AI-tool connections, per Section 2(a)(ii) of the Agreement.

Payment schedule

• Per phase: 100% of that phase's fee invoiced when the phase kicks off (signature of this SOW for Phase 1; written confirmation of readiness for Phases 2 and 3), per Section 2(a) of the Agreement.
• Registry subscription invoiced monthly in advance from each brand's publication date, after any included free month.
• Travel and expenses invoiced at cost as incurred, with receipts, per Section 2(b) and 2(g) of the Agreement.

Net 30, applicable taxes, and late-payment interest follow Section 2 of the Agreement and are not restated here.

Discipline responsibilities involved in process.

Who needs to be in the room.

What must be in place.

• DNS access (client) — ability to add verification records for each in-scope domain.
• Source materials (client) — brand guidelines, tone documents, claims registers, existing schemas, shared by end of week 1 of each phase.
• Stakeholder availability (client) — all named stakeholders in section 08, including the legal reviewer for claims sign-off, available and responsive within 5 business days of contact.
• Tool stack inventory (client) — list of AI tools and agents to be configured to read each file.
• Vendor platform inventory (client) — list of third-party platforms (CMS, DAM, e-commerce, martech, etc.) that hold source material or need to reflect the published BCP file.

What's public, on purpose.

Notwithstanding Section 9 of the Agreement, content RUM Group Inc. approves for publication through the Registry — each Verified BCP endpoint — is intentionally public and readable by third parties and AI systems, and is not Confidential Information once published. Working materials, drafts, and unpublished claims discussions remain RUM Group Inc.'s Confidential Information under Section 9.

Developing a measurement pilot together.

Encoded Brands is willing to design and support the execution of a measurement plan for this pilot, at no additional charge: an A/B test comparing how configured AI surfaces represent the brand with and without the published BCP file, and an employee survey capturing internal reaction to the rollout.

In exchange, Encoded Brands would like to use the resulting data and findings in its own marketing. Nothing goes live without RUM Group Inc.'s review and approval first, on a case-by-case basis for each specific use.

Separately, and notwithstanding Section 10(c) of the Agreement, each party may identify the other as a customer or supplier in customer lists, on its website, and in marketing materials, following any brand guidelines the other provides. None of this is a condition of the Fees in section 06.

What runs the Encoder, and your approval window.

Encoded Brands' Encoder uses one or more AI Tools that operate under a zero-data-retention standard: the AI Tool provider does not store or log Client Data beyond what is needed to generate a response, and does not use Client Data to train, fine-tune, or improve any model available to third parties, consistent with Section 6(b)(ii) of the Agreement. Encoded Brands may use, add, or substitute among AI Tools meeting this standard over the course of the engagement without further approval, provided each continues to satisfy Section 6(b)(ii) of the Agreement; on request, Encoded Brands will provide the current list of AI Tool providers in use. AI Output forms a material degree of each file's drafting, within the meaning of Section 6(b)(ii) of the Agreement. Per Section 6(b)(iii), RUM Group Inc. has 10 business days from the date of this SOW to object in writing to Encoded Brands' use of AI Tools meeting this standard; absent objection, this standard is deemed an approved basis for AI Tool use for this engagement, and the risk allocation in Section 6(e) applies to AI Output it produces.

When scope moves.

Changes to scope, schedule, or Fees are handled under Section 3 of the Agreement: written and signed by both parties. Activating Phase 2 or Phase 3 per sections 05 and 06 is not a change order; it is scheduled per the delivery plan once RUM Group Inc. confirms readiness. Adding brands beyond the three named in section 03, or expanding a phase's workstreams, does require a change order.

How this SOW, the Agreement, and our online terms relate.

The Agreement governs the parties' relationship. This SOW controls scope, Deliverables, schedule, and Fees, and modifies the Agreement only where it expressly identifies the provision being modified. Encoded Brands' online Terms of Service govern Client's use of the Encoder and Registry only to the extent they do not conflict with the Agreement or this SOW. The online Refund Policy does not apply to Fees invoiced under this SOW.

What this plan assumes.

• Client dependencies in section 09 land on schedule; slips extend the affected phase day for day.
• Working sessions run remotely unless travel is agreed and pre-approved.
• Stakeholders in section 08 have authority to make decisions in their area.
• One consolidated round of legal review per brand's claims set; additional rounds go through change control.
• Phase 2 and Phase 3 timing depends on RUM Group Inc. confirming readiness for RUM Group and Quake.ai; neither is guaranteed to start within Phase 1's 6 weeks.

All other terms — ownership, warranties, liability, indemnities, term and termination, confidentiality outside the carve-out in section 10, and general provisions — are governed by the Agreement and are not restated here.

Agreed and accepted.

Signed by authorized representatives of each party, pursuant to the Agreement.