Client Data & CRM · Prepared for Harneys · June 2026

Enter a client once.

One client record that flows to CRM, BD, events, matters and Elite 3E — so nobody re-keys the same client three times. A client-data and relationship system shaped around how an offshore firm really works: intermediary-driven, multi-jurisdiction, compliance-first — and adopted across your 11 offices in weeks, not years.

1×
Enter a client once → everywhere
3E
Synced to finance · not re-keyed
11
Offices · one client record
3
Delivery hubs · Taipei · Bangalore · US
◇ One system across your footprint
British Virgin IslandsCayman IslandsBermudaCyprusLuxembourgJerseyAnguillaHong KongSingaporeShanghaiLondon British Virgin IslandsCayman IslandsBermudaCyprusLuxembourgJerseyAnguillaHong KongSingaporeShanghaiLondon

  Who you'd be working with

Built by someone
who's done this before.

Founder-led — fourteen years of enterprise cloud, CRM and delivery experience, now applied to the systems your firm runs on.

◇ Founder & Principal

Lawrence Kuok

Fourteen years in enterprise CRM delivery, cloud, business development and AI — at Deloitte, Microsoft and Amazon — now three years building PGIntel. The exact blend a firm-wide CRM rollout needs: the platforms, the integration, and the delivery discipline to land it.

Previously Deloitte·Microsoft·Amazon
14+
Years · cloud, CRM & delivery
CRM
Dynamics · Salesforce · Oracle — implemented

  The path here

4 years
Deloitte
CRM implementation · Oracle, Salesforce
5 years
Microsoft
Cloud · Business Development · Dynamics CRM
2 years
Amazon
Cloud · AI / ML
3 years · now
PGIntel
Founder · building this

  And not a one-person shop

A senior bench of strategists, designers and engineers across three time zones — assembled around your engagement, close through delivery, and built to move fast.

Taipei
Bangalore
United States

  Cases delivered across

HospitalityRetailFMCGChambers of CommerceMembership OrganisationsFinancial & Professional Services

  In conversation with

LululemonAesopAgodaIHGAdidasTikTokEvercore

  The problem we're solving

The CRM is the
tip of the iceberg.

The visible ask is "manage client information better." The real project underneath is client master data — one record, entered once, reconciled across CRM, matters and finance. Here's the iceberg, and how we'd design around it.

01

You enter every client three times.

A new client is typed into the CRM, again into the deal/matter system, and again into Elite 3E for finance — same data, three silos, reconciled by nobody. Then multiply by 11 offices.

Our approachOne client master record, entered once, that flows to CRM, BD, matters and 3E. Change it in one place; it updates everywhere.
02

Partners won't feed it.

Fee-earners won't do data entry. Legacy CRMs die from empty fields and stale contacts — the firm pays for licences no one opens, and the data is never trusted.

Our approachAI captures relationships and interactions straight from email and calendar. The system fills itself; lawyers approve, they don't type.
03

It ignores how offshore works.

Your work arrives through intermediaries — banks, trust companies, accountants, onshore firms. Generic CRMs model "accounts," not referral networks, originations or cross-jurisdiction introductions.

Our approachA relationship graph built around intermediaries and who really originates work — across BVI, Cayman, funds and private client.
04

It has to honour privilege.

Confidentiality, conflicts and KYC/AML can't be bolted on afterwards. If a system can't honour ethical walls and clear security review, partners simply won't put real data in it.

Our approachRow-level security, ethical walls, conflicts and KYC in the core, full audit trail — and integration scoped with your IT team from day one.

  What we'd build for Harneys

Built for how
Harneys works.

Not a generic sales CRM bent to fit a law firm — a client-data and relationship system shaped around offshore practice, your intermediaries, and your compliance reality.

01

Single client master record

Enter a client once. One reconciled record flows to CRM, BD, events, matters and Elite 3E — current and prospective clients alike. No more typing the same name into three systems.

02

Intermediary & relationship intelligence

Map every referral source, intermediary and introducing firm — and see who actually originates work, across offices and practice groups.

03

BD pipeline, events & contacts

Pitches, engagements, events and contacts in one place across 11 offices — surfacing the BVI ↔ Cayman ↔ funds ↔ private-client cross-sell you're leaving on the table.

04

Conflicts, KYC & confidentiality

Conflict checks, KYC/AML status and ethical walls in the core — not bolted on. Built for privileged data and offshore regulatory scrutiny.

05

Integrates with your stack — built with IT

Outlook, iManage and Elite 3E, connected the way IT needs it. Anything touching your finance system of record is built with your IT team and designed to clear security and procurement.

06

AI auto-capture & partner dashboards

AI captures relationships from email so the system fills itself, surfaces dormant relationships worth a call, and feeds board-ready dashboards of originations and pipeline by office, jurisdiction and practice.

  The architecture

Enter once.
Sync everywhere.

Your existing systems stay exactly where they are. We build the one layer in the middle that makes them work as a single source of truth — so a client is entered once, not three times.

What people use
Enter once

Unified Client View

The CRM front-end — BD pipeline, events, contacts, current and prospective clients.
One screen for Marketing & BD — create and read here.
↓  create / update once
The layer we build

