July 28, 2026 · Earshot

A Realistic Look at Bullhorn + Twilio Referral SMS vs. Earshot

If you're running a staffing firm on Bullhorn, you've probably had this thought: "We should use SMS for referrals. I'll just connect our Bullhorn to Twilio. How hard can it be?" On the surface, the idea of a DIY Bullhorn Twilio referral SMS solution is compelling. You leverage tools you might already have, avoid a new software contract, and maintain total control.

We get it. We’ve spoken with hundreds of staffing leaders who went down this path. The initial appeal of a low-cost, custom-built solution is strong. But the reality of building, maintaining, and scaling this kind of system is a different story—especially for a high-performance referral program. This isn't just about sending texts; it's about generating a measurable return.

This article offers an honest, head-to-head breakdown. We’ll show you the true costs and limitations of the DIY route, helping you understand when it’s ‘good enough’ and when you need a purpose-built platform. As specialists in this space, we've seen firsthand how our Bullhorn referral integration for IT staffing fundamentally solves the problems that generic SMS tools create.

The Allure of 'Free': Why Firms First Look at Bullhorn + Twilio

The logic for exploring a custom build is simple and seductive. You already pay for Bullhorn; it’s the heart of your operation. Twilio offers powerful APIs with pay-as-you-go pricing that seems incredibly cheap per message. Why would you pay a monthly subscription for another platform when you can just connect the two?

The perceived advantages are clear:

Leveraging the Existing Stack: You’re not adding a completely new, unfamiliar vendor. You're just connecting two systems, one of which you already own.
Apparent Low Cost: Twilio’s pricing is pennies per message. It feels far cheaper than a SaaS platform's license fee.
Total Customization: You can build it exactly how you want. No feature bloat, just the simple functionality you think you need.

This line of thinking leads many well-intentioned ops leaders and recruiting managers to ask their dev team (or a contractor) for "a quick integration." This is where the simple idea begins to unravel.

Anatomy of a DIY SMS Stack: What You're Actually Building

"Connecting Bullhorn and Twilio" isn't like plugging in a toaster. There is no native "send referral SMS" button that magically appears. You are commissioning a custom software development project.

Here are the components you'll need to build and manage:

The Core Components

Bullhorn: Your source of truth for candidate, contact, and job data. You'll need API access to pull lists and maybe write back notes.
Twilio: The communications engine. You'll need an account, a provisioned phone number (or several), and to handle A2P 10DLC registration for carrier compliance.
The "Glue" (Custom Code): This is the most significant part. It’s not a simple script. It's an application that must be hosted somewhere. This "glue" typically involves:
- A Server or Serverless Environment: A place for your code to run, like an AWS EC2 instance, or more commonly, a serverless function like AWS Lambda or an Azure Function. This has its own costs and requires cloud infrastructure expertise.
- A Database: You need a way to store message logs, track opt-outs, and manage errors. You can't just rely on Twilio logs. What happens if a text fails to send? How do you retry? How do you ensure you don't text someone who replied "STOP"? This requires a database (like PostgreSQL or MySQL).
- API Authentication & Logic: Your code needs to securely manage API keys for both Bullhorn and Twilio. It needs logic to pull a list from a Bullhorn tearsheet, loop through the contacts, send a formatted message via Twilio, and handle the responses (both successes and failures).

Required Skillsets

This isn't a project for a tech-savvy recruiter or an operations manager with a Zapier account. To build and maintain this, you need:

A backend developer proficient in a language like Python, Node.js, or C#.
Experience with the Bullhorn REST API and the Twilio API.
Cloud infrastructure knowledge to deploy and manage the application.
An understanding of database management and security best practices.

Suddenly, the "simple connection" is a full-fledged application that needs to be scoped, built, tested, deployed, and maintained.

The Hidden TCO: Developer Hours, Bullhorn API Limits, and Maintenance

This is the section that turns most firms away from the DIY approach. The true total cost of ownership (TCO) for a custom Bullhorn Twilio referral SMS tool goes far beyond Twilio's per-message fees.

Upfront Build Costs

Let's be conservative. For a developer to build even a basic one-way broadcast system (pull list from Bullhorn, send SMS via Twilio) requires significant work:

Scoping & Architecture: 10-15 hours
Development (including auth, message logic, error handling): 40-60 hours
Testing & Deployment: 15-20 hours

You're looking at 65-95 hours of developer time at a minimum. At a blended rate of $125/hour (which is low for a contractor), you've already spent $8,000 - $12,000 before sending a single referral text. Want two-way messaging or any kind of tracking? Double that estimate.

Ongoing Maintenance Costs

Software isn't static. Your custom build will require ongoing attention.

API Changes: Bullhorn or Twilio updates their API. Your integration breaks. A developer needs to investigate and fix it.
Compliance: A2P 10DLC regulations are complex and ever-changing. Managing opt-in/opt-out logic and carrier filtering is a continuous job, not a one-time setup.
Bug Fixes & Security: Your code will have bugs. Your server will need security patches. This requires developer time.
Bullhorn API Limits: A poorly written script can hammer Bullhorn's API, eating up your daily call allowance and potentially disrupting other critical integrations (like your website or finance tools).

