🔄 089 — ShiftSwap — Team Shift Trade & Schedule Swap Board
Date: August 11, 2026 | Difficulty: ⭐⭐ | Est. Build Time: 2 days Category: scheduling, team-tools | Target: Small shift-based teams (retail, food service, healthcare, logistics)
🚀 Elevator Pitch
ShiftSwap is a dead-simple shift trade board for small teams. When a worker needs to swap, drop, or pick up a shift, they post it to a shared board — teammates browse open swaps and claim them with one click. No group texts, no clipboard sign-up sheets, no-manager-approval-if-manager-opts-in. The manager sees pending swaps on a dashboard and can approve or deny in one tap.
😤 Problem
Shift-based workers — retail associates, baristas, nurses' aides, warehouse pickers — swap shifts constantly. Life happens: dentist appointments, kid sick days, car trouble, double-booked. The current process is broken:
-
Group-text chaos. A worker texts the team group chat: "Anyone want my Thursday 2–10?" Messages get buried. Someone replies 3 days later. The worker isn't sure the swap is confirmed. The manager doesn't know it happened.
-
No visibility. Managers find out about unauthorized swaps after the fact (or never). Compliance and labor rules get violated quietly — overtime, rest-period violations, underage-hours conflicts.
-
Clipboard / paper sheets. Many small businesses still use a physical clipboard in the break room. Shifts get crossed out, initials are illegible, and remote workers can't participate.
-
Overkill solutions. Existing tools (When I Work, Deputy, Homebase) are full workforce management suites ($20–80/mo per location) with time clocks, payroll integrations, and complex permission trees. A 5-person coffee shop doesn't need that — they need a bulletin board.
Market signal: When I Work (acquired by Salesforce for $1.5B) started as a simple shift-swap tool. The demand is proven at every scale.
✅ Solution
A minimal, single-tenant shift-swap board:
- Post a Swap — worker selects their shift from the weekly schedule, marks it as "open for swap" with an optional note ("need morning shift in return"), and posts it to the board.
- Browse & Claim — teammates see a feed of open swaps (shift date, time, role, poster's name, note). One click to claim; poster confirms the match.
- Manager Dashboard — pending and completed swaps visible in a simple list. Manager can approve, deny, or set auto-approve mode. Optional: conflict warnings (overtime, rest-period).
- Weekly Schedule View — read-only weekly grid showing who's assigned to each shift, including confirmed swaps highlighted in a different color.
- Simple Auth — team invite code or single shared password. No per-user OAuth flows.
🎯 Target Users
- Shift managers at small retail shops, cafes, restaurants, clinics, and warehouses (5–30 employees).
- Shift workers who need a fast way to trade hours without bugging their manager.
🛠️ Suggested Tech Stack
- Next.js 15 (App Router) + React 19 + TypeScript — standard repo stack.
- PostgreSQL (Drizzle ORM) — single-tenant DB for shifts, users, and swap records.
- Tailwind CSS v4 + shadcn/ui — clean, minimal UI.
- Auth: NextAuth.js with credentials provider (shared team password + individual PIN).
- No external APIs, no webhooks, no billing.
🧩 Feasibility Gut-Check (2–3 Days)
| Component | Est. Hours | Notes |
|---|---|---|
| DB schema + seed data | 2h | Users, shifts, swaps tables; seed a week of sample shifts |
| Auth (team invite code + PIN) | 3h | Credentials provider, role column (worker/manager) |
| Shift schedule view (weekly grid) | 4h | Read-only grid; highlight swap-pending shifts |
| Post a swap flow | 2h | Select shift → post to board |
| Browse & claim + confirm flow | 3h | Feed of open swaps, claim, poster confirms |
| Manager dashboard | 3h | Approve/deny list, optional conflict warning |
| Seed script + docs | 2h | Realistic mock data, HOW_TO_USE.md, AGENTS.md |
| Total | ~19h | Within 24h budget |
Risk factors: None significant. Pure CRUD with a clean data model. No third-party integrations, no real-time requirements, no media processing.
📊 Brainstormer Score
| Metric | Score | Rationale |
|---|---|---|
| Feasibility | 5/5 | Pure CRUD, ~19h estimate, standard repo stack, no third-party integrations, simple credentials auth. |
| Market Fit | 4/5 | Strong demand signal (When I Work → $1.5B exit), clear wedge vs overkill incumbents ($20-80/mo suites), well-defined target users (small shift-based teams). Group texts/clipboards are "free" but broken. |
| Complexity | 4/5 | 5 clean CRUD features, no real-time/billing/webhooks/OAuth. Weekly schedule grid + swap highlighting + optional conflict warnings add moderate UI depth but nothing exotic. |
| Total | 13/15 | PROMOTED to 🎨 Ready for Design. |
🔗 Related ideas
(None — unique job-to-be-done in this portfolio.)
Architecture Design Spec
Status: ✅ Design Complete — Ready for implementation. Architecture document:
designs/089-ShiftSwap-architecture.mdC4 Container diagram:diagrams/shiftswap-architecture.htmlDesigned by: System Architect | Date: 2026-08-14