A lot of new brokers give away the hard part. They research vendors, run discovery, write the proposal, and only get paid if a tool gets sold. That trains clients to treat you like an unpaid analyst.

A setup or onboarding fee, even a modest one, changes the relationship on day one. It pays you for the work that happens before any vendor commission shows up. It also filters people who wanted free advice.

What it can cover:

• Discovery and stack review

• Vendor shortlist and intro

• The first 30 days of configuration and questions

You can still earn recurring margin after. The fee is not instead of brokerage income. It is so the first month is not a donation.

If naming a number still feels uncomfortable, start with one existing prospect and say it once. The people who need you will not vanish because you stopped working for free.

New brokers collect partner programs like trophies. Five categories, ten vendor logins, zero depth. That looks busy and closes slowly.

The operators who get to their first real recurring base usually do the opposite. They pick one category they already understand as a user, learn the 2-3 serious vendors, and run the same conversation for 90 days.

Why this works:

• Your discovery questions get sharp because you ask them every week

• Your objection handling stops being generic

• Vendors take you more seriously when you can show focused volume

• Clients can describe what you do in one sentence, which is how referrals happen

What this is not: locking yourself into a niche forever. It is a 90-day test so you actually finish the learning curve instead of restarting it every Monday.

If you cannot name the category you would run for the next 90 days, that is the decision to make this week. Not a new outreach tool. Not a fifth partner application.

Breadth comes after you can close one type of deal in your sleep.

Cold LinkedIn messages that open with a tool pitch get ignored for a reason. The person on the other side has no context and no reason to trust you yet.

A better first touch:

• Comment on something specific they posted or shipped, in a way that shows you read it

• Follow up a day later with one observation about a stack problem common in their industry

• Ask a question, not for a call

What not to do:

• Connection request plus a pitch in the same note

• "I help businesses save 30% on software" with no proof you know their world

• Mass sequences that could have been sent to anyone

Brokers who get meetings on LinkedIn look like they already understand the buyer's situation. The pitch comes after they reply, not in the connection request.

If your current approach is 50 identical DMs a day, cut it to 10 specific ones this week. Reply rate usually goes up even as volume goes down. Specific beats spray-and-pray in this channel.

New brokers spend most of their week hunting logos they have never spoken to. Operators who actually stack recurring revenue spend more time on people who already said yes.

An existing client already trusts you, already has billing set up, and already knows how you work. Asking "what else in the stack is messy" is a 10-minute conversation. Cold outreach to a stranger is a 10-week cycle.

Where the money hides:

• A second tool in a category you already opened (CRM plus helpdesk, payments plus invoicing)

• Seats they added since you last checked

• A sister company or second brand using the same messy process

A simple weekly habit: pick two live accounts and ask one specific question about a gap you already spotted. Do not pitch a catalog. Name the gap.

New logos still matter. They just should not be the only motion. If your pipeline is 90% strangers and 10% current clients, flip that ratio for 30 days and see what closes.

The cheapest deal you will ever close is an expansion of one you already won.

A lot of people talk themselves out of SaaS brokerage because they "aren't technical." That is usually the wrong filter.

Clients are not hiring you to configure servers or write code. They are hiring you to compare options, negotiate terms, and own the relationship when something breaks. Those are research and communication skills, not engineering skills.

What actually matters:

• Can you ask a business what is expensive, slow, or messy in their current stack

• Can you read a partner page well enough to know if the commission is recurring

• Can you explain a trade-off in plain language instead of feature lists

The technical work, when it exists, sits with the vendor's onboarding team. Your job is to pick the right vendor and stay in the loop.

If you can run a discovery call, write a clear proposal, and follow up when you said you would, you already have the core skill set. The rest is category knowledge you pick up deal by deal.

Don't wait until you "know enough about software." Start with a category you already understand as a user, and broker that first.

Most new brokers think they have a lead problem. More often they have a proof problem.

A single documented result ("we cut this client's tool spend by X and kept the same features") does more selling than weeks of unsolicited outreach. Prospects don't need another pitch. They need evidence that someone like them already got the outcome.

What a usable case study actually needs (keep it short):

• Who they were, without needing a famous brand name

• What was broken or overpriced

• What you changed

• One number: cost saved, time saved, or seats consolidated

You don't need a polished PDF. A 6-sentence write-up you can paste into a reply is enough.

How it compounds:

• Outreach reply rates go up because you're not asking them to trust a stranger

• Referrals get easier because the client can forward something concrete

• Pricing conversations get shorter because the value is already on the page

If you have even one closed deal, write that case study this week before you send another cold email. The bottleneck is rarely more volume. It's having something true to point to.