[BIP-847] Fund OpCo Product team - Q3 2025

Service Provider Name: Balancer OpCo (Product Team)

Pledge to abide by [BIP-702] Balancer DAO Service Provider & Grantee Standards: Yes

Domains of Operation: Frontend software development

Introduction

Balancer OpCo Limited (or the “Balancer OpCo”) is a wholly-owned operating subsidiary of the Balancer Foundation. It is an integral element of the Balancer Foundation corporate structure supporting the Balancer DAO. It serves two primary functions (1) Administrative and Operational; and (2) Product Development.

This proposal aims to extend the product development services for the next quarter (Q3 2025). The Product team is directly accountable to the Balancer Foundation and the Balancer DAO community through the reporting process applicable to all Balancer SPs, primarily with reference to the objectives and KPIs noted below.

Retrospective

Q2 2025 presented OpCo with a unique set of challenges and opportunities. Following almost a full turnover of the frontend team, we adapted swiftly, successfully leveraging Beethoven's leadership in UI/UX and increasing collaboration with Balancer Labs for partner integrations. This period underscored our resilience and commitment to delivering on our mandate, even with a leaner structure and a more focused budget strategy, which will be fully realized from Q3 onwards.

Looking back at our Q2 objectives, we are pleased to report that all key results were achieved, including the pending release of the new veBAL experience on the zen UI.

In summary, Q2 was a period of successful transition and strong execution. The team demonstrated exceptional adaptability and delivered on all key objectives, reinforcing Balancer's position as a leading protocol with a high-quality, user-centric UI/UX. We are well-positioned for continued growth and innovation into Q3 and beyond.

Focus. Ship. Repeat.

Length of Engagement & Budget

Balancer OpCo is requesting $80,490 for 3 months of funding, starting Jul 1, 2025 and ending Sept 30, 2025. The decrease is due to lower headcount in OpCo, which costs/staff have been supported by Beethoven and Balancer Labs.

The table below shows the applicable expense categories.

Cost breakdown:

People Costs: 2 FTE at $148,206 av. annually Non-People Costs: Frontend tools, design softwares and subscriptions (i.e. Sentry, Appzi, Figma, Adobe etc.)

In addition, the Balancer OpCo is requesting an allocation of 3,125 BAL for the period of the proposal that aligns with the grants included in staff employment packages. This ongoing BAL grant is being awarded to current team members on a 4-year vesting basis, with a 1-year cliff, starting from each employee’s initial employment date in the ecosystem.

Should any of these employees leave before the completion of the quarter, any unvested BAL would not go to the departing employee and would be available to the OpCo for allocation as incentives to potential replacement staff.

Objectives and Key Results (OKR) Approach

The Product Development team ensures Balancer has a high-quality UI/UX available everywhere that allows users to interact easily with the Balancer protocol. In addition, the UI serves as a branding tool where people can better understand what the Balancer Protocol allows.

Q3/25 main focus will still be on supporting new pool types in V3, and improving user experience based on community and bizdev feedback loop, but also looking at new chain deployments.

Objective #1: Supporting new pool types

• Build, Improve and Optimize the canonical UI for interacting with Balancer: We aim to provide the best possible experience for users to provide liquidity, swap, lock veBAL, vote on gauges, and claim earnings using Balancer.
• Implement new features or improvements made to the Balancer smart contracts to the primary UI for users to interact with them on launch.
• Design, build, copywrite and maintain the marketing pages for the Balancer protocol. The primary aim of these pages will be to inspire and help onboard potential partners into the ecosystem.
• Ensure this UI works across all modern devices including desktop and mobile browsers.
• Support the development and maintenance of the shared Beets/Balancer API. The Product Development team currently maintains the Balancer API at https://api.balancer.fi, which provides quick access to Balancer pool and token information.

Objective #2: Continuous improvement in user experience

• Optimize and improve this app so users have a great experience no matter how many features or how much data Balancer introduces in the future.
• Work on the stability and reliability of the UI by covering its critical functionality with unit and integration tests.
• Monitor relevant channels in Discord, Slack and Github issues for any reported problems and aim to respond within 24 hours and fix the problem as soon as possible.

Other OpCo operations

• Manage DNS for all Balancer DAO domains.
• Manage 3rd party accounts, upgrades, renegotiations, etc. For example, RPC providers, AWS, and wallet check providers.
• Github repositories: GitHub - balancer/frontend-v3: Official UI application for the Balancer protocol. GitHub - balancer/frontend-v2: Frontend app for the Balancer protocol (to be deprecated) GitHub - balancer/balancer-api: Deprecated (v2 API, to be deprecated) GitHub - balancer/tokenlists GitHub - balancer/metadata

Balancer OpCo’s product team is committed to building a market-leading DApp for the Balancer protocol and supporting growth opportunities through UI development as they arise. The product team is passionate about Balancer and committed to its long-term success.

Specification

The multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with USDC at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 by writing transfer, passing 0x3B8910F378034FD6E103Df958863e5c684072693 as recipient and the amount 80490 as 80490000000.