Same input
Worker shapes, hours, changes and expected exceptions are fixed before the run.
Evidence-led comparison
Compare the run, not the headline.
A payroll comparison should replay the same workforce, inputs, exceptions, correction and close path—then retain the outputs and date.
Method before scorecard
WageRun will not publish an unverified competitor grid.
The standard comparison uses one synthetic eight-worker scenario and records what the product actually did, what required support and what remained outside scope.
Same journey
Onboarding, calculation, approval, outputs, correction, close and support are attempted consistently.
Retained evidence
Dated screenshots, artefacts, receipts, invoices and support responses support every row.
Right to update
Material changes are re-tested. Stale findings expire rather than living forever in marketing.
Current publication state
No completed mystery-shop comparison is published yet.
Competitive research informs WageRun’s strategy, but the controlled eight-worker purchase-and-replay evidence is still an open programme item. We will not turn desk research into a product-performance claim.
What the eventual scorecard will separate
- Advertised feature vs demonstrated workflow
- Generated artefact vs external submission outcome
- Software price vs implementation and support cost
- Payroll calculation vs labour-process workflow
- South African depth vs geographic breadth
Product teams and practitioners
Want to challenge the method?
Send a correction, current product source or offer to participate in a reproducible comparison.