A services firm that ships software, prices against outcomes, and reuses agents across customers is not the same business as a traditional consulting firm with AI bolted on. The unit economics are different. The scaling curve is different. The exit math is different. The decade's defining companies in enterprise AI will look like the first kind of firm, and the capital that recognizes this earliest will hold the positions that the capital recognizing it later will not be able to win back. This post is the strategic case for the model.
Three components that have to work together
The economic structure has three components that have to work together. Services pricing, software economics, and end-to-end automation of the discovery-to-deployment arc. The customer relationship is worth multiples of a SaaS seat (because the customer is paying for the work to get done, not for access to a tool, and the work has services-tier pricing power). Marginal engagements do not require marginal teams (because the agent infrastructure built for previous customers handles most of what each new customer needs, and the human team scales sub-linearly with customer count). The discovery and integration work that consumed most of the cost in the consulting model is automated (because the agent does the discovery as a side-effect of being installed, and the same agent does the integration as the substrate of the production deployment). Each of these three components is necessary; none of them is sufficient on its own. A consulting firm that adopts outcome pricing without the agent reuse is still a consulting firm; it just has a different P&L. A SaaS firm that adopts services pricing without the embedded delivery is still a SaaS firm; it just charges more per seat. The combination is what is novel.
Why agent reuse changes the scaling curve
The scaling curve is the property that makes the model venture-backable rather than just operationally interesting. A traditional consulting firm scales linearly with headcount: revenue equals consultants times utilization times bill rate. There is no leverage; the next dollar of revenue requires the next consultant. A services-as-software firm scales the way software does once the agent reuse compounds. The first ten customers cost most of the engineering work to build the underlying agent infrastructure. The next hundred cost a fraction of that effort, because the infrastructure already exists and each new customer's needs are a configuration of capabilities the infrastructure already supports. The next thousand cost a fraction of that. The marginal cost of delivery falls as the customer count grows, which is the property that makes software a venture asset class and the absence of which is what makes traditional services a private-equity asset class.
The labor TAM versus the software TAM
The exit math, the third component of the strategic case, is the one that public-market and growth-stage investors are still working through. Sequoia's framing is six dollars of services spending for every one dollar of software spending; the labor TAM that AI now addresses is six times the size of the software TAM that SaaS addressed in the previous era. General Catalyst's Bhargava puts the ratio at fifteen times when the comparison is global services revenue against global software revenue. Foundation Capital's headline number is the four-and-a-half trillion services TAM their April 2024 piece coined. The point is not the precise multiple. The point is that the addressable market for services-as-software companies is roughly an order of magnitude larger than the addressable market for SaaS companies was, and the category-defining company in this market will accordingly be roughly an order of magnitude larger than Salesforce.
Addressing the AI roll-up counter-thesis
Engaging the counter-thesis directly is necessary at this point, because the most sophisticated objection to the venture-scale framing is the one Fortune wrote up in June 2025. The Fortune piece argued that AI roll-up investors think services firms can trade like software companies, and they are wrong. The data behind the piece is real. Concentrix and Genpact have deployed gen-AI at more than a thousand customers each. EBITDA margins remain at roughly ten percent. Multiples remain in the single digits. The Fortune line is the one to reckon with: AI roll-ups may still deliver returns, but not the kind VCs are underwriting; at best, tech-enabled PE.
The distinction worth making in response is the one made in the earlier post on services-as-software versus roll-ups. Concentrix is a tech-enabled services firm bolted onto a traditional services business. The pricing power is bounded by what the customer used to pay the non-AI version of the same service, because the customer can always go back to a non-AI provider in the same category. The firms that are built as services-as-software from inception (Crescendo, Eudia, Crete, Manifest OS, Crosby, Long Lake) are not bolting AI onto a legacy services business; they are building the entire business with software economics from the start. The customer of these firms is not comparing the offering to a non-AI version of the same service; they are comparing it to the in-house team they do not have. The pricing reference shifts from cost-of-service to cost-of-labor-displaced, which is the order-of-magnitude larger number. The exits will trade between the two depending on which model the firm actually built, and the firms that built the second kind will trade like the second kind even if they have services as a delivery mechanism.
Why the market window for services-as-software is open now
There is one more strategic point worth landing on. The market window for building this kind of firm in this category is open now and will not stay open indefinitely. The customer demand is real and growing (every operating business that watched the four-delivery-model post is a potential customer of the third layer the previous post described). The technology is finally adequate (foundation models can do the unstructured-input judgment work that was the structural bottleneck for fifteen years). The talent is reorganizing around the FDE shape (every published thesis from a major venture firm in the last twelve months names this directly). The capital is committed (more than three billion dollars has gone into adjacent strategies, and dedicated services-as-software funds have launched alongside). The next several years will determine which firms reach scale first, after which the category will consolidate around the winners and the late-stage capital will stop being available to the firms that did not move early enough.
Horizontal versus vertical services-as-software bets
A reasonable counter at this point is that the horizontal services-as-software bet (across verticals) is harder than the vertical bet (one industry at a time), and the vertical firms will win because the data and integrations compound faster within a single vertical. There is something to this. The vertical bets do compound faster within their vertical. The horizontal bet wins on a different dimension. The agent infrastructure that does observation, redesign, and deployment is the same regardless of the customer's industry; it reuses across customers in different verticals in a way that the vertical firms' integrations cannot. The vertical firms own a vertical's worth of data. The horizontal firms own the discovery-to-deployment infrastructure. Both can be venture-scale; they are not in direct competition because they capture different parts of the same market. flowscope is one of the firms building the horizontal version of the bet.
The bet is straightforward. The largest unaddressed market in enterprise AI exists, and the four existing delivery models do not serve it. The technology to address it now exists. The delivery model that fits the work has been described in detail across this sprint. The capital, the talent, and the customer demand are all in motion. The decade's defining services-as-software firms are being built now. The question is which firms reach scale first, and flowscope is building one of them.