The Front Desk Audit

The cheapest hire you'll make this year is going to find $74,000 you didn't know you were spending.

You're not going to find it yourself. You can't. Your founder chair was built so you couldn't.

A founder I've been working with for two months found his $74,000 the same way every operator I've ever watched find one. He sat in someone else's seat for a couple of weeks, watched a workflow he'd never seen up close, and walked out with two pages of notes about money routing into a wall.

He didn't go looking. His head of customer success went on parental leave in April and his senior CSM was on PTO the same week. He had to cover the renewal inbox himself for 14 days. He told me on a Friday, with the kind of laugh that wasn't a laugh, that he'd learned more about his company in those two weeks than in the previous nine months of dashboards.

The piece this week is about the chair.

Connect your email, calls, product data and more, and Attio instantly builds your CRM with enriched data and complete context. Whether you’re running product-led growth or enterprise sales, Attio adapts to your unique GTM motion.

Then Ask Attio to plan your next move.

Run deep web research on prospects. Update your pipeline as you work. Find customers and draft outreach emails. Powered by Universal Context, Attio's intelligence layer, Attio searches, updates, and creates across your data to accelerate your workflow.

Ask more from your CRM.

Ask Attio

I'll spare you the full inventory. The headlines were enough to get my attention.

Three customers had been re-submitting their integration credentials every quarter because the API token rotated and nobody had documented the renewal step. Each one of those tickets ate two hours of his senior CSM's time and ended with the customer apologizing for being confused. The workflow was broken in a place no dashboard he owned looked.

Five accounts were paying for licenses they hadn't activated in more than six months. His billing dashboard counted what they bought and never checked what they used. Those customers were going to notice on the next renewal call and pull the unused seats out of the contract. About $38,000 a year of soft revenue, already gone, still showing up on his ARR slide.

One AE was sending a 14-page onboarding doc to every new customer. The CSM had built it 18 months earlier when the product had a different shape. Nobody read it. Nobody told the AE to stop sending it. The AE kept sending it because it was on his welcome-sequence checklist.

A $4,200-a-month vendor invoice was hitting his card for a CRM enrichment tool that his head of revops had canceled in January. The cancellation had gone through inside the tool's dashboard. The credit card line item had not. The vendor's renewal email had been routing to the inbox of a CSM who had left the company. Nine months of invoices, paid on autopilot, for a service nobody was using.

That's $74,000 of leaks in a single CSM queue, and that's only the part he could find by sitting there. He's at $4.2M ARR. He thought his big problem was top-of-funnel demand.

Here is the part founders skip when they read a story like this.

He is not a bad founder. He is not lazy, distracted, or under-equipped. He has been building software companies for 11 years. He'd run an ops function inside a much larger company before founding this one. If you told him in November he had $74,000 leaking out of his customer success queue, he'd have walked you through every dashboard he owned to prove it wasn't possible.

Every one of those dashboards would have looked right.

The founder chair has a geometry. Every dashboard on it was scoped by you. Every report routing up was selected by somebody who decided you needed to see it. Every customer escalation in your inbox is one your team couldn't resolve. Every pipeline review covers deals above the threshold the team thought worth flagging.

Everything below that threshold, everything on a screen nobody built, everything that gets handled by a person doing it the same way they did last month, sits in a layer the chair cannot see. The role is engineered to surface what's been escalated and to absorb what hasn't.

The team absorbing the work is doing what good teams do. The senior CSM was re-walking the integration step for the three customers because the customers needed help and she's the kind of person who helps. From her chair, it looked like part of her job. The AE sending the 14-page doc was hitting the line item on his checklist. The card paying the vendor invoice was nobody's checklist. Nobody knew it was theirs.

This is how a growing company distributes the work you used to do across people who don't have your view of why the work exists. The work gets done. The reason for it dissolves. The waste shows up in a layer the chair cannot see.

I have watched this pattern at three growth-stage companies in the past six months. The dollar amounts differ. The shape is identical.

Walk through your own week for a second as a thought experiment. The audit comes later.

You see what your top customers tell you. You see what your sales pipeline reports. You see what your finance lead flags. You see what your direct reports raise as a problem. You see what the board notices. You see what's in your inbox at 11 PM Sunday because somebody escalated it.

Now walk the opposite list. You don't see the support ticket that got resolved on the first reply. You don't see the workflow your CSM has been hand-walking for a year. You don't see the vendor invoice that auto-renewed two weeks ago for a tool nobody opens. You don't see the inbound lead form question your marketing team has been answering by email for 18 months because nobody added it to the FAQ. You don't see the 40-minute conversation your sales engineer has on every demo to set expectations the website should have set.

The first list is the company on your dashboards. The second list is the company in the rest of the building.

At $500K ARR you saw both lists because you were the person doing both. At $4M with 22 people, you have someone doing every job on the second list, and the only way to know whether the job is being done well, badly, or wastefully is to be in the chair for long enough to feel the friction the person in the chair feels.

The dashboards were built for the first list. They will never give you the second one.

You can recover most of what's leaking with a calendar move and the discipline to sit somewhere unfamiliar for two weeks. Here are five steps. The first one is the only one you can't delegate.

