Ben Newton
Leading Customer Success, building with AI
Bristol, UK
Hi, I'm Ben
Customer Success Leader at Remote, and building with AI. Based in Bristol.
Click anything on the desktop:
- Jobs at Remote if you'd like to work where I work.
- CS advice if you're building a career in Customer Success.
- About me for my experience.
πͺͺ About me
I manage EMEA Midmarket and Enterprise Customer Success at Remote. I've spent 7+ years in Customer Success across SaaS and HR tech, 3 of them leading teams, and I've built CS functions and teams from scratch twice. I'm also the AI lead for our CS department. Based in Bristol.
What I'm good at
Twice: the whole CS function at OurPeople, then Remote's Scale CSM team, from the first hire to the playbooks.
Teams of up to 10 CSMs and portfolios of up to $28M ARR, with success planning and QBR frameworks used across the wider CS org.
Expansion playbooks for upsell and cross-sell, and holding a team to NRR, expansion and CSAT across seat-based and consumption pricing.
Hands-on with Claude Code or whichever AI you fancy. I've built several tools the team use every day.
Experience
- Nov 2025 β nowManager, Midmarket & Enterprise Customer Success, Remote
Accountable for expansion, NRR and CSAT across seat-based and consumption-based pricing, and partnering with Sales on expansion pipeline, renewal risk and account strategy. - Dec 2023 β Dec 2025Manager, Scale Customer Success, Remote
Built and led Remote's Scale (now Growth) CSM team from the ground up: a team of 10 and a portfolio of $28M ARR. Designed its expansion playbooks, plus success planning and QBR templates adopted across the wider CS organisation. - Aug 2022 β Dec 2023Senior Customer Success Manager, Remote
Strategic and enterprise accounts, focused on satisfaction, retention and growth. Started a peer-to-peer shadowing programme to share knowledge across the team, and led cross-vertical growth initiatives. - Aug 2021 β Aug 2022Customer Success Manager, Remote
My foot in the door, my first role at Remote. - Mar 2019 β Aug 2021Customer Success Lead, OurPeople, Bristol
Pioneered the Customer Success function: hired and developed the first team and built every foundational process from scratch, including onboarding flows and usage analysis to predict and reduce churn. - 2017 β 2018Head of Operations, MedCircuit (employee #3)
A true generalist role at a medtech startup building software for the NHS: clients, investors, software trials, compliance, hiring and grant applications.
What I'd move for
Senior CS leadership where AI is part of the plan from day one, not an afterthought.
πΌ Hire me
Got a role in mind? Start with the numbers.
Thanks, that's with me. I'll get back to you soon.
Want the background first? See my experience.
π Want a job at Remote?
I get a lot of messages about jobs at Remote. It's great that so many people want to work here. I can't give each one a proper reply, so this page is everything I'd tell you anyway.
These are my own views, not an official Remote page. The official careers site always has the final word.
Where do I find open roles?
All open roles are on the official careers page. If a role isn't listed there, it isn't open. I don't have a secret list.
Can you refer me?
If we've worked together, yes, happily. Message me with the link to the role.
If we haven't, probably not. A referral means I'm vouching for your work, and I can only do that honestly for people whose work I've seen. A referral from someone who can't speak to your work doesn't add much. A strong application does.
Can you check on my application?
I'm not part of other teams' hiring, so I can't see or speed up applications. The recruiting team will get back to you.
What makes an application stand out?
- Tailor it to the role. Map your experience to what the job description actually asks for.
- Show outcomes, not duties. "Cut onboarding time by 30%" beats "responsible for onboarding".
- Know the space. Understand what the company does, who it serves and why that's hard.
- Keep it tight. Short, clear CVs get read.
Are you hiring for your own team?
When I'm hiring for Customer Success, the roles go up on the careers page like every other role. If you've applied to one of them, you're welcome to send me a short note: the link to the role and three lines on why you're a fit.
Applying to a role that isn't in CS? That team is the right place to start, not me.
I'm new to CS. Where do I start?
Have a look at the CS career advice shelf. I wrote it for exactly this question.
π Customer Success career advice
These are the answers to the questions people ask me most, depending on where you are right now.
Breaking into CS from another field
Support, account management, teaching, hospitality, sales and consulting all give you skills that transfer straight into CS. Make that link obvious on your CV.
- Learn the vocabulary: onboarding, adoption, health scores, renewals, churn, GRR/NRR, QBRs.
- Have two or three stories ready about a time you kept a customer happy and moved a number.
- Pick companies whose product you understand. It shortens your ramp and shows in interviews.
Moving from Sales to CS
Lead with what transfers: relationship building, problem solving and stakeholder management. The difference in CS is that it's all longer term. The relationship doesn't end when the contract's signed: it's measured in years, not quarters.
- Show you build trust that lasts. Have stories about clients you stayed close to after the deal: ones who came back, referred others or grew with you.
- Show how you solve problems. You've unblocked deals by working out what a customer really needed. In CS you do that every week, long after the deal.
- Show you can manage stakeholders. Working a deal across champions, buyers and execs is exactly how you keep an account healthy and get it renewed.
- Translate your sales skills. Discovery becomes success planning. Objection handling becomes renewal conversations. Managing a pipeline becomes managing a book of accounts.
- Show you're in it for the long game. In interviews, talk about what happened after the close, not just the close.
- Expect a different pay mix. Usually more base and less commission, often tied to retention and expansion.
Moving from Support to CSM
- Move from closing tickets to owning outcomes: ask what the customer is actually trying to achieve.
- Volunteer for onboarding, escalations and anything that touches renewals.
- Learn the commercial side: contract value, renewal dates, expansion paths.
From CSM to Senior / Lead
- Know your book's numbers cold: retention, expansion, risk.
- Fix one process that makes the whole team better, and write it down.
- Start coaching newer CSMs. Leadership is visible long before the title arrives.
Into CS leadership
- Get good at forecasting retention. Your CFO will love you.
- Hire for judgement and curiosity. Product knowledge can be taught.
- Build real partnerships with Sales, Product and Support. CS can't hit its targets alone.
Interviewing for CS roles
Have a clear story ready for each of these:
- A save: a customer about to churn who stayed.
- An expansion you made happen.
- A difficult customer you turned around.
- A process or playbook you built.
Ask them how CS is measured, what the account ratio is, and how CS works with Sales. The answers tell you a lot.
π€ AI lab
As AI lead, my job is finding where AI actually helps customers and the people who look after them, and then making it part of everyday work.
What I'm working on
- AI strategy for Remote's CS department. It's moved through three stages: getting CSMs to use and trust AI, then curating what actually works once everyone started building, and now building tools that help CSMs build better tools. More on that.
Things I've built
- CSM Command Centre: the one-stop shop for Remote CSMs.
- An AI assistant in Gmail: a Chrome extension that pulls in each customer's CRM context and answers questions using Remote's internal AI, right where CSMs write their emails.
- My own AI harness: a custom setup with agents everywhere, which learns from me every time I use AI.
How I think about AI in CS
CSMs are the judgement layer. Automate everything around them, so they have the information they need, when and where they need it, to make the right calls.
- Start with the workflow, not the model.
- Measure time saved and outcomes changed, not prompts written.
- Keep humans where trust is built.
Writing
βοΈ Writing
Longer thoughts on AI and Customer Success.
- Three stages of AI in Customer Success
From getting CSMs to trust AI, to helping them build better tools. - How I became AI Lead
Short version: I built the tools I wanted when I was a CSM.
Three stages of AI in Customer Success
Looking back at how our AI strategy for Customer Success at Remote has changed, it falls into three stages. Each one felt like the whole job at the time.
Stage 1: Adoption
The first job was getting CSMs to use AI at all, and to trust what came back. Looking back from where we are now, it seems mad that this was ever the hard part. But it was, and trust had to come first.
Stage 2: Curation
Then everything changed. After our founder Marcelo launched AI for Actual Work, a free AI course built by the whole team at Remote, everyone was building like crazy. The problem flipped from "nobody's using it" to "what's actually good?"
So my job became curation: helping CSMs find what works and what's genuinely useful, and cutting through the noise.
Stage 3: Moving quality control up the chain
Now the focus is building tools that help CSMs build better tools. CSMs are always closest to the problem: they know where the friction is before anyone else does. So instead of checking everything they build after the fact, the aim is to build the quality in from the start.
What hasn't changed
CSMs are the judgement layer. Automate everything around them, so they have the information they need, when and where they need it, to make the right calls.
How I became AI Lead
Short version: I built the tools I wanted when I was a CSM.
Longer version
When I first started "coding", I'd post my problem on Stack Overflow. After 15 minutes, someone would give me working code. After an hour, there'd be several iterations that vastly improved and simplified it. With AI, that whole loop is almost instant. (Sorry, Stack Overflow. RIP π)
When I got access to AI coding tools, I had a laundry list of problems I wanted to solve. So, like a kid in a candy store, I set about solving them. First for myself, but I knew my problems were problems everyone on the team would have.
One of them became the Chrome extension my team now uses every day: it brings our CRM data and internal AI into Gmail, so nobody has to switch between tabs to get the context they need.
Build for yourself. Your biggest problem will definitely be someone else's.
πͺ Say hi
Thanks, that's with me.