When targets are hit,rewards happen automatically.
Define a trigger, set conditions, choose an action. Wudd handles the rest. Gifts, points, badges, nudges, and budget allocations fire without anyone lifting a finger.
Three building blocks. Infinite combinations.
Every automation follows the same pattern: when something happens, check who qualifies, then do something for them.
An event fires or a schedule ticks. The engine wakes up.
- +Badge earned by an employee
- +Cron schedule (daily, weekly)
- +KPI threshold crossed
Filter the audience by role, tenure, department, or custom criteria.
- +Role is employee or team leader
- +Tenure over 90 days
- +Department matches target
Send an in-app notification or allocate a SAR budget. Two action primitives that compose into rich workflows.
- +Send in-app notification
- +Email an employee with a manager-suggested action
- +Allocate SAR budget
Automations that run your culture.
Real scenarios that organisations set up in minutes.
When an employee earns 10 badges in a quarter, allocate a 500 SAR celebration budget for the team and notify their manager.
On each employee's birthday, send a personalised nudge to their manager with a reminder to recognise them.
At 1, 3, and 5 year milestones, allocate a celebration budget and trigger a company-wide recognition nudge.
When a team hits their quarterly OKR target, trigger a budget allocation for a team celebration.
When an employee maintains a recognition streak for 30 consecutive days, the system sends a wellness-day suggestion to the employee and their manager. The team arranges the timing off-platform.
New hires who finish their onboarding quest within 14 days trigger a welcome budget allocation and a manager nudge to grant the welcome badge.
Automations that can not run away.
Every automation has built-in safety limits. No runaway spending, no notification spam, no duplicate rewards.
- 01Budget cap (SAR/month)Set a maximum monthly spend per automation. The engine blocks execution when the limit is reached and logs it.
- 02Frequency cap (days)Prevent the same employee from being targeted more than once within N days. Eliminates notification fatigue.
- 03Audience capLimit the number of users affected per run. Protects against misconfigured conditions that match everyone.
- 04IdempotencyA SHA-256 hash prevents the exact same automation from firing twice in the same time window. Zero duplicates.
- 05Dry run modeTest any automation without executing it. See the full audience, actions, and budget impact before going live.
Every run is recorded.
Versioned definitions, execution logs, budget tracking, and audience records. Nothing happens in the dark.
Every change to an automation creates a new version with a SHA-256 checksum. Previous versions are preserved.
Start time, end time, status, audience size, actions dispatched, and budget consumed. Per run.
Monthly budget reservations are recorded per automation. Aggregated for finance reporting.
Guardrail blocks, idempotency skips, and audience touches are all logged with metadata.
Set it once. Let it run.
Automations that reward, nudge, and celebrate without manual intervention. Built-in guardrails ensure nothing goes wrong.