Sit in a chair you've never sat in. Cover a CSM queue for two weeks. Shadow an SDR for three days. Sit in on every onboarding call this week. Pick a role that touches customers, money, or both, and stay in the seat long enough that the person whose job it is forgets to perform for you. One day is performance. Two weeks is reality.

Hunt for the leaks. Stop measuring productivity. You will not learn anything new about productivity. Look for what gets done twice, what gets done by hand a script could finish, what gets paid for and ignored, what a customer is asking you to do that you already did once. Carry a notebook. Three pages of leaks is normal. Five is common.

Audit 12 months of vendor invoices. Pull every recurring charge on every card. Map each one to a tool somebody on the team uses every week. The lines that don't map need a phone call. Most growth-stage companies are paying for three tools they no longer touch, two licenses for a vendor they've replaced with a competitor, and one annual contract that auto-renewed for a service nobody has logged into since last summer. This part of the audit almost always pays for the rest of it in a week.

Hire the operator function. A fractional ops lead, a senior CS hire with operating chops, a chief of staff with budget and decision authority. The point of the role is to make the invisible visible to the person paying for it. The number this hire should be measured on is dollars found and friction removed. If month one is a status report instead of a leak inventory, you hired the wrong operator.

Build the dashboard you wouldn't have built. Whatever the audit surfaces gets a one-page weekly readout. The point of the readout is to make sure the leaks can't dissolve back into the substrate the second your attention moves. The dashboards you have now confirm what you thought was true. You need at least one that surfaces what you don't know yet.

Five moves. The first is the calendar block. The rest are downstream of it.

Capturing attention across TV, search, and social is harder than ever.

Now there’s a way to reach high-intent audiences during the planning phase, on the biggest screen in the house.

Worth a look if you want to prove the value of spending on TV.

Get Started Today

The first is the time cost. Two weeks in someone else's chair feels expensive when your week is already over-allocated. It is expensive in the moment and the cheapest two weeks you'll spend all year by August. Every founder I've watched do it has come out with a multi-five-figure leak inventory and a new appreciation for the people whose chairs they sat in.

The second is the trust question. Founders ask me whether sitting in a CSM's chair signals distrust of the person sitting there. It can, if you do it badly. The fix is to be straight about why you're there. You are auditing the role and the workflow the role inherited. Tell your CSM you want two weeks to understand what their day looks like, that you suspect there are workflow patterns nobody has had time to clean up, and that you want to see the shape of the work from inside the seat. The CSMs I've watched go through this come out relieved. They've been waiting a year for somebody at the founder layer to notice the integration token thing is broken.

The third is the operator hire. Founders push back on bringing in a senior operations person because they don't see the slot on the org chart, the budget is tight, and the existing team is doing its job. The slot you don't see is the one I'm pointing at. The operator hire is the layer that translates the work the team is absorbing back into visibility for you. Without that layer, the dashboards stay the same, the leaks compound, and you have this conversation again next April when somebody else goes on leave.

Back to the founder I opened with.

He killed the vendor invoice that morning, which gave him back $4,200 a month. He replaced the 14-page onboarding doc with a four-minute Loom, which his AE started sending the next week. He pulled the three integration-credential customers onto a 30-minute group call with an engineer and documented the renewal step, which removed about eight hours of CSM work per quarter on a recurring basis.

He brought in a fractional ops lead in early May at $4,000 a month. The leak inventory the ops lead built in his first three weeks surfaced another $30,000 of waste in adjacent workflows that hadn't shown up in the CSM queue. They're working through it this quarter.

The five unused seat licenses got handled differently. Instead of waiting for renewal and watching the customers cut them, he had his head of CS offer each account a credit toward unused seats in exchange for a longer-term commitment on the seats they were using. Three of the five accepted. Two upgraded to add new seats in a different module. A churn conversation at renewal turned into an expansion call in May.

He did not cut a dollar of marketing spend. He didn't have to. The leaks were offsetting the demand he was paying for. Plug the leaks and the marketing math gets four times more efficient by accident.

The most expensive thing he did this year was the two weeks he spent in his CSM's chair, because that was the week he learned he'd been running the company from the wrong seat. The cheapest hire he made was the fractional ops lead. Within 90 days, the ops hire had paid for itself nine times over and was on track to clear a quarter million in unblocked revenue and recovered spend by year-end.

The founders I work with all want the same thing: more output from their hours. They keep looking for it in the chair they're already sitting in. They tighten the dashboards they built. They push harder on the levers they understand. They optimize the funnel already on the screen.

The hours are in the chair you haven't sat in. The reason the hours are still there is because nobody in your chair has ever sat in the other one.

The founder I opened with told me, on the call where we walked through the audit, that the hardest thing about the two weeks was not the work. It was the moment on day four when he realized his CSM had been carrying a workflow problem for a year without escalating it, because from her chair it had always looked like part of her job.

Whatever your CSM thinks is her job that shouldn't be, you can find out in two weeks. Whatever vendor is billing you for nothing, you can find out in an afternoon. Whatever onboarding doc nobody reads, you can rewrite as a Loom by Friday.

The $74,000 is sitting on somebody's desk this week. Find which desk it is and sit there for a couple of weeks.