Broccoli Raises $52M for Home Services AI Across Two Rounds

A dispatch-fee policy is a small detail until software tells a homeowner the wrong thing. In the customer letter accompanying its financing news, Broccoli describes an office manager asking for fees to be handled her team's way, a reminder that an AI receptionist inherits the business decisions behind the greeting.

The San Francisco company announced $52M across its Series A and Series B rounds on October 28, 2026. Khosla Ventures led both financings, completed 9 months apart, with Y Combinator and Operator Partners participating. Broccoli plans to accelerate hiring and expand AI capabilities across the customer journey for home-service businesses.

That assignment reaches from answering a call to maintaining a relationship after a technician leaves. Broccoli's financing puts more resources behind a specific form of vertical AI: software that must understand how a contractor accepts work, carries it out and earns the next visit. For operators buying the product, its usefulness sits inside those connected decisions.

Two rounds finance a broader customer relationship

Broccoli's $52M announcement combines Series A and Series B financing. Keeping those rounds separate matters when interpreting the capital: the headline describes money raised across 2 rounds, rather than a single $52M Series B. The company-issued release identifies the aggregate and investor group without providing exact closing dates for each round.

The company says the proceeds will support hiring and expanded AI capabilities. That gives the financing an operating purpose beyond adding another call-answering feature. Broccoli already describes workflows involving estimates, memberships, customer follow-up and information gathered before a service visit, creating several places where a contractor's own rules must shape an automated action.

Y Combinator's company profile identifies co-founder AJ Jain as CEO and co-founder Aditya Ketkar as CTO. The founders previously built Telematica, an energy-management business. Their current work brings software into another physical operating environment, where a system's decision eventually reaches a person responsible for doing the job.

The first customer remains inside the business

Marcelle Flowers, formerly CEO of Armstrong Plumbing, is now Broccoli's Chief Industry Officer. The founders' October 28 customer letter places Armstrong at the beginning of the product and describes working from Flowers's office while learning how the business operated.

That relationship gives Broccoli a source of industry judgment inside its own organization. The distinction has practical weight as a product grows: somebody needs to recognize when a feature fits a demonstration but fails to accommodate the way a shop actually works. Flowers's experience belongs close to that conversation, particularly when the customer is handing over the first interaction with a homeowner.

The founders describe several requests becoming features, including Spanish-speaking support, dispatch-fee handling and booking alerts linked directly to a CRM job. Taken together, these examples explain how customer learning accumulates in the product. Each request carries a different kind of context: language, commercial policy or the office team's ability to find and act on new work.

Booking work connects AI to technician capacity

Broccoli markets inbound calling, outbound follow-up, lead response, call quality review and website chat. Its homepage also identifies integrations with ServiceTitan, Housecall Pro, Salesforce and AccuLynx, positioning the agents around systems contractors already use. These are the company's descriptions of product capabilities, rather than independent performance benchmarks.

The integration is commercially significant because accepting an appointment creates obligations elsewhere. A service area determines whether a visit is workable, a dispatch rule shapes who should attend, and the available schedule limits what can be promised. An agent taking bookings needs information that extends beyond the caller's immediate request.

That makes configuration and implementation part of the buying decision. A contractor evaluating Broccoli can examine how booking rules are represented, how changes reach office staff and how the company handles situations requiring a person. Those questions follow directly from the product's role in customer operations; the funding announcement supplies no universal measure of how well every deployment resolves them.

Reported activity establishes scale, with limits

Broccoli reports that more than 1,500 home-service businesses use its platform. The company names Ace Hardware Home Services, Any Hour Group, Mr. Electric and Authority Brands among its customers, and says the platform has handled more than 10M customer conversations and booked 2.5M service and sales appointments.

Those figures describe company-reported activity. A conversation count measures use, while an appointment count records a further step in the commercial process; neither should be read as a count of completed jobs or as independently audited revenue. For an operator, the relationship between those measures and the work actually delivered remains important when assessing a deployment.

The product spans HVAC, plumbing, electrical and other home services, giving Broccoli multiple sets of operating details to accommodate. A common conversation interface can provide a useful starting point, while the individual contractor still brings its own service boundaries and customer expectations. Broccoli's stated expansion across the customer journey increases how much of that context the software may need to carry.

Hiring expands the people behind the agents

Broccoli's careers page lists San Francisco, Lehi in Utah and Bangalore as work locations. The company says it is growing its teams, consistent with the hiring priority attached to the financing. Engineers and industry operators therefore share an assignment that reaches beyond improving how an agent sounds.

As the product takes on more interactions, decisions made in one part of the workflow can become relevant somewhere else. An estimate follow-up should reflect the job being discussed, and a membership conversation belongs to an existing customer relationship. Building those connections gives customer information a longer useful life inside the contractor's operation.

Broccoli's account of its beginnings puts an office manager's fee policy close to the software designer. The next stage of hiring will add more people between the original customer request and the eventual feature, making that flow of operating detail an ongoing responsibility for Jain, Ketkar, Flowers and the teams joining them.