# Darnell Pryce, Operations Manager at Gravel & Salt Hospitality — read of Roster, May 13 2026

> 11 years in restaurant ops, currently managing three locations (two bars, one fast-casual) in the Denver metro. 58 employees on payroll, none of them with consistent availability.

## How I got here

Googled "restaurant scheduling software that doesn't suck" at 9:40 PM on a Sunday after spending two hours redoing the Colfax location's schedule because someone updated their availability *after* I had already posted the draft. Homebase came up first. I've used Homebase. I cancelled Homebase. Roster was the third result. I clicked it because the meta description said "15 minutes" and I was desperate enough to give it 90 seconds.

## What I clicked first

The hero. "Stop losing Sunday nights to the weekly schedule." That sentence is doing real work. That's not "optimize your workflow." That's just true. Sunday nights are where scheduling goes to die for me. I kept reading.

Then I saw "1,400+ shift managers already cut schedule time by 85%" and the number is oddly specific enough that I didn't immediately bounce. Round numbers feel made up. 1,400 feels like someone actually counted.

## Where I paused

The compliance section. Specifically: "The average shift manager spends 4.6 hours per week building the schedule and still fields nine texts before it goes live." The 4.6 hours tracks for me. But then the testimonial from Priya at Volta Retail saying "I had no idea Oregon required 14-day advance notice." That stopped me. I manage a location in Colorado and I genuinely do not know if Denver has predictive scheduling rules that I'm currently violating. If that's real, it's the scariest thing on this page.

## What I distrusted

"$0 Compliance penalties paid by Roster customers in the last 12 months." This sounds like a guarantee but it isn't one. Either none of their customers got audited, or their compliance engine is actually bulletproof, or they just haven't been around long enough for anyone to find out. I don't know which one it is, and the page doesn't say.

Also the testimonials. Marcus T., Priya N., Jordan K. Last initials only. "Coast Kitchen (38 seats)" is specific enough that I'd try to Google it, but I didn't, so I'm just sitting with low-grade suspicion. Real operators usually have real last names.

The brand logos under "Trusted by operations teams" are text, not actual logos. Coast Kitchen, Urban Fade Barbershop, Bright Paws Grooming. Those are either real small businesses or GPT-generated company names. I honestly can't tell.

## What would convince me

A real compliance answer for Colorado specifically. Not "all 50 states for federal FLSA rules" - I need to know: does Denver have a predictive scheduling ordinance and does Roster know about it? A founder doing a five-minute Loom walking through the compliance setup for one state would do more than three pages of feature copy.

Also: what actually happens when a shift-swap goes wrong? The page says "The first person to accept locks the shift. You get a confirmation message, not a problem to solve at 6 AM." What if two people accept at the same moment? What if nobody accepts? What's the fallback? The hero scenario is covered. The failure scenario isn't mentioned anywhere.

A screenshot of the actual schedule view would help too. I'm buying software, not a promise. Show me the grid.

## What I'd ask in an email reply

1. Denver specifically: does the compliance engine cover any city-level ordinances, or is Colorado just federal FLSA? I need a straight yes or no, not a roadmap answer.

2. What happens to the shift-swap flow when nobody accepts within, say, two hours of the shift? Does it escalate to me, and how? Walk me through that failure path.

3. You mention "learns your preferences and improves each week automatically." What does that actually mean mechanically? Is it remembering who I tend to pair together, or is it just re-running the same algorithm with my saved settings?

## Verdict: curious-enough-to-reply

The Sunday night framing is earned, not manufactured, and the compliance angle scared me just enough that I need to find out if I'm currently exposed. I'm not buying today. But I'd send the email.

---
*Memo by skeptic persona, generated 2026-05-13. Studio breaks own self-grading loop.*