If you have been in a demo with an enterprise HR vendor recently, you have heard the monolith pitch. “Everything in one place.” “Unified data.” “Single source of truth for people operations.” It sounds like a feature. For startups, it is a trap.
This essay explains why the all-in-one HR suite model is structurally bad for growing companies, what vendor lock-in actually costs in dollars and time, and what a lean, modular alternative looks like.
What “all-in-one” really means in HR software
An all-in-one HR suite is a bundle that includes ATS, candidate CRM, onboarding, performance reviews, payroll, benefits, time tracking, learning management, and reporting, all sold under one contract by one vendor with one database. For a 5,000-person enterprise with a dedicated HR operations team and twenty recruiters, this can make sense; the cost of integrating ten point tools is real, and the dashboards-of-dashboards problem is solved by a single pane of glass. For a 25-person startup, the same bundle is overkill by about 80%. You pay for performance review modules nobody uses, learning management nobody touches, and compensation planning modules that solve a problem you do not yet have. Workable starts at $149/mo for a 1–20 employee Starter and scales by employee bracket regardless of how many features you actually use. Greenhouse, per buyer-reported data on PriceLevel, runs a median contract around $12,250/year for sub-100 employee teams, with the higher CRM and reporting features locked behind Advanced or Expert tiers that push five-figure annual contracts.
Three structural problems with the monolith for startups
1. You pay for features you do not use. A typical enterprise HR suite charges for the full bundle regardless of what your team actually touches. A 25-person startup that needs an ATS and basic onboarding ends up paying for performance reviews, compensation planning, and learning management because those modules ship with the base license. The math gets worse on upgrades. Greenhouse’s Essential tier includes the ATS but not the candidate CRM. To get CRM, you move to Advanced or Expert, which run roughly $12K–$50K+/year, an increase justified almost entirely by features most startups will not use for two more years.
2. Feature gating creates permanent upgrade pressure. Monolithic HR suites use feature gating strategically. The feature you actually need is always one tier up. Custom reporting lives on Enterprise. API access lives on Enterprise. Bulk actions live on Advanced. Your team hits a single missing feature, the contract goes from $12K to $35K, and the upgrade is justified by one button. This is not an accident; it is the product strategy.
3. Lock-in compounds. Once payroll, ATS, onboarding, and benefits all live in one vendor, switching any single module means migrating data across all four. Most startups never switch, because the migration cost is too high. The vendor knows this and prices accordingly. A single-vendor contract that started at $15K/year tends to climb 8–15% at every renewal, per buyer reports on PriceLevel, because the alternative (a multi-system migration) is worse than the increase.
What a modular HR stack actually looks like for a startup
The modular alternative is not a single integrated platform; it is three or four point tools that each do one job well and share data through APIs. For most 10–200 person startups, the working stack is roughly:
- ATS: a flat-rate, outcome-based product (CurriculoATS Pro at $100/mo flat, currently $50/mo early bird, with unlimited team members).
- Payroll + benefits: Gusto or Rippling, priced per-employee on payroll, which is the only HR cost that legitimately scales with headcount.
- Onboarding: a lightweight tool or just a Notion + Google Drive workflow until headcount justifies more.
- Performance reviews: not needed at all under 30 employees; a Google Doc per quarter is sufficient. Add a tool when the founder cannot read every review personally.
A 25-person startup running this stack pays $1,200/year for the ATS and whatever Gusto or Rippling charge for payroll. Total HR tech spend is a fraction of a single enterprise HR suite contract, and every dollar buys functionality the team actually uses. The trade-off is that you have three logins instead of one. That is a real cost, but it is roughly an order of magnitude smaller than the one you avoid.
Why the monolith makes sense for enterprise and not for startups
It is worth being precise about who the all-in-one HR suite is actually built for. Workday, ADP, SAP SuccessFactors, and the heavyweight Greenhouse contracts are not bad products. They are correctly priced products for a specific buyer: the 5,000+ person enterprise with a dedicated HR operations team, a compliance department, multi-country payroll, and a CIO who needs vendor consolidation for IT-budget reasons. For that buyer, paying $400K+/year for a unified suite is rational because the alternative (managing twelve point tools) costs more in HR ops headcount.
The startup buyer is structurally different. There is no HR operations team; the founder runs hiring directly. There is no compliance department; the CFO and legal counsel handle it case by case. There is no CIO; the founder picks tools by feel. The monolith’s value (vendor consolidation for IT-budget reasons) does not translate into value for the startup, because the startup is not buying along that axis. So the startup ends up paying enterprise prices for enterprise features it does not need, which is the worst part of every contract.
The McKinsey research summarized in The shape of talent in 2023 and 2024 shows the rise of skills-based hiring and modular tooling, both pointing in the same direction: best-of-breed point tools beat bundled suites for teams whose hiring volume is moderate but whose quality bar is high.
The hidden tax of switching out of a monolith later
Most founders who buy a monolithic HR suite assume they can switch out of it if they need to. The math says otherwise. Once payroll, ATS, onboarding, and benefits all live in one vendor’s database, switching any single module means migrating data across all four. A 50-person company on a unified suite that decides the ATS is broken cannot move just the ATS without decoupling payroll integration, benefits eligibility flows, onboarding workflows, and reporting dashboards that all reference the same employee records. The migration project becomes a multi-quarter engineering effort instead of a 30-minute CSV export. Most teams never start the migration, which the vendor knows. The price reflects this. Renewal increases of 8-15% per year, per buyer reports on PriceLevel, are absorbed because the alternative (a multi-system migration with revenue risk) is worse. Across five years, a $15,000/year contract becomes a $30,000+/year contract through compounded escalation alone, before any feature-tier upgrades. Modular stacks have the opposite property. Switching the ATS in a Gusto + CurriculoATS + Notion stack is a one-afternoon project, because the ATS only owns ATS data. The migration math is reversible. That reversibility is what keeps the modular stack honest: the vendor cannot increase price aggressively without losing the customer, because the customer can leave on a Wednesday afternoon. The hidden tax of monolith lock-in is not the contract escalation; it is the loss of leverage that produced the escalation in the first place.
What we learned at Amazon about platform versus point
Before CurriculoATS, our founder Dev spent years at Amazon working on search and recommendation systems. The lesson from that work that maps onto the monolith-versus-modular question is precise: bundling makes sense when the modules genuinely improve each other. Search and recommendations on Amazon improve each other because they share user behavior data. Most HR-suite modules do not improve each other meaningfully; an ATS does not get smarter because it is in the same database as a learning management system. The data overlap is small. The integration value is mostly imagined.
Once you remove the imagined integration value, the case for the monolith collapses. You are paying a bundle premium for adjacency that does not produce a better product. The point-tool route, with each module sold separately and connected by API, gives you a better product per module at a lower combined price. The trade-off is integration work, but for a startup that has Stripe, Slack, GitHub, Notion, and a payments processor already, one more API integration is not the constraint.
Founder questions
Is the monolith ever the right choice for a startup?
Rarely, and only at specific scale points. If you cross 200 employees, run multi-country payroll, and have a dedicated HR operations team that costs more than the suite contract, the consolidation can pay off. Below that, the math does not work.
How much does vendor lock-in actually cost?
Direct cost is the contract increase at renewal, typically 8–15% per year per buyer reports. Indirect cost is the unwritten tax: when the next ATS you want is cheaper or better, you cannot move to it because payroll and benefits are entangled in the same contract. That tax can run into hundreds of thousands of dollars over five years for a growing company.
What about API access for integrations?
Most enterprise HR suites lock API access behind their highest tier, which means a 50-person startup that needs to connect a custom Slack workflow ends up on a $35K+/year contract. CurriculoATS includes API access on Pro at $100/mo flat. This is not a small detail; for any team that has engineering capacity and wants to automate, it changes the build-versus-buy calculus.
Doesn’t a modular stack create more integration work?
A small amount, yes. In practice, the integration work is hours per quarter once the initial setup is done. The integration cost is real but is dwarfed by the price difference. A founder running ten roles a year does not notice the API maintenance.
What if my board pushes for a single-vendor stack for reporting reasons?
The reporting argument is the strongest case for a unified suite, and it is also overstated for under-200 person companies. A 50-person team’s HR reporting needs (headcount, time-to-fill, attrition, comp ratio) sit in 4-6 spreadsheets and can be aggregated with a 2-hour-per-quarter ops effort. A single-vendor dashboard saves 2 hours; the price difference between modular and monolith is $20,000+ per year. The board ROI math favors modular until the company hits a scale where dedicated HR ops headcount exists.
Where does CurriculoATS fit in a modular stack?
It is the ATS module. Outcome-based screening, $100/mo flat, unlimited team members, full API access. It pairs cleanly with Gusto, Rippling, Notion, Slack, and any of the standard onboarding tools. See pricing and features for the full integration story.
What to do next
If you are evaluating an all-in-one HR suite right now, the simplest test is to ask the vendor for the per-feature usage data of similar-sized customers. Ask what percentage of their 25-person customers actually use the performance review module. The answer is almost always under 20%. Then look at the modular alternative on our ATS buyer’s guide and the compare page. The free Starter tier of CurriculoATS is enough to test the ATS module on one role.