Services
Custom CRM development
A custom CRM when a generic sales tool does not match the day. For teams in Lebanon, and for GCC and remote clients. You own the code and the records.
Where it fits
A custom CRM is the system your staff use to keep clients and the day's work in one place.
Use something off the shelf when your week already matches it. A custom build is the better fit when the workflow will not bend to the product, when you need Arabic and English done properly, when it has to connect to a website or app you own, or when you want the data in your hands rather than rented. I wrote that test up for salons, spas and clinics in what a CRM for that work should do. The same questions apply to other service businesses.
If what you need is a public website, start with website and web app development. If customers also need an app on their phones, that is mobile app development. A CRM can connect to either. It does not replace them.
What you get
The first version stays small. We agree the core the team will actually use, import the records you already have, and launch with the people who do the work. Reports, messages and online booking wait until that core is in daily use.
For a salon, spa or clinic, the core I plan around is client profiles, scheduling, checkout, packages and reminders. That list is the approach in the salon article. It is not a menu I paste onto every company. Another business gets the screens its own day requires, including roles so each person sees the part of the system their job needs. How those roles should be drawn is in roles and permissions.
Where I can, I watch the work before drawing screens, including time at a front desk when that is the job. Remote projects use the same questions over the material you can share: a day of bookings, the spreadsheet, the notebook columns.
How a project runs
- 01
Email
You write to hello@eliechaaban.com with how the team works today. We talk through that workflow before any screens.
- 02
Proposal
A fixed quote, with the scope and timeline agreed in the proposal. The first version is the core, not every idea.
- 03
Build
Design and development, with regular previews. Existing records are imported when you want them in the new system.
- 04
Launch
We go live with the people who will use it, then agree what waits for a later version.
Ownership
You do. Full ownership of the code passes to you after the final payment. On a new project, the repository and the relevant Apple, Google, domain and hosting accounts are set up in your name.
You can take the client data with you. The point of building it is that the records are not locked to a vendor's plan.
After launch
Support and maintenance are agreed per project. The first weeks usually need more fixes than the months after, because real bookings reveal the edge cases a demo never does.
After that, maintenance is keeping the web app updated and backed up, and fixing bugs. New modules are new scope. The general split between care and new features is in maintenance after launch.
Selected work
One public CRM, using only the facts already published.
Other client work stays under NDA. The public example is the one above.
What to send
Email hello@eliechaaban.com with:
- What the team does in a day that the system has to support.
- Who uses it. Reception, practitioners, managers, or someone else.
- How records are kept today, and whether that data should be imported.
- What the first version must do, and what can wait.
- Arabic, English or both.
- Whether it has to connect to a website or app you already have.
You get a fixed quote after that scope is clear. I do not publish prices. If a standard product would serve you better, I will say so. A brief template that works for this is in how to write a brief.
Questions
Is a custom CRM always the right choice?
No. If a standard product already matches your week, use that. Custom fits when the workflow will not bend, when you need Arabic and English done properly, when it has to connect to your own site or app, or when you want to own the data.
What does the first version include?
The core your team will use every day, then the rest once that core is in use. For a salon, spa or clinic I plan around profiles, scheduling, checkout, packages and reminders. Other businesses get a core that matches their own work.
Can I see an example?
The public example is the custom CRM for Enchanté by Remy Daher, design and development, Lebanon, 2025. The site is https://enchantebyremydaher.com/. I do not publish a feature list or results for it.
Who owns the code and the data?
You do. Full ownership of the code passes to you after the final payment. On a new project, the repository and the relevant Apple, Google, domain and hosting accounts are set up in your name. You can take the client records with you.
What happens after launch?
Support and maintenance are agreed per project. New modules are scoped separately.
What should I email for a quote?
How the team works today, who uses the system, whether existing records should be imported, what the first version must do, and which languages you need. There is no standard price.
How do I pay?
By bank transfer, Whish or OMT.