Start Here
Start Here
Launch AI apps for GTM and marketing without waiting on a custom build.
drio helps GTM and marketing teams launch useful AI apps quickly. Use it to turn product information, support content, campaign assets, or connected APIs into branded experiences that run inside ChatGPT, Claude, Cursor, and other MCP-compatible clients.
Who This Documentation Is For
- GTM, growth, lifecycle, and product marketing teams evaluating drio
- operators building the first version of an AI app without a large engineering project
- technical reviewers checking API, auth, deployment, and architecture details
What Teams Usually Launch With drio
- product finders that guide buyers to the right plan, SKU, or offer
- support assistants that answer common questions and pull live account data
- campaign and enablement assistants that surface the right assets in context
- onboarding and education flows that collect information and guide next steps
- internal assistants for sales, success, or marketing ops teams
Choose Your Path
Start with business fit
If you are deciding whether drio is the right platform, focus on:
- Launch your first app for the fastest end-to-end flow
- Plan assistant actions to understand how tools should be scoped
- Choose the right response format to see how experiences show up in chat
- Match your brand to understand how the app will look and feel
Start with one clear use case
The fastest successful launch usually looks like this:
- pick one audience and one job to be done
- define two to five tools that solve that job well
- choose widgets that keep responses easy to scan
- connect one reliable data source or API
- test the endpoint in a real AI client before rollout
Start with Launch your first app, then move to Plan assistant actions.
Route technical reviewers to the right pages
Your technical team will usually care about:
- How drio works for platform architecture
- Connect to AI clients for endpoint and transport
- Add sign-in for protected systems when apps need per-user access
- Delegated OAuth configuration for the detailed MCP auth flow
- API quickstart and API overview for direct management API access
Core Concepts In Plain Language
| Concept | What it means |
|---|---|
| App | The AI experience your team is building and publishing |
| Tool | One action the assistant can take, such as finding products or checking account details |
| Widget | The response format shown in chat, such as cards, tables, charts, or forms |
| MCP endpoint | The URL that lets AI clients connect to your app |
| Branding | The visual identity applied to the app and its widgets |
What A Successful First Launch Looks Like
- the app solves one narrow problem for one audience
- answers are grounded in a clear system, dataset, or API
- the output format is easy to scan in chat
- branding feels close enough to your existing product or site
- the team knows which parts stay no-code and which parts may need technical review
Recommended Reading Order
- Launch your first app
- Plan assistant actions
- Choose the right response format
- Match your brand
- Connect to AI clients
If your app needs user authentication or direct API automation, continue into the pages under Technical Review.