Axiom ConnectAvailable
Your customers, your pipeline and your agents in one record.
Companies, contacts and opportunities with a named owner for every relationship, and agents that work inside the role a manager gives them.
- Workspace
- One per organisation
- For agents
- MCP with OAuth
- Record
- An audit log of every change
The relationship, the pipeline and the next step together.
Companies and contacts, with an owner
Every relationship has someone responsible for it, so the next person can pick it up.
A pipeline with the next action
Move each lead through its stages with the next action and its date always visible.
Outreach beside the opportunity
Templates for the messages you send, and a log of what went out and when, on the lead itself.
Payments matched to the lead
Link incoming payments to the lead they belong to, so revenue sits on the same record.
Agents work inside the limits you set.
Each agent acts for a named person, with a role and a speed limit, and every change it makes is recorded. A client connects with OAuth.
Agents are named team members
Live in ConnectEach agent acts for a named person, with a role a manager assigns. Email goes out as that person, and tools that send, merge records or move money tell the agent to ask them first.
Every change is on the record
Live in ConnectAn audit log that cannot be edited records each change and whether a person or an agent made it.
Keys a manager controls
Live in ConnectManagers issue each agent its own key and can switch the agent off at any time.
Limits on speed
Live in ConnectEach agent can make up to 600 requests and 60 changes a minute, the same as a signed-in person.
Sales agent
- 10:41
list_opportunitiesmine, open - 10:41
set_opportunity_stageproposal - 10:42
create_quotedraft from the line items - 10:43
send_quotesent after the person said yes - 10:43
merge_companiesblocked: merging companies needs a manager
- Requests this minute
- 5 / 600
- Changes this minute
- 3 / 60
- Actor in the audit log
- agent
Illustration of Connect's agent rules. The limits shown are the real ones.
Point your own agent at Axiom.
Add the Axiom MCP server. The client connects with OAuth, and you approve the agent in the browser. The agent guide covers the tools and the first calls to make.
{
"mcpServers": {
"axiom": {
"url": "https://portal.axiomsolutions.app/mcp"
}
}
}
Set up from the Axiom portal.
Your organisation comes with its own Connect workspace. Moving from another CRM starts with an export and a field map.
Create your organisation
Create your organisation in the Axiom portal, choose Business Essentials, then open Connect after payment is confirmed.
You become the administrator
The person who creates the organisation manages its members and access.
Invite your team
Invite teammates from People & access and choose who can use Connect.
Add your agents
Create an agent, grant the tools it needs, and connect a client with OAuth. It works inside the same record your team uses.
Before you move a pipeline.
- Can our own agents use Connect?
- Yes. A manager creates an agent and gives it a role. A client connects with OAuth. It works within that role, and every change it makes is in the audit log.
- Can I preserve custom fields and ownership?
- Yes — owners and the fields you care about are part of the map before a trial import. Unmapped fields stay out rather than being guessed.
- What happens to activity history?
- Recent outreach and stage changes come across with the opportunity. We will tell you if an older activity export is incomplete.
- How do permissions work?
- Organisation membership and Connect roles decide who sees which companies, contacts and opportunities. Shared context is not shared access to every record.
- What email or calendar connectivity exists?
- Keep the mail and calendar you already use. Connect holds the relationship and the next action beside it.
One record for the people and the agents.
Create your organisation in the portal and invite your team. Your agents can join the same record.


