OneClick was started by James Finlinson after he watched a Director drown in paperwork. Eight years later, the team is still mostly operators and Leaders who have run the shift.
James was a Team Member at a stand-alone Chick-fil-A® store in Ammon, Idaho. His Operator was good at the job (great at it, actually). She spent every Sunday afternoon writing the next week's operating plan on a whiteboard, the way every CFA store had always done it. Then re-writing it when someone called out. Then explaining it to each Leader. Every week.
James wrote a small app to fix the worst of that workflow. His Operator started using it. Then the Operator next door asked for it. Then James started building features the next-door Operator asked for.
Eight years later, OneClick runs in roughly one in five stand-alone CFA stores nationwide. The team is in Lehi, the customer support is in Lehi, and the engineers are mostly people who have run the shift.
1. We will not build for restaurants. We build for Chick-fil-A® Operators specifically. The product is shaped by the way CFA stores run: three-layer leadership, the daily operating cadence, and the CFA training framework. Trying to be "for restaurants generally" would dilute everything that makes the product work.
2. We will not chase enterprise feature requests. If a CFA Operator asks for something we have not built, we move fast. If a non-CFA enterprise customer asks for the same thing, we listen and decide later. The Operator's roadmap wins.
3. We will not hide pricing. The pricing page lists what each tier costs. The 30-day pilot is the same for everyone. The Operator P&L conversation is hard enough; we are not going to make it harder.
The leadership team includes people who have run the shift and one ex-Director who runs Customer Success. The product team meets with three Operators every week to test features against real shifts. Most internal hires come from the customer base.
A 20-minute demo run by the OneClick team.