How to hire SDRs for financial services SaaS

How to hire sdrs for financial services saas starts with a less exciting question: do you have a sales motion worth handing to another person?

Hire one SDR when the target account, buyer, trigger, and first-call standard are clear. Test candidates on research and judgment, not enthusiasm. Then give the rep a 60 to 90-day ramp with close coaching.

Most teams skip the first part. They hire someone who sold a cheap SaaS tool, hand over a spreadsheet of banks and fintechs, and wonder why the rep books nothing. Or worse, the rep books anyone who accepts a meeting. That isn't outbound. It's calendar damage.

Should you hire an SDR yet?

An SDR can create useful pipeline when an AE can take meetings quickly, the product has a defined buyer, and there are enough similar accounts to work repeatedly.

If the founder is still changing the product after every customer conversation, wait. A full-time SDR won't fix that. They'll just give you more evidence that the message isn't ready.

For a 10 to 30-person fintech SaaS company, I'd want to see a narrow segment, a few closed or late-stage deals in that segment, and an AE who can follow up within a day or two. For example, “financial services companies” is useless. “US payment processors with 100 to 1,000 employees, a growing transaction volume, and a reconciliation problem handled by a finance operations team” is something a rep can work with.

You also need a reason those accounts might act now. A new VP of Risk. A regulatory finding. A new banking partner. A funding round tied to expansion. A hiring spike in compliance or payments engineering.

If none of those signals exist, the SDR is forced to send generic messages and hope timing creates the sale.

The in-house versus agency decision is fairly practical. Hire internally when you have a manager, a working message, and enough account volume. Use a managed outbound partner when you need to test a market before hiring a manager or building a permanent team.

Write the role around the work, not the persona

Before you post the job, write a one-page operating brief. It should tell the candidate what they'll actually do:

They'll build and clean account lists, verify contacts, research buying signals, run cold outreach, qualify interest, and pass useful context to an AE. They may also spend part of the week listening to calls and rewriting messages.

Don't write “drive explosive growth” or “create a high-quality pipeline.” Those phrases attract people who interview well and have no idea how to research a regulated buyer.

Your ideal customer profile should include exclusions. A seed-stage fintech with no finance or compliance team might like the product but still lack the budget, owner, or urgency to buy. Put that in the brief.

The candidate should know which buyer they are calling, what problem that person owns, and what a reasonable first meeting is meant to establish. If you can't explain those things, the hiring problem is probably upstream.

What should the SDR understand about financial services?

They don't need to be a former compliance officer. They do need enough context to avoid making reckless claims.

Suppose the product automates payment reconciliation. The SDR should understand the difference between unreconciled transactions, exception queues, month-end close delays, and audit evidence. They should know that the daily user might sit in finance operations while the economic buyer is a CFO or controller. A technical buyer may care about integrations and data handling. Those are different conversations.

“We help fintechs work smarter” isn't a message. It's an invitation to end the call.

Prior experience selling to finance, risk, compliance, payments, or operations teams helps. But I think teams overvalue industry tenure. A disciplined SaaS rep from enterprise accounting software may outperform a financial services veteran who relies on old contacts and generic credibility.

I care more about whether the candidate can learn a technical product, find a credible reason to contact an account, handle an informed objection, and use coaching. Industry experience comes after those things.

Screen with work, not interview polish

The application tells you almost nothing. Give the candidate a small piece of the job.

Use a real account for the exercise. For example, give them a 200-person payment processor that hired a VP of Risk last month. Ask for a five-sentence email and a short explanation of the angle. You want to see a specific trigger, a restrained claim, and a clear next step. You don't want a paragraph about transforming risk management.

Then give them 20 minutes to find three contacts at the same company. Ask why each person matters. A good candidate will separate the operational user, the economic buyer, and the technical influencer. They won't simply copy the first three names from LinkedIn.

The role-play should be uncomfortable, but not theatrical. Play a skeptical Head of Compliance. Say the company already has a manual process and no budget this quarter. The candidate doesn't need to overpower you. They need to ask what the current process costs, understand whether the problem is active, and know when to stop pushing.

After that, give one piece of feedback and run the call again. This is the useful part of the interview. Strong candidates change their behavior immediately. Weak ones repeat the same script with more energy.

Don't hire polished confidence over careful thinking. Financial services buyers hear polished confidence all day. They notice when a rep pretends to understand something they clearly don't.

Set the quota after defining a good meeting

Compensation depends on location, seniority, sales complexity, and the buyer you're asking the rep to reach. A rep selling a simple product to small businesses is not the same hire as one selling compliance infrastructure to banks and payment companies.

For an early hire, I'd use a base-heavy plan with variable pay tied to qualified meetings accepted by the AE and, later, opportunities created. Raw meetings booked are a bad target. Reward the rep for filling the calendar and the calendar will fill with people who should never have been there.

Write the qualification standard before setting the number. A meeting should usually mean the account fits the segment, the contact owns a relevant problem, a current process has been discussed, and there's some reason to consider a change. The AE should receive notes that make the first call easier.

This matters even more in regulated markets. An SDR promising “full compliance” in a cold call can create a legal and credibility problem before the AE gets involved. Give reps approved language for security, compliance, data handling, and integrations. Teach them what to say when they don't know the answer.

The first 90 days

The first month is for product knowledge, buyer language, and practice. Have the rep listen to customer and lost-deal calls. Let them review support tickets and implementation questions. Make them rewrite weak emails. Don't hold them to a mature meeting quota in week one.

In days 31 to 60, give them a narrow account set and let them run live sequences. Watch valid contacts found, positive replies, conversations per 100 accounts, meetings accepted by AEs, attendance, and opportunities created.

By days 61 to 90, you should be able to separate a people problem from a motion problem. If the list is accurate, the accounts fit, the triggers are real, and coaching is consistent, a rep who still can't create conversations may be the wrong hire.

But if every rep struggles, stop replacing people. Fix the list, offer, or message.

You need a clean CRM, verified contact data, a sequencing tool, and a way to spot events such as executive hires, funding, technology changes, and audit activity. More activity won't rescue bad data. A smaller list of payment companies that recently hired compliance leaders is more useful than thousands of unqualified finance contacts.

When an agency makes more sense

An agency can fit a 15-person fintech SaaS company after a Series A, with two AEs, a proven product, and no sales development manager. The agency can test segments and messaging while the founders learn whether outbound creates qualified opportunities. If the evidence is good, hire internally with a clearer brief.

It can also help a European risk platform test the US market before hiring local reps. The question isn't whether an agency sounds impressive. It's whether the engagement produces usable evidence: which segment replies, which buyer takes meetings, which trigger creates urgency, and which message leads to opportunities.

Don't outsource a broken offer and expect the operator to repair it. A managed team can't compensate for unclear pricing, weak proof, poor onboarding, or an ICP that includes every financial company on earth.

Hire the SDR when those questions have somewhere close to an answer. Otherwise you're paying someone to discover your go-to-market strategy one bad call at a time.