> ## Documentation Index
> Fetch the complete documentation index at: https://relevanceai-docs-tsp-1332.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Solution Engineering
> Put AI Agents to work across pre-sales technical work — RFPs, demos, discovery — so SEs spend time architecting solutions, not chasing documents.
Solution engineers spend half their time on document work — RFP responses, security questionnaires, demo prep — and half on the strategic conversations that actually win deals. AI Agents take the document work so SEs can focus on the architecture and the relationships.
## Start with a Marketplace template
The Marketplace ships pre-built Agents you can clone in one click. Adapt them to your products, your security posture, your standard demo flow. Or [build a custom Agent from scratch](/build/introduction).
Pre-call research for discovery and demo prep — pulls company, tech stack, and stakeholder context before you walk in.
Upload an RFP or security questionnaire plus your knowledge sources — get a filled draft back with citations and trust scores.
The full catalog of Agents — RFP, security review, demo prep, discovery synthesis.
Click **Clone Agent** on any listing, connect the systems it needs (CRM, document storage, security reference docs), and run on a real opportunity.
## Pick your path
How hands-on do you want to be? Pick a tab — the rest of the page is written for you.
You don't need to touch the builder. Open the cloned Agent above, ask in plain English, and let it work across the systems it's connected to.
## Sharpen the answers with knowledge
Upload your security questionnaire archive, prior RFP responses, architecture diagrams, and standard demo scripts. Every conversation references them — sharper output, no new setup.
Upload context once. Every conversation references it.
## Make it run on its own
When the same kinds of opportunities keep landing, set a trigger — every new SE-flagged deal gets a demo-prep brief, every inbound RFP triggers a first-pass response. One toggle, no code, no builder.
Schedule runs, fire on CRM events, listen to webhooks.
## Ready to go further?
When prompting and templates stop being enough — when you want the Agent to follow your exact security posture and orchestrate multi-doc deliverables — pick the **Build visually** tab above.
You're comfortable in product UIs. You don't want to wire up an Agent from scratch, but you do want it to draft RFP answers in your exact voice and reference your real architecture decisions. Open the cloned Agent in the builder and shape every piece.
## Connect the tools it needs
SE Agents work best when they can read from and write to the systems your team already uses.
* **CRM** — [HubSpot](/integrations/popular-integrations/hubspot) or [Salesforce](/integrations/popular-integrations/salesforce) for opportunity context
* **Document storage** — [Google Drive](/integrations/popular-integrations/google-drive), [Notion](/integrations/popular-integrations/notion), [Confluence](/integrations/popular-integrations/confluence) for prior RFPs and architecture docs
* **Security reference** — your past security questionnaires, SOC 2 evidence, policy docs
* **Comms** — [Gmail](/integrations/popular-integrations/gmail), [Slack](/integrations/popular-integrations/slack) for delivery and internal review
See more about [Integrations](/integrations/introduction).
## Shape every surface
Each piece below changes how the Agent behaves. Run it on a real opportunity between every change — small iterations beat big rewrites.
Edit the system prompt to match your team's tone, your security posture, your standard demo flow.
Add or remove the actions the Agent can take — search past RFPs, query the CRM, draft response docs, run another Agent.
Upload prior RFP responses, security artifacts, architecture diagrams, demo scripts. The Agent draws on these whenever it works.
Run the Agent automatically — on a schedule, when a new opportunity needs SE involvement, when an RFP lands.
Get notified when a security question can't be answered confidently or when a demo prep flags missing info.
Persistent context across deals — prior architecture discussions, previously raised security concerns, repeated objections.
## Chain Agents into a workforce
When a single Agent isn't enough — discovery summary, then demo prep, then technical proposal — wire them together on the Workforce canvas.
Drag, connect, and run multi-Agent pipelines without code.
## Test before you trust
Set up evals so a wrong security answer or hallucinated architecture detail gets caught before it lands in front of a prospect.
Define test cases in the UI. Run them on every change.
## Ready to go further?
When clicking through the builder starts to feel slow — when you'd rather have your AI coding assistant build and edit Agents for you, drop into custom Python or JS code blocks, or call Agents from your own app via the SDK — pick the **Build with AI** tab above.
You already work in an AI coding environment. Clicking through a UI to edit RFP response logic feels slow. Have your AI assistant build, shape, and orchestrate Agents directly from your editor.
## Programmatic GTM
Programmatic GTM is an MCP server that connects your AI coding environment to Relevance AI. Describe what you want in natural language; your AI assistant reads and writes your Relevance workspace — system prompts, Tools, knowledge, triggers, workforces, evals.
The fastest setup. Install the Relevance AI plugin and build Agents from your terminal.
Connect from Claude Desktop, Cursor, VS Code, ChatGPT, OpenAI Codex, or any MCP client.
Clone the skills repo so your coding assistant has built-in knowledge of Relevance patterns.
The full reference for what you can do programmatically.
## The four levels in solution engineering
How the [autonomy ladder](/guides) plays out across pre-sales:
An SE asks the Agent to answer a specific security question or summarize prior architecture work for an account — the Agent returns a draft with sources.
An SE asks for an 80-question security questionnaire response — the Agent drafts all 80, the SE reviews and finalizes.
A new opportunity hits Stage 2 → discovery summary, demo prep, and a first-draft technical proposal all generate, the SE reviews and refines.
You set the objective — "improve technical win rate" — and the Workforce drafts RFP answers, discovery summaries, and demo prep, with its drafting criteria tuned through evals against win/loss outcomes.
## Zoom into a single use case
Each use case below is a working entry point — clone a template, then run it, shape it visually, or build with AI depending on which tab fit you.
Pull from your archive of prior answers to draft consistent, accurate responses to questionnaires.
Account-aware technical briefs the SE can read in five minutes before any call.
Post-call writeups that turn an hour of conversation into a structured summary with action items.
## See it in production