Case study · AI × CRM · Property & agriculture · Client unnamed

The CRM is the engine. The GPT is the driver's seat.

A property executive running two brands — residential association work and an agricultural investment arm — needed campaigns to move at the speed of a conversation, not the speed of a CRM login. The answer was not another dashboard. It was removing the interface entirely.

The client is not named at their request. Everything below is the architecture we designed, built and operate for them today.

Before the bridge

  • Every campaign meant logging into the CRM, building lists by hand and formatting emails one at a time
  • Sending addresses and brand identity depended on who set the campaign up that day
  • Turnaround from idea to sent campaign measured in days of back-and-forth
  • No reliable record of what was sent to whom without digging through the CRM

With the bridge in place

  • Draft to approved branded campaign in about ninety seconds, from a chat window
  • Brand identity, sender and reply-to enforced by the system on every send
  • Unsubscribes, do-not-contact and bulk caps handled without human memory
  • Every send logged and reportable back through the same conversation

What we built

A private Custom GPT on the client's own accounts

One assistant, configured per brand, that knows the voice, the offers, the audiences and the sending rules. The principal talks to it like a colleague: 'draft a follow-up for everyone who enquired on Wunkar and hasn't replied.'

A secure API bridge into GoHighLevel

The GPT never touches the CRM directly. Every action goes through a server-side bridge that validates the request, resolves the right project, applies audience filters, and enforces sending rules before anything moves.

Deterministic brand and sender routing

Agriculture contacts route through the FarmInvest identity; everything else through Property Association. The sending address and reply-to are chosen by the system, not by whoever happened to be logged in — and never a generic platform address.

Branded previews before anything sends

Every draft renders as a real, fully branded email the principal can open on their phone. Nothing goes out from an unreviewed blob of text — what is approved is exactly what lands in the inbox.

Explicit approval, then send — with guardrails

The GPT drafts; the human approves. Bulk sends are capped, do-not-contact and unsubscribe lists are honoured automatically, and every send is logged so the record of what went out, to whom, and when is never in doubt.

Reports without opening the CRM

Campaign results, lead counts and follow-up status come back through the same conversation. The principal asks a question; the system answers it from live CRM data.

Why it matters

Most CRM rollouts fail at the same point: the person with the relationships never logs in. This build accepts that reality instead of fighting it. The CRM stays the source of truth — every contact, every send, every report — but the interface becomes a conversation the principal was already having.

Campaign turnaround went from days of back-and-forth to about ninety seconds of chat. Brand consistency is no longer a training problem; it is enforced at the API level. And because every action passes through the bridge under explicit approval, speed never costs control.

Want your CRM driven like this?

Start with a paid working session. We map your CRM, your brands and the approval flow, then scope the bridge that fits.

See the automations service →