I didn't originally set out to build a software company.

I run a recruitment business, and for years we had the same problem that a lot of businesses using Salesforce have: Salesforce contained our jobs, candidates, applications and recruitment data, but our website sat outside of it.

That never made much sense to me.

Every time we wanted to change something on our job board, improve the candidate experience or introduce a new feature, we were dealing with the boundary between Salesforce and the website.

So I started building.

This wasn’t a knee-jerk decision.
And it definitely wasn’t because Bullhorn is “bad”.

For years, we ran our recruitment business on Bullhorn for Salesforce — the managed package that sits on top of Salesforce and promises the best of both worlds: recruitment-ready functionality, with the power of Salesforce underneath.

When people talk about recruitment platforms, they usually focus on the ATS.

Jobs. Candidates. Pipelines. Reports.

But after rebuilding our entire stack directly on Salesforce, I’ve come to a different conclusion:

Three months ago, I did something that most sensible people would probably avoid.

I ripped out a third-party timesheet system that technically worked…
and rebuilt the entire thing natively in Salesforce....