The most maddening complaint across these 49 reviews isn't wait time — it's inconsistency. 'You seldom get the same answer from 2 different people.' 'Different answers for the same questions.' 'Customer service was a struggle — hard to get in touch anytime we had issues.' HR teams spend time not just waiting for answers but then second-guessing whether the answer they got is correct, because a different rep said something different last quarter.
This happens because ADP's support org has high turnover and is siloed by module. A rep in the benefits department doesn't see what the payroll department told you last month. There's no shared memory between the client and ADP, and there's definitely no shared memory between clients who've solved the same problem.
The gap here is a structured, searchable knowledge base built from real resolution histories — contributed by HR practitioners at ADP client companies — that captures what question was asked, what ADP said (in whatever form that came — email, case portal response, phone notes), and whether it actually worked. This is different from a forum or Reddit thread because the resolution is tied to a specific ADP configuration context (which product, which version, which module), not just a free-text question.
ADP has no incentive to build this because it would document their support inconsistencies publicly and reduce inbound support volume, which is how their managed services headcount is justified. Third-party HR communities exist but they're not structured around ADP-specific configuration questions with verified resolution status.
This is a business because the need is permanent and high-frequency: every time an HR team hits a configuration wall, they're starting from zero. A verified, community-built resolution database compounds in value over time — the more clients contribute, the better it gets — and that compounding creates a defensible position that no single vendor can replicate.
What to build
Build a structured Q&A database where HR practitioners log ADP support interactions (question, ADP's response, outcome) tagged by product, module, and configuration context, with community voting on resolution accuracy and a search interface that surfaces the highest-confidence answer for a given question first.
Where to start
Seed the database by manually researching and documenting the 50 most commonly asked ADP Workforce Now configuration questions (drawn from public forums, Reddit, and HR community groups), then recruit contributors by offering early members a free 'submit your unresolved question' concierge research service where you do the ADP legwork for them.
The hard part
Cold start problem is severe — a knowledge base with 50 entries is nearly worthless, and getting HR practitioners to contribute their resolved cases requires a habit change on top of an already painful workflow. The incentive to contribute only exists if others are already contributing, so you need a seeding strategy before the product is genuinely useful.
How it makes money
Free to search, paid membership ($15–$40/month per user) for unlimited contributions, priority answers, and the ability to post an unresolved question to the contributor community. Team plans for HR departments at $99–$199/month.
See the evidence. The complaints behind this idea, the products they came from, and similar ideas in Core HR.
More ideas in Core HR