Rewards people earn. Automation that holds its limits.
Wudd ships a recognition-driven rewards store and an automation engine that fires nudges and budget actions inside hard, server-enforced caps. HR stops being a voucher desk; the budget stops running away.
Two action types, audit-grade.
The engine fires two action types today: nudges and budget actions. Both are auditable, both run inside the same five-layer cap stack as manual recognition, and both are throttled with daily-per-receiver and per-period limits.
- 01Nudge a manager when the recognition signal to a teammate thins out
- 02Top up a recognition budget when a Strategy KPI is verified or an OKR Key Result advances
- 03Fire an Occasion-template message on birthdays, anniversaries, and the lunar holidays once the matcher ships
- 04Surface candidates for the Promotion Engine pillar review when the threshold is crossed
- 05Every event written to the audit log with a 7-action enum, reason, and actor
Honest scope: in production today, two event keys emit, `culture.challenge_requested` and `culture.recognition_nudge_requested`. The four additional keys advertised in the engine UI (recognition_submitted, milestone_achieved, promotion_approved, anniversary_due) are wired in the surface but do not yet emit; they ship in Q3.
A store stocked from the supplier network.
Employees earn points from recognitions and from completing performance goals, then redeem in the in-app store. The catalog is sourced from a pre-approved supplier network, no inventory work on your side, no voucher emails to forward.
- 01Digital wallet, balance, and order management, every transaction logged
- 02Wallet top-ups and wallet aging so points cannot accumulate forever and break budgeting
- 03compliance-ready compliance through the accounting layer. Wudd does the books, the accounting layer issues the receipt
- 04Plan grandfathering, admins can update pricing without re-pricing legacy subscriptions
- 05Five-layer cap stack governs every reward issuance, same as recognition
Saudization compliance and Vision-2030 dashboards are not on the rewards surface. They sit in a separate Horizon C work-stream and are not advertised here.
Five-layer cap stack.
Every recognition and every automated reward passes through a five-layer fairness check, server-side, with `abort(422)` on breach. Caps are how points stay precious, how managers cannot quietly mint reputation for one favorite, and how the recognition signal stays honest enough to feed Strategy KPIs.
- 01
- Per-giver weekly capA finite weekly recognition budget per sender, so the act of recognizing carries a real opportunity cost.
- 02
- Per-receiver monthly capA monthly ceiling on what any one employee can accumulate, so a single favored receiver cannot saturate the signal.
- 03
- Per-value monthly cap (overridable)A ceiling on how much can be loaded onto a single Company Value in a month, with managed overrides, keeps every value alive in the data, not just the loudest one.
- 04
- Per-receiver daily cap on manual recognitionA daily floor against same-day burst behavior. Automated rewards are governed by their own per-period rules.
- 05
- Value-level period caps with per-receiver sub-capsPer-Company-Value, per-period limits with sub-caps per receiver so cross-team patterns are detectable in the data.
On top of the five layers, a Gini-coefficient concentration check is wired into the Recognition Equity, Culture Momentum, and Team Stability widgets. A rising concentration score lowers the index, which is the right direction for a fairness control. Surfacing this check as a single named "Concentration / Nepotism" page with a dedicated UI is on the Q3 roadmap.
What ships today, what is on Q3.
In production today.
- →Five-layer cap stack, server-side, `abort(422)` on breach
- →Nudge + budget action types, with the 7-action audit enum
- →Wallet, store, order management, wallet aging, automated compliance-ready receipts
- →Plan grandfathering, admin can update pricing without re-pricing existing subscriptions
Shipping inside the next quarter.
- ·Four additional automation event keys emitting in production (today only two emit)
- ·Concentration / Nepotism widget surfaced as a single named page with dedicated UI
- ·Lunar-holiday matcher for Eid al-Fitr, Eid al-Adha, and Ramadan welcome on the Occasion templates
Marketing copy that runs ahead of code is how trust dies. Where the IC verification flagged a gap between the surface and the emission, this page says so.