SuiteCRM and Vtiger, deployed, configured and extended for your business
Two open CRMs whose data and administration stay yours. We deploy them, configure them around your business and bring them in line with the law that applies to you.
What these platforms cover as standard
Compliance, where you operate
The platform is the same whatever the country. What changes is the configuration: chart of accounts, tax rates, exchange formats, transmission obligations. We set out France and Switzerland below because they are the two our clients meet most often. For another country the principle does not change: we start from what local law requires, and configure accordingly.
France
A CRM is first of all a file of personal data. The GDPR requires a lawful basis, a retention period and an effective right to erasure. The platform holds the data; it holds neither the register, nor the periods, nor the purges. We set up the processing register, retention by category, automatic purges and export on request.
Switzerland
The revised Federal Act on Data Protection sets the same requirements of purpose, information and retention. The mechanisms are the same, the configuration differs — and hosting can stay in Switzerland where the nature of your data calls for it.
Each country you operate in is handled on its own terms, with its own rules and formats. You still deal with one person, however many of them there are.
How we work
Integration in practice
We start from your real sales cycle — how a deal begins, who qualifies it, what moves it along — before drawing a single screen. We carry contacts, live deals and the history of exchanges across rather than starting from an empty base, then set stages, fields, permissions and document templates around your habits.
Where the standard stops, we build. The platform cannot retain what a salesperson knows about a long-standing customer: that is the subject of our clienteling applications. Nor can it arbitrate the allocation of a scarce item between several waiting customers, which is what allocation management addresses. And where the relationship is counted in donations rather than deals, the follow-up changes in nature — see donor CRM and tax receipts.
How we build is set out on Custom Development, and how we look after what we deliver on Support & maintenance.
The modules we have built around the core
The standard covers a great deal. It stops at a few specific points: those are the ones we build.
Onboarding and regulatory checks
The platform records a prospect; it does not collect their documents, checks no list and carries no signature. The onboarding journey, and the proof of it, have to be built.
KYC & Onboarding WorkflowsCommission calculation and allocation
The platform issues quotations and invoices; it calculates no intermediary remuneration — no agreement per introducer, no tier, no split across networks.
Complex Commission ManagementDistribution network extranet
The portal that ships with one of the two platforms opens support to the end customer; it does not open a partner’s live deals, pipeline or commissions to them.
Broker ExtranetsAppointments booked by the client
The platform’s calendar arranges meetings between colleagues; it does not let the client book one themselves, against real availability and with their own reminders.
Appointment Booking & ConciergeYour CRM after go-live
A CRM is not software you install, it is a record that lives. Retention periods run, erasure requests arrive, and the database degrades if nobody tends it. Mail connectors break when the provider changes its authentication rules.
We keep purges, retention and data rights working, and we rebuild connectors when a provider changes its rules. BUILD installs the CRM; RUN keeps the database sound and compliant.
Support & maintenance