ShiftShield — wage-compliance copilot for US restaurant groups

1. One-liner

Catches tip-credit and wage-law violations before DOL or a class-action lawyer does — for 3-25 location US restaurant groups.

2. Trend signal — why now?

Three hard things happened in the last 12 months, and they stack.

One. US restaurant wage-theft enforcement is cresting. BHG (a Lexington restaurant group of 7 concepts) settled for $9M in March 2025. DC AG won a $1.75M judgment against a District restaurant. NY AG extracted $1.5M from RHR (Taco Bell + Dunkin’ franchisee) in March 2026. Seattle’s Canlis paid $1.45M. These are not faceless chains — these are exactly the 5-25 location groups that make up the independent restaurant market.

Two. The legal landscape keeps shifting. Chicago’s City Council voted March 18, 2026 to keep the tipped-wage credit at 24% — a mid-year configuration change that requires every Chicago restaurant payroll to reconfigure on a non-standard date. New York has region-specific minimum wages that vary by NYC / Long Island+Westchester / rest-of-state, by employer size, and by worker category — a single restaurant group can owe three different cash wages. FLSA’s 80/20 rule (tipped employees can spend ≤20% of time on non-tipped sidework) was re-litigated in 2024 and is still a live plaintiffs’ cause of action.

Three. The SMB tooling gap is real. Gusto, Homebase, Toast Payroll, Paylocity — all process payroll. None of them are audit-posture tools. “You ran payroll through us” is not a legal defense. The defense an operator needs is a documented, per-shift audit trail that proves the tip-credit math was correct, the sidework ratio stayed under 20%, and the applicable state/city/ZIP rule was applied — every single shift. Nobody serves 3-25 location groups with that posture at SMB prices. Restaurant365 touches it, but bundled into a $400+/mo accounting platform.

Provenance:

• Signal 1 (demand + urgency): “Restaurants say they’re bearing the brunt of delivery chargebacks” + BHG $9M + RHR $1.5M + DC $1.75M wage-theft settlements cluster — https://www.restaurantbusinessonline.com/workforce/canlis-agrees-pay-145m-settle-wage-theft-lawsuit — 2025-2026
• Signal 2 (regulatory shift + urgency): Chicago tip-credit vote March 18, 2026; NY region-specific minimum-wage complexity — https://www.symmetry.com/payroll-tax-insights/tip-credit-laws-by-state-2026-guide — 2026-01
• Signal 3 (feasibility + economic): US DOL data + LLM cost collapse make a structured rule engine + per-shift audit viable for a 2-3 person team; enterprise GRC (Vanta, Drata) absent from restaurant wage compliance — https://www.dol.gov/agencies/whd/state/minimum-wage/tipped — 2026 Category: Regulatory arbitrage

3. The opportunity

Restaurant-group owners live with a low-grade daily fear: one server-turned-plaintiff with a good attorney can kick off a class action that wipes out a year of profit. Existing payroll software runs the math you give it. It does not challenge the math. It does not say “your GM in Queens clocked five servers out late on three consecutive Fridays and the tip-credit no longer applies for those shifts — here’s your $18,000 exposure.”

That second layer — the audit posture — is the product. It plugs into Toast / 7shifts / Gusto / Homebase / Paylocity, ingests shifts + timeclock + tip declarations + the menu of tasks, and runs an LLM-backed rule engine across a structured taxonomy of federal + 50 state + ~150 city/county wage rules. Output: a weekly posture score, a per-shift flag list in plain English, dollar-denominated exposure, and an export-ready audit pack the operator can hand a labor attorney or DOL investigator.

Incumbents miss this because (a) payroll processors don’t want to give legal opinions, (b) enterprise HRIS targets Workday-budget customers, (c) labor lawyers sell hours not software, (d) Restaurant365 bundles it into a finance suite too broad for a 4-location operator.

4. Target market