These maintenance costs can easily add up to 10-20 hours per quarter, representing thousands of dollars a year in reactive, unplanned developer work.

Why General SMS Fails for Referrals (Tracking, Attribution, Payouts)

Even if you build a perfect SMS broadcasting tool, you’ve only solved the communication problem. You haven’t built a referral program. This is the most crucial distinction.

A generic SMS tool can send a message like: "We're hiring a GRC Analyst. Know someone? Apply here: [link]."

This creates immediate, unsolvable problems:

No Tracking: You have no idea who shared that link. When a candidate applies, their source is "your website." You have no visibility into which referrer drove that application.
No Attribution: John texts your job to his friend Sarah. Jane posts it on LinkedIn. Sarah applies. Who gets the referral bonus? Your system has no clue. This leads to disputes and manual detective work.
No Engagement: Your referrers are in the dark. They send a name and never hear anything again. They can't see the status of their referral (e.g., Submitted, Interviewing, Hired). This kills motivation.
Manual Payouts: This is the biggest operational headache. Finance needs a clear, auditable trail to release a $2,000 referral bonus. With a DIY system, you're stuck reconciling spreadsheets, email chains, and Bullhorn notes. It’s messy, error-prone, and unsustainable.

Earshot: The Purpose-Built Bullhorn Referral Platform

Earshot is not a generic SMS tool. It's an end-to-end referral management platform that uses SMS as its core, hyper-engaging channel. We solve the communication problem and the entire referral workflow problem.

With Earshot's native Bullhorn integration, your workflow is transformed. We sync your jobs and contacts directly from Bullhorn. When you launch a referral campaign for a new DevOps Engineer role, here’s what happens:

Unique Links: Every person in your talent pool receives an SMS with their own unique tracking link.
Automatic Attribution: When a candidate applies through a unique link, an Earshot custom object is created on the candidate's record in Bullhorn attributing it to the exact source. There is zero ambiguity.
Automated Status Updates: As the candidate's status changes in Bullhorn (e.g., from "Web Response" to "Interviewing"), Earshot automatically sends an SMS update to the referrer. They stay engaged because they see progress.
Effortless Payouts: When a placement is made in Bullhorn, Earshot automatically calculates the bonus due and alerts your team, creating a clean, auditable record for finance.

This isn't just sending texts. It's running a fully automated, measurable, and scalable referral machine on top of your existing Bullhorn data.

Comparison Grid: DIY vs. Earshot for Key Referral Functions

Feature / Function	DIY (Bullhorn + Twilio)	Earshot
Referral Tracking	Manual. Requires building a separate database and complex logic.	Automated. Every click and submission is tied to a unique referrer.
Attribution Logic	Non-existent. You have no idea who referred whom.	Built-in. First-touch attribution is tracked automatically in Bullhorn.
Payout Management	Manual. Requires spreadsheets, email, and manual verification.	Automated. Triggers on placement status in Bullhorn for a clear audit trail.
Bullhorn Sync	Limited & Fragile. Custom-coded, risks hitting API limits.	Deep & Robust. Real-time sync of jobs, candidates, and statuses.
Compliance (A2P 10DLC)	Manual. You are responsible for registration and ongoing opt-out management.	Managed. We handle carrier registration and compliance for you.
Referrer Engagement	None. Referrers are in the dark after sharing.	Automated. Real-time SMS updates on referral status.
Setup Time	2-4 weeks (minimum) of developer time.	1-2 hours of onboarding.
Ongoing Maintenance	High. Constant bug fixes, API updates, and security patches.	Zero. We manage the platform, you run your program.

The Final Verdict: When to Build vs. When to Buy

So, should you build or buy? The decision framework is actually quite clear.

Build a DIY solution if:

Your only goal is simple, one-way SMS job alerts, not an interactive referral program.
You have an in-house development team with significant spare capacity and expertise in Bullhorn/Twilio APIs.
You are comfortable with a 5-figure upfront cost and ongoing, unpredictable maintenance expenses.
You accept the manual work required for tracking any referrals that happen by chance.

Buy a platform like Earshot if:

Your goal is to build a scalable, high-ROI referral program.
You need ironclad tracking, attribution, and payout management.
You want to avoid the cost, complexity, and technical debt of a custom software project.
You want your team focused on recruiting, not managing a fragile, custom-built tool.

For nearly every staffing firm, the time, cost, and functional gaps make a DIY Bullhorn Twilio referral SMS project a non-starter for serious referral generation. The initial allure of "free" quickly gives way to the expensive reality of custom software ownership.

How Earshot helps

Earshot turns Bullhorn into your firm's referral engine. We handle the complexities of tracking, attribution, compliance, and payouts so you can focus on building relationships and placing candidates. By automating the entire workflow via SMS, we make it effortless for your network to send you great talent and see the rewards.

If you're ready to stop managing spreadsheets and start driving measurable revenue from referrals, let's chat about what a true referral platform can do.