← Back to essays

The Three Services That Sell an Agent Platform

·2 min read·By Ry Walker

Everyone selling agents into the enterprise eventually hits the same wall. The customer wants the outcome, but their team is not ready to operate the product. So you end up doing services. The mistake is treating those services as one undifferentiated blob of "help." They are not. They are three distinct engagements, and if you can name them, you can price them and sequence them.

The first is building agents for the customer. You go in, you use your platform to construct the general agents they actually want, and you hand them a working system. This is the most concrete and the easiest to sell, because the deliverable is obvious.

The second is readiness. This is forward-deployed adoption for your core product. A CEO tells you their engineers claim to use AI but are barely faster. They are right to be suspicious, because those engineers are almost certainly using AI as a fancy autocomplete, not delegating real work to it. Service two is loaning a developer for two weeks to sit on their team, connect the tooling, write the opinions file, wire the integrations, and show them what full delegation looks like. In a perfect world you would not need this. In the real world, the infrastructure to support agents is never set up right.

The third is just building the thing for them. Software development services, done with your own agent platform. It is the least scalable of the three, but some customers love the vision and have no devs willing to execute it, and meeting them there beats losing them.

Here is the strategic point. None of these three is the business. The business is the product. Each service exists to convert the customer into a product user. Service one requires hooking the product up, which creates product usage. Service two is literally adoption. Service three puts your own engineers in the seat of the user, which is the fastest way to improve the thing.

That is why a software-first company can run services at break-even and still win. If services were your whole company, break-even would mean a broken business. As an add-on to the product, break-even is a bargain. You are buying adoption, reference cases, and hard-won context at cost. Name the three, sequence them toward the product, and stop pretending services is the destination.

Key takeaways

  • Enterprise agent adoption breaks into three service types - building agents for the customer, readying their team for agentic engineering, and doing the build yourself.
  • Each service engagement exists to convert the customer into a product user, not to become a standalone consulting revenue line.
  • A software-first company can break even on services because the real return is product adoption and reference cases, not services margin.

FAQ

Why would a software company run services at break-even?

Because the services are an add-on to the core product. The return shows up as product usage, reference customers, and pipeline, not as services profit. A dedicated services firm must profit; a product company just needs the door opened.

How do you keep services from cannibalizing product focus?

By treating every engagement as a wedge into product adoption. The moment a service stops driving people toward using the platform themselves, it stops earning its place.

Tembo

Drowning in pull requests that need your review? Try Tembo Review, a beautiful AI-assisted PR review tool unlike anything you’ve used.