• Primary customer: Owner/operator or multi-unit director of a 3-25 location US restaurant group. Most acute in multi-jurisdiction regions: NY metro, Chicago metro, Bay Area, DC metro, Boston metro. Concepts range from full-service groups (steakhouses, trattorias, pubs) to fast-casual multi-brands.
• Why they buy: “We got a nastygram from a former server’s attorney. Our lawyer quoted me $450/hour to audit the last 2 years. We don’t know if we’re compliant. The payroll software shows us what we paid, not whether it was right.”
• Rough TAM reasoning: US has ~30,000 multi-unit independent restaurant groups with 2-25 locations (NRA + IRS business data). Even narrowing to 3-25 locations in the top 10 metro areas = ~8,000 groups. At $300/mo/location avg × 6 locations avg × 1% penetration = ~$1.7M ARR; 5% penetration = $8.6M ARR. Well inside the bootstrap target zone.
• Why now for them: Every headline settlement makes the phone ring at the operator’s attorney’s office the next morning. Insurance premiums are rising. The Chicago mid-year rate change is the most recent “you didn’t know about this, now you owe.” The cost of getting sued is 30-100× the cost of the tool.

5. Product sketch (MVP)

• One-click integrations with Toast, 7shifts, Homebase, Gusto, Paylocity — ingest shifts, timeclock, tip declarations, pay rates, job codes.
• Per-shift compliance check — for each shift, apply federal + state + city + ZIP rule stack: minimum wage, tip-credit eligibility, overtime multiplier, FLSA 80/20 sidework ratio, meal/rest break rules where applicable.
• Weekly posture dashboard — a single score (0-100) + dollar-denominated exposure + top 5 risks ranked. The operator sees in 30 seconds what a lawyer would charge $4,500 to explain.
• Real-time flag feed — end-of-shift push when a manager just clocked someone in a way that created exposure (“Jenna worked 35% sidework hours tonight — tip-credit no longer applies for this shift, $127 make-up owed”).
• Audit-ready evidence pack — on demand, export a PDF + CSV that a labor attorney or DOL investigator would accept: every shift, the applied rule, the math, the decision.
• State/city rule library — curated + versioned. When Chicago changes 24% mid-year, every customer’s rules auto-update; each customer gets a one-click “acknowledge update” record.
• Manager coaching nudges — a short weekly “here’s what your Chicago GM needs to know this week” note, customized to the rules affecting their shifts.

6. AI angle — what’s load-bearing

AI is load-bearing in three specific places, none of them decorative.

• Rule interpretation — state and city wage rules are written in legalese. An LLM ingests a new city ordinance, converts it into a structured rule (applies-when, thresholds, cash-wage floor, tip-credit %, exceptions) with a human-in-the-loop review from a domain advisor. Without LLMs, this is a full-time legal-research job; with them, it’s an hour of review per new jurisdiction.
• Job-code classification — every POS calls things differently. “Prep,” “side-station,” “expo,” “busser.” The 80/20 sidework rule hinges on whether a task is tipped or non-tipped. An LLM classifies each job code + shift note + tip-declared signal into tipped/non-tipped with confidence scores and escalates the ambiguous ones.
• Plain-English translation — “Your GM in Queens clocked Jenna 7:05 PM and she declared $42 in tips — that combined with her $12.75 cash wage puts her under NY’s $16.50 NYC tipped floor by $0.43/hr for 4.2 hours — $12.04 exposure.” Generating these from structured events at scale, per shift, in the operator’s actual language, is what makes the product feel like a lawyer-in-the-pocket rather than a spreadsheet.

Strip the AI out and you have a rigid rules engine that needs a legal team. The AI layer is what lets 2-3 people scale this without becoming a law firm.

7. Localization angle (if any)

N/A — this is a US-first play. The wage/tip-credit complexity is uniquely American (no tip-credit in most of Europe, different labor-code structure globally). A future v2 could address UK (different tipping-and-service-charge law, 2024 Tipping Act) or Australia (award-based wages) but the go-to-market is US multi-location operators.

8. Business model — path to $1M–$5M ARR

• Pricing: $149/mo/location Core (<10 employees) · $249/mo/location Pro (full audit pack + multi-state rule coverage + API access) · $499/mo/location Enterprise (priority DOL-response support + custom rule work). Typical customer has 5 locations.
• ACV: ~$15K blended across segments.
• Rough math to $1M ARR: 67 customers × 5 locations × $250/mo × 12 = $1.0M. Achievable in 12-18 months.
• Rough math to $5M ARR: 335 customers × same mix, OR 200 + 20 enterprise groups with 15+ locations. Requires ~2-4% penetration of the 8,000-group ICP.
• Expansion path: (a) add adjacent wage-hour concerns (meal/rest breaks, predictive scheduling ordinances like Seattle/NYC Fair Workweek), (b) pivot into hospitality beyond restaurants (hotels, catering), (c) offer “compliance as insurance” bundling with an EPLI carrier — real unlock at $5M+.

