Why we built Orion
We didn’t start Orion because we had a grand mission to change the world.
We started it because hiring felt rushed, noisy, and careless on both sides of the table.
We kept seeing the same pattern. Roles defined too quickly. Assumptions treated as facts. Strong candidates failing in setups that never really made sense to begin with. Most hiring problems didn’t start with the search.
They started earlier, when nobody slowed down long enough to ask what the role actually needed, how it would function day to day, and what kind of person could realistically succeed in that context.
So we built a way of working that does exactly that. We slow down where clarity matters, and move faster everywhere else. We ask better questions before we start chasing answers. We focus on decisions that still make sense six months in, not just hires that look good on paper. It’s not louder. It’s not flashier. But it leads to fewer resets, stronger ownership, and hires that actually stick.
Turns out that works
The crew behind the mission
CEO
Finn Thoolen
I focus on helping companies get clear on what they actually need before rushing into a hire. Most of my work sits at the start of the process: understanding where things are stuck, what decisions are being avoided, and what kind of role will really move the business forward. My job is to keep hiring structured, honest, and tied to reality, even when there’s pressure to move fast.
CFO
Henri Fagel
I’m responsible for the structure behind the work. That means keeping processes tight, expectations realistic, and decisions grounded. I look at hiring through an operational and financial lens, making sure what we’re doing makes sense not just today, but months down the line. My role is to bring calm, discipline, and clarity to how searches are run.
CTO
Marcel Voeten
I focus on the systems and tooling behind our work. That means building and maintaining the technical setup that supports sourcing, tracking, and decision making. I’m responsible for making sure our processes scale without becoming bloated, and that the data we use actually helps us make better calls. My role is to turn structure into something practical and usable, not another layer of complexity.
Let’s talk through the hire
We’ll look at what’s blocking the hire, what the role actually needs, and whether it makes sense to work together.



