A CRM built for six beds, not six hundred

What it is

A custom CRM is a database of the records a business actually keeps, a set of screens for the people who touch them, and a few automations for the steps somebody is doing by hand today. Nothing beyond that, and none of it shaped by a vendor's idea of a sales team.

Internal tools are the same object under another name. A booking system for six rooms. A job board for four vans. A quoting tool that ends in a PDF and a follow-up. The technology is unremarkable on purpose: a relational database, a web application, roles and logins, and integrations only where a documented interface exists.

Who it is for

Four kinds of buyer. Teams paying per seat for a platform they use a tenth of, where the tenth they use is the wrong tenth. Businesses run on a spreadsheet, a shared mailbox and a messaging group, where the process works and nothing records it. Operators whose bookings are the business: guesthouses, clinics, rental fleets, small hire and tour operations. And firms who have outgrown a white-labelled subscription and want to stop renting what the business runs on.

The common shape is small and particular. Six beds, not six hundred. Four staff, not four hundred. That is the size the enterprise vendors price badly, because both the licence and the implementation assume a company with a procurement department. The work goes to the Gulf, Europe, the United Kingdom and North America, in English and in writing.

What it costs

Three rungs, published so you can rank this studio against others before writing to anyone. There is no hourly rate here or anywhere else on the ladder, because an hourly rate makes working quickly a penalty.

USD is the anchor on every quote and invoice. The figure in parentheses is the same price in dirhams at the pegged rate of 3.6725 to the dollar, given as one local equivalent rather than a currency list, and correct as of 5 September 2026. Prices exclude any VAT, sales tax or withholding your own country applies to imported services.

Why this costs less than the quotes beside it

The published market bands sit far above these. Shops working at Central and Eastern European rates quote USD 30,000 to 50,000 for a basic custom CRM, and enterprise vendors start near USD 90,000 for an entry-level system. A build from USD 9,000 is under a third of the cheapest of those bands, and a number that far under the market has to show its structure or it reads as a scam.

The structure is this. One person does the discovery, the data model, the interface and the code, so nothing is paid twice to be handed between people. There is no sales team, no account manager, no idle bench and no office rent, and the studio runs from Pakistan, where the cost of living does the rest. The stack is chosen to be boring, because a fashionable one bills its own learning curve to the client.

What that buys is a working system for one team's process, not an enterprise platform. The higher quotes usually carry a project manager, a QA department and a compliance programme. Where you need those, the higher number is the honest one.

Build or buy

Buying is right more often than a studio selling builds likes to admit. If an off-the-shelf CRM fits the way you already work, buy it, configure it properly, and spend the difference elsewhere. No build competes with a good fit.

Building wins in three situations. When the licence is priced per seat and most seats are people who look rather than type. When the process the business is actually good at is the one the platform will not model, so the team keeps a spreadsheet beside the tool it pays for. And when the platform owns the customer relationship, the phone number or the data, so leaving means starting again.

The sprint is where that is decided honestly. If the map and the model show an existing product fits, that is written down and no build follows.

Automation, and where it stops

Automation is added where a person repeats an identical action, and nowhere else. Speed to lead is the usual first one: an enquiry arrives, the record is created, the right person is told within seconds, and the follow-up is scheduled rather than remembered. After that come reminders, status changes, recurring invoices, and the daily summary nobody then rebuilds by hand.

Language models get used where a job is genuinely fuzzy: sorting an inbox, drafting a reply for a person to send, summarising a long thread into a record. Each of those is drafted rather than sent, because a model writing to your customers unattended is a liability in the costume of a feature.

What will not be built here: anything that messages customers with nobody in the loop, anything that makes a pricing or credit decision on its own, and anything whose behaviour cannot be explained to the person who has to answer for it.

How it runs

1. You write the brief in a sentence. The card below takes it: what the team does now, what breaks, and what you pay for at the moment.
2. I reply in writing, usually inside a day, saying whether this is a build, a configuration of something you can buy, or nothing at all.
3. The discovery sprint, one week, USD 1,500 fixed. Process map, data model, clickable prototype, and a fixed written quote with its exclusions named. You keep all four.
4. The build in the open. Screens arrive as they are made rather than at a reveal, on a staging copy you can log into and break.
5. Your data, staged in. The real records go in before launch, because a tool that has only held test data has not been tested.
6. Handover and running. Accounts, repository, roles, training, and a written account of how the system works. The monthly rung is optional and is not a lock.

What it has proved

Two systems built here are running. Neither carries a measured series, so this section is description rather than proof and is marked as such.

• Orlux Rides. A white-labelled subscription replaced by a custom-built CRM: calls, texts and email on one number, invoicing and payments inside the same records, and a speed-to-lead automation. It runs at crm.orluxrides.com.
• ClearQuest. A custom lead pipeline wired into a Wix site: form to contact record to a dashboard notification, with an email failsafe behind it so a lead survives a broken step.

Both descriptions are mine. There is no before-and-after series for either, no measured time saved and no revenue figure, because none was instrumented from the start. What stands in their place is the market comparison above and two live systems that can be shown. There are no testimonials on this site and no star rating in its markup, because it has neither.

Who it is not for

Questions people ask before they write

Sources

1. Custom CRM market bands, ShepherdUX research note 18, September 2026, finding 5: USD 30,000 to 50,000 for basic features at Central and Eastern European rates (Cleveroad, updated 3 December 2025), and USD 90,000 for entry level at an enterprise vendor (Itransition).
2. Orlux Rides and ClearQuest: systems built by this studio and described by its owner. Neither is a measured result, and no figure is claimed for either.
3. United Arab Emirates dirham pegged at 3.6725 to the United States dollar, Central Bank of the UAE, rate as of 5 September 2026.