The moment that drives someone here: an HR coordinator has been trying to resolve a payroll discrepancy for two weeks. She's called four times, spoken to three different reps, gotten three different answers, and there is no record anywhere of what was said or promised. She has to re-explain the issue from scratch every time. ADP's case tracking is on their side; she has nothing on hers.

This gap persists because the information asymmetry is structural and benefits ADP. Their support reps see the case history; the customer doesn't. When a rep gives a wrong answer or fails to follow through, the customer has no leverage — no documentation, no timestamp, no record of what was promised. 'Requiring users to mail them and wait up to 72 hours' is not just slow; it means there's no accountability trail. The complaints about 'conflicting answers' and 'requiring multiple calls to resolve a single issue' are fundamentally a documentation and escalation problem, not just a training problem.

What's needed is a lightweight case management layer that sits on the customer's side: log a support interaction, record what was promised and by when, set an automatic follow-up reminder if it's not resolved, and generate a written escalation trail you can send to ADP's account management team if the front-line support fails. This is not a ticketing system — it's a log of your ADP support interactions, owned by you, with escalation templates pre-written for common failure modes (locked out more than 24 hours, payroll error not resolved before pay date, conflicting instructions from two reps on the same issue).

Without something like this, an HR team has no way to hold ADP accountable. They call, wait 30 minutes, talk to someone, and if it doesn't get resolved, they start over. With a paper trail, they can escalate within ADP's own structure to an account manager or implementation specialist — a path that exists but that most HR admins don't know how to navigate.

This is a business because ADP support quality is consistently bad across products and years, the HR admins who suffer most are not the buyers who could threaten to cancel, and the need to document and escalate recurs every single month around payroll cycles. It's also a trust-building wedge into a broader HR operations workflow product.

What to build

Build a browser-based interaction log for ADP support contacts — capturing date, rep name, what was promised, and deadline — with automatic follow-up reminders and pre-drafted escalation emails keyed to common ADP failure scenarios like account lockouts, unresolved payroll errors, and conflicting rep guidance.

Where to start

Distribute through HR forums and Reddit communities (r/humanresources, r/payroll) where people actively complain about ADP support — offer it free for solo HR admins, which gets you real usage data and word-of-mouth before you charge teams.

The hard part

The hardest early challenge is that this product only shows its value after a bad support experience, which means users who haven't yet had a two-week nightmare won't see why they need it — so acquisition has to happen at the moment of frustration, not before it.

How it makes money

Free for individual users tracking their own interactions; flat monthly fee (~$29-49/month) for HR teams that need shared logs, escalation history, and multi-user access.

See the evidence. The complaints behind this idea, the products they came from, and similar ideas in Core HR.

More ideas in Core HR