Anchor Growth Partners

At a Glance

• Founding Year - 2015
• Location - Denver, Colorado
• Industry - B2B SaaS (Workforce Management and Scheduling)
• Revenue - $67M
• Number of Employees - 112
• Current Stage - Series C
• Starting HQ Score - 47/100

About Anchor Growth Partners

Anchor was founded by James Liu, who appears throughout the Headroom HQ narrative as a CEO who understands the importance of operational infrastructure while remaining primarily oriented toward revenue growth and product.

Anchor Growth Partners is a B2B SaaS company that sells to mid-market organisations and reached $67M ARR on the back of a Series C hiring surge that took the company from forty-two to sixty-one employees in six months.

At this scale, Anchor is precisely in the phase most SaaS companies describe as their hardest which is too large for founder-managed operations, too small for public company infrastructure, and moving fast enough that the decisions made today about operational structure will determine whether the company arrives at scale efficiently or expensively.

His relationship with Marcus Webb is one of the more instructive in the series. James is a CEO who genuinely wanted an excellent COO and had to learn what that required in terms of authority delegation, board preparation, and the willingness to have the uncomfortable conversations about what the operations function could not yet do.

Anchor's growth from $40M to $67M ARR over 18 months was the testing ground for every framework Headroom HQ addressed under Measurement Sophistication, Technology Coherence, and Decision Rights Clarity.

When Rachel Chen noticed the change in James's questions in August which was a shift from revenue metrics to questions about documentation, vendor contracts, and operational continuity, she understood before James confirmed it that an acquisition conversation was underway.

The fourteen months of exit preparation work that followed produced a data room that the buyer's integration lead described as the cleanest they had seen in the category. The operations due diligence completed in eleven days rather than the twenty-two-day benchmark.

The company's operational story in Headroom HQ is told through two voices:

Elena Costello, VP of Business Operations, built the operations function from within over fourteen months before Marcus Webb joined as COO.

Their working relationship — Elena's institutional knowledge and operational execution capability combined with Marcus's strategic framing and board communication produced results that neither would have achieved independently.

Together they turned an operations function that was receiving six to nine minutes of board attention per meeting into one that received twenty-two minutes and drove a $220k investment approval that had been deferred twice.

Anchor's board is engaged and demanding in the way that Series C boards tend to be. The lead investor, a former public company CFO sent Elena a four-sentence email after her seventh board presentation that changed how she thought about operational reporting:

"Your presentation contained a lot of data. I read the operations section before the meeting and I still cannot tell from your slides whether Anchor is running better or worse than it was six months ago."

That email is the origin of the Finance-Operations Translation Framework, the one-page board format, and most of what Anchor's operations function became.

Primary Challenge

A B2B SaaS company scaling toward a $100M exit, where the operations function went from a reporting function to a valuation driver in 14 months.

The Team

Elena Costello, VP of Business Operations

Elena Costello had been at Anchor for fourteen months when Marcus Webb joined as COO. She understood the company's operational history more deeply than anyone except the founding team and had navigated the shift from a builder role to a strategist role while remaining genuinely close to the operational details that made her analysis reliable.

She is the person who kept a running list called "Things I Do Every Week That a Machine Should Be Doing" for fourteen months, identified twelve hours per week of intelligent but non-judgmental work, and automated five of eleven items in a single Saturday afternoon while tracking the exact return on investment.

Marcus Webb, COO

Marcus Webb joined Anchor as COO twelve months after the Series C, walking into three problems that nobody had named:

• Three teams working on overlapping initiatives without knowing it
• A new hire cohort that had developed eleven different working models of their own authority
• A founding team's cultural understanding that had not been transmitted to the company's newest third.

He spent his first month assessing before proposing a single solution.

Marcus is methodical, comfortable with honest assessments that produce difficult conversations, and specific about what each level of the organisation is accountable for in ways that prevent the bottleneck from re-accumulating.

Daniel Torres, Head of Revenue Operations

Daniel Torres had been leading Revenue Operations at Anchor informally for eighteen months before Marcus formalised the role.

When Marcus asked him whether he wanted the independent leadership position, Daniel's answer was: "I have been making these decisions for eighteen months. The only difference is that you have been the signature on all of them."

That clarity told Marcus what he needed to know about readiness.

Daniel led the customer onboarding process redesign that reduced average implementation time from fifty-two days to thirty-four days. The entire improvement came from the transitions between functions, not from improvements within any single function

Rachel Chen, Chief of Staff

Rachel Chen has been James Liu's Chief of Staff for two and a half years. She led the exit readiness programme alongside Marcus, managed the data room construction for the due diligence process, and ran the dry-run due diligence that identified eleven documentation gaps before the buyer's team arrived.

Five formatting gaps addressed in two days, three access problems resolved through system exports, and two genuine ambiguities documented as known operational uncertainties in the risk register.

The dry run made the difference between an eleven-day due diligence and a twenty-two-day one.

Is it relevant for me?

The Anchor Growth Partners case studies are relevant if,

• You are an operations leader at B2B SaaS company between $40M and $120M ARR, particularly those preparing for acquisition, navigating a post-Series C operational build-out, or working to translate operational performance into language that boards and financial decision-makers can act on.
• You are managing an accumulated technology stack that has never been formally audited.