Waiting shouldn't be the hard part
Queued replaces the clipboard by the door with something your clients can actually see.
The problem we started with
Almost every walk-in shop runs the same way. There's a sheet of paper by the door, a row of chairs, and a room full of people quietly doing math about how long they've been sitting there. Nobody knows if it's twenty minutes or an hour and a half.
That uncertainty costs the shop real money. A client walks in, sees six people ahead of them, and leaves — not because they didn't want the cut, but because they couldn't plan around an unknown. The shop never even knows it happened.
What we built instead
A client scans the code on your door and joins the line from their phone. No app to download, no account to make. They see their position and an honest wait estimate, and both update on their screen as the line moves.
That means they can wait in the car, run to the store, or grab lunch and still keep their place. When it's their turn, their screen tells them. On your side, you tap one button to pull the next person into your chair.
The whole goal is narrow and specific: the client should never have to ask “how much longer?”, and you should never have to guess at an answer.
Who builds it
I'm Johnathon Brumfield, a computer science graduate from the University of Missouri. I build software that solves problems people actually run into, and I care a lot more about whether a thing works on a busy Saturday than whether it demos well.
Queued is built and maintained by one person, which has one real advantage for you: when something is broken or missing, you can tell me directly and I'm the one who fixes it. If you run a shop and something here doesn't fit how you actually work, I want to hear about it.