Classification: opportunity / idea_filter.
One-line thesis: Build a narrow evidence-and-exception workspace for UK payroll bureaus, accountants, and pension/payroll advisers that tracks automatic-enrolment staff status, statutory communications, scheme handoffs, opt-in/opt-out evidence, re-enrolment cycles, and audit-ready retained records across many SME employer clients.
This is a credible but not slam-dunk micro-SaaS wedge. The regulatory workflow is real, recurring, and multi-client: employers must assess workers, enrol eligible staff, send required communications, pay and report contributions, keep records for years, and re-enrol/re-declare every three years. The Pensions Regulator explicitly tells business advisers that clients must keep staff and scheme records, have processes to manage changes, and make sure payroll processes work with pension-provider data transfer.
The skepticism is important: much of automatic enrolment is already covered by payroll software. Moneysoft says Payroll Manager assesses employees, handles postponement, calculates pension contributions, creates employee letters/emails, keeps records/reports, and produces files/direct integration for pension providers including NEST. BrightPay markets auto-enrolment automation, alerts, bureau batch processing, and payroll/accounting integrations. IRIS/Staffology, Sage, Xero-connected payroll, and pension-provider portals also overlap. A standalone product only works if it does not try to replace payroll or pension administration. The wedge is cross-client exception control and evidentiary completeness: “prove what happened, what remains unresolved, who owns the next handoff, and what can be shown to TPR if asked.”
Best initial buyer: payroll bureaus and accountancy firms processing payroll for dozens to hundreds of small employers, especially those using mixed payroll products, pension schemes, old desktop files, client email chains, and separate document storage. For a single small employer, this is probably overkill; for a bureau, the multi-client queue and audit trail can be worth paying for if it saves coordinator time and reduces missed re-enrolment/communication failures.
Do not build “auto enrolment software.” Payroll incumbents already do that. Build an AE evidence and exceptions cockpit:
The product should ingest payroll outputs and pension-provider receipts rather than calculate payroll. That keeps the MVP weekend-buildable and avoids head-on competition with BrightPay/Moneysoft/Sage/IRIS.
Primary ICP:
High-intent triggers:
First-party evidence supports the underlying workflow.
The Pensions Regulator’s business-adviser guide says clients must keep records about staff and the pension scheme they enrol staff into, ensure records are ready for automatic enrolment, have processes to manage changes, and provide the right information to the pension scheme. It states employers must keep staff and scheme records for at least six years, except opt-out records for four years, and must keep records legible and available to TPR in a timely manner if requested. Importantly, it warns that if business or pensions administration is outsourced to a third party, the employer remains legally responsible.
TPR’s adviser guidance on payroll processes says staff records needed for AE include dates of birth, salaries, National Insurance numbers, contact details, and amounts paid into the pension scheme each pay period. It says the client’s payroll software/process should support AE duties, work with the pension scheme for easy data transfer, and help enrol staff as they become eligible.
TPR’s ongoing-duties guidance reinforces recurrence: duties do not end after the duties start date. Employers must keep paying contributions, keep staff records up to date, monitor changes in age and earnings, manage opt-in/leave requests, and re-enrol/re-declare every three years. The employer-facing re-enrolment page says employers must complete a re-declaration of compliance whether or not they have staff to re-enrol, and warns they can be fined if they do not act.
The scale is large enough for a niche. TPR’s declaration-of-compliance report showed 2.72 million employers had declared compliance by April 2026, covering 36.37 million workers, with 11.44 million eligible jobholders automatically enrolled and 12.41 million already active qualifying-scheme members. A 2025 DWP analysis says automatic enrolment has brought more than 22 million people into workplace pensions as of 2023, over 10 million more than in 2012.
Enforcement remains current. TPR’s July-December 2024 compliance and enforcement bulletin reported 52,914 AE cases closed in the period and 830,982 cases closed to date. For AE powers in that six-month period, it listed 31,740 compliance notices, 18,254 unpaid-contribution notices, 21,504 fixed penalty notices, and 7,608 escalating penalty notices. TPR’s penalty-notices page publicly lists employers with escalating penalty notices over £14,000, including examples from July-December 2024.
The buyer pain is not usually “I don’t know what automatic enrolment is.” It is “I need to prove every small monthly AE thing happened across many clients, and my evidence is split across payroll software, pension-provider portals, emails, uploaded CSVs, old letters, and client-specific spreadsheets.”
This is a mature regime, not a new-deadline gold rush. That makes the opportunity smaller but also more operationally stable.
Weekend-buildable first version:
1. Client registry: employer PAYE/reference fields, duties start date, re-enrolment date, declaration/re-declaration deadline, pension provider, tax relief method, contribution basis, payroll system, adviser owner.
2. AE task calendar: monthly/weekly checklist per client with generated tasks for assessment, communications, provider upload, contribution confirmation, opt-out refund handling, and record retention.
3. CSV/email evidence ingest: upload payroll AE reports, pension-provider upload receipts, contribution schedules, and sent communication logs; store normalized metadata and original files.
4. Exception queue: flag missing NI/contact data, missing provider receipt, unresolved opt-in/opt-out, postponement ending, overdue re-declaration, or no evidence attached for a statutory communication.
5. Record-retention map: tag evidence as staff record, scheme record, opt-in/join/opt-out notice, contribution payment, communication, provider handoff, or declaration support; show six-year/four-year retention logic.
6. Client/adviser comments: notes and owner assignment for ambiguous cases without making legal determinations.
7. Audit pack export: zip/PDF/HTML package per client/date range with event timeline, evidence links, unresolved exceptions, and retained documents.
Avoid pension-provider integrations at first. Start with CSV/import templates and inbox-forwarding. Direct NEST/People’s Pension/Aviva integrations can come only after validating that bureaus will pay.
Best channels:
The landing-page language should be operational: “Stop reconstructing AE evidence from payroll files, pension portals, and email when TPR asks.” Avoid fearmongering as if AE is a new law.
The strongest counterargument is that the proposed product is just a disciplined checklist layered on top of payroll software. Public evidence proves duties, record retention, enforcement, and scale, but it does not prove payroll bureaus are actively seeking standalone AE recordkeeping software. Moneysoft’s “keeps records and provides reports” claim is a serious warning sign: if common bureau payroll products already satisfy the practical need, standalone AE evidence software becomes a nice-to-have.
The next validation step should be 15-20 calls with UK payroll bureau managers. Ask: How many AE exceptions are tracked outside payroll? How often do you reconstruct evidence for TPR/client disputes? What does re-enrolment planning look like across all clients? Which payroll/pension systems are hardest to coordinate? Would a cross-client AE evidence pack save paid staff hours, and what would you pay? If they answer “BrightPay/Moneysoft handles it,” skip or reposition as a plug-in/reporting layer for firms using mixed systems.
Promising as a narrow compliance-evidence cockpit for payroll bureaus, but only worth building if customer discovery confirms spreadsheets and payroll-system tools are failing at multi-client exception tracking.