Every experience.
One core.
XPEFY fuses CRM, website, brand assets, inbox, commerce and service into one experience platform. Built on shared primitives, so a person, a page or a brand is defined once — and works everywhere.
Lina Haddad
Person- lina@northwind.example
- +971 50 000 2210
- Dubai, UAE
Relationships lensas Client
- Stage
- Customer since Mar 2025
- Lifetime value
- $4,820
- Owner
- Omar K.
Same record, same ID — eight modules. Nothing is synced, because nothing is copied.
One platform instead of
- CRM
- CMS
- DAM
- Shared inbox
- Helpdesk
- Invoicing
- Project boards
- HR records
The problem
Six tools. Six versions of the same customer.
Every business system invents its own Contact, User, Client or Requester. Integrations try to keep them in sync — and every new tool multiplies the work, the cost and the drift.
How tools see Lina today
- CRM
Contact #4821 - Helpdesk
Requester 99-1A - Online shop
cus_8Fh2Lx - WhatsApp
+971 •• ••• 2210 - Newsletter
subscriber 0x7f - Invoicing
Client: L. Haddad
Integration mesh
XPEFY core
Connecting n tools pairwise takes n(n−1)/2 integrations. Sharing one core takes n — and nothing ever needs to be synced.
Primitives
Define it once. Use it everywhere.
XPEFY is built from a small set of shared building blocks. Modules don’t own their own copies of people, pages or brands — they reference the same ones.
Person
One record for everyone — customers, leads, teammates, vendors. Roles are relationships, not copies.
Used byOrganization
Companies, households, branches and teams. People can belong to many.
Used byBrand
Logo, colour, type and voice as live data. Change it once and everything that renders follows.
Used byPage
Sites, landing pages, portals and emails — composed from content and dressed by the brand.
Used byAsset
Files, media and documents with versions, rights and every place they are used.
Used byConversation
Every message on every channel, threaded around the person — not the tool it arrived in.
Used byTransaction
Quotes, orders, invoices, payments and bookings on one ledger.
Used byTask
Work items, tickets and approvals that can point at anything else in the core.
Used by
Underneath it all: one event timeline. Every change to every primitive is recorded as an event — auditable, replayable, and the trigger for every journey, report and agent.
Cross-fed, not copied
Change the brand once. Watch everything follow.
Your website lives in Content, your brand lives in Assets — but they render as one. Update a colour, a logo or a typeface and every page, email and portal picks it up instantly.
Brand primitive
Pick a brand kit. Every surface re-renders from it — no re-publishing, no copies.
Website · Content
Book your visit in two taps
Email · Journeys
Your appointment is confirmed
Thursday · 3:00 pm
Portal · Service
Modules
Lenses, not silos.
Each module is a focused way of looking at the same core. Turn on what you need today; add more as you grow — with nothing to integrate.
- CRM
Relationships
Pipelines, segments, lifetime value and follow-ups.
A Person seen as lead, client or partner.
- CMS
Content
Websites, pages, blogs and customer portals.
A Page fed by content, dressed by Brand.
- DAM
Assets & Brand
Media library, brand kits and approvals.
Brand and Assets that every surface inherits.
- CPaaS · Inbox
Conversations
One shared inbox for every channel.
Conversations on the Person’s timeline.
- ERP-lite · POS
Commerce
Catalogue, quotes, orders, invoices and payments.
Transactions linked to people and orgs.
- Helpdesk · CSS
Service
Tickets, SLAs and a self-serve help centre.
Tasks and Conversations with a clock.
- PMS
Work
Projects, boards, checklists and approvals.
Tasks that point at anything in the core.
- HRM
Team
Members, roles, access and schedules.
A Person seen as a teammate.
Journeys
Automations triggered by any event on any primitive — no glue code between tools.
Insights
Reports across every module from one dataset. No ETL, no exports to reconcile.
Agents
AI that works on the same primitives, under the same roles and audit trail as your team.
Identity & access
One login, role-based permissions, SSO and a full audit history.
API & events
Every primitive is readable, writable and subscribable. Export everything, anytime.
Omnichannel
Meet people where they already are.
Every message, on every channel, lands on the same person’s timeline — with their orders, tickets and history one glance away.
- Website
- SMS
- Messenger
- Telegram
- Live chat
- Voice
- Customer portal
Getting started
Up and running in an afternoon.
- 01
Create your workspace
Bring in people, products and content from spreadsheets or the tools you already use.
- 02
Set your brand once
Logo, colours, type and voice become data every page, email and portal inherits.
- 03
Connect your channels
Website, email, WhatsApp and social messages land in one inbox, on one timeline.
- 04
Switch on modules as you grow
Each module is a new lens on the same core. Nothing to integrate, nothing to sync.
Principles
Built differently, on purpose.
The commitments that shape every decision we make about the platform.
- P1
One source of truth
Every record exists once. Modules reference it; they never copy it.
- P2
Composable, not bundled
Turn modules on and off freely. Your data and history stay exactly where they are.
- P3
AI-native, permission-aware
Agents read and act through the same roles, approvals and audit log as people.
- P4
Secure by design
Tenant isolation, least-privilege roles, encryption in transit and at rest, and a complete audit trail.
- P5
Open by default
Documented API, webhooks and event streams. Your data is always exportable.
- P6
Light by default
Fast pages, small footprint, no tracking scripts you didn’t ask for.
Who it’s for
Built for businesses that run on relationships.
If your customers talk to you, buy from you and come back to you, XPEFY is shaped for you.
- 01
Clinics & practices
Bookings, reminders, patient messages and reviews in one place.
- 02
Agencies
Run every client’s brand, site and inbox from separate, connected workspaces.
- 03
Retail & e-commerce
Catalogue, orders and conversations on the same customer record.
- 04
Professional services
Proposals, projects, invoices and client portals without five subscriptions.
- 05
Hospitality
Guests, reservations, menus and campaigns that follow your brand.
- 06
Education & training
Learners, enrolments, content and communication on one core.
FAQ
Questions, answered.
Is XPEFY a CRM, a CMS or something else?
All of those jobs, without being any one of them. XPEFY is an experience platform: a shared core of primitives (Person, Organization, Brand, Page, Asset, Conversation, Transaction, Task) with modules that act as lenses over that core.
How is this different from an all-in-one suite?
Most suites are separate products sold together, connected by internal integrations — so a customer still exists five times. In XPEFY a person exists once; the CRM, inbox, shop and helpdesk all point at the same record.
Do I have to replace all my tools on day one?
No. Start with the module that hurts most, import what you have, and connect the rest through the API. Retire tools only when you’re ready.
What is a primitive?
A small, shared building block that every module understands. Because modules share primitives, a brand change, a new contact detail or a payment shows up everywhere it matters — automatically.
Who owns the data?
You do. Every primitive is exportable through the API and in standard formats, at any time.
How does AI fit in?
Agents operate on the same primitives with the same permissions and audit trail as your team, so they can draft, summarise, route and act — without a separate data copy.
When can I start?
XPEFY is in pre-release. We are onboarding a small group of design partners first — request early access and tell us what you run today.
Early access
One core. Every experience.
We’re onboarding a small group of design partners. Tell us what you run today and what you’d love to stop juggling.