Skip to content

Sales, invoices, purchasing, stock and HR on one platform. People and the Agent work on the same records, under your rules.

You ask the Agent which invoices are overdue. It finds three, drafts a reminder for each, and sends nothing until you approve.
Alerts from separate tools pile up. In one organization, three reminders wait for your approval.

It works inside
your rules.

The Agent works through the same tools and permissions your team has, and never more. How much it does on its own is a setting you control.

The rules

  • Same tools, same permissions as the person it works for
  • A step and AI-credit budget on every run
  • Anything sensitive stops at an approval card
  • Every action logged on the record it touched
Seven acts under the Agent's four autonomy modes. Reads always run on their own; adding a record to a list runs from Auto inside; sending to a customer from Auto with replies; changing the data model only in Full auto. Changing a record's values and sharing a record always come as a card, and changing someone's role is for people only.
● working

Pipeline triage

finds what's stuck.

Surfaces quiet deals and proposes a concrete next step for each. You approve before anything moves.

● working

Drafts on the record

ready for you to send.

Follow-ups, replies and reminders, saved as drafts on the record they belong to. By default, nothing is sent until you approve it.

● working

Data chores

the boring work, on request.

“Load this CSV into contacts.” Imports, bulk updates, restores from the recycle bin. All through the same gates.

● working

Answers with numbers

ask, get the number.

“How much did Q1 bring?” A real number from your records. Permission-aware, like everything else.

Two ways to work.
One organization.

Work in the app yourself, or tell the Agent in the chat. The records, permissions and approval rules are the same, so you choose per task.

One request, two ways. In the app, the overdue invoices fill the screen and the Agent answers in the side panel; in the chat, the conversation fills the screen and an invoice opens beside it. Either way the three reminder emails wait for approval.

app.salexhub.com

The app

You drive. Pipelines, documents, reports and settings are on screen, and the Agent helps from a side panel on every page.

How the app works

chat.salexhub.com

The chat

You say what you need. The Agent does the work with your permissions, brings records and approval cards into the conversation, and waits for your approval.

How the chat works

Try the chat before you sign up: five messages, no account. Open the chat

Four directions.
One crossing.

Deals, data, people and agents meet in one organization. The Agent works where they cross.

Every signal flows into the node, and every answer flows back out as work done on the same records.

Deals
Data
People
Agents

◆ the Agent at the crossing

Three steps to a first result.

No implementation project. No consultant. You just start.

01

Create your organization

Free for one person. Contacts, companies, deals, and any object you add are there from the first minute. Connect your own AI key (Anthropic, OpenAI, Google, DeepSeek or a Vercel AI Gateway key) and the Agent is ready.

One short form, one key.

02

Bring your data

Import a CSV, or ask the Agent to load it. With the Marketing hub on, a form on your website matches each submission to a contact or creates one.

First data in your first session.

03

Choose how much the Agent may do

By default it asks before every change and every send. The Owner can let it act on its own inside the organization; changes to access and personal data always ask.

Approve, and the Agent acts. Decline, and it skips.

One door.
For every agent.

The Agent, workflows and API keys go through one door. Every call meets your approval rules, and every change is written to the audit log. Calls from people, the Agent and API keys are also checked against a role.

  • One registry of 523 permission-aware tools behind the Agent, workflows and the API
  • A REST API and an MCP server on the same registry, open with a key from Settings
  • Permission-aware: an agent sees only what the person it works for can see
  • No shortcuts: approval rules hold machines too, and only a person decides an approval
Four callers take turns at one door: a person in the app, the Agent working for her, a workflow and an API key. The person, the Agent and the key are checked against a role, and the workflow runs as itself; the workflow is held by an approval rule, the API key is refused, and every attempt is written to the log.

Put the Agent to work.

Bring your pipeline, keep your rules, and let people and the Agent work on the same records.

start@salexhub.com · free to start