Custom Applicant Tracking System vs Greenhouse: Build or Buy
The threshold is roughly 200 recruiter seats, or a hiring shape your applicant tracking system (ATS) was not built for. Below that, Greenhouse, Lever and Ashby are good products maintained by someone else, and staffing firms whose workflow fits Bullhorn or JobDiva should stay there.
On this page
The threshold is roughly 200 recruiter seats, or a hiring shape your applicant tracking system (ATS) was not built for. Below that, Greenhouse, Lever and Ashby are good products maintained by someone else, and staffing firms whose workflow fits Bullhorn or JobDiva should stay there. Above it, a custom ATS usually costs less within about two years: $60,000 to $130,000 for a first release in 12 to 16 weeks and $150,000 to $400,000 for a full platform phased over 6 to 12 months in Digital Heroes delivery experience. Most teams reading this should not build.
When is off the shelf genuinely the right call here?
Greenhouse, Lever and Ashby are good products, and if your hiring volume fits their shape a custom build is a distraction from work you do not need to own. That shape is considered hiring: a recruiter touches every candidate, the funnel moves stage by stage over weeks, and headcount is planned rather than surged. Twenty engineers evaluated over a quarter is exactly what these tools were designed around, and they do it well.
The same logic applies on the staffing side. If Bullhorn or JobDiva already models your submissions, placements and assignments in a way your recruiters accept, and the per seat cost is tolerable at your headcount, stay there. Being rigid is not the same as being wrong, and replacing a system your whole delivery team knows costs more than the licence line suggests.
Buy also when your seat count is genuinely stable. The economics that favour a build come from per seat pricing colliding with a business that adds fifteen sourcers for a fourth quarter ramp and drops them in January. If your recruiter headcount moves by five people a year, per seat pricing is not the problem you think it is.
None of this is a defect in Greenhouse. It is a product built for a specific hiring model, sold to companies with a different one. The failure is in the purchase, not the software. Before you conclude you have outgrown it, check whether you are paying for an Expert tier you have never configured, or piping data into a business intelligence (BI) tool because nobody set up the reporting you already own.
When does a custom build actually pay off?
Three conditions, and you want at least two before you spend anything.
The first is seat economics at scale. Modern applicant tracking vendors price per seat or per employee, billed annually. At two hundred recruiters and a hiring team that expands and contracts with demand, the bill grows with your headcount while a custom build hosts on infrastructure you already pay for. Adding fifteen sourcers becomes a permissions decision rather than a purchase. That structural difference, rather than any judgement about product quality, is why a build usually costs less within about two years at that scale.
The second is high volume hourly hiring. At thousands of applications a week, a stage by stage funnel where a recruiter touches every candidate makes the recruiter the bottleneck. Coordinators start dispositioning by hand, copying phone numbers into a separate texting tool, and scheduling interviews one email at a time. What you need is knockout logic with automatic disposition, bulk actions, apply by text message and self scheduling against real interviewer availability. Some of that exists as marketplace apps, each with its own subscription and its own copy of your candidate data.
The third is staffing economics. An employer applicant tracking system has no concept of a submission, a placement, a margin or a redeployment pool, and no custom field turns a candidate into a reusable billable asset. If bill rate minus pay rate is how you run the business, that belongs in the data model rather than in a spreadsheet beside it.
Compliance can be a fourth. Generic equal employment opportunity capture and standard disposition reasons do not encode your industry's credential logic or run a compliant adverse action sequence with mandated waiting periods.
How do they compare on the things that matter in this industry?
- Pricing shape. Per seat scales with your team, not with your hiring. A build scales with infrastructure. At fifty recruiters this barely matters, at two hundred with seasonal ramps it is the whole argument.
- Bulk throughput. Ask any vendor to demonstrate dispositioning four hundred candidates against knockout criteria in one action, then texting the survivors and letting them self schedule. Watch the demonstration on your own volume, not theirs.
- Staffing objects. Submission, placement, assignment, bill rate, pay rate, margin and redeployment pool either exist as first class objects or they do not. Custom fields are not the same thing, because you cannot report on a margin that is a text field.
- Vendor management integration. A connection to Fieldglass or Beeline is heavier than a job board, because requisition intake, submission rules and timesheet flow all have to behave, and the client controls the testing schedule.
- Marketplace sprawl. Count what plugs in: job distribution to Indeed and ZipRecruiter, background checks through Checkr or Sterling, assessments, texting, electronic signature, onboarding, payroll handoff. Each is a subscription and a copy of your candidate data.
- Reporting access. Time to fill, cost per hire, recruiter productivity, source return and margin by client either sit in the tool or one export away from the decision. Ask which tier that lives in before you compare prices.
What does total cost of ownership look like at your scale?
A focused first release covering the high volume pipeline with knockout auto disposition and bulk actions, apply by text message, self scheduling, two critical integrations and the reporting your operations review needs runs $60,000 to $130,000 and ships in 12 to 16 weeks in our delivery experience. A full platform adding staffing economics, vendor management system integration, credential and compliance engines, multi client support and migration off your incumbent runs $150,000 to $400,000 phased over 6 to 12 months.
A worked example: a staffing firm with two client vendor management platforms came to $128,000 for phase one over fourteen weeks, $216,000 across the following nine months, and $46,000 to migrate eight years of candidate history with resumes, notes and stage history. Total $390,000, at the top of the band. Within phase two, staffing economics with bill rate, pay rate, margin and redeployment pool was $58,000 and vendor management integration across two client platforms was $52,000.
Migration alone commonly runs $25,000 to $60,000 depending on record volume and attachment count, and it should be priced by counting rather than estimated.
Against that, a $390,000 platform is roughly $78,000 a year of capital plus continuing engineering, and it does not increase when you add fifteen sourcers for a seasonal ramp. Compare that against your renewal, plus every marketplace subscription, plus the tooling your coordinators bought on a card because the pipeline did not do what they needed.
What does the hybrid look like, and when is it the honest answer?
The hybrid is real here and it is underused. Keep the applicant tracking system for corporate and considered hiring, and build a thin high volume layer beside it for the hourly pipeline.
In practice that means Greenhouse or Lever continues to run engineering, sales and corporate roles where its model fits and where hiring managers already live. The build owns the hourly funnel: deduplicated ingest, knockout auto disposition, bulk actions, apply by text message, self scheduling and the operational reporting. The two share candidate records through the vendor's interface so a warehouse applicant who later applies for a supervisor role is not a stranger.
This is the honest answer when your volume problem is concentrated in one business unit rather than spread across the company, which is common in retail, healthcare, logistics and hospitality. It is also the right first step when you suspect you will eventually replace the incumbent but cannot justify the full project yet, because the high volume layer is the part that pays for itself fastest and it can absorb corporate hiring later.
The hybrid stops working when you are paying full seat price for an incumbent that now handles a minority of your hiring. Watch that ratio and revisit at renewal.
Which should you choose, by operator size and stage?
Under fifty recruiter seats with considered hiring: buy. Greenhouse, Lever or Ashby, configured properly, and put the money into sourcing. A build at this size is a project you will resent.
Fifty to two hundred seats with a mixed model: buy for corporate, build the high volume layer if one business unit is drowning. The first release at $60,000 to $130,000 covers this and it is the highest return version of the project.
Above two hundred seats with seasonal ramps: build, and expect the full path. Start with the pipeline and two integrations, not eight. Each vendor management, background check, assessment, job board and payroll connection is separate engineering with its own authentication, failure modes and deduplication problem, and a build with eight integrations costs roughly double the same feature set with three.
A staffing firm whose workflow fits Bullhorn or JobDiva: stay. The argument for building is margin, redeployment and vendor management integration, and only when those are actively costing you placements rather than merely irritating you.
A high volume employer with no engineering function of its own: think carefully. Owning an applicant tracking system means owning it when a job board changes its posting rules in November, when a background check provider deprecates an authentication method, and when a client's vendor management platform schedules its own upgrade. That is a standing commitment of a few days a month, not a project that finishes. If you have no internal owner for it, budget the continuing engineering as a retained arrangement from the outset rather than discovering the need after launch.
Any firm mid contract: do the arithmetic at renewal, not in month four of a twelve month term. The comparison you want is the full stack cost against the build plus its continuing engineering, over three years.
When the shortlist is down to two and you need a tiebreaker, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. Nothing about that commits you to the build.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- An EY survey found one in five U.S. payrolls contains errors, each costing an average of $291 to remediate, with a typical 1,000-employee organization spending roughly 29 workweeks per year fixing common payroll errors. Source: EY (Ernst & Young) (2022) →
- An earlier SHRM benchmarking report (reflecting fiscal year 2015, published 2016) established a widely cited baseline average cost-per-hire of $4,129, illustrating how recruiting costs have climbed over time (SHRM's separate 2025 Benchmarking Report shows $5,475 for nonexecutive roles). Note: the $5,475 figure is not on this linked page; it comes from SHRM's 2025 report. Source: SHRM (Society for Human Resource Management) (2016) →
- SMS reminders that stated the specific cost of the appointment to the health system reduced missed appointments in Trial One, with the DNA (did-not-attend) rate falling from 11.1% (control) to 8.4% (specific-costs message) - an odds ratio of 0.74 (95% CI 0.61-0.89), i.e. roughly a 24-26% relative reduction - at no additional cost. (Trial Two replicated this at an 8.2% DNA rate.). Source: PLOS ONE (Hallsworth et al.) (2015) →
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
Frequently asked questions
Is a custom build cheaper than Greenhouse at two hundred recruiters?
Usually within about two years, and the reason is structural rather than a judgement about the product. Greenhouse and similar tools price per seat while a custom build hosts on infrastructure you already pay for, so adding fifteen sourcers for a seasonal ramp becomes a permissions decision rather than a purchase. Below that headcount, or where your recruiter count barely moves year to year, the arithmetic does not work and you are buying a maintenance obligation. Run the comparison over three years including continuing engineering before deciding.
What does migrating candidate history off Greenhouse or Bullhorn cost?
Commonly $25,000 to $60,000 depending on record volume and attachment count, and it should be priced by counting rather than estimated. In one worked example, eight years of history with resumes, notes and stage history came to $46,000. Ask for record counts and total attachment size from your incumbent before anyone quotes. The parts that surprise people are stage history, which is what your reporting depends on, and resume files, which are numerous rather than large. Plan to run both systems for a full hiring cycle.
What happens if our ATS vendor changes its pricing tiers?
The exposures are per seat rises, which punish staffing up exactly when demand is high, and reporting moving behind a higher tier, which puts the metrics you run the business on one export away from the decision. Neither is a reason to build on its own. The practical protection is to keep your own copy of candidate, requisition and placement data flowing into a warehouse you control, so a tier change becomes a negotiation rather than an emergency, and so a future migration is a known quantity rather than an archaeology project.
How long before recruiters are working in a custom ATS?
Twelve to sixteen weeks for a first release covering the pipeline, apply by text message, self scheduling, two integrations and operational reporting. Discovery takes the first two to three weeks and is mostly spent on the data model covering candidate, requisition, submission, placement and assignment, because getting that wrong is expensive later. Plan a pilot with one business unit and one requisition family before wider rollout, and keep the incumbent running for corporate hiring until the volume funnel has survived a real peak.
Can a custom ATS handle bill rates, pay rates and margins?
Yes, and that is exactly where employer tools fall short, since they have no concept of a submission, a placement or a margin. A build models candidate, submission, placement and assignment as first class objects, calculates margin as bill rate minus pay rate on every deal, and maintains a redeployment pool so a contractor rolling off is an asset rather than a closed record. In a worked example that piece came to $58,000. Custom fields in an employer tool do not reach this, because you cannot report on a margin held as text.
Should a staffing firm build or stay on Bullhorn?
Stay on Bullhorn or JobDiva if their workflow fits and the per seat cost is tolerable. They cover submissions, placements and assignments, which is why so many firms live there. Build when two things are true together: the seat bill has become a material line, and the gaps are costing you placements rather than merely irritating recruiters. Vendor management integration with Fieldglass or Beeline, redeployment and margin reporting are the usual triggers. Rigid and dated is annoying, it is not by itself a business case.
How many integrations should be in the first release?
Two, and choose them by which failure costs you candidates. Usually that is your primary job source and your background check provider, since Checkr or Sterling triggers a regulated pre adverse and adverse action sequence with mandated waiting periods. Each additional vendor management, assessment, job board and payroll connection is separate engineering with its own authentication, failure modes and deduplication problem. A build with eight integrations costs roughly double the same feature set with three, so stage them against proven need rather than a wish list.
What does it cost to run each year once it is live?
Budget continuing engineering at roughly a fifth of the build cost in year one and closer to a tenth thereafter. On a $390,000 platform that is around $78,000 a year of capital plus maintenance, spent on integration changes, new client requirements and compliance updates rather than a support retainer. The number that does not appear is a seat bill, which is the point: internal access becomes a permissions decision, so a fourth quarter ramp of fifteen sourcers costs nothing extra in software.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
What tech stack should custom HR software use?
Choose boring and hireable: React or Next.js on the front end, Node.js or Django behind it, and PostgreSQL for data, since Postgres row-level security maps cleanly onto salary visibility rules. That is the Digital Heroes default for HR systems because any future team can maintain it. Be wary of agencies pushing an exotic stack; you will be hiring for it for a decade.
What should I prepare before contacting an agency about HR software?
Bring four things: your current tool list with annual costs, headcount now and projected in two years, the five workflows that waste the most HR hours each week, and any compliance requirements like multi-state employment or union rules. A sample data export from your current system helps too. Digital Heroes scoping calls with this prepared produce a fixed quote in days instead of weeks.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
What happens to our HR system if the development agency shuts down?
Nothing, if the handover was done right: you hold the repository, the cloud accounts, the deployment runbook, and the schema documentation, so any competent team can take over maintenance. This is why code ownership and infrastructure access belong in the contract rather than in goodwill. Ask for the handover package as a deliverable of the first release, not something promised for later.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
Who can build a custom HR software system?
Digital Heroes builds custom HR software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other HR software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Connor.
Account Manager · Sydney · 1 post on the site
Published · Last updated .
