Guest Episode Episode 04

Gaby of Robin
Do You Really Need a Chief of Staff and How Much Should You Pay Them?

A no-nonsense look at the most-hyped role in startup hiring: when a founder actually needs one, how to tell a Chief of Staff apart from a Founder's Associate, what to test for in the interview, and what fair pay looks like at Series B in London.

About This Episode

Gaby joins Ceci and Bea for a guest-led conversation about the Chief of Staff role itself. Gaby is the founder of Robin, a consultancy that helps founders identify and place the most important hire they will ever make: their right hand. Before Robin she was Chief of Staff at McKinsey, supporting a managing partner inside one of the most structured environments in the world, and then at Codat, the high-growth fintech, where the role was the polar opposite: building the organisational scaffolding from scratch and dipping into whichever part of the business needed help that week.

The episode is the practical, slightly contrarian conversation founders rarely get when they decide they want a Chief of Staff. Gaby walks through her diagnosis process, why most founders are right that they need help and almost always wrong about the title, the test that separates a great hire from an expensive mistake, and how to recognise when a Founder's Associate would actually serve them better. She is also direct about pay: at Series B in London she anchors fair base around £110-130k, plus meaningful equity, with a clear narrative for upside.

What We Cover in This Episode

From McKinsey to Codat: The Conductor vs. The Scaffolder

Gaby didn't plan to be a Chief of Staff. She fell into it at McKinsey supporting a managing partner, and quickly realised the generalist nature of the work suited her. At McKinsey the role was what she calls "the conductor": institutional authority sat behind every decision, the support system around the managing partner was already in place, and her job was to bring the right people to the right room at the right time, keep the leadership team aligned, and stop things from falling through the cracks. Codat was the opposite end of the spectrum: high-growth, no scaffolding, no clear definition of what good looked like. The role turned into building the scaffolding itself, while also dipping into specific functional areas that needed extra firepower. The biggest surprise wasn't intensity, it was risk appetite. She expected scale-ups to be more cautious because every decision has tangible consequences. The reality was the opposite: faster decisions, faster failures, faster learning, and an explicit cultural permission for that to be fine.

Chief of Staff as a Founder Pipeline

Gaby went from Chief of Staff to founder, and she sees this as a natural pattern rather than a coincidence. The Chief of Staff seat gives you proximity to the founder during the hardest moments, which de-glamourises the founder mythology. You see the emotional ups and downs, the bad days, the things that don't make it into the all-hands. By the time you start something yourself, your expectations are calibrated. Cecilia adds the same observation from her own seat at Seqera: the Chief of Staff role strips the mystique away from founding, in a way that paradoxically makes you more ready to do it. The piece Gaby has had to unlearn as a founder is decision authority. As a Chief of Staff you're a thought partner; as a founder, every decision falls to you, and that weight is both draining and energising at the same time.

Why 2026 Is the Year of the Chief of Staff

