The dream is fully self-service: a buyer describes the agent they want, hits create, and the platform generates it. That dream runs straight into a wall the moment a real customer touches it. A sharp, non-technical buyer is being asked to think in terms she has never needed: prompt design, Slack apps, OAuth connections, what a given integration can actually do. The templates are close but not right, and tailoring them requires exactly the vocabulary the product assumes. The product is sound. The market has not caught up to it yet, and that is the product's problem to solve, not the buyer's.
So you put a person in the loop. A junior developer sits between you and the customer, because nobody wants to run two-hour meetings iterating on how to turn vague ideas into real agents. That intermediary is not a failure of the product. It is the shape of the market right now, and it points directly at the business model.
Sell the service. People pay for services everywhere. A funded startup that wants agents for its CS and sales teams is usually about to hire a developer to build them. The pitch that lands is the comparison: for a fraction of that developer's cost, you get an experienced team with a reputation on the line, building your agents. Easy yes. Repeat it a handful of times and you have real revenue and real customer results, and it is far easier to sell than a logo-on-a-page subscription.
The reason services win here is the same reason the forward-deployed model is often the only one that actually works. You are not asking the buyer to learn your abstractions. You are solving their problem and dropping the result into your platform. The consulting conversation, what agents would help your business, doubles as product discovery.
The trap to avoid is putting a price on the page before the buyer can self-serve, because that number becomes the ceiling of what they will pay. Wrap the product in service while the market catches up. The platform is how you deliver. The service is how you get paid today and how you learn what to build for tomorrow.
Key takeaways
- Non-technical buyers cannot author or modify agents themselves, so a pure self-serve product stalls at the configuration step.
- Selling agent-building as a service converts your reputation and expertise into immediate revenue that templates cannot.
- Services are not a detour from the product business; they are how you fund it and learn what to productize.
FAQ
Why can't non-technical buyers just use the templates?
Because they cannot think in the terms the system requires. OAuth connections, MCP tools, automations, what a given integration can actually do. Even a great template needs tailoring, and the buyer does not know how to tailor it.
Isn't a services business a distraction from building product?
No. Services fund the product, surface what to productize, and let you charge based on value rather than a price tag the buyer anchors to. The platform is the delivery mechanism; the service is the wedge.
Related Essays
The Forward-Deployed Model Is the Only One That Actually Works
Every agent needs to be personalized and context engineering is hands-on, so the vendor who embeds engineers inside the customer has a structural advantage. Self-serve ships shelfware.
The Forward-Deployed Engineer Is the Wedge
Forward-deployed engineers are not a cost center. They are the fastest path to turning enterprise pilots into six-figure accounts.
Developers Want Raw Access, Not a Wrapper
Teams have invested months of workflow into their coding agents. Platforms that wrap those agents in proprietary magic are asking buyers to throw that away.
Drowning in pull requests that need your review? Try Tembo Review, a beautiful AI-assisted PR review tool unlike anything you’ve used.