Broccoli's Ashby Board Beats a Headcount Story

Broccoli AI's Ashby board listed 33 open positions when we checked it in early November 2026. Titles spanned sales, engineering, product, marketing, customer success, strategy, and a Talent Operations Associate seat. Cities included San Francisco, Lehi, Utah, and Bangalore, with a mix of on-site, hybrid, and remote lines. That titled list is the research record a boutique desk can audit. A story that the company grew from 15 people to more than 150 is a headcount history. History is not an open requisition list.

Secondary business reporting around October 30 and November 1, 2026 attributed a $52 million Series A and B package, Khosla leadership, and hiring plans for engineers and sales to coverage of a Fortune interview. We did not find a matching primary funding post on Broccoli's own site during this pass, so financing claims stay in a secondary-reporting field. The Ashby board does not need that field to be useful. Broccoli Ashby board, accessed November 2026. Broccoli careers page, accessed November 2026.

What the board actually lists

Ashby's thirty-three lines included Account Executive seats for enterprise and mid-market, multiple AI strategy and transformation leads, Head of Engineering, Head of Enterprise Sales, Head of Growth, Head of Marketing, Head of Revenue Operations, Head of AI Success, product and senior product managers, software engineers in San Francisco, software development engineers in Bangalore, AI tech support and SDR seats in Lehi, and Talent Operations Associate in San Francisco. Work modes were printed per role. Do not collapse every title into "SF on-site" because the company is based in San Francisco.

The careers marketing page states work locations as San Francisco, Lehi, and Bangalore, and lists benefits such as medical coverage, 401(k), equity, PTO, parental leave, and a $200 monthly Broccoli Boost. Those lines help candidate conversations later. They do not create a job order for an outside recruiter today.

How headcount growth gets misused

A report that headcount moved from 15 to more than 150 over twelve months can explain why a board is busy. It cannot tell you whether the open role is Staff Software Engineer in San Francisco or SDR in Lehi. It also cannot tell you how many of the 150 seats are already filled versus still open. Past hiring is not the same artifact as current titled openings.

If secondary coverage says the company plans to hire engineers and sales, open Ashby and name the engineering or sales title you mean. "They plan to hire engineers" is not a brief. "Staff Software Engineer, San Francisco, on-site, accessed November 2" is a brief you can defend.

How to log Broccoli cleanly

1. Board title list with city and work mode, plus access date.
2. Careers-page location statement stored separately from individual role modes.
3. Financing and headcount-growth claims labeled as secondary reporting until a company primary page confirms them.
4. Talent Operations Associate marked as an internal staffing signal.
5. Agency access and fee left blank until a human answers.

Thirty-three titled Ashby roles are a research inventory. A 15-to-150 headcount story is background. Outreach needs titles and cities.

Who should ignore this board for now

Ignore it if you do not place home-services SaaS, AI ops, or multi-hub engineering seats. Ignore it if you cannot work San Francisco on-site or Lehi hybrid roles and the Bangalore lines are outside your geography. Ignore it if a Talent Operations seat on the board means, in your process, that outside agencies wait until internal ops is staffed.

This market note does not claim Broccoli uses agencies, does not treat secondary funding coverage as a company blog, and does not freeze the thirty-three count as permanent. Boards change. Re-open Ashby before follow-up. The useful habit is refusing to let a headcount narrative write your job-order fields.

San Francisco lines on the board include multiple Head of seats. Those are leadership searches with on-site expectations on the rows we read. Lehi rows skew toward support, implementation, and SDR style coverage. Bangalore rows are software development engineer levels. Pitching a single "engineering hiring spree" email that ignores hub differences will read as lazy to anyone who opened Ashby for thirty seconds.

Talent Operations Associate in San Francisco should change your first question from "do you use agencies" to "who owns overflow for SF versus Lehi." Internal ops capacity is hub-specific at multi-site companies. Log the seat, then ask for the rule by location.

Secondary funding coverage can wait in a parking lot field. Your outreach does not need Khosla or a $52 million figure to name Staff Software Engineer in San Francisco. It needs the title, the mode, and a clear ask about agency process.

If you only work retained executive search, the Head of Engineering and Head of Enterprise Sales rows may be your only relevant lines. Say so in the CRM and hide the rest. Coverage discipline is part of multi-hub hygiene. A board with thirty-three roles is not an obligation to pitch all thirty-three.