Software can be built in weeks. Trust takes years.

There has never been a faster moment to build software. With AI tools, a new dispatch system, platform or app can be put together remarkably quickly, whether by an operator for their own use or by a newcomer offering it to the rest of the industry. There are now more options than ever, which makes choosing chauffeur software more important than it has ever been, and operators are right to look hard at what they pay for. Every pound spent on software is a pound that is not spent on vehicles, drivers or service.

But speed is not the same as depth. A system built in weeks can show what software does on the surface. It cannot bring the years of knowledge that sit behind an established platform. Simple apps are quick to build. Solutions that depend on complex problem solving and deep industry knowledge are not, especially in a specialist industry like ours. A dispatch platform holds your clients, your passengers, your rates and your drivers, and it has to work at four in the morning on a bank holiday.

And every system will one day have a problem. A booking fails to save. Driver apps stop updating. A partner integration changes overnight. Putting that right takes real technical expertise: tracing the fault, protecting the data while it is fixed, and making sure it does not happen again. When a system has been built at speed with AI, the people who built it, or who are selling it, may not fully understand how it works underneath, and an urgent fault is the worst moment to find that out.

The question is not whether something can be built. It is whether it can be run, repaired, protected and trusted, year after year.

Whether you are choosing a dispatch platform, weighing up one of the newer alternatives or thinking of building your own, these are the questions worth asking.

1. How long have they been doing this?

When choosing chauffeur software, experience is the first thing to look at. Dispatch software looks simple from the outside. A booking comes in, a driver is assigned, a job is completed and invoiced. The reality is years of edge cases: multi-leg international jobs, flight changes at midnight, partner work in three currencies, fares that change by client, zone and date, VIP passengers with very specific preferences.

Features are now the quick part to build. What cannot be built quickly is everything a platform has learned from real operators using it every day. When you choose an established system, you are not just paying for what it does. You are paying for the thousands of problems it has already solved, so that you never have to meet them.

Built alongside operators, for operators

That knowledge comes from the road, not from a specification. Chauffeur work is a physical, real-world operation, and software for it has to survive the environment it runs in.

CDS has been built alongside operators, for operators, by a team that understands both the technology and the road. That balance matters. Software built by people who know technology but not the industry misses the realities of the job. And software sold by one operator to the operators it competes with can never be truly neutral.

That has been our approach for over a decade. From the start, our aim has been simple: to give independent operators the same tools as the biggest names in the industry, at a fair price. In that time the platform has grown to at least five times the functionality it launched with, and we release updates every week. Independent operators deserve enterprise-level tools, and a price that reflects the value they get.

2. Is it just software, or is there a network behind it?

This is where the difference is greatest when choosing chauffeur software. Software can be built fast. A network cannot, because a network depends on other people choosing to be part of it.

CDS Connect links operators who work to a shared standard, so jobs can move between trusted partners with confidence. When you send work to another CDS Connect operator, you know how it will be handled, and your client sees your brand from start to finish. With more than 350 operators on CDS across around 25 countries, that network grows every time an operator joins.

Alongside CDS Connect, integrations with GNet, HBX, Groundspan, Transferz, Carey International and the CDS Open API connect operators to the wider industry. Each of those connections has to be built, tested and kept up to date as partners change their own systems.

3. What does the price actually cover, and where does it run?

Building software is a one-off cost. Running it is a cost that never stops. Hosting, security, backups, monitoring, updates and support all have to be paid for every month, by someone. A cheaper platform either includes them or leaves them out.

Many newer, low-cost and in-house systems run on budget servers, chosen because they are cheap rather than because they are right for a business-critical system. Before you trust one, ask some simple questions:

• Who manages the server, and how is it protected?
• Who has access to it, and is the data encrypted?
• How often is it backed up, and has anyone tested restoring it?
• What happens if it goes down on a Saturday night with twenty jobs on the board?
• Who applies the security updates, and how quickly?

Building a system is not the same as being able to maintain it. Running a dispatch platform properly is a serious, ongoing commitment, and it is worth asking whether a system built at speed, whether bought in or built in-house, has the people and the expertise behind it to keep that commitment for years to come.

