Can AI replace When I Work?
The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For When I Work, build a small shift schedule, availability form, and swap approval workflow. The hard boundary is mobile apps, time clock, notifications, scheduling edge cases, and support, plus compliance, payroll, and regulated integrations.
01What it costs
Checked Aug 10, 2026 · source: wheniwork.com.
| Plan | Monthly | Billed yearly | What you get |
|---|---|---|---|
| Essentials | $2.5 | $2.38/mo | Scheduling and team messaging; price per user/month |
| Pro | $5 | $4.75/mo | Expanded scheduling, controls, and reporting; price per user/month |
| Premium | $8 | $7.6/mo | Advanced scheduling and workforce controls; price per user/month |
Hidden costs: Time Tracking & Attendance is a separately toggled add-on with no public price on the live plan table. Annual plans cannot reduce seats or downgrade until within 30 days of renewal, use manual renewal, and are non-refundable.
02Could AI build it for you?
The core job: Build a small shift schedule, availability form, and swap approval workflow, maintain approvals and records, and export data without calculating payroll or making employment decisions.
What a working version needs:
- PostgreSQL
- private self-hosted deployment
- strict admin access
- documented retention policy
Editorial comparison targets the Essentials plan and a internal records tracker without payroll DIY substitute. Recheck price before merge.
03What you'd give up
- mobile apps, time clock, notifications, scheduling edge cases, and support
- payroll rails
- tax and labor-law compliance
- benefits integrations
- identity checks and global employment infrastructure
People still pay for When I Work because HR platforms survive because mistakes affect pay, benefits, immigration, and legal obligations, not because forms are difficult to render. The recurring cost buys sensitive data, access, retention, audit, payroll calculations, filings, benefits, employment law, incident response, and support, not just the visible interface.
04Free and cheaper alternatives
Schedules, availability and manager-approved swaps for 30 people; the time clock costs extra.
Versus paying: It covers scheduling for thirty users but the free plan omits the time clock and several labor-management features.
getsling.com →A small roster, availability form and approved shift trades for one 15-person location.
Versus paying: The free plan is restaurant-specific, limited to one location and fifteen employees, and lacks a free time clock.
7shifts.com →Scheduling, availability and shift changes for ten people; employee eleven ends the free plan.
Versus paying: It is clean for ten users, but employee eleven ends the free plan and the product is broader than a dedicated scheduler.
connecteam.com →05The build prompt
Paste this into an AI coding tool (such as Claude, ChatGPT, Lovable or Replit) to build your own version.
Build a personal replacement for When I Work in an empty repository. Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Docker Compose; do not offer alternative stacks. The core loop is: build a small shift schedule, availability form, and swap approval workflow, maintain approvals and records, and export data without calculating payroll or making employment decisions. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Implement employees, teams, roles, documents, leave requests, equipment, onboarding tasks, and acknowledgements. Use least-privilege roles and log every read or change to sensitive records. Add approval workflows, expiry reminders, export, retention, deletion holds, and encrypted backups. Keep compensation fields optional and never calculate payroll, taxes, benefits, or statutory filings. Provide a data dictionary and explain which fields should not be stored without legal review. Ship Docker Compose, health checks, disaster recovery, and an emergency-access procedure. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out payroll calculation or money movement. Deliberately leave out automated hiring decisions or applicant scoring. Deliberately leave out tax, benefits, immigration, identity, and global-employment compliance. Finish by running the tests and listing the exact commands used.
06Open-source starting points
- Frappe HR: Active open-source human-resources and payroll application built on Frappe.
App prices, verdicts, alternatives and build prompts are adapted from Can I Vibecode It? (MIT License, © 2026 Rob Hallam). Each price shows the date it was checked and its source. Prices change; confirm on the vendor's site before you decide.
Get new verdicts in your inbox.
One short email when new verdicts land: what AI can now do for you, and what it still gets wrong. No spam. Unsubscribe anytime.