On the desk at Jordan Boesch's family restaurant sat the operating system for a small chain: sticky notes. Employees scribbled their availability. A manager collected the scraps, opened last week's Excel file, erased the shifts and started again. Then came the calls, the swaps and the sick day that undid the whole puzzle. Boesch, working in his father's quick-service restaurants in Saskatchewan, taught himself to code and made a basic tool that let a manager upload a schedule for staff to download. It was not a grand theory of work. It was an answer to a messy desk.
That modest fix became 7shifts, founded as a business in 2014 and now used by more than 55,000 restaurants and 1.5 million workers across North America. The software handles scheduling, availability, time clocks, communication, compliance, tips, onboarding and payroll. Its customers range from independent coffee shops to franchise groups and national brands. Yet the most useful part of the story is not the scale. It is the moment the company chose to become smaller.
The growth move that looked like retreat
Early on, 7shifts did what many scheduling startups do: it widened the aperture. Retail shops, construction crews and medical teams all had shifts, so why limit the market to restaurants? The customer count rose, but enthusiasm did not. Boesch later described the product as a jack of all trades. It worked, but it could not speak fluently about a Friday dinner rush, front-of-house and back-of-house roles, labor as a percentage of sales, tip pools or a point-of-sale terminal that doubles as a time clock.
“I was never satisfied knowing that our customers weren’t over the moon about what we were doing.”Jordan Boesch, founder and CEO
The company reversed course and focused exclusively on restaurants, effectively firing roughly two-thirds of its customers. On a spreadsheet, that is a frightening strategy. In product terms, it gave 7shifts permission to stop compromising. It could integrate with Toast, Square, Clover, Lightspeed and TouchBistro; pull sales and punch data into the same view; enforce a published schedule at the clock; and forecast labor using the information restaurants already generated.
The sharpest distinction from broad workforce tools such as Homebase, Deputy, When I Work and Connecteam is not the calendar interface. It is the data loop around the calendar. Yesterday's POS sales help shape next Tuesday's forecast. The schedule establishes who should clock in. The time clock records what happened. Tips flow from the POS into distribution rules. Approved hours and wages move toward payroll. A familiar scheduling grid becomes the front door to a restaurant labor system.
What it actually sells
Owners and admins use 7shifts to manage settings, labor budgets, reports and payroll across locations. Managers drag shifts onto a calendar, approve time off, fill open shifts, send announcements and leave notes in a digital log book. Employees use the mobile app to see schedules, submit availability, swap shifts, clock in and give post-shift feedback. Higher tiers add compliance warnings, performance tools, onboarding, task lists and multi-location reporting.
The five verbs 7shifts now uses - hire, train, schedule, pay and retain - reveal the expansion strategy. It did not bolt on an unrelated expense card or reservations marketplace. It followed the same employee. Onboarding puts documents in the profile. Training assigns courses and real-world tasks. Scheduling uses availability and forecasts. Time and tips become pay inputs. Feedback and communication try to keep the worker from leaving.
In July 2026, that stack gained an employee-training beta. Operators can turn a handbook or text prompt into draft lessons with built-in AI, add quizzes and acknowledgements, and assign on-floor tasks such as shadowing a shift. Managers can track completion and scores by person or location. The beta is practical but carries an obvious caution: a generated allergen lesson or compliance course still needs a human review. In a restaurant, an elegant hallucination can become a health problem.
The feature that failed before the strategy worked
The company's best product parable involves a local operator whom Boesch calls Rick. In 7shifts' early days, Rick watched a demo and said he needed a budget tool. Boesch and his wife, Andrée, asked questions, went home and built what they thought he had described. A few weeks later they returned, ready for praise. Rick had not tried it. He simply supplied another list of features required before he would use the product.
The budget tool remained in the app for years, neither celebrated nor challenged. When Boesch finally checked the data, fewer than 2 percent of users touched it. Interviews exposed the miss: managers were still doing labor calculations in Excel because the feature did not match their process. The pain was real. The first solution was wrong.
A feature request is evidence of pain, not a signed architectural drawing.
The correction was to watch operators work, understand the spreadsheet and redesign the budget workflow around actual behavior. That episode answers two questions founders often dodge. What failed first? A requested feature built too literally. What changed the team's mind? Usage below 2 percent, followed by customers demonstrating the offline job the software was supposed to replace. Opinion became observation; observation became a better product.
What it costs - and how the model compounds
7shifts is sold per restaurant location, which fits the buyer better than a generic per-seat model. Its published annual-billing prices in August 2026 start with a free Comp plan for one location and up to 20 employees. Entrée is $29.99 a month per location for teams of up to 30. The Works is $69.99 with unlimited employees and adds labor, compliance, retention and reporting tools. Gourmet is $135 and adds onboarding, tasks, deeper permissions and multi-location insights. Monthly billing costs more, enterprise groups call for a quote, and prices can change.
Add-ons make the revenue model more interesting. Tip Management is listed at $49.99 per location per month, with a transaction charge for instant payouts. Manager Log Book is $14.99, Task Management $12.99, and US onboarding costs $2.99 per package sent. Payroll adds another recurring layer. Infrastructure partner Check reported that embedded payroll lifted average monthly recurring revenue by $160 per participating location, moved $310 million in payroll funds and was paying more than 20,000 restaurant workers by the end of 2024.
This is conventional vertical SaaS economics with an unusually clean expansion path. A free or inexpensive schedule lands in one store. The restaurant connects its POS. Managers depend on communication and time data. A growing group adds locations, reporting, tasks, tips and payroll. Each module reuses information already in 7shifts, so adding a product can remove a login rather than create another one.
What readers can copy
The stealable 7shifts playbook
- Choose the customer whose vocabulary and workflow you can learn deeply.
- Use integrations to turn specialist knowledge into product behavior.
- Expand along one user's journey, where every module can reuse existing data.
- Measure requested features after launch and watch the offline workaround when adoption is weak.
- Price around how the customer's operation grows, not merely around software seats.
The most copyable decision is also the most uncomfortable: define who the product is not for. Restaurant-only positioning gave sales a crisp story, product a useful constraint and partnerships a reason to prioritize 7shifts. A generic scheduler might integrate with a payroll provider. A restaurant specialist can connect last night's covers, early clock-ins, pooled tips and next week's labor target. The nouns get specific, and specificity compounds.
Where the recipe breaks
Vertical depth is not magic. The model works when an industry has repeated workflows, painful coordination, specialized rules, valuable data sources and enough locations willing to pay. Restaurants qualify: labor is large, margins are thin, turnover is high and POS systems create a useful stream of sales and time data.
It works less well for a non-restaurant workforce, where 7shifts' language and integrations become constraints. A tiny café content with a paper rota may not recover the switching effort. A restaurant whose POS, payroll vendor or jurisdiction is unsupported may get only part of the promised loop. Groups already committed to an all-in-one POS suite may prefer its included scheduler, while enterprises with unusual union rules or global payroll needs may require heavier customization. And software cannot repair a manager who publishes schedules late, ignores availability or treats recognition as an app notification.
That last condition matters. 7shifts can shorten the path between a worker requesting time off and a manager seeing it. It cannot make the manager say yes. It can measure shift sentiment, but not create a humane shift. The product is strongest as an operational amplifier. Good practices become easier to repeat; bad practices become more efficiently documented.
A back office hiding inside a calendar
7shifts occupies a contested patch of restaurant technology. Fourth's HotSchedules has deep industry history. Homebase, Deputy and When I Work serve broad hourly teams. Toast and other POS companies can bundle workforce features beside payments. The Canadian company cannot rely on scheduling alone. Its defense is becoming the connective layer that makes the rest of a restaurant's stack more coherent.
The evidence is in the product's movement: from a downloadable schedule to a mobile communication network; from POS-fed forecasts to time clocks and compliance; from pooled tips to embedded payroll; and now from onboarding documents to training courses. The calendar remains the wedge because every restaurant needs one every week. The larger business is the set of decisions and dollars that flow through it.
Boesch started by cleaning up a desk. The more consequential act came later, when 7shifts cleaned up its own customer list. That cut did not guarantee success, and it would be foolish advice for a company without evidence of a better segment. Here, it aligned an origin story, a product roadmap and a partner ecosystem around one demanding buyer. The result is not software for everyone who works a shift. It is software that knows why dinner service is different.