Brokers AllianceWhat an AI-enabled BGA means for an agency
Your downline is yours, and it stays yours. You decide who in your office can see what, and your agents are off unless you turn them on.
Your hierarchy stays yours
This page is written for the owner of an agency who runs a downline: the principal whose agents are contracted under them, whose office does the contracting paperwork, and who has heard the word AI from every direction lately. Here is what the word means at Brokers Alliance, and, more usefully, what it does not.
Brokers Alliance is a family owned IMO, FMO and BGA, founded in Fountain Hills, Arizona in 1982 and owner-led since 2009. We are a wholesale partner to independent agents and to the agencies that run them. We are not a lead vendor and not a captive agency. Our model is contracts, case design, technology and marketing support for people who run their own practice, and that includes people who run a practice made of other practices.
We run our own recruiting, marketing and case operations on automation we built and monitor ourselves. A named person is responsible for every regulated decision. That is a description of how the firm works, not a category we are claiming, and nothing on this page asks you to take it on faith. What a visitor can check is at the bottom.
For an agency the meaning comes down to three things. Your hierarchy stays yours. Brokers Alliance does not contact your downline agents. And the connection we are building for principals reads, and changes nothing.
Brokers Alliance does not contact your downline agents
An agency principal's real asset is the hierarchy: the agents, the contracts that sit under the principal's, and the relationships that put them there. A distributor that reaches around the principal to those agents is spending the principal's asset. We do not do that.
Our relationship is with you. Your agents contract under your hierarchy and stay there. Nothing we are building, and nothing described on this page, puts Brokers Alliance in front of your downline. That sentence is part of the negative definition we print on every page that describes our automation, and it is printed again lower on this page, next to the rest of the not-list.
Suppose you are weighing two BGAs. Ask each one, in writing, who owns the relationship with your agents, and what happens to that relationship if you leave. Ask how the answer changes when software is involved. If the answer takes a paragraph, that is the answer. Our version takes a sentence: your hierarchy stays yours, and your agents are yours to contact.
What a principal could see
Brokers Alliance is building a connection that lets an agency principal point their own Claude or ChatGPT at the business their own hierarchy places through Brokers Alliance. It is a pilot. One hierarchy is being selected with the Brokers Alliance sales team, and it joins by invitation.
What is in it: the cases and the contracting packets your hierarchy has placed through us. Case status, requirements outstanding, appointment progress, the things your office calls our case-management team about today. Scoped to your hierarchy and to nothing outside it.
How it is scoped: the connection carries read access. Read access means it changes nothing. Your assistant can look at a case; it cannot touch one. It cannot move a requirement, alter a packet, or send anything to a carrier. A question asked of the connection produces an answer, not an action.
Who is in the conversation: you and your assistant. Brokers Alliance is not in that conversation. The assistant is yours, chosen by you, running under your own account. Our part is the connection and the scope, nothing more.
Because it is a pilot, the honest description is present tense. We are building it. A hierarchy is being selected. It joins by invitation. If you want to be the hierarchy in that sentence, the path is on the join page, and the fuller description for principals is on the principals page.
You decide who in your office has access
The permission model is the part we would ask you to read twice, because it is the part that makes the rest safe to say. Every decision about access sits with the principal.
| Who | Access to the connection | Who decides |
|---|---|---|
| The agency principal | Read access to the cases and contracting packets placed through their own hierarchy | The principal, by joining the pilot |
| Office staff | Off unless the principal turns a person on, and the principal names who | The principal |
| Downline agents | Off unless the principal turns an agent on | The principal |
| Brokers Alliance | Not in the conversation | Fixed by the design |
In plain words: agents are off unless you turn them on, and anyone you turn on can be turned off again by you. No access arrives by default, and no access is granted around you by Brokers Alliance. Turning someone on is your decision. So is turning them off.
What stays out of the connection
A connection is defined as much by what it leaves out. Three things stay out of this one, on purpose.
Commission grids
No commission grids in the connection. Compensation comparison already has a home in MyAdvisorGrids, where a contracted producer sees carrier compensation side by side. The pilot connection is about cases and contracting, and it does not mix the two.
Case changes
Nothing in the connection changes a case. Not a requirement, not a note, not a status. If your assistant reads that a requirement is outstanding, the way to clear it is the way it is cleared today, through your office and our case-management team.
Transactions
Nothing in the connection sends a transaction. No application goes to a carrier through it, no money moves, no policy changes. Anything of that shape is a carrier question, and it is not part of this pilot.
One more line, because the phrase gets stretched: read access describes what the connection can change, which is nothing. It is not a claim about anything else.
What your agency gets today
The pilot is one hierarchy and an invitation. Everything that follows is what any agency gets by contracting with Brokers Alliance, and there is no fee to contract.
Technology built in house
MyAdvisorCloud is the advisor platform and CRM, provided to contracted producers at no monthly charge, and it can carry your agency's own name. MyAdvisorGrids compares carrier compensation side by side. RetirementBrain handles the retirement income planning conversation. Contracting and onboarding are automated. All of it is developed and maintained by our own in-house development team, led by a technology-focused owner-operator, rather than licensed from a vendor.
Contracting and case support
Carrier appointments are processed in house, across 73+ carrier relationships. Case records are tracked digitally through our case-management system and reviewed daily. Case status, requirements and appointment progress are tracked digitally and reviewed daily by a dedicated case-management team. What we measure and how we work is written up on the service standards page. What we do not publish there is a turnaround promise, and the page says so.
A desk for the hard cases
A dedicated advanced-markets and IUL desk handles case design, premium finance, Section 79 and estate planning support, beside the producer who owns the client.
Lines: life insurance, fixed and indexed annuities, final expense, IUL, long-term care and linked-benefit, disability, and support for advisory business.
What the automation does not do
This is the negative definition. It is on every page of this hub that describes our automation, and it is the part we would want a principal to hold us to.
- No suitability verdicts. Whether a product fits a client is a licensed person's judgment, and it stays one.
- No policy health scores. Nothing grades a policy or ranks a case.
- No product recommendations. Nothing picks a carrier or a product for you or your agents.
- No case changes. The connection reads. It changes nothing.
- No transactions. Nothing is submitted, moved, or sent to a carrier through it.
- No contact with your downline agents by Brokers Alliance.
If a page on this site ever says otherwise, the page is wrong, and we would rather hear about it than have you wonder. The way to reach us is on the contact page.
What you can check, and the questions we get
Three things on this site are open to anyone: brokersalliance.com/llms.txt, the JSON-LD in the source of every page, and the signer line on regulated pages. Regulated content here is reviewed and signed by a named person before it is published, and the name is on the page. We point at those three because you can open them. We do not describe monitoring you cannot see.
Does joining the pilot change my hierarchy or my contracts?
No. The connection reads the business your hierarchy places through Brokers Alliance. It does not touch contracts, hierarchy or compensation, and commission grids are not in it.
Which assistant does it work with?
Your own. The connection is built for a principal to point their own Claude or ChatGPT at their hierarchy's cases and contracting. Brokers Alliance is not in that conversation.
Can my agents see it?
Not unless you turn them on. Downline agents are off by default, and an agent you turn on can be turned off again by you.
Does Brokers Alliance contact my agents?
No. The relationship is with you. Your hierarchy stays yours.
How does a hierarchy join?
By invitation. One hierarchy is being selected with the Brokers Alliance sales team. Start on the join page, or read what an AI-enabled BGA is for the plain definition.
Reviewed and signed by David Racich, President and CEO, Brokers Alliance, Inc., 2026.
Keep your hierarchy. Get the support and the technology.
Brokers Alliance is a second-generation, family owned life and annuity IMO, FMO and BGA, founded in 1982 in Fountain Hills, Arizona. No fee to contract.
How to joinQuestions first? Talk to contracting. or call (480) 210-7892