Solution guide

A customer record your whole team can trust.

Customer details live in people's phones, in spreadsheets, in WhatsApp chats and in old email. When a colleague is away, the relationship goes with them. A CRM gives every customer one record that the team shares — and, used well, it makes follow-up routine instead of heroic.

Request a project quote Draft a project brief

Start by asking: do you need to build one?

For most businesses the honest answer is to adopt an existing CRM and configure it well. Mainstream products are mature, cheaper than a custom build and maintained by someone else. Building makes sense in narrower cases:

your sales or service process is unusual and standard pipelines do not fit;
customer data must be tightly combined with your own operations — bookings, orders, jobs;
you need a data model, permissions or workflows that products cannot express;
you are paying for a large product but using a small slice of it.

Even when you adopt a product, projects often still need work around it: importing and cleaning data, connecting website forms and messaging, and building the reports you actually read.

What makes a customer record useful

One record per customer or company, without duplicates, with the contacts that belong to it.
A running history of conversations, quotes, bookings and notes, so anyone can pick up the thread.
Next steps that cannot be forgotten — follow-up tasks with owners and dates.
A simple pipeline showing where each opportunity stands, with stages that mean something to your business.
A few reports that answer real questions: who has gone quiet, what is waiting on us, what is likely to close.

Resist the urge to track everything. A CRM with eight fields people actually fill in beats one with eighty that nobody does.

Decisions to make before importing a single contact

What is a "customer" here? A person, a company, a household? Many problems start with an unclear unit.
Who owns the data and who may see it? Sales, service and management usually need different access.
How is existing data cleaned? Expect duplicates, missing fields and several versions of the same company name, in two languages.
What does each person agree to? Record where contact details came from and what the person consented to, particularly for promotional messages.
How does new information get in? Website forms, messaging, email and manual entry should all land in the same place.

Hong Kong specifics: names, consent and ID numbers

Names in two scripts. A customer may be known by an English name, a Chinese name or both. Searching and de-duplicating should handle this deliberately.
Direct marketing rules. The Personal Data (Privacy) Ordinance has specific requirements when personal data is used for direct marketing, including how you tell people and how they can opt out. Build consent and opt-out into the record, and take advice before running campaigns.
Hong Kong ID card numbers. Official guidance restricts collecting them without good reason. Do not make them a field by default.
WhatsApp as a channel. Many relationships run on it. Decide how those conversations and the consent behind them are reflected in the record — see the messaging guide.

These are points to plan around rather than legal advice; the right answers depend on your business.

What makes a CRM project large or small

The state of the existing data and how much cleaning it needs.
The number of user roles and the permission rules between them.
Connections: website, email, messaging, accounting, booking or orders.
How custom the pipeline, fields and reports are.

If you want to size it, use the project cost estimator; a CRM is closest to a web application or internal tool with a few integrations.

Frequently asked questions

Should we buy a CRM or build one?

Usually buy, then configure it well. Building is worth considering when your process is unusual, when customer data must combine tightly with your own operations or when products cannot express what you need. We will say so honestly if a product fits.

Can you connect a CRM to our website and WhatsApp?

Often, yes. Website forms and messaging can create or update records automatically. What is possible depends on the CRM and on the messaging provider's rules.

Can you help move our existing contacts in?

Yes, and the import is often the hardest part. We would review your sources, agree what to keep, clean duplicates and import in stages, so the new system is trusted from day one.

How do we handle consent and marketing messages?

Record where each contact came from and what they agreed to, and make opt-out simple. Hong Kong's Personal Data (Privacy) Ordinance has specific direct-marketing requirements, so take professional advice before running campaigns.

Is a custom CRM more expensive?

The build costs more up front than a subscription, but it can cost less over time if you are paying for many seats you barely use. Compare the total cost over a few years, including the effort of bending a product to fit.

Customer details scattered everywhere?

Tell us where they live today and what you wish the team could see. We will tell you whether to adopt a product or build.

Request a project quote