A lower-cost alternative often turns out to be a narrower one. The gaps show up later, as workarounds, extra tools bolted on to fill them, and staff time spent doing by hand what the system should do for them. When you add those up, cheaper is rarely cheaper.

4. Who answers when something goes wrong?

Support is one of the most overlooked questions when choosing chauffeur software. Every system will have a moment that needs attention. What matters is who is on the other end when it does, and whether they truly understand the system. With an in-house build, the answer is often you, or the one person who built it.

CDS is a family-run, local team based in Stirling, Scotland, UK, working side by side every day and serving operators in around 25 countries. We are proud of that combination: locally rooted, internationally connected. When a business-critical issue comes in, it is picked up straight away, even by email, by the people who built the platform and know it inside out. If a call is the quickest way to resolve it, we pick up the phone. General questions that are not urgent are worked through in turn, so the critical ones always come first.

Alongside that, every CDS user can join our free one-hour training bootcamps, held twice every week, so new staff and experienced users alike can get the most from the platform. Support is not a queue. It is a conversation.

5. Is your data safe, and are you compliant?

Your dispatch system holds some of the most sensitive information in your business: client details, passenger names and phone numbers, home addresses, travel plans and, for VIP passengers, exactly where a high-profile person will be and when. In the wrong hands, that is not just a data problem. It is a security problem for the people you drive.

What data protection law means for operators

Under data protection law, including UK GDPR and the EU GDPR, the operator is the data controller. That means you remain responsible for that data, whoever builds or hosts your software. You are required to use only providers who can give sufficient guarantees about how personal data is protected, and that relationship should be covered by a written data processing agreement.

If there is a personal data breach, it must usually be reported to the relevant regulator, such as the Information Commissioner's Office in the UK, within 72 hours, and serious failures can lead to fines of up to 4% of annual worldwide turnover. Many other countries now have similar laws, so wherever you operate, the same principle applies: the data is your responsibility.

That is a heavy responsibility to place on a system built at speed and hosted on a budget server. When choosing chauffeur software, it is worth asking any provider, or yourself if you are building in-house:

• Is there a data processing agreement in place?
• How is the data held, and is it protected to the standards the law requires?
• When a driver or member of staff leaves, can their access be removed immediately?
• If something went wrong, could you detect it and report it within 72 hours?

Where CDS stands

CDS is entirely cloud-based, hosted on the Microsoft Azure cloud, giving operators the security, resilience and compliance standards of one of the most trusted cloud platforms in the world. Your data is processed securely in the cloud and stays in your possession.

There is one more question, and it is easy to overlook. Is your software provider also an operator in your market? A platform owned by one operator can never be neutral ground, because the owner can see everyone on it. If the company that holds your client list and pricing is also competing for the same work, it is reasonable to ask who can see what. CDS is completely independent. We are IT specialists, not operators, and we leave chauffeuring to the experts. We do not run chauffeur jobs, and we never compete with our clients.

6. Will they still be here in five years?

When choosing chauffeur software, it pays to think long term. Switching dispatch systems is a significant job. Data has to move, staff have to retrain and clients have to keep receiving the same standard of service throughout. It is not something any operator wants to do twice, and it is harder still when the system you are leaving was never built to export your data cleanly.

CDS has grown by word of mouth and reputation, and our retention speaks for itself. Many of our clients have been with us from the very start. We exist to support independent operators, and we are independent ourselves.

A checklist for choosing chauffeur software

Before you sign up to any dispatch platform, or decide to build your own, ask:

• How many years of real chauffeur operations has this software learned from?
• Is there a network of trusted operators behind it?
• What does the price include, and where is the system hosted?
• Who responds when something business-critical goes wrong?
• Who is responsible for data protection, and is there a data processing agreement?
• Does the provider compete with me for work?
• How long do their clients typically stay?

Paying for professional software is, in the end, paying for not having to worry about it. The right provider will be glad you asked, and so will your clients.

Always building, always evolving.