ShiftText — The SMS-Native Rota Manager for Hourly Teams Whose Staff Will Never Download Another App
Your kitchen staff will not download Homebase, will not check the scheduling portal, and will definitely not log into anything with a password. ShiftText manages your entire weekly rota over SMS — managers text in schedule changes, staff get shift reminders and can swap via reply, and nothing requires a smartphone app. If they can text, they are on the schedule.
Difficulty
intermediate
Category
Business Automation
Market Demand
High
Revenue Score
7/10
Platform
Web App
Vibe Code Friendly
No
Hackathon Score
6/10
What is it?
Independent restaurant owners and retail managers consistently report that scheduling apps fail because hourly staff — especially kitchen workers, cleaners, and warehouse staff — refuse to download or log into apps. The entire scheduling software market has built for desk workers and ignored the majority of the hourly workforce. ShiftText uses Twilio to make the entire scheduling workflow happen over SMS: managers send a CSV or fill a simple web form, Twilio broadcasts personalized shift notifications to each staff member, confirmations and swap requests come back as SMS replies, and the manager sees a live web dashboard. The web UI is only for managers — staff never touch it. Precedent in ShiftBoard and When I Work proves the market, but both require app downloads and Wi-Fi. Twilio SMS is stable, cheap at scale, and requires no smartphone capability beyond basic texting.
Why now?
Twilio's pricing has dropped to $0.0079/SMS in mid-2026, making bundled SMS scheduling economically viable at $79/month, and the post-pandemic hourly workforce retention crisis has made scheduling tools a top expense priority for independent restaurant owners.
- ▸CSV or web form schedule upload that triggers personalized SMS to each staff member with their shift details
- ▸Two-way SMS reply handling: staff can confirm, request swap, or report sick via text reply keyword
- ▸Manager web dashboard showing real-time confirmation status per shift with one-click swap approval
- ▸Automated shift reminder SMS sent 2 hours and 24 hours before each shift with no manager action required
Target Audience
Independent restaurant owners, retail store managers, and cleaning company operators managing 5-30 hourly staff — estimated 500,000+ in the US who have failed with app-based scheduling tools.
Example Use Case
Carlos manages a 12-person kitchen crew, uploads next week's rota as a CSV on Sunday night, ShiftText texts each staff member their shift in Spanish and English, three people reply to confirm, one requests a swap, and Carlos approves the swap via the dashboard — total time: four minutes.
User Stories
- ▸As a restaurant manager, I want to upload a CSV schedule and have staff automatically texted their shifts, so that I spend four minutes on scheduling instead of forty.
- ▸As a kitchen staff member, I want to reply CONFIRM or SWAP to a text message, so that I can manage my shifts without downloading any app.
- ▸As a cleaning company owner, I want to see which staff have confirmed their shifts in real time, so that I can fill gaps 24 hours before they become no-shows.
Done When
- ✓Schedule blast: done when manager uploads a CSV and all staff phone numbers receive personalized SMS within 60 seconds.
- ✓Reply handling: done when staff member texts CONFIRM and their shift card on the manager dashboard immediately changes to a green confirmed badge.
- ✓Reminder cron: done when a shift scheduled 25 hours from now triggers an automated reminder SMS to the staff member at the 24-hour mark without any manager action.
- ✓Billing: done when Stripe processes payment and manager can create unlimited rota weeks without hitting a trial gate.
Is it worth building?
$79/month x 50 customers = $3,950 MRR at month 4. $79/month x 200 customers = $15,800 MRR at month 9. Math assumes local Facebook group outreach converting at 4% and referral from restaurant supply communities.
Unit Economics
CAC: $15 via local Facebook group outreach and setup call. LTV: $948 (12 months at $79/month). Payback: month 1. Gross margin: 85% after Twilio costs.
Business Model
SaaS subscription
Monetization Path
$79/month per location, flat fee up to 30 staff. $149/month for multi-location. SMS costs bundled into pricing at Twilio wholesale rates.
Revenue Timeline
First dollar: week 2 via local Facebook group beta. $1k MRR: month 3 (13 locations). $5k MRR: month 7. $10k MRR: month 12.
Estimated Monthly Cost
Twilio SMS: $50 at 20 customer locations (6,000 messages), Vercel: $20, Supabase: $25, Stripe fees: ~$30. Total: ~$125/month.
Profit Potential
Full-time viable at $8k-$15k MRR targeting a specific local restaurant cluster in one city first.
Scalability
High — multi-location, WhatsApp fallback via Twilio, payroll export integration, and a white-label tier for staffing agencies.
Success Metrics
Week 1: 5 restaurant managers in beta via local Facebook groups. Month 2: 20 paying locations. Month 4: 80% 60-day retention.
Launch & Validation Plan
Post in three local restaurant owner Facebook groups offering free setup for anyone willing to try — five yes replies in 24 hours validates before building.
Customer Acquisition Strategy
First customer: post in local city restaurant owner Facebook group offering free 60-day trial for first three restaurants to sign up, then get on a 20-minute call to set up their first rota personally. Ongoing: referral program ($20 credit per referred location), restaurant supply company partnerships, r/KitchenConfidential, and local business association outreach.
What's the competition?
Competition Level
Medium
Similar Products
Homebase requires app download and is free-tier dependent. When I Work requires smartphone app for staff. 7shifts targets mid-market restaurants with $30+/month per location. Gap: zero-app SMS-native scheduling for the 5-30 staff segment whose workers do not use smartphones for work apps.
Competitive Advantage
Zero app download required for staff, bilingual SMS support (English and Spanish), and pricing that bundles SMS costs unlike competitors who charge per message on top of a subscription.
Regulatory Risks
TCPA compliance required in the US — all staff must opt-in to receive SMS messages before being added to the system. Opt-in consent logging must be stored in Supabase per staff member. GDPR for EU expansion.
What's the roadmap?
Feature Roadmap
V1 (launch): CSV upload, SMS blast, reply handling, reminder cron, manager dashboard. V2 (month 2-3): WhatsApp fallback, Spanish/English bilingual toggle, swap request approval workflow. V3 (month 4+): payroll CSV export, multi-location dashboard, staffing agency white-label.
Milestone Plan
Phase 1 (Week 1-2): Twilio integration, CSV parser, SMS blast, inbound webhook ships. Phase 2 (Week 3): reminder cron, dashboard UI, Stripe billing live. Phase 3 (Month 2): 10 paying restaurant locations, TCPA consent audit complete.
How do you build it?
Tech Stack
Next.js, Supabase, Twilio SMS API, Stripe — build with Cursor for Twilio webhook logic, v0 for manager dashboard UI
Suggested Frameworks
Next.js App Router, Twilio Node SDK, Supabase
Time to Ship
2 weeks
Required Skills
Twilio webhooks and two-way SMS, Next.js, Supabase, CSV parsing.
Resources
Twilio Messaging API docs, Twilio webhook guide, Next.js App Router, Supabase quickstart.
MVP Scope
app/page.tsx (landing + signup), app/dashboard/page.tsx (schedule grid + confirmation status), app/api/schedule/route.ts (CSV parse + SMS blast via Twilio), app/api/sms-webhook/route.ts (inbound reply handler), app/api/reminder/route.ts (cron-triggered reminder blasts), lib/db/schema.ts (locations, staff, shifts, confirmations), components/ShiftGrid.tsx (weekly rota UI), components/StaffStatus.tsx (confirmation tracker), seed.ts (demo restaurant with 8 staff), .env.example
Core User Journey
Sign up -> add staff phone numbers -> upload CSV rota -> staff get SMS -> confirmations appear on dashboard -> renew.
Architecture Pattern
Manager uploads CSV -> Supabase stores shifts -> Twilio SMS API blasts personalized messages -> staff replies hit Twilio webhook -> inbound handler updates confirmation status in Supabase -> Supabase cron triggers reminder blasts 24h and 2h before each shift -> dashboard reflects live status.
Data Model
Location has many Staff. Staff has many Shifts. Shift has one Confirmation (status: pending/confirmed/swap_requested). Location has one TwilioPhoneNumber.
Integration Points
Twilio SMS API for outbound and inbound SMS, Supabase for database and auth, Vercel Cron for reminder scheduling, Stripe for billing, Resend for manager account emails.
V1 Scope Boundaries
V1 excludes: WhatsApp channel, payroll export, mobile app for managers, multi-language beyond English and Spanish, time clock or attendance tracking.
Success Definition
A paying restaurant manager uploads a rota, all staff receive SMS confirmations, one swap is approved via dashboard, and the manager renews after month one having never contacted support.
Challenges
Twilio SMS costs must be built into pricing carefully — at 30 staff getting 4 messages per week, that is 480 messages per month per customer at $0.0079 each, adding $3.79/month per customer which is easily absorbed into $79/month pricing.
Avoid These Pitfalls
TCPA opt-in is non-negotiable in the US — build the staff consent collection flow before anything else or you risk legal liability. Do not build multi-location support before validating single-location retention. Finding first 10 paying customers via local outreach will take 2-3 weeks of personal DMs — do not wait for inbound.
Security Requirements
Supabase Auth with email magic link. RLS on all location and staff tables. TCPA consent timestamp stored immutably per staff member. Twilio webhook signature validation on inbound endpoint. Rate limiting 30 req/min per location.
Infrastructure Plan
Vercel for Next.js and cron jobs, Supabase for Postgres and auth, Twilio for SMS, Sentry for errors, GitHub Actions for CI. Total infra $125/month at launch.
Performance Targets
50 DAU managers at launch, 500 req/day plus Twilio webhook volume. SMS blast for 30 staff under 10s. Dashboard load under 1s. Cron reminder accuracy within 5 minutes of scheduled time.
Go-Live Checklist
- ☐TCPA opt-in flow tested and consent stored correctly.
- ☐Twilio webhook signature validation active.
- ☐Stripe billing tested end-to-end with real card.
- ☐Sentry error tracking live.
- ☐Custom domain with SSL live.
- ☐Privacy policy with TCPA disclosure published.
- ☐3 restaurant managers completed full rota cycle in beta.
- ☐Rollback: revert Vercel deployment.
- ☐Local Facebook group and r/KitchenConfidential launch posts drafted.
First Run Experience
On first run: app shows a pre-seeded demo restaurant called 'Harbor Grill' with 8 staff members and a sample weekly rota. User can immediately click 'Send Demo SMS' to see what a shift notification looks like (sends to a Twilio test number). No manual config required: demo mode uses Twilio test credentials pre-configured in the demo environment.
How to build it, step by step
1. Define Supabase schema for locations, staff (with TCPA consent field), shifts, confirmations tables with RLS. 2. Run npx create-next-app with TypeScript and Tailwind. 3. Build staff onboarding flow with mandatory SMS opt-in consent checkbox and timestamp stored in Supabase. 4. Build CSV upload and parser that maps columns to shifts and validates required fields. 5. Build Twilio outbound SMS route that sends personalized shift details to each staff member. 6. Build Twilio inbound webhook handler that parses CONFIRM, SWAP, and SICK keyword replies and updates confirmation status. 7. Build ShiftGrid dashboard component showing weekly rota with live confirmation badges per staff member. 8. Build Vercel Cron job that queries upcoming shifts and fires reminder SMS at 24h and 2h intervals. 9. Add Stripe billing with $79/month plan gating schedule creation beyond one test week. 10. Deploy to Vercel, verify full flow: add staff, upload CSV, receive test SMS on real phone, reply CONFIRM, see dashboard update, process Stripe payment.
Generated
June 7, 2026
Model
claude-sonnet-4-6
Disclaimer: Ideas on this site are AI-generated and may contain inaccuracies. Revenue estimates, market demand figures, and financial projections are illustrative assumptions only — not financial advice. Do your own research before making any business or investment decisions. Technology availability, pricing, and market conditions change rapidly; always verify details independently.