Built, sold and supported in Dubai. Every conversation lands on one record.
Book a demo on WhatsApp Call +971 50 688 7063

Yumin CRM

The whole company, on one record.

Sales, service, marketing, commerce, growth and talent are six clouds on one data model. Turn on what you need. The AI works inside the limits you give it, and every channel writes back to the same place.

One record per person and company Permissions per role Dubai implementation team
How Yumin CRM is put togetherA schematic of the Yumin CRM operating system. Six functional clouds sit on a ring and all feed one central core. Clockwise from the top they are Marketing (campaigns, journeys, consent), Service (cases, service levels, knowledge), Commerce (catalogue, orders, invoices), Talent (people, roles, onboarding), Growth (renewals, referrals, expansion) and Sales (pipeline, quotes, approvals). The core is labelled One record, holding every person and every company on one timeline under one set of rules. Two smaller layers connect to the same core from below: Control, covering roles, permissions and limits, and Channels, covering WhatsApp, web chat and email. A small panel at the top left, marked illustrative, shows an open pipeline figure with a rising bar chart drawn from the same record. Signals travel along every connection: the clouds write into the record, and the record drives the channels and the figures.One recordevery person · every companyone timeline, one set of rulesMarketingcampaigns, journeys, consentServicecases, SLAs, knowledgeCommercecatalogue, orders, invoicesTalentpeople, roles, onboardingGrowthrenewals, referrals, expansionSalespipeline, quotes, approvalsControlroles · permissions · limitsChannelsWhatsApp · web chat · emailOpen pipeline · illustrativeAED 1.24M

Functional clouds

Six clouds, one data model.

They are not separate products glued together. Each cloud reads and writes the same record, which is why a quote knows about an open case and a renewal knows about an unpaid invoice.

01

Sales

Pipeline, quotes and approvals in one place. The AI drafts the quote, applies your discount ceiling and waits for a person above it.

  • Accounts, contacts, deals
  • Quote and approval chains
  • Forecast by stage and owner
02

Service

Cases raised from any channel land on the same record, with response targets, ownership and a knowledge base behind them.

  • Cases, queues, escalation
  • Response and resolution targets
  • Answers drawn from your own content
03

Marketing

Campaigns and journeys that read from the record rather than a separate list, so consent and unsubscribes are respected everywhere.

  • Segments from live data
  • Journeys across channels
  • Consent held on the record
04

Commerce

Catalogue, orders, invoices and payments, so the money side of the relationship sits on the same timeline as the conversation.

  • Products and price books
  • Orders and invoices
  • Payment status on the record
05

Growth

Renewals, referrals and expansion worked deliberately instead of remembered. The record knows what is due and who owns it.

  • Renewal and dues cycles
  • Referral tracking
  • Expansion and upgrade plays
06

Talent

Your own people modelled the same way as your customers: roles, teams, onboarding steps and the permissions that follow them.

  • People and teams
  • Roles and onboarding
  • Permissions that follow the role

The core

Everything resolves to one record.

Person and company

Two object types, deduplicated on the way in. A person can belong to more than one company, and the history follows them.

One timeline

Conversations, quotes, cases, invoices, event attendance and automated actions in one chronological view.

Rules on the record

Consent, ownership, visibility and limits live with the record, so they hold in every cloud and every channel.

Open API

Accounting, calendars, your website and your payment provider connect through the API. Our team does that work during implementation.

Control and permissions

Autonomy you can turn down.

The useful question about an AI CRM is not how clever it is, but what it is allowed to do without asking. In Yumin that is a setting on a role.

Set the ceiling

Discount ceilings, refund limits, which case types may be closed automatically, and whether a quote may leave without a person reading it. Different ceilings for different roles.

See what happened

Every automated action is written to the record with the rule that permitted it and the data it used, so any outcome can be traced back and the rule changed.

Role-based visibility

People see the records their role allows. Field-level rules cover the parts of a record that should be narrower than the whole.

Held, not sent

Work above a limit is drafted, flagged to the right owner and held. Nothing leaves the building on a maybe.


Editions

Six editions, and two more coming.

Each edition ships with the objects, stages and documents that sector already works with. Manufacturing and distribution, and education, are described as coming.

Associations and federations

Members, dues cycles, chapters and committees.

Chambers and trade bodies

Delegations, documents and member services.

Legal and consulting firms

Matters, time, retainers and billing.

Publishers and media

Subscriptions, advertisers and renewals.

Retail and ecommerce

Catalogue, orders and post-purchase care.

Nonprofits and foundations

Donors, grants and programme delivery.

Channels

Every channel writes to the same record.

WhatsApp Business, web chat and email are layers on the CRM. They are how the record gets updated, not a separate place where information goes to be lost.

WhatsApp Business

One official number, shared by the team, with assignment, templates and the thread attached to the record.

Web chat

Started on your site, continued anywhere, with the history intact.

Email

Threaded onto the record alongside quotes and invoices.

Events and check-in

Attendance writes back to the same person record, so the follow-up knows who actually turned up.


Pricing

A written quote, same day.

Price depends on the edition, your team size and which clouds you switch on. Nothing is added to a total until it is in writing.

Get a quote

Live pricing is not published yet, so no figure here forms part of a total. Send us the edition, the team size and the clouds you want.

Ask for a quote

Questions

The six we are asked most.

How is this different from a chat tool?

A chat tool holds conversations. Yumin CRM holds the record those conversations belong to: the person, the company, the deal, the invoice, the event they attended. The WhatsApp layer is one of the channels writing into that same record.

Do we have to move everything on day one?

No. Most organisations start with one edition and one or two clouds, keep their existing tools running, and move the rest over the following quarter. Our team does the migration.

What does the AI actually decide by itself?

Only what you allow. You set limits per role: a discount ceiling, a refund limit, which case types it may close, whether it may send a quote without a person reading it. Above the limit it drafts the work and waits.

Where is our data held?

On your own tenant, with role-based permissions and a full history of who saw and changed what. We confirm the hosting region with you before anything is set up.

Can it work with the systems we already have?

Yes. Accounting, email, calendars, your website and your payment provider connect through the API. Our team in Dubai does the integration work as part of implementation.

What does it cost?

It depends on the edition, your team size and which clouds you switch on. Send us those three things on WhatsApp and we confirm a written quote.

See it on your own data.

Send us a message and we will walk through the CRM with your process in front of us.

WhatsApp