Google Contacts

The first real setup decision is auto-creation. Google Workspace can automatically save people you email into an "other contacts" pile, which is convenient but turns your account into noise within weeks. Decide whether you want that on. I lean towards keeping the auto-saved pile separate and only promoting people into your real, labelled contacts when they matter, so the address book reflects relationships rather than every reply-all you were copied on.

Next, sort out labels before you have hundreds of contacts, because retrofitting structure onto a mess is painful. Labels are Google Contacts' only real organising primitive, and they are flexible, so a contact can carry several. Set up a small, deliberate set: clients, prospects, suppliers, personal, and whatever segments matter to your work. Resist the temptation to create thirty labels you will never maintain. A handful you actually use beats a taxonomy you abandon.

Finally, confirm sync. If you are on Workspace, your contacts should flow to your phone, your mail client, and anywhere else you sign in with the same account. Check this works on your phone early, because a contact that exists in the web app but not on your device is a contact you will not have when you need it.

How to actually use it

The core loop is simple: capture, label, enrich, in that order. When a new person matters, create the contact deliberately rather than relying on auto-save, and add the fields you will actually use: name, company, role, email, phone. The notes field is underrated, and I treat it as the place where context lives, so when I open a contact months later I remember why this person is in my orbit.

Labelling is the workflow that makes everything else pay off. The moment you create or promote a contact, attach the right label or two. This is what lets you later email a whole segment at once, or filter your address book down to just clients when you need to. A contact with no label is a contact you cannot find by intent, only by name, and you will not always remember the name.

Merging duplicates is the third habit. Google Contacts has a built-in suggestion that surfaces likely duplicates and merges them, and running it every so often keeps the address book honest. Duplicates are inevitable once you sync across devices and import from a few sources, so make this a periodic chore rather than waiting until the mess is unmanageable.

Power moves

The biggest non-obvious lever is using labels as send-lists. Because Gmail lets you type a label name into the recipient field and expand it to everyone in that label, a well-maintained label becomes a lightweight mailing list with zero extra tooling. Keep the label tight and current and you have a free segment you can email in seconds.

Treat the structured fields as a future export schema. Everything you put into the proper fields (company, job title, custom fields where available) comes out cleanly when you export to CSV, and that export is what you will feed into a real CRM like HubSpot the day you outgrow the address book. Notes typed loosely do not migrate; structured fields do. So if you suspect a contact will matter commercially, capture the data in the right boxes now and your future migration is a clean import rather than a rebuild.

The export and import flow itself is a power move. You can pull your whole contact set to CSV, clean it in a spreadsheet, and push it back, which is far faster than editing hundreds of records by hand. Used carefully this is how you do a bulk relabel or a mass field correction.

Where it fits your stack

Google Contacts is the connective tissue of a Google Workspace setup. It feeds Gmail autocomplete and label-based sends, populates Calendar invites, and syncs to your phone's native dialler and messaging, so the same clean record shows up everywhere you work. That ubiquity is its real value: get the record right once and every Google surface inherits it.

In a growth and ops stack it plays the role of the pre-CRM. It is where contacts live before they earn a place in a pipeline tool, and the CSV bridge means you are never locked in. When you adopt a dedicated CRM, Google Contacts becomes either the clean source you import from or the personal address book that sits alongside the commercial system. It is not trying to be the deal tracker, and you should not force it to be.

Pitfalls to avoid

The first pitfall is letting auto-saved contacts pollute your real list, so keep the operational set separate from the auto-captured pile. The second is skipping labels, which leaves you with a flat list you can only search by name, defeating the point of having a structured address book. The third is ignoring duplicates until they multiply across every device, so merge periodically rather than never. The fourth is treating Google Contacts as a CRM and trying to track deals, tasks, and pipeline in the notes field, which it handles badly: when you need that, move to a real CRM and let Contacts stay the clean address layer underneath. The last is dumping context into free-text notes that will never export cleanly, so put anything you will want later into proper fields.