What a Director of Customer Success actually owns at Restaurant365.
A research note on the role. Where the function sits in 2026, what the first ninety days should look like, the three metrics that matter, the questions worth asking in the interview, and the risks worth naming out loud.
Restaurant365's Director of Customer Success seat is not a renewals desk. It is a portfolio operator seat for the multi unit restaurant customer base. The right operator runs it like a multi state P&L: cohort customers by operator profile, instrument the leading indicators of churn six months early, and turn the CS function into a margin compounding engine for both R365 and the operators it serves.
The operator side problem is still open.
Four observations from the public record. Each is the kind of thing the team running the function thinks about every Monday morning.
Eric Cox joined as COO
The announcement framed the mandate as "customers getting full value from the platform" and "strengthening internal operations." That is the operator facing CS function. It is the seam between customer success and ops, and it is the discipline this role exists to install.
Kim Peretti owns customer success
She brought the Klaviyo IPO era CS playbook (renewals, expansion, health scoring, NRR). That playbook works for self serve SaaS. It only partially fits multi unit restaurant operators who buy R365 to fix a P&L, not to graduate to a higher tier. The Director of CS is the person who translates between the two playbooks.
The buyer is a multi unit operator at 5 to 50 units
R365's ICP has a controller, a director of operations, and a CFO they share with their parent group. They evaluate software the way an operator evaluates a poultry contract: by margin impact, not by feature. CS that does not speak fluent unit economics is the bottleneck on retention.
Toast, ADP, 7shifts already integrate
The dashboard, accounting, scheduling, and POS layers are converging. R365's edge is being the accounting and ops backbone that holds the rest together. Integration friction is the silent churn driver. CS owns the customer side of that conversation.
What the first ninety days actually look like.
Three things any Director of Customer Success owns from day one. The operator health score, the renewal motion, and the bridge between Kim's CS team and Eric Cox's COO function.
Stabilize.
days 1 → 30- Build the operator profile health score. Not "did they log in this week." A composite of food cost variance, labor variance, schedule adherence, period end close speed, and three vendor benchmarks. Operators feel R365 working when their P&L feels lighter on Mondays.
- Interview 20 customers in the 10 to 30 unit band. The mid segment is where churn and expansion both live. Cohort by lifecycle stage. Specific churn signals only show up by talking to the operators directly.
- Map the integration friction. Toast, Square, ADP, 7shifts handoffs. Each integration that fails silently costs a CSM 2 hours of debugging per ticket. Quantify the cost.
- Walk one customer for a week. Sit in the back office of a 12 unit operator. Watch the close. That is the R365 ground truth.
Compound.
days 31 → 60- Ship the multi unit operator playbook. Eight chapters: onboarding the GM, period end close, vendor benchmarking, labor scheduling against forecast, food cost variance triage, audit readiness, expansion stage transition, lender grade reporting. CSMs use it as a curriculum, not a manual.
- Reframe QBRs. Standard SaaS QBR talks adoption and feature usage. The operator QBR talks margin impact and one specific operating fix. Pilot with the top 20 accounts.
- Build the renewal risk model. Operators do not churn because R365 lacks features. They churn because their controller retired or their PE sponsor pushed Sage Intacct. Both are predictable 60 days out. Model both.
- Stand up the operator advisory council. Twelve customers across band, paid in product access, monthly. They become the source of truth on what to ship next, and a referral engine into similar groups.
Scale.
days 61 → 90- Convert the playbook into a CS curriculum. Every CSM trained in multi unit operator literacy. Reading a P&L is not a stretch goal. It is the floor.
- Publish the first R365 Operator Index. Quarterly benchmark report drawn from anonymized customer data: food cost ranges by region, labor as a percent of revenue, period close speed. Free to the industry. Becomes the standard reference. Inbound leads compound.
- Productize Customer Success as a revenue line. Premium CS tier for the 30 to 50 unit operators who need monthly ops review, vendor benchmarking, and a real time labor model. Margins compound. The tier funds itself.
- Hand the operating model to Eric Cox. Documented, instrumented, repeatable. The COO function gets a CS engine that runs without daily intervention. That is the deliverable.
The three things I'd watch from day one.
Not a dashboard of fifty KPIs. Three numbers that, if they move, the rest of the function moves with them.
Where R365 wins and where it has to defend.
Four competitors, four dimensions. The CS function defends or expands on each axis depending on the customer's stage and sponsor.
| Restaurant365 | MarginEdge | CrunchTime | Sage Intacct | |
|---|---|---|---|---|
| Multi unit operator depth (5 to 50 units) | strong | building | strong, enterprise | generic |
| Restaurant vertical specificity | native | native | native | cross vertical |
| Accounting backbone strength | strong | add on | mid | strong |
| Customer success operating model | building | building | mature | channel led |
Hypothetical NRR by customer unit band
Six questions I'd want answered in the interview.
The point of these is not to demonstrate that the JD got read. The point is to surface where the team thinks the function is weakest, so the first 30 days do not get spent rediscovering what leadership already knows.
How does the operator profile health score work today, and how confident is the team in it?
If the answer is precise, the function has a working instrument. If the answer is "we use product engagement metrics," that is the first 30 day build.
What is the QBR cadence and content for mid segment accounts, and where does it fall short?
The QBR is the trust ritual. If it is feature focused, it is not earning trust. If it is operator focused, the function has the foundation to compound.
How does CS hand off to and from sales on expansion deals?
The expansion seam is where mid segment accounts get under served. Knowing where leadership thinks that seam is broken is the highest leverage early intervention.
What is the current cause taxonomy for churn, and how confident is the team in it?
If the taxonomy has six causes and four of them are "other," that is a research project. If the taxonomy is precise but the predictive accuracy is low, that is an instrumentation project.
How does CS interact with the product team on customer feedback?
Multi unit operators are R365's best product research. If that feedback channel exists with weekly cadence, the function compounds. If it is ad hoc, the function loses value to ticket queues.
What does success at the 12 month mark look like for this role specifically?
Not the NDR number. The team change, the cadence change, the leading indicator that says the function compounds even if Q4 misses by a few points.
Four risks worth naming out loud.
Honest read on what could trip the function. The point of writing these down is to be ready for them, not to talk anyone out of the bet.
The Klaviyo playbook does not fully port
Klaviyo's CS model worked for self serve SaaS customers who graduate up the tier. R365's customers do not graduate. They grow units, hire controllers, and renegotiate. The function has to be a hybrid: Klaviyo discipline on the back end, operator literacy on the front end. Hiring against one half misses the other.
CS positioned as renewal defense, not value driver
If leadership reads CS as the team that keeps churn down, the function gets resourced for defense. If leadership reads CS as the team that drives margin expansion in customer P&Ls, the function gets resourced for offense. The difference is whether the Director gets a seat at the strategy table.
Integration friction with Toast / ADP / 7shifts
Silent integration failures erode customer trust faster than any feature gap. The CS function inherits the customer side of that conversation regardless of whether engineering owns the fix. Building the diagnostic layer that surfaces integration issues to customers before they raise tickets is part of the role.
PE sponsor migration pressure
When a PE sponsored operator changes hands, the new sponsor often pushes a standardized stack across portfolio companies, most often NetSuite or Sage Intacct. Those churn events are not won at the renewal table. They are won at the sponsor relationship table eight months earlier. The CS function has to know which customers have which sponsors and which sponsors run which playbooks.
The fuller portfolio at kiyonglee.com is the canonical record of how I think about operating businesses, multi unit restaurants, and the architecture that lets a customer success function compound.
$ cat ~/kiyonglee.com →Twenty minutes is enough to see if this lands.
If the diagnostic reads true to how the R365 customer success function feels from the inside, a working call is worth setting up. If it reads wrong, that is also useful information.
Start the conversation// sources
- Restaurant365 · Kim Peretti named Chief Customer Officer (PR Newswire)
- Restaurant365 · Eric Cox joins as Chief Operating Officer (PR Newswire, January 2026)
- Restaurant365 product positioning and multi unit customer profile
- Industry coverage on restaurant accounting and back office software competitive landscape
- Customer side market knowledge from sixteen years operating multi unit restaurants under Michelin recognition and multi state franchise contracts