Build your core. Partner to make the most of it.
Common questions about building your own agent
Should we build or buy our AI agent?
It's not a question of build vs. buy. Build your core. Partner to make the most of it. Your core is what customers pay you for: proprietary data, domain-specific algorithms and the product-specific agents only your team can build. Partner for the hands and eyes in the product: the Product Agent acts for users or works in tandem with them through your APIs, and Conversational Analytics shows what they asked for.
We already built our own agent. Where does Foldspace fit?
Beside it. Your agent keeps the domain reasoning. The Product Agent hands it a task over the A2A protocol when a request needs its skills, shows the result in the conversation, and does the work in the product with actions, navigation, Tandem and Generative UI. A multi-product platform that already had its own agent loop added the Product Agent to work beside it: 3 products, 1 sprint, 1 engineer on their side.
What does my engineering team still own?
Everything your customers pay you for: your APIs, permissions, business logic, domain models and product-specific agents. Actions are yours too. With the Developer plugin they're typed code in your repo, versioned and code-reviewed like everything else you ship, and each action handler runs in the user's browser with their session. Foldspace runs the agent loop, real-time context and the inference gateway.
Why do in-house AI agent projects stall?
Often because most of the effort goes to the layer inside the product, not to the domain logic. Before the agent does anything specific to your product, the team has to build the loop that chains actions and stops safely, per-turn context, navigation routes, Shared State for Tandem, Generative UI, voice, identity signing and intent analytics. It happens to strong teams. That layer is its own discipline.
What happens when a product team builds an AI agent from scratch?
Vidmob's product manager wrote about her team's build. They spent months building an agent in-house, and it stalled: it only ever launched behind a feature flag, and adoption stayed low. She called it "a massive prompt engineering experiment that delivers less value than you expected." On Foldspace, they had something more flexible within a week, and she now makes most changes herself, rarely needing an engineer. Read her post.
How long does it take to build an agent in our product?
The build takes minutes. The Agent Builder builds a working Product Agent on your own product with Claude and a Chrome browser, and building it changes no product code. Minutes is the build, not production: it asks before publishing anything, and going live is one snippet and your team's approval. Start free.