Limits per role
A discount ceiling, a refund limit, which case types may be closed, whether a quote may leave without a human reading it.
Yumin CRM
Six functional clouds — sales, service, marketing, commerce, growth and talent — working on one record for every person and every company, under permissions and limits you set. Conversations are one layer of it, not the point of it.
The six functional clouds. Switch on what you need, add the rest when you are ready.
The core
One record per person. One per company. Everything else hangs off it.
A deal, a case, an invoice, an event attendance and a WhatsApp thread are views of the same record, not separate systems that need reconciling.
Whoever picks up the conversation next can see what was said, what was sent, what was paid and what was promised, in order.
Consent, ownership, visibility and spending limits are held on the record itself, so they apply the same way in every cloud and on every channel.
Your data sits on your own tenant with role-based permissions and a full history of who saw and changed what. We confirm the hosting region before anything is set up.
Control
Autonomy is a setting, not a personality. You set the ceiling per role, and above it the system drafts the work and waits for a person.
A discount ceiling, a refund limit, which case types may be closed, whether a quote may leave without a human reading it.
Every automated action is recorded against the record with the rule that allowed it, so a decision can always be traced back.
Above the limit nothing is sent. The work is prepared, flagged to the right owner and held until it is approved.
Editions
The same data model, shipped with the objects, stages and documents your sector already uses, so implementation starts from something recognisable. Editions for nonprofits and foundations, manufacturing and distribution, and education are in build.
Members, dues cycles, chapters and committees.
Delegations, documents and member services.
Matters, time, retainers and billing.
Subscriptions, advertisers and renewals.
Catalogue, orders and post-purchase care.
Donors, grants and programme delivery. Not available yet.
Channels
WhatsApp matters here more than almost anywhere, so we treat it properly — as an official business channel writing into the record, not as a side inbox on somebody's phone.
One official number the whole team works from, with templates, assignment and a thread that belongs to the record rather than to a person.
The same conversation, started on your website and continued wherever the customer prefers, without losing the history.
Threaded onto the record, so quotes, invoices and replies sit in the same timeline as everything else.
Around the CRM
Our team in Dubai does the configuration, the migration and the integration work, and looks after the infrastructure it runs on.
Configured to your process, your data migrated, your team trained until they actually use it.
From a narrow pilot with a measurable outcome to something running in production with limits around it.
Portals, apps and integrations with your accounting, calendars, website and payment provider through the API.
Google Cloud and Workspace, AWS, Microsoft Azure and business email on your own domain.
Find the exposure, fix it, and keep watching it.
Pricing
Cost depends on the edition, the size of your team and which clouds you turn on. We give you a written quote rather than a list price you have to decode.
Live pricing is not published yet. Tell us the edition, the team size and the clouds you want, and we confirm a written quote.
Message us on WhatsApp. A person in Dubai answers, not a queue in another time zone.