Xappex is one workspace for customers, support, marketing, docs and billing, with AI built into every corner of it. Ask in plain English, get answers from your live data, and approve the changes it lines up. Built for teams of 5 to 30 who run all of it, and opening to a few of them at a time.
Invitation only · A few teams at a time · Onboarded personally by the founder
Why we built it
We run our whole company on it. Now we're letting in a few teams like us.
For years Xappex has built Salesforce connectors for Excel and Google Sheets, so I've spent a long time inside other people's CRMs. Meanwhile we struggled to keep a good system of record for our own customers: subscriptions, payments, support, and documentation for both customers and the team.
HubSpot was the closest match, so we signed up. For a team of 10 we ended up paying over $2,000 a month, and every new hire raised the bill. We paid for about 80,000 marketing contacts to cover the occasional campaign burst while using under 10% of them most months. Then an AI support bot we'd piloted announced $800 a month on top.
So I built our own with Claude Code, and moved our company onto it one pillar at a time.
AT
Alex Tarasevich
Founder, Xappex
SupportRunning on Xappex since August 2026
Marketing emailMoved over shortly after
Lead and trial nurture agentsLive November 1, 2026, the day after our HubSpot contract ended
Why Xappex
AI is only as smart as what it can see
An AI add-on in your help desk sees tickets. One in your billing tool sees invoices. Xappex keeps the contact, the ticket, the subscription and the article on one record, so its AI answers from the whole customer, not a slice.
One record per customer
Contacts, companies, tickets, chats, emails, subscriptions, invoices and articles share one object graph, and the AI reads all of it.
AI that shows its work
Every reply, chatbot answer and data answer comes from your own records and articles, and shows exactly what it read.
Your permissions, always
The AI acts as the person asking. A field or record you can't see, it can't see either, in the app, in Claude or in ChatGPT.
You approve what matters
Reads and drafts run freely. Emails, deletes, bulk and billing changes wait for a one-tap approval. The AI never approves itself.
AI at work
AI where the work happens
Not one chat box bolted on the side. Every part of Xappex has AI built in, and all of it reads the same records with the same permissions.
Assistant
Ask, and it's done
Press ⌘K and ask in plain English. It finds records, updates them, logs the call, creates the task and builds the report. Every edit comes with undo.
Data answers
Answers over all your data
Ask "MRR by plan for the last six months" and get a number, a chart or a table computed from every row, not a sample. Export it to CSV.
Bring your own AI
Your model, your key
Runs on Claude out of the box. Prefer OpenAI, Gemini, Grok, Llama, Mistral, DeepSeek or your own endpoint? Plug in your key in Settings and every assistant, reply and agent step uses it.
Support
Replies drafted from your docs
Suggested replies in the ticket composer come from your own articles. Open the grounding panel to see the passages it used, and fix the article in one click.
Chatbot and inbox
First answers on autopilot
Grounded chatbots on your site and AI auto-reply on your Gmail inboxes answer around the clock, with daily caps, loop guards and a clean handover when a customer asks for a person.
Translation
Speak every customer's language
Live chat arrives translated into each agent's language, and replies go back in the customer's. Your team answers in one language, customers read theirs.
Lead scoring
Scores that explain themselves
Every contact gets a 0–100 score and a hot, warm or cold tier from a calibrated decision model that matches your ideal customer profile. "Why this score?" answers in plain English.
Knowledge
Docs that write themselves
Draft articles with AI, and turn a resolved ticket into a solutions article in one step. Each new answer makes the next reply and the chatbot smarter.
Claude and ChatGPT
Your CRM inside the AI you use
Add Xappex as a connector in Claude or ChatGPT and work your customers from there. Sign in once, and it acts with your exact permissions.
AI agents
Agents that think, then check with you
Lay out the workflow on a visual canvas and hand the judgment calls to AI. It reads the record, decides and drafts. Anything a customer would see waits for a person.
AI steps that classify, extract, summarize and draft with structured output
AI Branch with a calibrated confidence score, so unsure runs take a fallback path instead of guessing
Triggers on customer questions in chat and email, record changes, forms and schedules
Proposed actions approved from Slack, email or the app, with budgets, frequency caps and exit goals
Let the AI do the busywork without handing it the keys. Rules decide what it can do alone, and the model can't change them.
Permissions
Acts as the person asking
The assistant, the brief and the Claude or ChatGPT connection see only the objects, fields and records that person can.
Risk tiers
A human decides the big moves
Reads run freely and edits are logged with undo. Sending email, deleting, bulk and admin changes always wait for a person.
Transparency
Every answer shows its sources
See the customer's question, the search the AI ran and the article passages behind each grounded answer.
Spend
Costs you control
Monthly caps per user, budgets per agent and usage by user. Runs on Claude out of the box, or bring your own provider and key.
AI optional
Don't trust AI? Turn it off completely.
One switch in Settings turns AI off for your whole workspace. No model ever sees your data, and you still get an integrated CRM, Support, Marketing, Billing and Documentation platform with built-in reporting.
Contacts, companies, custom objects and real permissions
A shared inbox and live chat that hand every message to your team
Audiences, email sends and forms
Subscriptions, invoices, seats and a customer portal
Internal docs and a public help center
Reports across every object, and automations built from rules
Change your mind later? Flip it back on and the AI catches up on the articles and tickets added in the meantime.
Use AI in this workspace
Settings → AI
CRM and custom objectsOn
Support inbox and live chatOn
Marketing and billingOn
Docs and reportingOn
AI modelsOff
What's inside
Six pillars, one object graph
Turn a pillar off for a team that doesn't need it. Everyone who has it on works on the same data.
Customers
CRM
Contacts, companies, activities and tasks out of the box. Custom objects, custom fields, formulas and validation rules when your business isn't.
Amazon SES, SendGrid or SMTP with verified sender identities
Opens, clicks and conversions tied to the contact
Knowledge
Internal and customer docs
Every article is tagged internal or customer-facing. The help center shows one set, your team sees both.
Public help center on your domain
Write with AI, import existing docs, inline images
Promote a resolved ticket into a solutions article
Billing
Subscriptions and seats
Chargebee or Stripe subscriptions, plans and invoices mirror into the CRM and stay in sync through webhooks.
Customer portal with Admin and License Owner roles
Seat assignment and a license API for your add-ins
Bank reconciliation via Plaid, every write logged
Agents
Automation
A visual builder with triggers from tickets, chats, forms, emails and schedules. Steps read and write CRM data directly.
AI steps and an AI Branch with calibrated confidence
Proposed actions held for one-tap approval in Slack
Frequency caps, re-entry caps and per-agent budgets
Before and after
One request, two ways to handle it
An everyday ask from a growing customer. Here's what it takes with a stack of tools, and what it takes in Xappex.
MR
Maya Ruiz · Northwind Labs
"We just hired three people. Can you add three seats to our plan, and what will it cost?"
With a stack of tools4 tools · 2 handoffs
Help deskRead the email. There's no plan or billing info next to it.
CRMLook up the company to see who owns the account.
BillingLog in to find the plan, the seat count and the price per seat.
ChatAsk the account owner if it's OK to change the subscription, then wait.
BillingChange the seats, then come back and write the reply from scratch.
The CRM never learns about the changeThe customer waits on the handoffs
With Xappex1 screen · 2 approvals
Open the ticket and press ⌘K: "Add three seats for Maya and draft a reply."
The assistant reads the ticket, finds Northwind's subscription and holds the change for you, with the estimated next invoice:
Change quantity · Pro · 8 → 11Approve
It drafts the reply as a second card. You edit it if you like, then approve it to send.
The billing system and the subscription update, and "Seat count changed 8 → 11" lands on Maya's timeline and in the audit history.
Nothing changes until you approveEvery change is on the record
Knowledge base
Two audiences, one knowledge base
Most tools make you pick between a public help center and an internal wiki. Xappex tags every article by audience. The help center and the customer chatbot only see customer articles. Your team, and the AI drafting their replies, see everything.
Help center on your domain, with categories and search
Internal articles are never indexed, returned or quoted to a customer
Promote a resolved ticket into a solutions article in one step
Team viewHelp center view
Managing seats and license owners
Billing · updated 3 days ago
Customer
Refund policy and how to issue one
Billing · internal runbook
Internal
Connecting Gmail to your inbox
Getting started
Customer
Escalation ladder for enterprise accounts
Support · internal
Internal
Exporting contacts with custom fields
Data · promoted from ticket #3877
Customer
The customer chatbot retrieves from the help-center set only. Internal drafts for your team retrieve from both.
Security and control
Permissions like a real system of record
Xappex borrows the parts of enterprise CRM that operator teams actually need, and leaves the consultants at home.
Profiles, roles and permission sets
Object, field and record-level access. Sharing rules and groups for the exceptions. A billing-only profile sees invoices and nothing else.
Per-pillar gating
Marketing, billing, support and docs can each be switched off for a whole team. Disabled pillars leave navigation, search and the API.
Audit log and history
Who changed what, when, from where. Every record carries its history tab. Deletes go to a recycle bin first.
Public API, tokens and webhooks
Scoped API tokens with rate limits, idempotency keys on writes, and an outbound events bus so your other systems hear about changes.
Compliance built into sending
CAN-SPAM, CASL and GDPR unsubscribe handling, bounce suppression and opt-out imports are on by default.
Hosted on AWS, isolated per workspace
Each organization is a separate tenant with its own data, roles and pillars. HTTPS everywhere.
Your providers, your accounts
Bring the providers you already trust
Email, enrichment and billing run on your own accounts with the providers you choose. Your data and your sending history stay with them, under your name.
Email
Amazon SES, SendGrid or SMTP
Send through your own account, so your sending reputation stays yours: your domain, your history, never shared with anyone else's campaigns.
AI
Claude, or your own key
Claude is built in. Or bring your own provider and key, and set monthly caps per user.
Enrichment
Your data vendors
People Data Labs, Apollo, Coresignal and Crunchbase, with your own keys.
Billing
Chargebee or Stripe
Subscriptions, plans and invoices stay in the billing system you already use, mirrored into Xappex.
Integrations
Plugs into what you already run
Native connections, not recipes. Syncs are resumable, incremental and logged.
Gmail
Multiple inboxes into one queue. Threaded replies, inline images, automated-sender detection.
HubSpot
Import contacts, companies, tickets and segments. Incremental after the first pass.
Chargebee
Subscriptions, plans and invoices mirrored. Seat writes through one audited path.
Slack
Notifications, chat handoff threads, approve agent actions without leaving Slack.
SendGrid
Marketing and transactional sending. Bounce and unsubscribe webhooks handled.
Claude and ChatGPT
Connect over MCP with OAuth sign-in. Search, read and update the CRM from the chat you already use.
Data enrichment
People Data Labs, Apollo, Coresignal and Crunchbase fill in contacts and companies, one at a time or in bulk.
Stripe
Customers, subscriptions and invoices mirrored through signed webhooks. Connect it beside Chargebee or on its own.
Amazon SES
Send marketing email from your own AWS account, with your own domain and sending reputation.
SMTP
Any SMTP server for marketing sends, when you'd rather keep the provider you already have.
Telegram and WhatsApp
Personal notifications, approval alerts and agent messages, on the messenger your team uses.
Plaid
Bank feed for invoice reconciliation, with learned counterparty aliases.
Also: an embeddable chat widget and forms with a JS API, website visitor tracking, CSV import and export for every object, Claude built in or your own AI provider (OpenAI, Anthropic, Google, Azure, Bedrock and more), and a REST API with webhooks.
FAQ
Questions we get asked
How does early access work?
Request access with the form below and we review it personally. If it looks like a fit, we have a short call to understand how you work today. Then we onboard you and help migrate your data from HubSpot or a CSV.
Why invitation only?
We onboard every team personally and want each one to succeed. We would rather grow carefully than fast.
Is it production-ready?
We run our own company on it. Our support has run on Xappex since August 2026, marketing email moved over shortly after, and our lead and trial nurture agents run on it from November 1, 2026.
Do I have to replace my CRM?
Not on day one. Start with one pillar, usually support or marketing email, and keep the rest where it is. The HubSpot connection and CSV import bring your data in, and you turn on the other pillars when you're ready. That's how we moved over ourselves.
Where does the AI get its answers?
From your own records and articles. Suggested replies, chatbot answers and agent decisions retrieve from what you've stored in Xappex, and the grounding panel shows the exact passages they used. The customer-facing chatbot only ever sees customer-facing articles.
Can the AI take actions on its own?
Only the ones you allow. Reads, drafts and classification run freely, and record edits are logged with undo. Sending email, deleting, bulk changes and billing or admin actions are held as proposed actions until a person approves them from Slack, email or the app. The AI can never approve its own proposal.
Can I use Xappex without any AI?
Yes. An admin unticks Use AI in this workspace in Settings → AI, and from then on no AI model is called for your workspace, not even for search. The AI features disappear from the app, the chat widget sends every message to your team, and Claude or ChatGPT can't connect. CRM, support, marketing, billing, docs and reporting all keep working. Turn it back on any time.
Which model does it run on?
Claude, built in, with nothing to set up. Or bring your own key for OpenAI, Anthropic, Google, Azure OpenAI, AWS Bedrock, Mistral and others, or any OpenAI-compatible endpoint. Set monthly caps per user and budgets per agent, and see usage by user in Settings.
Can I use Xappex from Claude or ChatGPT?
Yes. Add Xappex as a custom connector, sign in, and ask from the chat you already use: look up a customer, pull a report, log a note. The connection acts with your own CRM permissions, and you choose read-only or read-and-write when you connect.
Early access
We're letting in a few teams at a time
Every early-access team is onboarded personally by the founder. We help you migrate from HubSpot or a CSV, and you get a direct line for feedback that shapes the roadmap. You don't have to move everything at once: start with one pillar, support or marketing email, and bring the rest over when you're ready. That's how we migrated ourselves.
We review every request personally and reply within a few days.
