Case study · Enterprise SaaS · Multi-unit architecture
Helping restaurant groups manage their data in one place
Scale: 76 restaurant groups · 1,180 active locations
Timeline: Approximately 2022–2025, with a temporary shift toward accounting development.
My role: Product Manager leading research, prioritization recommendations, requirements, and rollout, partnering with our president, principal architect, and lead designer.
The business opportunity
Orderly, later known as Back Office, began as food cost management software designed for small operators with 1–5 locations. As the company pursued larger restaurant groups, the platform needed to be rearchitected for shared data and corporate control across locations. This expansion was not guided by a consistently defined ideal customer profile.
But the existing experience made managing a restaurant group difficult. Customers with shared menus and ingredients had to repeat the same updates at every location. This was our biggest customer complaint and a barrier to serving the market we wanted to reach.
Through interviews and support feedback, we found that one person often managed the system for an entire group. They needed a way to make changes once and apply them across their restaurants.
Building the foundation
I recommended prioritizing centralized ingredient management because ingredients supported inventory, recipes, accounting categorization, and food-cost reporting. Establishing that foundation would enable the capabilities that followed.
We created a corporate location linked to individual restaurants, giving customers a dedicated place to manage shared data. I wrote the requirements and partnered closely with design on the corporate views, navigation, and how changes made by corporate users would appear to restaurant users.
Alongside the customer experience, we built a Customer Success-only interface to configure multi-unit structures and reporting groups.
Customer demand then guided us toward centralized recipe management. After launch, we discovered that restaurants missing an ingredient could reject recipe updates, leaving recipes incomplete. I partnered with our architect to ensure missing ingredients were created automatically at each location and with design to explain that behavior to users.
Sequencing control and flexibility
Centralized management launched without a policy system. Customers adopting the multi-unit structure had to manage the shared data centrally; they could not yet configure where corporate control ended and local flexibility began.
I recommended deferring the policy layer after our quarterly prioritization workshops showed that its expected business impact relative to implementation effort was lower than other needs. Centralization delivered value, but its mandatory nature remained a limitation.
The RASI acquisition temporarily shifted priorities toward rebuilding accounting capabilities within Orderly, later known as Back Office. When multi-unit work resumed in 2025, I focused on introducing a policy system to give groups more flexibility.
The policy system governed recipes, conversions, and inventory across corporate and restaurant locations, defining where shared standards applied and where local overrides were permitted. Counting-unit overrides, for example, let corporate users choose between standardized inventory counting and local customization. Broader local ingredient management remained on the roadmap.
Measurement context
Success measures were not consistently established before development. The evidence here shows adoption of the multi-unit structure and the revenue footprint of customers using centralized management; it does not establish incremental revenue or retention caused by these capabilities.
What changed for customers
Restaurant groups could update shared ingredients and recipes once instead of repeating changes at every location. They could also reuse corporate data when opening new restaurants and maintain greater consistency across their existing locations.
The multi-unit structure grew from 2 to 76 restaurant groups, encompassing 1,180 active locations. Each group had at least one corporate account configured and at least one active restaurant.
Paying restaurant groups using centralized management represented approximately $30,000 in monthly recurring revenue—equivalent to $360,000 in annualized recurring revenue.
What I learned
The initial research emphasized eliminating repeated work through centralized management. As larger groups adopted the system, their needs showed that consistency and flexibility had to coexist.
My approach evolved from centralizing shared data to helping customers decide where control belonged. The experience reinforced the importance of sequencing foundational capabilities while continuing to reassess the limitations customers encounter after launch.