How to actually evaluate an FMO

An FMO contract looks like a small decision at the moment you sign it. You are usually signing because you want one appointment, or because someone offered to handle the paperwork, and the terms you skim are the ones that decide how hard it will be to leave. Two years later that contract is sitting underneath your entire book, and by then the questions you did not ask have answers you did not choose.

Start with the exit, not the entrance

Every recruiting conversation is organized around what happens if you say yes. The more useful question is what happens if, three years from now, you want to say no. In this business, moving from one FMO to another usually requires a release from your current upline before a carrier will accept a new contract under a different hierarchy, and the terms of that release are set in the agreement you are about to sign.

So ask directly. Is a release granted on request, or is it discretionary? Is there a waiting period written into the agreement, and does that period run separately from whatever waiting period the carrier itself imposes? Does a release cover every carrier at once, or is it handled carrier by carrier? Is the process a signature, or is it a negotiation that starts the day you are already unhappy?

None of those questions is hostile. An FMO that is confident in its own service will answer them without flinching, because it does not expect to need a lock to keep you. An FMO that becomes vague at this point in the conversation has just told you something important, and it did not require a single unkind word.

Level transparency, without published tables

You will not find a public table of contract levels on our site, and you should be suspicious of one anywhere else. Levels move with production, structure, carrier, and product, so a published number is either a marketing figure disconnected from your situation or a promise nobody intends to keep at renewal. That is not a reason to accept vagueness.

What you can insist on is specificity about your own arrangement before you sign anything. What level are you being placed at, by carrier and by product line? What, exactly, moves you up, and is that movement automatic on production or discretionary on review? Is there any circumstance in which your level moves down? If you build a downline, how is the override structured, and can you see the full structure rather than a description of it?

Who owns the file

The word "ownership" gets used loosely in recruiting. Untangling it takes three separate questions, because there are three separate things people mean.

The first is the client relationship. When you write a policy, is the client yours, or does the agency treat that client as house business that can be reassigned? The second is the data. If the client sits in a platform the FMO controls, can you export the records, the notes, and the contact history, or does leaving mean walking away from a database you built? The third is the renewal, which is really a question about the carrier contract: are renewals paid to you directly by the carrier, are they paid through the FMO, and does the answer change if you are no longer contracted under them?

Get those three answers separately. A reassuring answer to one is often used to imply the other two, and they do not travel together. The person telling you the clients are yours may be describing a relationship while the agreement is describing a database.

Included technology versus resold technology

Almost every FMO now advertises a technology package. The distinction that matters is whether the organization owns the software or is passing through somebody else's subscription with its name on the login screen.

Resold software has predictable characteristics. It is usually billed separately or bundled against a production requirement, so it stops the moment your production dips or the relationship ends. Support is a forwarded email. Feature requests go into a queue nobody in the building controls. And the data lives with the vendor, which means an export request has to travel through two companies.

Software the distributor actually owns behaves differently, and you can test for it. Ask who writes the software. Ask who you talk to when it breaks at 9am during a selling season. Ask what happens to the data you put in it if you leave. Ask whether it is billed as a separate subscription, and if the answer is no, ask what triggers it becoming one.

How statements get reconciled

This is the least glamorous question on the list and the one that most often turns out to matter. Commission is paid on business that carriers record as having been written, and carrier records are not always complete, timely, or correct. Somebody has to compare what you wrote against what you were paid, and the honest question is whether that somebody is you.

Ask how statements arrive: as a carrier document forwarded to you, or as a reconciled view that matches submissions against payments. Ask what happens when a policy you know you wrote does not appear. Ask who chases the carrier, how long it typically takes, and whether the outcome gets reported back to you or quietly dropped. Ask how chargebacks are handled, how you are told about them, and how a disputed chargeback is worked.

Advance terms belong in the same conversation. Whether advance or as-earned is available varies by carrier, and each has real consequences for your cash flow and your exposure on a lapse. The answer you want is not "we offer advances." It is a carrier-by-carrier picture and an explanation of which one fits how you sell.

Red flags

• Vagueness about release. Any variation of "we have never had a problem with that" instead of a description of the process.
• A level quoted only verbally. If it cannot be written down, it is not a term, it is an impression.
• Technology tied to a lead purchase requirement. A platform you only keep while you buy something else is a discount, not an inclusion.
• A carrier list with no depth. Dozens of logos nobody at the organization can actually support is worse than a short list they know cold.
• No named contact. If contracting runs through a shared inbox before you sign, it will not improve afterward.
• Recruiting pressure on a deadline. A real opportunity survives you reading the agreement over a weekend.
• Silence about what they cannot do. Every distributor has gaps. One that will not name any is describing a brochure.

The honest case for a big national FMO

We are a distribution company writing about how to choose a distribution company, so here is the part that does not favor us. A large national organization has advantages that are structural rather than promotional, and pretending otherwise would waste your time.

Carrier breadth is the first. An organization that has been placing business at volume for decades holds contracts with more carriers, in more states, across more product lines, and can usually get you appointed with the specific carrier your book already depends on. If you have a regional carrier that drives most of your production, the FMO that already holds that contract at a good level is a serious argument on its own.

Scale is the second. Bigger organizations tend to have deeper back-office capacity during certification season, more product training, a larger bench of people who have seen your exact underwriting problem before, and enough volume with a carrier that an escalation gets picked up. Scale also buys stability, and a distributor that will still exist in ten years is worth something when your renewals run through it.

Where a smaller, vertically integrated organization competes is narrower and should be stated narrowly: who answers when you call, how quickly a stuck submission moves, and whether the technology you sell with is owned by the same company you contracted with. That is the trade. It is a real one in both directions.

A one-page checklist

Take these into the call. The hesitation in an answer tends to be more informative than the answer.

1. How does a release work, who approves it, and is there a waiting period in the agreement itself?
2. What level am I placed at by carrier and product, and what specifically moves it?
3. Will you put the level, the advance terms, and the override structure in writing before I complete packets?
4. Who owns the client relationship, the client data, and the renewal, answered separately?
5. Which software do you own, which do you resell, and what happens to each if I leave?
6. Is a lead purchase required to keep the contract, the level, or the technology?
7. How are statements reconciled, and who chases a missing commission?
8. Who is my named contact, and what is the escalation path when a submission stalls?
9. Which carriers can you not get me appointed with?
10. What does onboarding look like in the first thirty days, concretely?

The decision underneath the decision

Choosing a distributor is not really a choice between carrier lists. It is a choice about who you want between you and the carrier when something goes wrong, what you want included in the price of that relationship, and how easily you can undo the arrangement if it stops working. Carrier lists converge over time. Release terms, statement reconciliation, and whether anybody picks up the phone in October do not.

If you want to run this list against us, that is exactly what a first call is for. We will answer all ten, including the ones where the answer is that a larger organization would serve you better. Start with a conversation rather than a packet.