9. Go-to-market wedge — first 100 customers

Specifics beat “content marketing.”

1. Direct outbound to restaurant-group owners in NYC, Chicago, SF, Boston, DC. Scrape state LLC filings + OpenCorporates + state ABC licenses to build a list of ~5,000 multi-unit operators. Cold-email the owner with a free “tip-credit exposure snapshot” — upload one week of payroll CSV, get back a 2-page risk summary. 2% conversion → 100 trials. ~25 paying customers.
2. Partner with labor & employment attorneys who represent restaurants (defense side, not plaintiff). Give them a white-label version of the audit tool to recommend to clients. Rev-share 30% year one. Target 15 partnerships in top metros. Each attorney brings 3-8 clients. ~60 customers.
3. Sponsor the NRA Show + state restaurant-association newsletters (NYS Restaurant Association, Illinois Restaurant Assn, CA Restaurant Assn). These are buyer concentration zones. A $5K newsletter sponsorship + $15K NRA booth presence = measurable, named conversion. ~15 customers.
4. Create and promote a free “Wage-Law Radar” by state on the site — when Chicago changes, customers in Chicago get emailed. SEO + direct engagement. Target: 200 newsletter sign-ups/mo, 5-10% → paid trial over 6 months.
5. Product Hunt launch pointed at restaurant operators + cold-DM operators who recently commented on wage-theft articles in Restaurant Business, Eater, or Food & Wine. Lower-yield, but qualified. ~5 customers.

If steps 1+2 don’t hit 40 customers combined in 90 days, rethink pricing or channel. Kill criterion.

10. Build complexity — justification

Medium. Tech is standard (Next.js + Postgres + LLM + Stripe + integration SDKs). The hard parts are (a) curating and versioning the rule library across federal + ~15 priority states + ~30 cities/counties, (b) building integration connectors to 5-6 payroll/POS platforms (each has quirks; Toast API is well-documented, Paylocity less so), (c) a domain advisor — either a restaurant-experienced labor attorney as co-founder or on retainer. A two-person team can ship v1 covering NY + CA + IL + MA + DC + federal in 14-18 weeks. Full 50-state coverage is a 2-year roadmap.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	We’re a compliance tool, not practicing law. Clear disclaimer; optional attorney-review upgrade.
Ethical — no harm / dark patterns	✅	Product protects workers’ wages as a byproduct — compliance tool aligned with wage-theft laws’ intent.
Market exists (evidence above)	✅	Multiple named $1M+ settlements; 30,000+ multi-unit operator TAM.
1–5 person team can build this	✅	Medium complexity, standard stack, rule library is the crux.
Launchable with <$50K / ₹40L	✅	~$30K for 14-18 week build + $10K/yr attorney retainer.

All pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	17/20	Hair-on-fire — operators genuinely fear the lawsuit. Downstream of every wage-theft headline.
Demand evidence	15	11/15	Multiple 7-figure settlements + aggressive AG enforcement + regulatory changes. No direct “would you buy this” survey yet — hence Medium confidence.
Build feasibility	15	10/15	Rule library is real work. Integrations are gated on partner API responsiveness. 14-18 weeks, not 6.
Distribution clarity	15	11/15	Attorney-channel is named and concrete. State-association channel is proven. Direct outbound list is buildable.
Revenue mechanics	15	13/15	Benchmarked pricing against Restaurant365. ACV realistic. Per-location billing scales with customer.
Time to first revenue	10	7/10	60-90 days to first paid pilot. Not self-serve checkout; some sales work required.
Defensibility	10	7/10	Rule library + attorney-channel relationships + evidence-pack format become a soft moat in 12-18 months. Incumbents can copy, but rule-library maintenance is a grind most won’t sustain.
Total	100	76/100

