# aside

> aside (always lowercase, at aside.pro) is an assistant that lives inside a B2B web app. The app registers the actions it can do — functions it already has, like changing a plan or inviting a teammate — and when a user asks for something, aside picks the action and its arguments and the app's own code runs it: it opens the screen and fills the form, and the user presses what saves, sends or deletes. It answers from the company's documentation and hands the conversation to the team when it cannot help. It speaks English and Spanish.

The model never reads the page or chooses where to click; the page decides what can be done. aside does not record or share the screen and has no voice mode.

## Product

- [Home](https://aside.pro/): what aside does, pricing and frequently asked questions
- [Integration guide for coding agents](https://aside.pro/skill): how to add the script tag and register actions with `aside.register()`

## Blog

- [Chatbot, product tour or in-app assistant: which one takes work off you](https://aside.pro/en/blog/chatbot-vs-product-tour-vs-in-app-assistant/): A fair comparison for small SaaS teams: what a docs chatbot, a product tour and an in-app assistant that runs actions each take off you, and when each is the wrong pick.
- [How to let an assistant act inside your web app without handing it the keys](https://aside.pro/en/blog/let-an-assistant-act-inside-your-web-app/): Expose a few named functions, not your DOM or your API. The model picks one and its arguments, your code runs it, and the user presses what saves, sends or deletes.
- [Prepare, don't commit: the rule for assistants that touch customer data](https://aside.pro/en/blog/prepare-dont-commit-assistants-customer-data/): An assistant inside your app should open the screen and fill the form. The person presses what saves, sends or deletes. Why, and where to draw the line.
- [From help article to action: turning your 3 most repeated tasks into code](https://aside.pro/en/blog/from-help-article-to-action/): Take the help article you send most often and turn its steps into one action your page registers, so the assistant does the steps and the customer presses send.
- [Why product tours stop working after the first week](https://aside.pro/en/blog/why-product-tours-stop-working/): Tours are good at a first look around. They break when the interface moves, when users take a path you didn't script, and when the job changes from learning to doing.
- [What founder-led support really costs (a worked example)](https://aside.pro/en/blog/what-founder-led-support-costs/): A worked calculation of founder-led support you can redo with your own numbers: four inputs, one table, and why the tasks cost far more than the questions.
- [How to cut support calls when you're a 3-person SaaS](https://aside.pro/en/blog/cut-support-calls-small-saas/): A seven-step plan for small SaaS teams: count your conversations, split questions from tasks, fix the docs, and let the product do the repeated tasks with the user.
- [Questions or tasks: sort your support inbox in 20 minutes](https://aside.pro/en/blog/questions-or-tasks-sort-your-support-inbox/): A copy-paste table to sort your last 30 support conversations into questions and tasks, and find the three tasks that keep turning into calls.
- [The same question, every week: what a small team pays to answer it by hand](https://aside.pro/en/blog/the-same-question-every-week/): Your docs already say where the button is. Customers still write in, book a call, or ask for a Loom. Here is why, and what changes when the help can press the button.

## Optional

- [Blog in Spanish](https://aside.pro/es/blog/)
- [RSS](https://aside.pro/en/blog/rss.xml)