Can I Code This?

Can I code When I Work?

A shift schedule with a grid of employees and time slots is genuinely bounded, well-understood CRUD. Handling shift swaps and conflict-free scheduling across many employees is where the real fiddliness starts.

VIBE SCORE 94/100

how this is worked out

categoryhr
time to codea weekend
Borderline
their price$8/mo · $96/yr
last checked2026-08 · source ↗

Why CanICodeThis says Borderline

  • A weekly shift grid (employee x day x time slot) is a straightforward data model
  • Publishing a schedule and notifying employees by email or SMS is a well-documented pattern
  • Employees clocking in and out against their scheduled shift is simple CRUD with a timestamp

What you give up building When I Work yourself

  • Shift-swap requests between employees, with manager approval, need a small workflow engine to get right
  • Auto-scheduling that avoids double-booking and respects availability preferences is real constraint-solving, similar to this register's auto-scheduling-task-assistant idea
  • Labor law compliance (mandatory breaks, overtime rules) varies by jurisdiction and carries real legal weight if handled wrong

What you'd have to build

The parts this build actually needs, each rated on its own — the average is the Vibe Score above.

Landing page99
CRUD database95
User login92
Email notifications91

How to build your own When I Work

Build shift scheduling, sharing this register's own booking-adjacent build patterns: 1. A weekly shift grid (employee by day by time slot) — a straightforward data model. 2. Publish a schedule and notify employees by email — a well-documented pattern. 3. Clock-in/clock-out against a scheduled shift — simple CRUD with a timestamp. That's a real, working shift scheduler. Out of scope: shift-swap requests between employees with manager approval, which need a small workflow engine to get right, and auto-scheduling that avoids double-booking and respects availability preferences, real constraint-solving, similar to this register's own auto-scheduling-task-assistant idea.

What it actually costs to build

Two real costs, not just "free": the AI agent's own usage, and hosting once it's running. Both are estimated from this app's own effort rating and component list — see the assumptions on the method page.

AI agent — with a subscription (Claude Pro/Max, Cursor, etc.)$0 marginal
AI agent — pay-per-use API, no subscription$43–$86 one-time
Hosting, once it's running$0/mo (free tier)
Domain name, if you want your own~$12/yr

When I Work costs $8/mo. Even paying per-token with no subscription, and accounting for hosting, this build pays for itself in about 11 months.

Questions

Can I code When I Work?

Borderline. A shift schedule with a grid of employees and time slots is genuinely bounded, well-understood CRUD. Handling shift swaps and conflict-free scheduling across many employees is where the real fiddliness starts.

How much does When I Work cost?

When I Work costs $8/mo (about $96/yr) as of 2026-08. That's what a working rebuild would save you.

What do I lose by building it myself?

Shift-swap requests between employees, with manager approval, need a small workflow engine to get right Auto-scheduling that avoids double-booking and respects availability preferences is real constraint-solving, similar to this register's auto-scheduling-task-assistant idea Labor law compliance (mandatory breaks, overtime rules) varies by jurisdiction and carries real legal weight if handled wrong

Similar products you could build

Closest matches on the register — ranked by the build parts they share with When I Work, not just by category.

BambooHRhr · variesJust payCulture Amphr · variesJust payIndeedhr · variesJust payLinkedIn Recruiterhr · variesJust payRipplinghr · variesJust pay

Browse all finance tools · every comparison · how scoring works · the full register