76 = solid GO. Held back from STRONG GO by (a) slower time-to-revenue than a self-serve SaaS, (b) domain-expertise dependency, (c) a rule library that becomes real work at scale. Honest score reflects that.

13. Qualitative modifiers

Founder-fit tags

technical-heavy · domain-expertise-required — ideal founding team is one strong full-stack engineer + one ex-restaurant COO or restaurant-specialty labor attorney. Pure tech founders without a domain partner will ship a pretty tool that misses the real edge cases (80/20 rule, service-charge-vs-tip distinction, Fair Workweek overlap).

Key assumptions to validate (3–5)

1. Assumption: 3-25 location restaurant groups will pay $149-250/mo/location for compliance audit on top of existing payroll. How to test: 25 phone interviews with multi-unit operators. Target: 40%+ “yes, would pay $200/location/month today if it worked.”
2. Assumption: The attorney-referral channel converts at 30-50% on warm intros. How to test: Sign 3 defense-side labor attorneys in NYC, Chicago, SF to a 6-month pilot. Measure referrals → paid conversion.
3. Assumption: LLMs can classify POS job codes into tipped/non-tipped with >90% accuracy. How to test: Ingest Toast job-code dumps from 10 friendly restaurants; hand-label ground truth; measure.
4. Assumption: Restaurant-group owners are willing to share payroll data with a 3rd-party SaaS. How to test: 10 free “risk snapshot” offers → % who actually upload.
5. Assumption: Operators prefer “audit posture” product over “automated compliance insurance” bundling. How to test: Split A/B on landing-page copy; measure lead quality.

Risk flags

1. Liability exposure: If we say “you’re compliant” and they get sued, we’re in the crosshairs. Mitigation: clear “we are not legal advice” disclaimer, optional attorney-review upsell, carry E&O insurance.
2. Platform/API dependency: Toast, 7shifts, Gusto API changes can break integrations overnight. Mitigation: diversify across 5-6 integrations + CSV upload fallback.
3. Rule library decay: 50 states × ~3-5 rule changes/yr = unending maintenance. Mitigation: use LLM + domain advisor workflow; charge Enterprise customers for priority rule updates to fund maintenance.
4. Incumbent capture: Toast, 7shifts, or Gusto could ship this as a native module. Mitigation: first-mover + attorney-channel relationships + multi-platform integration (incumbents only cover their own data).
5. Market softness: Restaurant failures are up; smaller operators cut discretionary SaaS first. Mitigation: position as insurance, not optional; anchor pricing against attorney-hour cost.

14. Structured verdict

Score:                  76/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder + restaurant-specialty labor attorney or ex-COO
Time to revenue:        10–14 weeks (first paid pilot); self-serve by month 6
Capital to launch:      $30-40K (build + attorney retainer + initial outbound + E&O insurance)
Top 3 assumptions to validate first:
  1. Willingness-to-pay at $149-250/mo/location — 25 operator interviews
  2. Attorney-referral channel — 3 pilot partners, 6 months, measure conversion
  3. Job-code classification accuracy — ingest 10 real Toast dumps, hand-label, measure
Kill criteria:
  - Abandon if <30% of 25 operator interviews express willingness to pay
  - Abandon if <5 paid customers after 90 days of active outbound
  - Abandon if Toast, Gusto, or 7shifts launches a native wage-compliance module before v1 ships
  - Abandon if rule-library maintenance exceeds 40% of engineering time at 100 customers

15. Next step — 1-week validation sprint

• Day 1–2: Build a landing page positioning “ShiftShield — see your wage-compliance exposure in 10 minutes.” CTA: upload a payroll CSV for a free risk snapshot. Drive 20-40 restaurant-group LinkedIn + cold emails to it.
• Day 3: Call 8 defense-side labor attorneys in NYC, Chicago, SF who represent restaurants. Ask: “Would you recommend a tool that shows your clients their wage-compliance posture? What would make it credible to you?”
• Day 4: Interview 5 operators from the landing-page signups. Ask pricing + which integrations they actually use + how they currently assess compliance risk.
• Day 5: Sum up — would >30% of operators commit at $200/loc/mo and >1 attorney agree to a pilot? If yes, go. If no, hand back to the pipeline.