For web agencies
Build recruitment websites on Bullhorn without building the integration
If you build WordPress sites for recruitment clients, the Bullhorn connection is usually the riskiest part of the project. W3Bullhorn makes it a plugin you install and configure, not code you write, debug and maintain for years.
Installs on the site and theme you build, like any other plugin.
The usual project
Where recruitment website projects go over budget
-
A bespoke integration per client
Every Bullhorn client gets its own connection code, and every one of them needs maintaining long after launch.
-
Support that never ends
When Bullhorn or WordPress changes and the job board stops updating, the call comes to you, not to a vendor.
-
Themes that fight the portal
A career portal widget ignores the design you built, so the job pages never look like the site you delivered.
Your theme
Job pages built from the theme you deliver
Job listings and job pages are WordPress templates, so they take your theme’s styles by default. When a client needs something bespoke, you override the template in the theme and work the way you already work.
- Template overrides in your own theme
- Blocks for job lists, search and apply
- No iframe and no vendor stylesheet fighting your design
A privately owned main contractor in Leeds is hiring a senior QS to take commercial ownership of a £40m mixed-use scheme through to practical completion, reporting to the commercial director.
- Five years’ post-graduate experience with a main contractor
- Valuations above £5m run without supervision
Every client
One integration for every Bullhorn client
The same plugin on every client site, set up from the WordPress admin and updated through WordPress like anything else. The connection is a product with a roadmap behind it, rather than a piece of your agency’s code on someone else’s site.
- Set up from the WordPress admin
- Updates through WordPress, like any plugin
- Run history and errors in plain language, for handover
| Started | Result |
|---|---|
| 09:14:02 | 34 changes |
| 09:09:01 | No changes |
| 09:04:00 | 3 submissions |
Handover
A recruitment site you can hand over and leave
The part of a recruitment build that outlives the project is the integration. Jobs keep changing, Bullhorn keeps changing, and whoever wrote the connection owns the consequences. That is the work W3Bullhorn takes off your plate.
What stays yours is the part you are good at: the design, the templates and the client relationship. The job data, the applications and the connection behind them are the plugin’s job.
At handover
- The client edits nothing. Jobs come from Bullhorn, so nobody is re-typing vacancies into WordPress after you leave.
- Your templates, in your theme. Overrides live in the theme you built, under your own version control.
- A plugin, not your code. The Bullhorn connection is maintained as a product, so a change there is not your support ticket.
- The same build every time. One way of doing Bullhorn across your whole client list, instead of one per project.
Where to go next
What your client is buying
-
Their candidates
A job board on the client’s own domain
Listings, filters and a page for every role, in the theme you built.
The job board: A job board on the client’s own domain -
Their consultants
Applications back in Bullhorn
Applications arrive against the right job, with the CV attached.
Applications: Applications back in Bullhorn -
The build
How the connection works
What happens between Bullhorn and the website, in both directions.
The integration: How the connection works
FAQ
Questions from web agencies
Short answers here. Anything else, ask us directly.