What Building Kolvera Taught Me About SaaS Hiring

By Daniel Bryant · 15 April 2026

You Cannot Assess What You Have Not Done

Building a SaaS product fundamentally changes how a recruiter evaluates GTM candidates. Technical depth becomes table stakes rather than a differentiator. Customer success becomes about outcome delivery, not relationship management. Onboarding quality emerges as the strongest predictor of retention. And the best Sales Engineers and CSMs think like product people, not feature lists. These lessons only come from operating on the product side, not from reading job descriptions.

I spent two years building Kolvera, a sales intelligence platform for Australian recruiters. Before that, I was placing SaaS professionals into B2B companies. After building Kolvera, I started placing them differently.

The shift was not subtle. It changed how I evaluate candidates, how I brief hiring managers, and how I think about what “good” actually looks like in a Sales Engineer or a Customer Success Manager.

Here is what changed.

Lesson 1: Technical Depth Is Table Stakes

Before I built software, I thought technical ability was the hard part of SaaS hiring. Find someone who can demo the product, handle API questions, and build a proof of concept. Tick those boxes and you have a strong SE.

After building a product, I realised technical depth is the minimum. What separates a good SE from a great one is the ability to diagnose a prospect’s problem in real time — not recite product features. The best SEs I have placed since building Kolvera are the ones who listen to a prospect describe their workflow, spot the gap, and position the product into that gap live. No script. No slide deck.

When I interview SE candidates now, I do not ask them to walk me through a feature. I give them a scenario and ask them to figure out what the customer actually needs. The difference in quality is stark.

Lesson 2: Customer Success Is Not Account Management

Before Kolvera, I treated CSM hiring like account management with a retention metric. After onboarding our own users, running QBRs, and watching churn happen in real time, I understood the difference viscerally.

A CSM is not there to “manage the account.” They are there to make sure the customer gets the outcome they bought the product for. That sounds obvious written down. In practice, most CSM job descriptions — and most CSM interviews — still focus on relationship management and upsell targets rather than outcome delivery.

The CSMs I place now get assessed on something specific: can they identify when a customer is not getting value from the product, and can they intervene before the customer realises it themselves? That is the skill. Everything else is secondary.

Lesson 3: Onboarding Quality Predicts Retention

We learned this the hard way at Kolvera. The correlation between a customer’s first-week experience and their likelihood of churning at month three was almost perfect. Bad onboarding meant slow adoption, which meant low usage, which meant cancellation.

This taught me something about hiring Heads of Customer Success. When I assess senior CS leaders, I ask them to walk me through how they would redesign onboarding for a product they have never seen. The ones who start with “what does the customer need to achieve in the first seven days?” are the ones worth shortlisting. The ones who start with “I’d set up a kick-off call template” are not.

Lesson 4: The Best GTM Hires Think Like Product People

Building a product changed how I see every go-to-market role. The strongest Sales Engineers think about product gaps, not just feature lists. The strongest CSMs think about user behaviour, not just NPS scores. The strongest RevOps people think about data architecture, not just dashboard layout.

When you have sat on the product side — dealing with feature requests, prioritising a backlog, watching users struggle with something you thought was intuitive — you develop an instinct for who else has that mindset.

What This Means for Hiring Managers

If you are hiring for a SaaS GTM role and your recruiter has never used a SaaS product beyond their own CRM, you are getting surface-level candidate assessment. They can check the boxes on a job description. They cannot tell you whether a candidate actually understands how SaaS companies work.

This is the core of what we do at Zionic. We place Sales Engineers and Customer Success leaders into B2B SaaS companies. The assessment goes deeper than keywords because the experience behind it is deeper than recruiting.

If you are scaling your GTM team and want candidates who have been evaluated by someone who builds and sells software for a living, let’s talk.

Share on LinkedIn

← Back to Insights