Client Data Hub

Golden client record · validation & de-dupe · sync engine.
One source of truth that reconciles every system below.
↕  two-way sync
Systems of record — unchanged
Elite 3E
Finance & billing
System of record
Intapp
Conflicts, intake & matters
Stays
Outlook
Email, calendar & contacts
Stays
Excel
Manual lists & shadow data
Retire / absorb
Your systems stay in place — we build the layer that makes them stop re-keying the same client three times. Illustrative; the exact depth of the 3E connection is what we'd pin down together first.

  Proven foundations

The hard parts,
already built.

We're not starting from a blank page. The closest analogue to what Harneys needs — a relationship CRM for a membership organisation — is already built and running, on foundations engineered for exactly this.

◇ Flagship analogue · Membership relationship CRM

Chambers of Commerce

We've built the member and relationship systems for international chambers of commerce — the AmCham / BritCham kind of organisation. Hundreds of member companies and their contacts, the events that connect them, the sponsors and the referrals between them: one member record, entered once, driving the directory, events, dues and board reporting.

→ A chamber is a relationship network. So is Harneys.
Enter once
One member record drives the directory, events, dues and board reporting — no re-keying.
Relationship graph
Members, contacts, sponsors and referrals — exactly the originations map your BD needs.
Adoption, cracked
The same "staff won't update it" problem that kills legal CRM — already solved.
Secure multi-tenant platform

The engine behind it

The multi-tenant platform those chamber systems run on: role-based access (partner / fee-earner / staff), tenant isolation, audit logging, secure portals and PDF reporting.

→ The spine of a partner-grade CRM.
Next.js · NextAuth · Postgres · Vercel
Master data & system-of-record sync

Data Integration Pipelines

Production pipelines that reconcile, de-duplicate and sync records across systems — exactly the "enter once, reconcile to the system of record" problem 3E sits at the centre of.

→ One client record, synced — not re-keyed into 3E.
API sync · field mapping · de-duplication
Confidentiality by design

Security Hardening

Row-level security, least-privilege access policies and full audit trails — a repeatable discipline for locking down sensitive data and clearing security review.

→ Privilege, conflicts & KYC, enforced in the data layer.
Postgres RLS · audit logging · access policy
Live intelligence dashboards

Real-Time Dashboards

Platforms that integrate 30+ live sources into board-ready dashboards with momentum scoring and alerts — the data muscle a CRM lives or dies on.

→ Originations & pipeline intelligence, auto-generated.
Data pipelines · BI · alerting
AI pipelines in production

LLM & Agent Workflows

Summarisation, enrichment, voice and autonomous agents — shipped inside real, paying products. The auto-capture and assistant layer is something we run today, not slideware.

→ The adoption engine: a CRM that fills itself.
Claude · LLM pipelines · agents
CRM platform implementations

CRM, implemented

We've delivered CRM implementations end-to-end — configuring and integrating the right platform, or building bespoke where a platform won't fit. Fluent across Microsoft Dynamics 365, Salesforce, and newer tools like Monday.com.

→ Deploy the right platform, or build — chosen for Harneys.
Dynamics 365 · Salesforce · Oracle · Monday.com

  Where we'd start — with you

First, we learn
how Harneys works.

Before a line of code, we'd sit with your teams and map reality — not assume it. The questions we'd start with:

Q1

When a new client comes in, what gets created — and in which systems, entered by whom?

Q2

Where does the re-keying hurt most today — and what's the cost when a record is wrong or out of date?

Q3

Do you need data to flow automatically into Elite 3E, or is the real goal simply single point of entry?

Q4

Which relationships and intermediaries matter most to see — and who really originates the work?

Q5

Current vs. prospective clients, BD and events — one unified view, or kept separate today?

Q6

Twelve months on, what does "this is working" look like — for partners, BD and IT?

  How we'd run it

Weeks to value.
Not years.

Start with a focused discovery that ends in a working prototype of the highest-value piece. Prove it on one practice group, then roll across all 11 offices with the model already validated.

Week 1–3
01

Discovery

Map exactly how a new client gets entered today, in every system — and where the re-keying and risk live. Ends with a clear plan and a working prototype of the highest-value piece: enter-once sync.

Week 2–6
02

Configure & build

Stand up the client master record, BD pipeline, events and partner dashboards. Integrate Outlook + calendar first, so relationship capture is automatic from day one.

Week 4–8
03

Integrate Elite 3E

Connect to 3E and the DMS as the systems of record, migrate and de-duplicate contacts across offices, and embed conflicts/KYC. Done with IT, built to clear security review.

Ongoing
04

Adoption

AI auto-capture switched on, partner dashboards live, light-touch enablement. Success measured by usage and originations — not licences purchased.

Built with IT, not around it. Anything that touches Elite 3E is scoped and delivered alongside your IT team and designed to pass security and procurement review.

Client Master DataSingle Point of EntryElite 3E IntegrationCRM ImplementationDynamics 365 · Salesforce · MondayOutlook · Calendar SynciManage / DMSConflicts · KYC / AMLRow-Level SecurityContact Migration & De-dupBD · Events · PipelinePartner DashboardsAI Auto-CaptureMulti-Jurisdiction