Skip to content

When a Custom ATS Stops Paying Off: Lupa's Move to One ATS + CRM

Lupa places senior talent from Latin America with employers in the United States and Canada.

The agency started by commissioning its own applicant tracking system, then found the build was costing more than it returned. This page walks through what broke, what replaced it, and the checks an agency owner should run before making the same call. The account below is drawn from the original published case study; quotes and cost figures are attributed to that source and are not independently verified here.

The setup: a cross-border agency with a homegrown ATS

According to the original case study, Lupa was founded by Joseph Burns to connect senior Latin American talent with companies in the U.S. and Canada. To run that pipeline, the team chose to build a custom applicant tracking system rather than buy one.

That decision is common in agencies that expect unusual workflows. The trade-off is that a custom build becomes a product you now have to maintain, staff and extend — while your recruiters still need to place candidates.

Three failure modes, not one

The problems that surfaced at Lupa, as reported in the source case study, are worth separating because each one calls for a different remedy.

The money problem is the easiest to see: operating the custom system was reported at $6,000 to $10,000 per month, an ongoing expense that does not shrink as the business changes. The data problem is subtler — one part of the team worked inside the custom ATS while another worked in HubSpot, so candidate and client context was never in one place. The growth problem is structural: the system, as built, could not absorb what the agency needed next.

A budget fix alone leaves the split records and the ceiling in place. A replacement only earns the switch if it removes all three constraints at once — consolidating the records and keeping pace with volume, not just lowering the invoice.

A quick cost check before you keep building

Use the captured monthly range as a reference point, not a benchmark for your own agency. The arithmetic below shows why the comparison matters more than the sticker price.

Before renewing a build budget, list every recurring line: engineering time, hosting, integrations and the hours recruiters lose switching between systems. If the total is in the same order of magnitude as the range above, a consolidated platform is worth evaluating on cost alone. These figures are a dated reference from the agency's own account as published in the source case study and should be re-checked against current conditions.

What changed after consolidation

Moving to a single ATS + CRM put sourcing, client relationships and candidate history in one record set. The source case study describes the result as faster, more structured and less expensive hiring, with the team no longer reconciling two systems.

Two capabilities carried most of the day-to-day value in that account:

  1. Workflow Automation. Outreach steps run without a manager manually confirming that each recruiter contacted each candidate. The agency's founder is quoted in the source as judging the subscription cheaper than adding another hire to supervise that activity; that pricing comparison is the source's own claim and should be confirmed against current plan pricing before relying on it.
  2. Candidate interaction history across clients. When a new search opens, the team can review everyone previously approached and what happened with each client, rather than rebuilding that context from memory or scattered notes.

What a consolidated record should hold

If you are evaluating a switch, test whether one system can carry all of the following without a parallel spreadsheet or CRM:

  • Candidate record: source, current stage, outreach status, prior client submissions and outcomes.
  • Client record: open roles, submission history per role, and feedback tied to the specific candidate.
  • Interaction link: the join between a candidate and each client they were presented to, so history survives when a new search begins.
  • Automation trigger: the rule that fires outreach or follow-up without a human check step.

If any of these lives in a second tool, you have not consolidated — you have added a sync.

Decision checklist for agency owners

Work through these before committing either way:

  • [ ] Is the custom system's monthly cost documented, including engineering and hosting?
  • [ ] Are any teams working outside the ATS in a separate CRM?
  • [ ] Can the current system absorb your next twelve months of volume?
  • [ ] Does a candidate's history with each client survive a new search?
  • [ ] Can outreach run without a manager verifying it manually?
  • [ ] Would the subscription cost be lower than the cost of one additional hire to supervise outreach?

A "no" on the fragmentation or history questions is the strongest signal to evaluate a replacement, regardless of price.

A quick cost check before you keep building
LineCaptured reference
Custom ATS operating cost$6,000–$10,000 per month
Equivalent annual run rate$72,000–$120,000 per year
Work split across toolsCustom ATS plus HubSpot

Frequently asked questions

Why did Lupa move away from its custom ATS?

Per the original case study, three reasons combined: the build cost $6,000 to $10,000 per month to operate, the team was split between the custom system and HubSpot, and the system could not scale with the agency's growth. A single ATS + CRM addressed all three at once.

Which feature mattered most after the switch?

Workflow Automation. In the source account it removed the need for a manager to confirm that recruiters had contacted candidates, and the agency's founder is quoted as judging the subscription cheaper than hiring another person for that oversight. That cost comparison is the source's own claim and should be checked against current pricing.

How does candidate history work across clients?

Each candidate's prior conversations and client interactions stay attached to their record. When a new search starts, the team can review who was already approached and how each client responded, instead of starting from scratch.

Is a custom ATS ever the right choice?

It can be, if your workflow is genuinely unlike anything on the market and you can fund ongoing maintenance. The test is whether the build cost stays below the alternative and whether the system keeps up as you grow. Lupa's case shows what happens when both answers turn negative.