Years before I ran a presales team at Sumsub, I sat on the other side of the table. I was a fraud and AML analyst, and later a compliance team lead, evaluating the kind of tools I now help sell.
One demo still sticks with me. In 2022 I was leading a KYC and onboarding operations team of 30+ people across three regions. We were looking at tooling to cut manual review time. The vendor's SE opened their laptop, said hello, and launched straight into the product. Feature after feature. Screen after screen. Not once did they ask what my team actually struggled with.
By minute twenty, I had stopped listening. I wasn't annoyed at the product. I was annoyed that nobody had asked me a single question.
Today I lead a Transaction Monitoring Solutions Engineering team that covers EMEA, LATAM and APAC. I've built it from the ground up, and I've hired people from very different backgrounds. That experience has convinced me of something that goes against how most companies hire SEs:
In specialist markets, some of the best SEs you'll ever hire used to be your buyers. Not engineers. Not AEs. The people who once sat through your demos.
In this article I'll cover why former buyers make strong SEs, the mistake almost all of us make in our first months, what I now look for when hiring, and when this approach doesn't work.
Why former buyers make strong SEs in specialist markets
When your customer is a compliance officer, a security analyst, or a finance controller, they can tell within minutes whether you've done their job. Former practitioners have three advantages that are very hard to train.
1. They know what the buyer's day actually looks like
I spent years reviewing alerts, investigating suspicious transactions, and writing up case files for auditors. So when a prospect tells me their analysts are "overwhelmed," I know what that means in practice: a queue of false positives, an SLA clock running, and a regulator who will ask why a case took three weeks.
That changes the conversation. Instead of asking "What are your pain points?", I can ask "How many alerts does one analyst close per day, and how many of those turn out to be nothing?" The second question gets a real answer.
2. They see the deal from more than one angle
In most of my deals, the buyer isn't one person. Compliance cares about audit trails and regulatory defensibility. Operations cares about analyst workload. Product and engineering care about integration and latency. Leadership cares about cost and risk.
Because I've worked in compliance, operations, and fraud, I can speak to each of those people in their own terms.
On one deal with a fast-growing payments company, the head of compliance wanted every monitoring rule to be fully explainable to their regulator. The CTO was worried about latency on real-time payments. Each side saw the other as the blocker.
I had written case files for auditors myself, so I could show the CTO why explainability wasn't optional. I could also show compliance which checks could safely run after a payment rather than before it. Both of them signed off on the same PoC plan, and that alignment is what moved the deal forward.
3. They earn credibility fast
Specialist buyers are sceptical of vendors. They've been oversold before. When you can say "I used to do your job" and then prove it with the questions you ask, the room relaxes. The customer stops defending and starts sharing.
That's the moment discovery actually begins.
The mistake almost every domain expert makes first: asking the wrong questions
Here's the irony. I moved into presales because I knew what buyers needed. And in my first months, I still asked the wrong questions.
My questions were the questions of an investigator or a compliance reviewer. They were thorough, technical, and focused on how the controls work: Which typologies do you cover today? How are your thresholds calibrated? How do you handle Travel Rule for unhosted wallets?
Those are good questions for an audit. They are weak questions for a sale. They told me how the customer's controls worked, but not:
- Why they were looking now, and what had changed
- Who else had to agree, and what each of them cared about
- What would happen if they did nothing
- How they would decide, and by when
In other words, I was running a compliance review, not a discovery call. I collected a lot of information, but I couldn't connect it to a decision.
What fixed it
What helped me most was learning a structured discovery approach. The PreSales Collective courses were a big part of that for me. They gave me a way to sort my questions into layers: the situation, the business problem behind it, the impact, and the decision process.
I kept my domain questions. I just stopped leading with them. Now I use them to go deeper after I understand why the customer is talking to us at all.
On one early call, I spent most of the hour on rule logic and alert thresholds. I left with pages of notes and no idea that the customer had a regulatory inspection coming in a few months. Later, on a very similar call, I asked about timelines and triggers in the first ten minutes. That inspection date ended up shaping the whole PoC plan, and the deal moved faster because of it.
Discovery is an investigation
The good news is that former investigators already have the right instincts. Good discovery works a lot like a good case review:
- Start with the trigger. In AML, you ask what raised the alert. In discovery, ask what made them take the call.
- Follow the evidence, not the story. Customers describe the problem they think they have. Ask for numbers, examples, and recent incidents.
- Notice what's missing. If nobody mentions the budget owner or the regulator, that gap is a finding.
- Document as you go. A clean discovery summary sent back to the customer is your case file. It shows you listened, and it keeps the deal honest.
Once I started treating discovery like an investigation, my former career stopped being a habit I had to unlearn and became an advantage.
What I hire for now
When I started building my team, I assumed I'd hire people who looked like me: ex-compliance, ex-AML. I didn't. My team today includes people from compliance and investigations, solution engineering, consulting, and customer-facing fintech roles.
What I learned is that background matters less than I expected. The people who succeed share three things, wherever they came from.
1. They can explain complex things simply
Transaction monitoring is complicated. So is any specialist domain. If a candidate can't explain a concept from their own field to a non-expert in two minutes, they'll struggle in front of a mixed buying committee.
How I test it: I ask candidates to explain something from their past work as if I were a CFO with no background in it. I'm listening for plain words, a clear structure, and whether they check that I'm following.
2. They listen more than they talk
Remember the SE from my opening story? They knew their product well. They just never stopped talking long enough to learn anything about me.
Domain experts are especially at risk here, because they want to show what they know. The best candidates resist that.
How I test it: In a role-play discovery call, I watch how much of the time they spend asking versus telling, and whether their follow-up questions build on my answers.
3. They connect everything to real value
Knowing the product and knowing the regulation are both table stakes. What separates good SEs from great ones is the ability to link a feature to an outcome the customer cares about: fewer false positives, faster onboarding, a cleaner audit, lower cost per case.
How I test it: I give a short scenario and ask, "Why should this customer care?" Weak answers describe features. Strong answers describe the customer's world after the problem is solved.
What I teach first to new hires from the buyer side
For people who join from compliance or operations, I focus first on the commercial side they've never seen: how deals are qualified, how a PoC is scoped so it ends in a decision, and how to work with an AE as a partner. In their first weeks they shadow live discovery calls. Then they run parts of calls with me in the room, and only after that do they lead their own.
The domain knowledge they already have. The selling skills can be learned, just as I learned them.
When hiring former buyers doesn't work
I don't want to oversell this. Hiring from the buyer's side has real risks, and I've seen them.
- The advisor trap. Former practitioners love solving the customer's problem, even when it has nothing to do with your product. That builds goodwill, but it doesn't move deals. They need to learn when to help and when to redirect.
- Discomfort with commercial pressure. In compliance, "no" is often the safe answer. In presales, you have to be comfortable pushing for a decision, a next step, or a close date.
- Over-explaining the domain. It's tempting to prove expertise by teaching the customer their own regulation. Most customers already know it. They want to know what you'll do about it.
- Technical gaps. In products with heavy integration work, a domain expert still needs a strong solution architect or engineer beside them, at least at first.
None of these are reasons not to hire former buyers. They're reasons to coach them on purpose, starting in week one.
Key takeaways
The vendor who demoed at me years ago taught me more about presales than they'll ever know. Here's what to do with these lessons.
If you're a practitioner thinking about moving into presales:
- Treat your domain experience as an asset, not a starting gap. You already know what your future buyers need. Lead with that in interviews.
- Learn structured discovery early. Your instinct will be to ask audit questions. Learn to start with why now, who decides, and what happens if they do nothing, then go deep.
If you lead a presales team in a specialist market:
- Look at your customers' teams when you hire. Analysts, operations leads, and practitioners can become your most credible SEs.
- Hire for three skills, not one background. Look for people who explain complex ideas simply, listen more than they talk, and tie everything to customer value.
- Coach the commercial side from day one. Domain experts rarely need help with the product's subject matter. They need help qualifying, scoping PoCs, and pushing for decisions.
The best SE I can imagine is someone who has sat through a bad demo and decided never to give one. Some of them are already on your customers' teams.

About the Guest
Wadim Godniew is a Unit Lead and Deputy Head of Transaction Monitoring Solutions Engineering at Sumsub, leading teams across EMEA, LATAM, and APAC. With nearly a decade of experience in fintech, financial crime prevention, and presales, he specialises in transaction monitoring, AML, and crypto compliance.
Wadim is passionate about building high-performing solutions engineering teams, translating complex customer challenges into practical solutions, and exploring how technology is transforming financial crime prevention.





.webp)

