JobScience holds your data.
It doesn't do enough with it.
JobScience gives you the full power of Salesforce, and enough complexity that most teams never tap it.
I build the automation and integrations that put it to work.
JobScience holds your data.
It doesn't do enough with it.
JobScience gives you the full power of Salesforce, and enough complexity that most teams never tap it.
I build the automation and integrations that put it to work.
get the most out of jobscience
JobScience can do almost anything. Out of the box, it does the basics.
Most firms run JobScience, configure the essentials, and then spend years working around it.
Consultants retype interview notes by hand. Compliance gets chased over email. The data sits in Salesforce while the partners' reporting happens in a spreadsheet.
It can do far more than that. It's built on Salesforce, with a full REST API, Flows and Apex that can fire automations the moment anything changes.
Most firms never touch it, often because the people who set it up have long since moved on. That's where I come in.
get the most out of jobscience
JobScience can do almost anything. Out of the box, it does the basics.
Most firms run JobScience, configure the essentials, and then spend years working around it.
Consultants retype interview notes by hand. Compliance gets chased over email. The data sits in Salesforce while the partners' reporting happens in a spreadsheet.
It can do far more than that. It's built on Salesforce, with a full REST API, Flows and Apex that can fire automations the moment anything changes.
Most firms never touch it, often because the people who set it up have long since moved on. That's where I come in.
here's the process
What a JobScience build actually looks like.
Every build starts with mapping what's actually in your Salesforce setup, because on an older JobScience instance, that's rarely documented. From there it's typically one of four things, or a combination.
Interview write-ups: the notes from an interview captured and written straight into the candidate record in Salesforce, so a senior consultant never retypes them again.
Custom Salesforce work: Flows, Apex, fields and the REST API integrations to connect JobScience to the rest of your stack. If there's a manual export anywhere, there shouldn't be.
Compliance and process automation: built around how a search firm actually works, so the right things happen on their own when a candidate or a deal moves stage.
Reporting and dashboards: a clear view of the desk for partners, pulled from the Salesforce data you already hold, instead of a spreadsheet someone rebuilds every month.
here's the process
What a JobScience build actually looks like.
Every build starts with mapping what's actually in your Salesforce setup, because on an older JobScience instance, that's rarely documented. From there it's typically one of four things, or a combination.
Interview write-ups: the notes from an interview captured and written straight into the candidate record in Salesforce, so a senior consultant never retypes them again.
Custom Salesforce work: Flows, Apex, fields and the REST API integrations to connect JobScience to the rest of your stack. If there's a manual export anywhere, there shouldn't be.
Compliance and process automation: built around how a search firm actually works, so the right things happen on their own when a candidate or a deal moves stage.
Reporting and dashboards: a clear view of the desk for partners, pulled from the Salesforce data you already hold, instead of a spreadsheet someone rebuilds every month.
Is this you?
We should talk if...
You're running a recruitment or search firm on JobScience, and some version of the following is true:
Your setup is old, and the person who built it has long since moved on.
Your consultants, some of the most expensive people in the building, spend hours on interview write-ups and data entry.
You've got Salesforce data you don't fully trust because it depends on people updating it consistently.
You've wondered whether you should migrate off it, but the risk and the cost keep putting you off.
It doesn't matter how big you are. The problems are usually the same, just at different scales.
Is this you?
We should talk if...
You're running a recruitment or search firm on JobScience, and some version of the following is true:
Your setup is old, and the person who built it has long since moved on.
Your consultants, some of the most expensive people in the building, spend hours on interview write-ups and data entry.
You've got Salesforce data you don't fully trust because it depends on people updating it consistently.
You've wondered whether you should migrate off it, but the risk and the cost keep putting you off.
It doesn't matter how big you are. The problems are usually the same, just at different scales.
How it works
Every process goes through the same three steps.
Discovery
A focused look at what's actually in your setup, your manual workflows, and where the friction is. On an older instance, mapping what's there is half the job. I'll map what's automatable, the priority order, and what a realistic build looks like. This takes a week.
Discovery
A focused look at what's actually in your setup, your manual workflows, and where the friction is. On an older instance, mapping what's there is half the job. I'll map what's automatable, the priority order, and what a realistic build looks like. This takes a week.
Build
I build the workflows, integrations and automations we've agreed on, on the Salesforce platform underneath JobScience: Flows, Apex and REST API integrations, documented as it's built. Typically two to four weeks depending on scope.
Build
I build the workflows, integrations and automations we've agreed on, on the Salesforce platform underneath JobScience: Flows, Apex and REST API integrations, documented as it's built. Typically two to four weeks depending on scope.
Handover
You get working automation, full documentation, and a walkthrough of how everything fits together. I stay available for 30 days post-launch. After that, retainer support is available if you want someone keeping an eye on it.
Handover
You get working automation, full documentation, and a walkthrough of how everything fits together. I stay available for 30 days post-launch. After that, retainer support is available if you want someone keeping an eye on it.
what clients say
But don't just take it from me.
We bring Jack in whenever we need serious Bullhorn Automation expertise. He takes our most tangled requirements and turns them into clean automations that just work, and he's become our go-to second pair of eyes whenever a build needs sense-checking. It's clear he has a deep understanding of Bullhorn and the recruitment industry as a whole. Overall, he's saved us hours of build time.
Kathy Walker, Fractional Marketing Director & Co-Founder, JK&Co.
We’ve had the pleasure of working with Jack across several projects and have consistently been impressed with the quality of work delivered. Communication is always clear, deadlines are met without issue, and there's a strong sense of accountability and transparency throughout. What stands out most is the flexibility to adapt to varying requirements while maintaining a high standard of execution.
Tina Tucker, Marketing Account Director, Thrive Recruitment Marketing
what clients say
But don't just take it from me.
We bring Jack in whenever we need serious Bullhorn Automation expertise. He takes our most tangled requirements and turns them into clean automations that just work, and he's become our go-to second pair of eyes whenever a build needs sense-checking. It's clear he has a deep understanding of Bullhorn and the recruitment industry as a whole. Overall, he's saved us hours of build time.
Kathy Walker, Fractional Marketing Director & Co-Founder, JK&Co.
We’ve had the pleasure of working with Jack across several projects and have consistently been impressed with the quality of work delivered. Communication is always clear, deadlines are met without issue, and there's a strong sense of accountability and transparency throughout. What stands out most is the flexibility to adapt to varying requirements while maintaining a high standard of execution.
Tina Tucker, Marketing Account Director, Thrive Recruitment Marketing
what clients say
But don't just take it from me.
We bring Jack in whenever we need serious Bullhorn Automation expertise. He takes our most tangled requirements and turns them into clean automations that just work, and he's become our go-to second pair of eyes whenever a build needs sense-checking. It's clear he has a deep understanding of Bullhorn and the recruitment industry as a whole. Overall, he's saved us hours of build time.
Kathy Walker, Fractional Marketing Director & Co-Founder, JK&Co.
We’ve had the pleasure of working with Jack across several projects and have consistently been impressed with the quality of work delivered. Communication is always clear, deadlines are met without issue, and there's a strong sense of accountability and transparency throughout. What stands out most is the flexibility to adapt to varying requirements while maintaining a high standard of execution.
Tina Tucker, Marketing Account Director, Thrive Recruitment Marketing
Book a Call
Book a Diagnostic Call
The diagnostic call is 30 minutes. You tell me what your current setup looks like and where the pain is. I'll tell you honestly what's worth automating, what isn't, and roughly what it would cost.
No pitch deck. No proposal you didn't ask for.
Trusted by SMEs from Recruitment and HR to Marketing, Finance and Tech.
frequently asked questions
Common questions answered
We're on JobScience, or Bullhorn for Salesforce. Same thing?
Effectively yes. JobScience became Bullhorn for Salesforce, so either way it's Salesforce underneath, which is what I build on. Everything I do works the same across both.
We're on JobScience, or Bullhorn for Salesforce. Same thing?
Effectively yes. JobScience became Bullhorn for Salesforce, so either way it's Salesforce underneath, which is what I build on. Everything I do works the same across both.
Will this break anything we already have, and do we need a developer to look after it?
Neither. The first thing I do is map your existing configuration before touching anything, so nothing gets broken during a build. On maintenance: everything I deliver is documented properly and built to be understood without technical knowledge. If something needs changing - a status label, a document template, a notification recipient - your ops team can handle it. You don't need a developer on standby.
Will this break anything we already have, and do we need a developer to look after it?
Neither. The first thing I do is map your existing configuration before touching anything, so nothing gets broken during a build. On maintenance: everything I deliver is documented properly and built to be understood without technical knowledge. If something needs changing - a status label, a document template, a notification recipient - your ops team can handle it. You don't need a developer on standby.
Can you connect JobScience to our other tools?
Usually yes. It's Salesforce underneath, so anything with an API or a webhook connects through the REST API. Finance systems, job boards, client portals, BI and reporting tools. If you're unsure about something specific, ask on the call and I'll tell you straight.
Can you connect JobScience to our other tools?
Usually yes. It's Salesforce underneath, so anything with an API or a webhook connects through the REST API. Finance systems, job boards, client portals, BI and reporting tools. If you're unsure about something specific, ask on the call and I'll tell you straight.
What if our process changes after the build?
It's expected. Processes change, teams grow, platforms update. The documentation I deliver means your team can make minor adjustments themselves. For anything more substantial - a new workflow, a change in how placements are handled, a new tool coming into the stack - I offer retainer support, or you can come back for a scoped piece of work. You're not locked in and nothing is built in a way that only I can understand.
What if our process changes after the build?
It's expected. Processes change, teams grow, platforms update. The documentation I deliver means your team can make minor adjustments themselves. For anything more substantial - a new workflow, a change in how placements are handled, a new tool coming into the stack - I offer retainer support, or you can come back for a scoped piece of work. You're not locked in and nothing is built in a way that only I can understand.
What does it cost?
It depends on scope, but to give you a useful frame: a focused build - one or two workflows, clear requirements, straightforward integrations - typically starts from around £3,000. A more complex engagement covering multiple workflows, several integrations, and a full documentation and handover process sits in the £5,000-£12,000+ range. I price by project rather than day rate, so you know the number before anything starts. The diagnostic call is free and will give you a much clearer picture of where your engagement would sit.
What does it cost?
It depends on scope, but to give you a useful frame: a focused build - one or two workflows, clear requirements, straightforward integrations - typically starts from around £3,000. A more complex engagement covering multiple workflows, several integrations, and a full documentation and handover process sits in the £5,000-£12,000+ range. I price by project rather than day rate, so you know the number before anything starts. The diagnostic call is free and will give you a much clearer picture of where your engagement would sit.