
•
•

Summarize blog with








In Episode 26 of Implementation Stories, Alisha Hardoon, Manager - Customer Success at Robin, shares how you can make the most of executive business reviews (EBRs) and build a strong foundation for them.
Robin is a workplace experience software that optimizes office usage and helps employees find each other and spaces fast. Alisha was one of the first CSM hires at Robin and currently manages a portion of the CSM and the customer onboarding teams.
In this session, Daria focused on:
The goal of an EBR is to:
An EBR is an opportunity to:
An EBR is NOT a roadmap conversation–it’s about the customer and their journey.
QBRs are stupid. OBRs are smart.
The CS team takes a 3-wide-3-deep approach to stakeholders: they expect involvement from three relevant departments and three levels within those departments, at the minimum.
Purpose: Understanding if you have the adequate breadth and depth of inputs from the customer
Guiding questions: Who in your organization has a perspective/opinion on the subject?
Purpose: Summarizing current usage and account health insights, guiding the conversation to inform/validate the roadmap
Guiding questions:
Purpose: Ensuring transparency about successes, challenges, areas of improvement
Guiding questions:
Purpose: Building alignment on key results for the partnership
Guiding questions:
Here are a few things to consider when you evaluate which customers need EBRs:
Here is Robin’s approach:
On average, CSMs spend between one to three hours preparing for an EBR, depending on the account size. CSMs are provided a template with talk tracks and suggested visuals. The team relies on Looker dashboards to understand product usage and adoption metrics and further identify areas of success and risk factors.
Customer onboarding and EBRs
The onboarding team’s inputs about the customer are critical for the CSM to
A typical EBR agenda at Robin includes:
Best practice(s) at Robin
“Speeds up CSV importing and saves me from having to get customers to use a template file or create mapped data exports. Quick to integrate and flexible outside the happy path. We found defining workbooks and templates confusing; at a prior job it was configured through code, which I preferred.”
Source: G2 review


AI that executes your delivery work (Add to any plan)
Most popular
Ideal for expanding organizations needing more in-depth capabilities and integration for scaling.
Most popular
Great for teams desiring tailored workflows with comprehensive reporting capabilities.
Most popular
Tailored for large enterprises requiring a fully customizable, comprehensive delivery engine.

A Forward Deployed Engineer (FDE) embeds in the customer environment to implement, customize, and operationalize complex products. They unblock integrations, fix data issues, adapt workflows, and bridge engineering gaps — accelerating onboarding, adoption, and customer value far beyond traditional post-sales roles.





70–85% utilization. 94% G2 rating.
One platform does what the entire table above tries
to split across tools.
70–85% utilization. 94% G2 rating.
One platform does what the entire table above tries
to split across tools.

70–85% utilization. 94% G2 rating.
One platform does what the entire table above tries
to split across tools.
Enterprise implementations fail because customers don’t follow the process or provide clean data on time. Most delays are purely “customer-side” issues.
Implementations fail because complex environments need real-time technical problem-solving. FDEs unblock workflows, integrations, and unknown constraints that traditional onboarding teams can’t resolve on their own.
Get a better all-in-one PSA
Get a better all-in-one PSA
Companies that embed engineers directly with customers see significantly higher enterprise retention compared to traditional post-sales models — because embedded engineers uncover “unknowns” that never surface in ticket queues.

VP Sales, Intercom

A Forward Deployed Engineer (FDE) embeds in the customer environment to implement, customize, and operationalize complex products. They unblock integrations, fix data issues, adapt workflows, and bridge engineering gaps — accelerating onboarding, adoption, and customer value far beyond traditional post-sales roles.






.webp)