Executive summary
What Acellas delivered, and what it means for the business
Acellas established the operating model Owner RevOps now runs on: one path from intake to release, on which the team has completed 633 of 803 backlog items and 353 dated production deployments.
Every cancellation now opens a Churn Opportunity with required reasons, so leadership sees churn, saves and losses in the same pipeline as new bookings.
Retention and Engagement cases open on each restaurant's highest-priority issue before it cancels, and CSM workloads stay balanced.
Owner RevOps retired more than 100 unused fields, and integration users moved to least-privilege permission sets and integration licenses.
353 production deployments on the operating model Acellas built
The challenge
Owner.com doubled headcount to about 200 and scaled toward a 50-seller sales team, the kind of hypergrowth that stretches any Salesforce org. Finance leadership named 5 priorities: refactor the Salesforce configuration that had carried that growth, prepare for provisioning and a post-sale Stripe integration, give Customer Success churn reporting, equip CSMs with a proactive retention process, and settle a support stack in transition. Service cancellations ran through deactivation automations, so no opportunity record captured a save or a loss, and churn stayed outside the pipeline view. RevOps also needed one way to take in, size, test and release work as requests multiplied across Launch, Customer Success and Sales.
Why Owner.com chose Acellas
Acellas works only with technology companies, operates as an extension of the client's RevOps team and brings two decades and more than 60 full lifecycle Salesforce Quote to Cash implementations. Acellas also brought an architect who could plan the integration and the software development lifecycle (SDLC) for a platform heading toward Stripe provisioning.
Results
Acellas started with the operating model: an Agile Working Contract, Notion backlog, sprint board and documentation hub, 7 ceremonies from daily scrum to a Deployment Party release, and 4 standard subtasks on every story (QA, UAT, documentation and production deployment). Knowledge transfer across 3 core areas (Leads and intake, Opportunities and Cases) fed an org documentation repository. We built Retention & Engagement case infrastructure, an Attribution field Finance analyzes in the warehouse, role-based activity relationships, and a Churn Opportunity process: a cancellation from any of 3 entry points opens an opportunity with required churn reasons, routed to a churn-save queue, so leadership sees churn and saves in the pipeline.
What Acellas delivered
Agile operating model for RevOps
An Agile Working Contract, a Notion backlog and 7 ceremonies gave RevOps one path from intake to release; Owner RevOps has since completed 633 of 803 backlog items on it.
Retention and Engagement case infrastructure
Acellas shipped 4 stories: automatic follow-on Engagement and Retention cases, an R&E quick action on Account and Support Case, an automated Attribution field and role-based activity relationships.
A Churn Opportunity for every cancellation
Churn Opportunity fields and cancel-service quick actions on the Account, Support Case and Onboarding Case turn every cancellation into an opportunity with 5 required churn-reason categories.
Org assessment and knowledge transfer
Assessment and knowledge-transfer sessions across 3 core areas (Leads and intake, Opportunities and Cases) produced a Salesforce documentation repository in Notion.
Release discipline from the first release
Acellas's first 5 production deployment events, each with a smoke test, set the release rhythm behind 353 later dated deployments by Owner RevOps.
Business benefits
Churn visible in the revenue pipeline
Cancellation requests from the Account, Support Case and Onboarding Case now open Churn Opportunities, so leadership reports churn, saves and losses with the same pipeline stages and amounts it uses for new bookings, rather than reconstructing them from service deactivation records.
Retention outreach before restaurants cancel
Priority scores from the data warehouse create Retention and Engagement (R&E) Component records, which open an Engagement case on each restaurant's highest-priority issue, from Sudden GPV Drop to Quiet Churn, and a follow-up case when it closes. Each case records the GP Score at open and at close, a measure of each intervention's effect.
Churn reasons Product and CS act on
Required Churn Initiation and Churn Request Reason fields, 5 issue categories from product to process, and a Moving to OLO field for competitive losses give Customer Success and Product a structured, reportable record of why restaurants leave and where they go.
Release velocity without disruption
Every story carries QA, UAT, documentation and production-deployment subtasks plus a smoke test, which let Owner RevOps run 353 dated production deployments for Launch, Customer Success, Sales and Growth without destabilizing the org that sellers and CSMs depend on.
Dashboards managers coach from
Dynamic AE dashboards show each rep's pre-SQO backlog, open pipeline by age and eMRR, forecast and launch health, and Partnerships and Launch leaders gained their own reporting, so managers coach from one current view of pipeline and onboarding.
Attribution Finance and RevOps trust
Automation writes one of 8 attribution values, from Client Referral to Cold Outbound, to every opportunity from Lead Source and HubSpot timing, as data rather than a formula, and a backfill extended it to historical opportunities, so Finance analyzes channel return in the warehouse.
Operational benefits
Saves and reversals on the record
The Closed Won flow on a Churn Opportunity records which save levers worked, and the Rescinded Churn process reverses account status and cancels the hardware return, so retention playbooks rest on evidence and a restaurant that stays sees no disruption.
Balanced, capacity-aware CSM workloads
New R&E cases route to the account's CSM, or else to the available CSM waiting longest under a manager-set case threshold, and cancellations route to a dedicated churn-save queue, so workloads stay balanced and no at-risk restaurant sits unowned.
Activity data sellers can rely on
Role-based rules relate each activity to the right Lead, Opportunity, Case or Account for CSMs, onboarding specialists, AEs and XDRs, and Talkdesk calls relink to their Case or Opportunity, so Last Activity Date, stale-deal alerts and activity reports reflect real engagement.
Alerts where sellers and CSMs work
Slack alerts warn XDRs and AEs before an idle opportunity auto-closes, post lead-enrichment failures to an API error channel, and surface scheduled deactivations and unqualified-churn approvals, so teams act inside the tool they already use.
A leaner org with room to grow
Owner RevOps retired more than 100 unused Account and Case fields and their dependent flows on the operating model, so layouts and reports carry only fields people use, and the Account object regained headroom for the fields new products require.
Least-privilege integrations, protected data
The HubSpot, Talkdesk and Salesloft integration users now hold package-scoped permission sets and integration licenses in place of named employees, and EIN data on onboarding cases is encrypted and masked. Together these reduce security exposure and keep integrations running when people leave.
Technologies
- Salesforce Sales Cloud
- Customer Service Management
- Salesforce Analytics & Reporting
- Slack Integration
- HubSpot Integration
- Custom Salesforce Platform Development
- Custom Salesforce Automation Development
Begin with a conversation
Talk with the experts who did this work.