The role has become trendy, and Gaby is honest that some of the noise around it is hers. But the demand is real and structural. She names three drivers. One: the role of the leader has expanded. Founders are now expected to be strategic operators, culture setters, communicators, crisis managers, and still make 50 micro-decisions a day. That's a structural problem, not a bandwidth one. Two: execution pressure is higher than ever. Startups are leaner, the days of inflated leadership teams are gone, and that environment can't be solved by hiring more specialists. The generalist who can context-switch and hold the whole company in their head becomes disproportionately valuable. Three: AI. AI does a lot of the doing, which makes the judgment, nuance, and connective tissue layer (the parts AI can't do yet) more important. And Chiefs of Staff are usually the ones leading internal AI rollouts because they're the ones operating cross-functionally.

The Diagnosis: What Kind of Chaos Is This?

Founders almost always know they need help. They almost never know in what shape. Gaby's process is to take the title off the table and dig into the actual pain. She runs a structured conversation: walk me through a typical week, where does your time usually go, where do you still need to step in because it materially improves the outcome, where do decisions slow down or lose clarity if you're not in the room. From those answers she's trying to surface whether the gap is capacity, judgment, trust, or execution, because each of those points to a different hire profile.

Her core distinction: there are two types of chaos a founder can be feeling, and each one points to a different person. Chaos in the business, projects stalling, no operating rhythm, things getting 60% done, is an operations problem. That's a Founder's Associate: someone working on the doing, in the business. Chaos in the organisation, priorities unclear, leadership not aligned, vision not translating into execution, is a Chief of Staff problem. That's someone working on the business, with judgment about what should be executed and why.

Values, Behaviours, Skills (in That Order)

One founder Gaby worked with described talent as three things: skill sets, behaviours, and values. For a Chief of Staff, the right model is values and behaviours aligned with the founder, and skill sets that complement rather than mirror them. If the founder is product-led, the Chief of Staff carries the rest of the business. If the founder is more introverted and culture-and-comms isn't a natural lane for them, the Chief of Staff who can build relationships across the business is the right complement. The opposite approach, hiring a clone, doesn't create leverage.

Gaby is candid that Chief of Staff hiring is hard precisely because the values and behaviours are where the candidate has to spike, and they're notoriously the toughest things to test. Skill sets matter less than founders typically think. The case study or live exercise has to be designed around behavioural signals.

The Sparring Partner Test

Her recommended structure: a non-negotiable conversation with the founder upfront (chemistry is the foundation; without it nothing else works), then a live, lightly-prepared whiteboarding session on a real problem the founder is currently facing. Not deep subject-matter expertise, not a take-home that gives the candidate time to over-prepare with ChatGPT. Live, in-person, on something real. You're testing how the candidate thinks, structures thoughts, asks questions, and digs into things they don't know. From there, exposure to other stakeholders the Chief of Staff will work with, because their buy-in matters too. The talent market is competitive at the top, so the founder also has to be selling the company throughout.

Red Flags on Both Sides

Gaby's framing: it's a real working relationship, and the same pattern-matching applies as any other. If you can't ask hard questions in the interview, that's a red flag, because that's what the role will require every day. If the founder isn't willing to share openly during the process, that's a bigger red flag, because the relationship runs on trust and transparency. Bea makes the point sharply: if you can't ask "how do you work, what kind of people create friction with you" before you take the job, you're already in trouble.

Why 80%+ of Chiefs of Staff Are Women

Gaby's observation, from talking to Chiefs of Staff every week, is that more than 80% of them are women. Her read on why: the role rewards a generalist skillset, very high EQ, the ability to build relationships at every level of the organisation, and a willingness to do invisible work, championing other people, taking responsibility quietly when things go right and getting called out only when things go wrong. Those qualities have historically lent themselves to women, and the world of work was structured around men succeeding in different conditions. The interesting question isn't why the cohort skews female today; it's whether the next generation of founders, executives, and C-suite leaders ends up reflecting the talent pipeline that exists right now. If the Chief of Staff role is a launching pad, an 80% female pipeline should produce something the rest of the leadership world hasn't seen yet.

The First 30 Days

The role can fail because of the first month. Gaby's framework splits the work into Chief-of-Staff-side and founder-side responsibilities.

From the Chief of Staff: build trust fast, but don't pressure yourself, trust is earned through reliability. If you said you'd do it, do it. Small habits compound. Then absorb how the founder thinks, decides, prioritises, and operates under pressure, ideally in person. The goal is to become almost interchangeable with their judgment in their absence. Then build relationships across the business through coffee chat after coffee chat, partly to be useful and partly to break the "Chief of Staff as spy" misconception, especially in companies that have never had one before. Communicate relentlessly about what you're working on and why, including to yourself, because in the early days the role is ambiguous and it's easy to confuse busy with productive.

From the founder: over-communicate to the nth degree, end-of-day voice notes if needed. Even if there are no actions, the Chief of Staff is calibrating to your thinking. Give access and authority deliberately, because a Chief of Staff without authority becomes a facilitator. Delegate properly: be clear on the ask, then let go of it. The letting-go muscle is the hardest one for founders to develop, and it's the difference between a good and great Chief of Staff outcome.

What's a Fair Salary?

Gaby's market read for a Chief of Staff at a Series B company in London: £110-130k base, with the median around £120-125k and £130k for an exceptional candidate. The bandings are always broad because the role is so scope-dependent, and she pushes founders to anchor on what the role actually owns rather than title or stage. That base figure is part of the total comp picture. Meaningful equity is expected, and founders need a compelling narrative for why this person is joining this company and what the upside actually looks like. Cecilia's line in the episode: there's too much hush-hush around Chief of Staff salaries, and the people who lose from that are the candidates.

Frequently Asked Questions

Who is Gaby and what does Robin do?

Gaby is the founder of Robin, a consultancy that helps founders identify and place the right "right-hand" hire — typically a Chief of Staff or Founder's Associate. Before Robin she was Chief of Staff at McKinsey (supporting a managing partner) and at Codat (high-growth fintech). She works directly with founders to scope the role, design the interview process, and place the candidate.

Do I actually need a Chief of Staff or a Founder's Associate?

Gaby's diagnostic: identify the type of chaos. If projects are stalling and the operating rhythm is broken, that's a business problem, and a Founder's Associate (working in the business, on execution) is usually the right hire. If priorities are unclear, leadership isn't aligned, and the vision isn't translating into execution, that's an organisational problem, and a Chief of Staff (working on the business, with judgement about what should be executed) is the right hire.

What's the typical background of a successful Chief of Staff?

There isn't a single typical background, but the most common pattern Gaby sees is consultancy, VC, or investment banking as the foundation, plus one or two years in an operating function (growth, product, or ops) before stepping into the Chief of Staff role. The consistent thread, regardless of background, is tangible impact in prior roles and the ability to point clearly to where they moved the needle.

What's a fair salary for a Chief of Staff at Series B in London?

Roughly £110-130k base, with most placements landing around £120-125k. Exceptional candidates can push to £130k. Base is part of total comp; meaningful equity is expected, and founders should have a clear narrative on the upside.

Why are 80%+ of Chiefs of Staff women?

Gaby's view is that the qualities the role rewards (generalist skillset, very high EQ, relationship-building at every level, willingness to do invisible work) have historically lent themselves to women. The bigger question is whether the resulting talent pipeline converts into the next generation of founders and C-suite leaders.

What's the most common reason a Chief of Staff hire fails?

From the Chief of Staff side: not building trust early, not communicating clearly about scope and progress in an inherently ambiguous role. From the founder side: not over-communicating in the first 30 days, not granting real authority, and not actually letting go after they delegate. When hires fail, it's usually one of these.

Episode Transcript

Introduction

Bea [00:00]

Welcome to Top of the Ops, the podcast where we have real conversations about what happens behind the scenes of startups. I'm Bea, ex-VC at Lakestar and now Chief of Staff at Praktika.

Ceci [00:11]

And I'm Cecilia, ex-VC at Talis Capital and now FD at PortalOne.

Bea [00:15]

Well, today it's not just us. We're super happy to have our guest, Gaby, who is an ex-Chief of Staff both at McKinsey and Codat and now the founder of Robin, a consultancy that helps founders identify and place the single most important hire they'll ever make, their right hand. Hi, Gaby.

Gaby [00:34]

Hi guys, really excited to be here.

From McKinsey to Codat

Bea [00:38]

Let's get straight into it, starting with your Chief of Staff experience, which spans from McKinsey, a huge consultancy, to Codat, a startup and scale-up. Can you maybe talk us through how the Chief of Staff role looked differently at each company, and what surprised you most about making the jump from consulting to a growth-stage startup?

Gaby [01:01]

I think firstly I didn't plan to be a Chief of Staff. I fell into it at McKinsey, and the role there was very much supporting the managing partner. I just loved it. I've always been quite a generalist by nature in any role I've had, and I was so excited to find something that allowed me to have breadth, but also, at a time when I was quite junior, gave me really special exposure to the managing partner and the senior team at a huge company.

At McKinsey, the role was what I'd describe as the conductor. The managing partner had an incredible support system around them. The job was very much bringing the right people together at the right moment to move things forward, making sure the leadership team was super aligned, and nothing was falling through the cracks. Somewhere like McKinsey, you have institutional authority behind you, the structure around you, and a very clear sense of what good looks like.

I knew I loved the role, but I really wanted to see what it looked like in a totally different environment. Almost the other end of the spectrum, high-growth scale-up. I went and found that at Codat, where none of what I described existed at all. It was a role where I was getting involved in everything. It turned into building the organisational scaffolding, which was great, but also dipping down into some really key areas where they just needed extra support. It was way more hands-on, which meant it was a great learning opportunity for me too.

What surprised me at Codat was that I felt the stakes were a lot higher, every decision has real tangible consequences to the organisation, the team, the company. I assumed that would make people more risk-averse and more cautious. The opposite is true. You're moving quickly, failing fast, iterating faster, with the mindset that that's fine. For someone with an innate bias to action, that was an environment I could really thrive in.

Chief of Staff to Founder

Ceci [03:33]

That was such a good overview. You went from Chief of Staff to founder. Did being in the Chief of Staff role help you become a founder?

Gaby [03:41]

Considering what I'm doing now, yes, I'm now operating in a space where I'm solving a problem that relates to the Chief of Staff ecosystem, so having had that experience puts me in a really good position to solve it. In terms of skill set, I hope so. Chief of Staff to founder is definitely a trajectory you see often. As a Chief of Staff you do a lot of things; as a founder, you're doing everything too.

What really helped set me up was that as a Chief of Staff you see the good, the bad and the ugly because of the relationship you have with the founder. So your expectation is that it's going to be hard. You've seen the emotional ups and downs. It's helped me be more resilient in moments where I've really needed it.

Bea [04:42]

I completely agree. As a Chief of Staff you de-glamourise the figure of a founder because you see everything that happens behind the scenes and how much hardship they actually go through. That brings so much more awareness of what it actually takes when you're doing something yourself.

Gaby [05:05]

The one thing I've maybe missed about the Chief of Staff role and have had to unlearn is that you've got that partnership with the founder and a team around you. You're all working to the same mission and outcome. When it comes to decisions, you're often helping inform that as a thought partner. Having every decision fall to me is quite draining, but also exciting, because it's all on you and that makes the opportunity greater. I admire anybody who enters the founding journey so much.

Why 2026 Is the Year of the Chief of Staff

Ceci [05:57]

Talking about the Chief of Staff role, you wrote recently on LinkedIn that 2026 is the year of the Chief of Staff. We're seeing it too. When I joined Seqera over two years ago, most people weren't really sure what the role was. Now there are so many job openings. Why? What has changed in the operating environment?

Gaby [06:17]

It's something that gets me going because it's definitely a trendy role at the moment, and someone like me is probably adding to that noise, hopefully in a helpful way. But it's becoming popular for good reason, and I think it's a consequence of what we're seeing around it.

The role of the leader has changed and expanded. It's not just that all founders are busier than ever, it's that the scope of the role itself has changed. The founder is expected to be the strategic operator, a culture setter, a great communicator, a crisis manager, and still the person making 50 micro-decisions a day. That's not a bandwidth problem, it's a structural problem. The role of leader has just become too big for one person to hold in a sustainable, effective way.

The second thing is execution. No matter what stage, size, or type of founder I'm speaking to, this comes up time and time again. The execution pressure on companies right now is bigger than ever. Startups are leaner, the days of building with huge inflated leadership teams are over. The expectation on founders to move fast, run tight, and make real progress with fewer people is real. That environment creates a very specific kind of pressure you can't solve by hiring more specialists. That's where the value of the generalist has come in. Someone who can move fast across multiple areas, context-switch, and hold the context of the whole company.

And then the third is, how long could we have a podcast about this without mentioning AI. AI can do a lot of the doing. So the Chief of Staff role becomes more important because it's the judgment, the nuance, the bringing people together, the connective tissue that AI can't do yet. Also, in terms of how teams should approach AI experimentation, that often lands with the Chief of Staff because they're operating cross-functionally.

The Diagnosis Process

Bea [09:01]

I'd love to get into the meaty stuff. Your core thesis seems to be that founders know they need support, but many times don't know in what shape or form. Could you walk us through your diagnosis process? What questions do you ask, and how do you assess what type of support they need?

Gaby [09:28]

That's exactly why I started Robin. I was seeing all these Chief of Staff roles coming up, and getting into the job descriptions, an early-stage biotech had the same job description as a Series C fintech with 250 plus people. That just can't be true. You wouldn't expect that of any other role. The scope is different.

I don't think I had a job description. I'm not sure if you had one, Bea?

Bea [10:04]

I did not have a job description. I didn't even apply. The role was not out. I just kind of volunteered myself to an angel investment that I made.

Gaby [10:13]

That creates problems too. You're saying we need something, come and do something, and then a person gets lost. So when I sit down with a founder, they always know they need support because they can feel it. It's not that they need convincing. They're sold on that. The question is, what does the shape of that support look like?

Normally in those conversations, the founder really wants to be: this is who I need, this is the job description we've come up with. And it's, okay, let's take a step back. I really hone in on understanding what the pain points are and where they live in the business. Not what they think they need, very much what they're feeling. What's becoming harder to sustain as the company grows? Where do things slow down without them being involved?

Nine times out of ten a founder will come to me and say they need someone who can execute. Things aren't getting done, priorities are stalling, they're the bottleneck. That's valid, but underneath there's usually something more specific driving it. So I drill down. Before we talk about any role, I have to understand the business, where it is now, and what's going to get meaningfully harder as the company scales.

Then I go into the founder themselves, because the Chief of Staff role is unique in that it's for the business, but it also leverages the founder. So: walk me through a typical week. Where does your time go? Where do you personally still feel you need to step in because it materially improves the outcome? Where do decisions slow down or lose clarity if you're not in the room? Also their working style, who they work with best. That conversation tells me where the problem is. Is it capacity? Judgment? Trust? Execution? Those things lead to quite different hires.

Profiles and Complementary Skills

Ceci [12:23]

You mentioned profiles before and I'd love to dig in. I believe for each founder profile, there's a Chief of Staff profile. How do you tend to categorise those archetypes?

Gaby [12:41]

It's something I'm really trying to work on and codify. A Chief of Staff works well when they complement the founder in terms of skill set. A founder I worked with described talent in three parts: skill sets, behaviours, and values. For a Chief of Staff to complement their founder in skill sets and behaviours is really nice, and you've got solid alignment on values and what you're driving towards.

If the founder is product-led, this person can carry the rest of the business. If the founder is more introverted and culture-and-comms isn't supernatural to them, having a Chief of Staff who can talk and build relationships across the whole business is really helpful.

Bea [13:47]

I've been listening to you and thinking about my relationship with my previous CEO. It was very much like that. Values completely aligned, but very different people, different skill sets. He was more of an optimist, I'm more of a reality-check kind of person. You need that to create the healthy debate and challenges between that duo.

Chief of Staff vs Founder's Associate

Ceci [14:15]

I have a question. When do you actually tell founders they don't need a Chief of Staff? When do they need a Founder's Associate instead, and what is the difference?

Gaby [14:30]

The Founder's Associate role is getting the same exposure as the Chief of Staff, and it's a really great role. What I try to do is get the founder off title, because sometimes they come in saying "I need a Founder's Associate" or "I need a Chief of Staff" and you fall down that rabbit hole. The title is almost where the confusion starts, often shaped by something they saw on LinkedIn or a founder they respect.

So I bring it back to two things, because there are really two types of chaos a founder can be experiencing. If your business is feeling chaotic, projects are stalling, no operating rhythm, things getting 60% done and no further, that's an operations problem. That tends to need a Founder's Associate, someone working on the doing and getting things done in the business.

If the organisation is feeling chaotic, but it's more around priorities being unclear, leadership not aligned, the vision not translating into execution, that's a different problem. That's Chief of Staff territory. Someone who works on the business. A Chief of Staff can also work in the business, but Founder's Associates are usually just in. So it's not just execution, you want someone with judgment about what should be executed and why.

The boundaries blur, but you have to start somewhere, and that's what I've found most useful.

Bea [16:19]

I think that's the clearest definition between the roles I've heard. Ultimately the Chief of Staff has the strategy layer, and a lot of the job is translating the big blurry vision into actualising it. It's making sure the company is set up to execute, that systems are aligned and able to scale.

The Hiring Process

Bea [16:50]

Moving forward, you've realised the founder needs a Chief of Staff. It's a really hard hire. What are your top suggestions and tips for founders for the interview process?

Gaby [17:04]

You really need to align on the criteria you're going after. I come back to those three things: values, behaviours, and skill sets. What makes the Chief of Staff hire so hard is that yes, there's some skill set you want, but actually it's the values and behaviours where you want the person to spike, and they're notoriously the toughest things to test.

You have to be clear on what you need, that's why the scoping conversation is so important, and then clear on how you'll test for it. I always start with a conversation with the founder, because that's the non-negotiable. Working chemistry is really important, and there's a lot of great talent looking for these roles right now. Companies need to do a really good job at selling to the best talent.

What I think is non-negotiable now is some case study or task. It's hard with the Chief of Staff role to go off conversations and vibes, especially with referrals. You need something that lets you test for certain qualities. And it's not deep subject-matter expertise, I think the opposite. That's why I really like a live case study. Founders often say they want a sparring partner. So let's test that capability. Get them in the room. Give them a chance to be prepared, but not over-prepared, where they've ChatGPT'd it a million times. Talk about an actual problem you're facing and have a whiteboarding session. You see how they think live, how they structure their thoughts, how they communicate, how they ask questions when they don't know the answer.

Then a standard process from there. If you want this person working with lots of stakeholders, make sure they meet those stakeholders and have buy-in.

Red Flags on Both Sides

Ceci [19:39]

When do you know a Chief of Staff and founder pairing isn't going to work? Are there early warning signs, or what do you tell founders to look out for?

Gaby [19:52]

It's like real-life relationships. There's someone out there for everyone, but you have to find the fit. You have to be really clear as a candidate on what your non-negotiables are. Is it that values are really aligned? Is the founder really people-centric in his thinking? Or actually, do you care about pure ambition and the high-intensity culture they set? It's on you to test for those in the conversation. If a low-ego founder is important to you, ask in the conversation: how do you think about your strengths and weaknesses? You're allowed to have those conversations.

Then trust your instinct. I push people to be really clear on what they like and what they work with well, and to facilitate environments where those things can show up. The first 30-minute call, a separate coffee, speaking with other stakeholders.

Bea [21:19]

Feeling empowered to ask the questions: how do you work, what kind of people create friction with you. As a Chief of Staff you need a trusted symbiotic relationship with your CEO. If you don't feel comfortable asking those questions to begin with, that's probably a red flag. You're going to have to create a deep bond based on trust. If the founder isn't willing to share openly, that would be my biggest red flag.

Gaby [21:54]

It's funny. In interview processes as a candidate, you can feel maybe not so empowered to ask. You're conscious about how it comes across. But it's a non-starter if that relationship just isn't working. It's so important, it's the single person you'll chat to every day about everything. If you don't have that chemistry, it's impossible.

Why 80%+ of Chiefs of Staff Are Women

Bea [22:20]

Controversial question. Is there a typical background for Chief of Staff that you've found to be successful? VC, consulting, something else? And, why do I only know women Chiefs of Staff? Where are all the guys? Does it work because founders tend to be male and we tend to be good support for them?

Gaby [22:54]

First, in terms of profile, there isn't anything typical. The most typical you might get is a foundation in consultancy, VC, or investment banking, plus one or two years in an operating environment doing something like growth, product, or ops, and then they elevate into the Chief of Staff role. That's about as typical as it gets, but profiles can be really varied. The one thing that is consistent is that whatever role they've done, they've had really tangible impact. The execution point has been really clear. Someone who cares deeply and can really point to where they've moved the needle, that stands out more than tier-one names.

To your second question: I speak to Chiefs of Staff all the time, and I haven't done the numbers, but I'd say 80% plus are women. If you take a step back, what makes a really successful Chief of Staff is the generalist skill set, the ability to context-switch, very high EQ, building relationships at all levels, and being super low-ego. A lot of the work you do as a Chief of Staff is invisible. You have to be happy championing and leveraging someone else. It's not about saying "by the way, that was me." It's, "if this organisation is running super seamlessly, I know that's me." Normally you get called out when things are on fire.

Those qualities tend to lend themselves to women, and I don't think that's a controversial statement. The world of work historically has been set up for men to succeed in different environments. We're seeing a shift. The really interesting thing is, if you believe, and I do, that the Chief of Staff cohort is almost tomorrow's leaders, the platform for the next founders, the next heads of the next C-suite, then we've got an amazing pipeline of women coming up. Will it convert? That's to be seen. But we should see a huge conversion in terms of those women becoming the leaders and future leaders of tomorrow. A pipeline of 80% is pretty nice.

First 30 Days and Why Hires Fail

Bea [26:01]

One last question before rapid fire. You've done the prep, the hire, the Chief of Staff is starting. Why do those hires fail? What can founders do to avoid a Chief of Staff hire that's great on paper from failing?

Gaby [26:19]

From the Chief of Staff side, first, build trust with the founder. Don't pressure yourself, building and earning trust takes time, but start from day one. You cannot do this role without it. Get early wins on the board. If you said you'd do it, do it. "I'll get this back to you by X" — do that. Small habits develop trust over time. Then absorb how the founder thinks, decides, prioritises, operates under pressure. Be in person as much as you can. You want to understand them so well you almost become interchangeable.

Second, build relationships across the team. The first 30 days is coffee chat after coffee chat. You also want to break the misconception of a Chief of Staff being a spy. If they've not had one in that organisation before, there's almost a mistrust about it. Be really clear on how you position yourself internally. Yes, you work closely with the founder, but that has a great business impact for them and how they show up. Develop genuine relationships.

Third, clarity. Communicate relentlessly and repetitively. The role will feel ambiguous in the early days, that's okay. Your role will evolve and you have to be proactive about identifying where you can help. Constantly check in and be clear about what you're working on and why. Communicate it to the people around you, to your founder, to yourself. It's so easy for days to go by feeling busy, but what have I actually moved the needle on?

From the founder side, the single most important thing is communication. They should feel they're over-communicating to the nth degree. In the first 30 days they need to share every thought out loud. I sometimes recommend an end-of-day voice note debrief. Even if no actions come out of it, you get a sense for how they think.

The second is access and authority. This is where most founders accidentally restrict the role before it even starts. A Chief of Staff without authority becomes a facilitator. Be clear about ownership and authority. That's the difference between a good and a great Chief of Staff. They will naturally push on it, but in the early days you need to be quite clear.

The third is delegate properly. Be clear on what you're asking for. It doesn't mean hand-holding, but in the early days, be clear on the ask, then let go of it. Give the Chief of Staff the chance to build trust and deliver for you. Letting go is really hard for founders, so actively use that muscle from day one.

It's hard because when I've placed a Chief of Staff, the founder usually hasn't had one before, and more often than not the Chief of Staff hasn't been a Chief of Staff before. So you sit down and just communicate. "I don't think this is working." Great, fine, let's change it. Acceptance that there will be ups and downs, but we're on the same team, and let's communicate through it.

Rapid Fire

Ceci [29:55]

If you could fix one thing about how the tech ecosystem thinks about the Chief of Staff role, one misconception or one bad habit, what would it be?

Gaby [30:19]

It would be that it's just a trend, just a moment, that in two years we'll look back and ask what the fuss was about. That frustrates me because it undersells what the role actually is and the value it has. The Chief of Staff role isn't popular because it's fashionable. It's popular because the shape of building a company has changed, and this role is one of the best responses to that change. The founders who treat it seriously and scope it properly will feel the difference. The ones who hire because everyone else is hiring will probably conclude it doesn't work, because they didn't do it properly.

Bea [30:55]

A Chief of Staff is not a cheap software subscription you get because everybody else is. It's an expensive hire, so it's an expensive mistake. Definitely not one to take lightly.

Ceci [31:11]

What's one habit that helps you, or other Chiefs of Staff, stay grounded through the rollercoaster?

Gaby [31:22]

A founder told me she does a weekly written reflection. She said: it sounds like you never have time for it, but if I can make time, you can make time. If you sit down at the end of the week and think, "what have I actually achieved, what have I done?" and write it down, that can be really helpful. It's also helped me zone in on the bits I really enjoy and get most energy from versus where I feel weaker. As I think about building a team, that's really helping me get clarity around me.

Bea [32:06]

I used to do weekly newsletters with my BizOps team and it was so much fun. Maybe 10 minutes on a Friday. Lots of random sarcasm, then the list of things we did. At the start of the week I always had this anxiety of, my god, have we even done enough? At the end of the week I'd have loads of bullet points and updates and it'd be, okay, the week has gone by, but I've done something.

Ceci [32:37]

What is a fair salary for a Chief of Staff role at a Series B company in London?

Gaby [32:43]

To caveat, the bandings are always quite broad. The important thing is to hone in on the scope of the role, less around title and stage and more on what the role is actually owning day-to-day and the impact it can have. The market data right now is pointing to about £110 to £125, maybe pushing £130 for a super exceptional person. In pounds. Averaging out around £120 to £125.

Ceci [33:25]

That's a great reference point for founders watching and for other Chiefs of Staff in salary negotiations. There's always a bit of hush-hush around salary. You have the market data, you hire, you consult founders on hiring. So let's just talk it out.

Gaby [33:43]

To add to that, I'd say that's a portion of total comp. You're also expecting meaningful equity. I'd push founders to have a really compelling narrative as to why this person is joining this company and what's the upside potential.

Ceci [34:03]

This was fantastic. Thank you so much for joining us, Gaby. It's been great having you and learning more about what you're doing with Robin and how many founders you're helping.

Gaby [34:13]

No, thank you so much. I've really loved it. This is my first podcast as well, so I'm honoured.

Keep Listening

Will Chiefs of Staff survive the age of AI?
Two operators on the automations they've already built, and why the best Chiefs of Staff are about to become 10x more valuable.
Alejandra Otero: First Principles and Operational Excellence at ElevenLabs
Chief of Staff at ElevenLabs on the Barcelona dinner that changed everything, building a rocket ship at $330M ARR, and why first principles thinking is the job.
From the Board to the Trenches
Two ex-VCs on why they left the boardroom behind, and what nobody tells you about becoming an operator.