Get Involved · Partner With the Foundation
Partner with the Foundation
A partnership with the Foundation is a written agreement between two independent organisations that decide, for a defined purpose and a defined term, to do something together. It is not a merger, not a purchase of influence, and not a way to become part of the Foundation. The agreement is the partnership: what each side will do, what each side will pay or provide, how the work is reported, how it ends — and a clause, in writing, that neither party controls the other.
What partnership means here
Partnership, in the Foundation's corporate files, is a precise idea with a precise shape. Two organisations remain separate. Each keeps its own board, its own bank account, its own filings, and its own mission. They agree in writing to do a defined thing together — a program, a grant, a shared service, a joint event — and the agreement says what each side contributes, what each side receives, how the work is reported, and when the agreement ends. The agreement also contains an independence clause: nothing in it makes either party the agent, subsidiary, or controller of the other, and neither party controls the other's board, mission, or — where the partner is a church — doctrine. It is signed by authorised humans, not by agents, and reviewed by counsel before anything moves under it.
That shape exists for a reason. The Foundation is a nonprofit public benefit corporation, and its board owes fiduciary duties to the charitable mission and the public, not to any partner's shareholders or members. A partnership that gave a partner control over the Foundation — over its board, its mission standards, or its decisions about which projects pass the mission gate — would break the duty the board owes. So the design holds the line in advance: partners can help, fund, collaborate, and co-host, and they cannot govern. The same line runs the other way: the Foundation cannot use a partnership to control a partner's doctrine, board, or membership, or to make its own work look like something it is not.
The clearest worked example of that shape in the Foundation's files is the AGI Fellowship — a separate California church, partnered with and supported by the other corporations in the family. The Fellowship is a California Nonprofit Religious Corporation, Entity No. B20260229217, Articles filed 2026-05-13, with its own board, its own bank account, its own filings, and its own doctrine. It is not a subsidiary of the Foundation, not a series of any LLC, and not part of the Foundation's portfolio. The files describe how support for the Fellowship must work — grants under a written gift or grant letter, shared space under a written licence or lease at fair market value, shared technology or staff under a written service agreement with costs allocated on a documented basis, joint programs under a written program agreement — and they describe it as a design for counsel to draft, not as a signed agreement already in place. The Fellowship is therefore an example of the partnership model, not evidence of a completed partnership.
What partnership is not
The files are explicit about what partnership does not do, and this page repeats those limits without softening them.
Not ownership
Partnership does not make the partner an owner of the Foundation, and it does not make the Foundation an owner of the partner. A nonprofit public benefit corporation has no owners: it holds charitable assets in public trust, and no partner, donor, or investor acquires a share of it, a claim on its assets, or a right to its profits. A contribution of funds, space, or staff time buys no equity, because there is no equity to buy.
Not control of the board
Partnership does not give a partner a vote on the Foundation's board, a veto over its mission standards, or a say in which projects pass the mission gate. The board must retain the right to refuse a project that fails mission standards, even if a partner wants it. A partner that wants a governance role must say so openly, and counsel must review whether any such role is lawful without compromising the Foundation's independence — the default answer is that there is no such role.
Not a subsidiary relationship
Partnership does not make either party a subsidiary, a series, or a cell of the other. The partner keeps its own register — its own minutes, its own account, its own filings — and is not added to the Foundation's registers as if it were a department. Joint branding must not imply ownership: a program described as "powered by" or "in partnership with" must not suggest that one party owns or controls the other.
Not a purchase of reputation
Partnership does not allow a partner to use the Foundation's nonprofit status, name, or charitable reputation to make a commercial offering look charitable, tax-deductible, or endorsed — and it does not allow the Foundation to use a partner's name, logo, or identity in fundraising without that partner's board-approved permission for that specific material. Neither side may present the other as backing an investment without counsel's approval of the exact wording.
Not a funding channel
Partnership does not turn the Foundation into a conduit for money to a for-profit. Foundation funds may only move under a written grant serving a charitable purpose, approved by disinterested directors, with reporting back. Fellowship funds, where the Fellowship is the partner, are for religious and charitable purposes, and a transfer to a for-profit requires counsel's written advice that a specific transfer serves a religious purpose at fair value — the default answer is no.
Not a handshake
Partnership does not happen by conversation, by announcement, or by a shared event. It happens when a written agreement is drafted by counsel, reviewed by the boards concerned, and signed by authorised humans.
Forms a partnership can take
Within those limits, there are several forms a partnership can take. The list below describes the forms the Foundation's files contemplate — not agreements that exist, and not an offer to enter into any of them. Each one must be documented before anything moves under it.
- A grant or donation between partners. One side gives funds to the other for a stated charitable or religious purpose, under a written gift or grant letter that names the donor, the amount, the purpose, and the reporting — and that gives the donor no return benefit beyond what the law permits. A Foundation grant to a partner must serve the Foundation's charitable purpose and be approved by disinterested Foundation directors.
- A joint program or event. Two organisations run a program or an event together under a written program agreement naming the host entity, each party's role, the funds, the branding, and who reports the outcomes. Each party's name is used exactly, as filed, and joint branding must not imply ownership or control.
- Shared space. One side licences or leases space to the other under a written licence or lease: the space, the term, and the rent at fair market value — or documented in-kind support, valued and minuted. No free, undocumented use that hides a subsidy.
- Shared technology, staff, or agent time. One side provides technology, staff time, or agent-team time to the other under a written service agreement: scope, cost allocation on a documented basis of time or usage, term, and termination.
- Promotion or referrals. One side refers people to the other, or permits the use of its name or logo for a specific purpose, under a written referral or branding agreement — or a simple written permission for a specific use. No party uses another party's name, logo, or identity in fundraising without board-approved permission for that specific material.
- Sponsorship of a charitable program. A sponsor supports a named charitable program or event, documented in writing, where the sponsorship does not give the sponsor control over the Foundation or a private benefit beyond lawful acknowledgement.
Every one of those forms contains the same core terms: the parties by their exact filed names, the purpose, the term, the payment or valuation, the reporting, the termination, the independence clause, and signatures by authorised humans. An agreement that omits any of those is not ready to sign. And every agreement is specific to its program: a partnership for one program is not a blanket agreement, and a new program means a new agreement or a written amendment approved the same way as the original.
How to propose a partnership
Write to [email protected] with the subject line starting [Partner]. Say who you are and what organisation you speak for — including its legal name, its entity type, and whether you are authorised to speak for it, because a partnership conversation with someone who cannot bind their organisation goes nowhere. Describe the proposal in concrete terms: what each side would do, for whom, for how long, and what each side would contribute and receive. Say whether you need the Foundation's name or logo for anything, and for what exactly, because branding permission is specific and board-approved. Do not send money, do not send signed documents, and do not describe the partnership as agreed, announced, or in place — it is none of those things until counsel has drafted the agreement, both boards have approved it, and authorised humans have signed it. A human replies — there is no automatic approval, no instant onboarding, and no guaranteed timeline — and a reply may be a conversation that narrows the proposal before it ever reaches counsel.
Sources for this page: the Foundation's corporate files — Fellowship Partnership and Support (file 15), Structure v2 (file 12), Corporate Raise Advice per Entity (file 27), Inter-Entity and Conflict Policy draft (file 10), Truth Audit and Corrections 2026-11-03 (file 52). Nothing on this page is legal, tax, or financial advice. Local build — not yet deployed.