When I Work icon

Can I vibecode When I Work?

price $2.5/moyou'd save $30/yrbuild time closest consolation build: multi-daycategory hrreplaced by 0 people
KINDA
MOATcompliance regulationintegrationsexecution polish

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.

In-List Ad$79/30 days
promote your product in the vibecoded list

The Build Prompt

copy it and go build
ready to paste · 2,451 chars
Build a comprehensive, mobile-first personal replacement for When I Work in an empty repository.
Use exactly this stack: Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Docker Compose; do not offer alternative stacks.
Primary job: Build an all-in-one shift scheduling and workforce management platform optimized for hourly teams, with a strong focus on operational efficiency and employee self-service.

Core Requirements & Architecture:
- Implement a drag-and-drop shift builder that allows managers to create schedules quickly and attach specific site locations or roles to shifts.
- Build an "OpenShifts" feature where managers can post unassigned shifts that eligible employees can claim.
- Create an employee self-service portal where staff can view their schedules, submit availability, request time off, and initiate shift swaps with coworkers (pending manager approval).
- Integrate a lightweight centralized communication board for shift-related updates, announcements, and shift notes to replace fragmented text chains.
- Design the application to be completely responsive and mobile-first, ensuring employees "on the floor" have full access to their tools on smartphones.
- Implement least-privilege roles (e.g., Employee, Manager, Admin) and log sensitive record changes.

Technical Constraints:
- Make the first run work locally with one documented command using Docker Compose.
- Store all user data locally by default and make export straightforward.
- Put secrets in .env, ship .env.example, and never commit credentials.
- Add approval workflows, expiry reminders, and encrypted backups.
- Keep compensation fields optional and provide a data dictionary for sensitive fields.
- Include clear empty, loading, success, and recoverable error states.

Deliberate Exclusions:
- Never calculate payroll, taxes, benefits, or statutory filings.
- Deliberately leave out automated hiring decisions, compliance automation, applicant scoring, or complex geofenced time-clock enforcement.
- Do not add accounts, billing, telemetry, analytics, or a hosted control plane.

Testing & Documentation:
- Write focused tests for the shift-swapping approval workflow and core scheduling data transformations.
- Create a README with setup, architecture, permissions, data location, and disaster recovery steps.
- Ship Docker Compose, health checks, and an emergency-access procedure.
- Finish by running the tests and listing the exact commands used.
In-List Ad$79/30 days
promote your product in the vibecoded list

What you lose

  • Hosted infrastructure and managed operations from When I Work
  • The original service's mature integrations and ecosystem

Why it still works

🏛️ compliance & regulation · 🔌 integrations · 💅 execution polish

In-List Ad$79/30 days
promote your product in the vibecoded list
Share on X ->Your vote helps rank the vibecoded list.

Questions

5 answers