Brand-Consistent AI Outputs for Commercial Real Estate Brokers: Fixing Siloed Projects

Some of the AI outputs a commercial real estate broker generated with Claude came back off-brand, with logos missing and the wrong colors. The AI was not the cause. The brand kit lived in only some of the broker's Claude projects, and each project is walled off from the others.

The broker and a partner source commercial deals, and they had already built several AI workflows. When we audited them, the off-brand output pointed to a wider pattern we see with real estate agents and teams: tools get added one project at a time, and nobody sets up a shared home for brand assets and deal files.

The situation

The broker works commercial deals as both a broker and an investor, together with a partner. Both of them use Claude for deal documents, graphics for listings and scheduled tasks. We opened the call by auditing what already existed.

Two brand kits were in play, one for a national brokerage and one for the broker's own team. Neither was saved somewhere every project could reach.

What was broken

The audit turned up four separate problems.

• Brand kits lived inside individual Claude projects. Projects do not share files with each other, so any project without the kit produced generic graphics with no logo and the wrong colors.
• Deal folders in Google Drive had no parent folder. Claude, and the scheduled tasks we plan to run, could not reliably find the property photos and documents for a given deal.
• The letter of intent template was the same each time, but the fields changed deal by deal, and a lease differed from a purchase.
• Headshots and building photos were scattered. The design tool needs them in a known place to produce listing graphics without a person hunting for files.

What we built

The call covered the first layer. The rest was queued.

• We began connecting Gmail, Google Drive and both brand kits to Claude's account-level design systems, so one brand kit can serve every project instead of being copied into each. The brand kit upload started during the call.
• The goal is a single operating dashboard for all commercial deals. Version one is queued, with its scoring logic taken from a spreadsheet of past deals that the broker had already exported.
• We queued a Gmail scrape to feed the dashboard, plus interviews with Claude to capture the letter of intent template from example documents, including the lease and purchase differences.
• We queued a Drive reorganization under one parent folder, with a central folder for headshots and building photos.
• We assigned the partner to audit each project's context folder, so every project points at the account-level design system.
• We queued a voice-first dictation tool for daily use, because typing speed had been named as a bottleneck for prompts and email.

What changed

No result was reported when the call ended, and the build was interrupted. A Claude outage stopped the Gmail scrape and may have cut off the brand kit extraction, so both were set to resume once service returned.

What did change is where the pieces live. The brand kit is set to get one home instead of a copy in every project. Each deal is moving toward one parent folder with its photos and documents in predictable places. The letter of intent template is being captured through an interview Claude can refer back to.

Check your own account in ten minutes

This section is advice, not a description of the client's account. Open three or four of your AI projects and ask each for the same simple graphic. If the logos and colors differ, your brand kit is trapped in individual projects. Move it to the account level, then point each project at it.

Then pick one deal and try to find its photos, its documents and its template from a single folder. If you cannot do that in about a minute, an AI or a scheduled task cannot either. Create the parent folder before you automate anything on top of it.

Frequently asked questions

Why do Claude projects produce off-brand graphics?

Each project holds its own files and instructions. If the logo and color palette were added to some projects and not others, the projects without them have nothing to match, so they produce generic output. Saving the brand kit once at the account level removes that dependency on each project.

Where should deal files live so AI can find them?

In one parent folder, with each deal in its own subfolder that has the same structure every time. Claude and any scheduled task can then locate property photos and documents by a predictable path instead of searching through unrelated folders.

How do you capture a template whose fields change every time?

Interview the person who fills it in. Give Claude several finished examples, such as a lease version and a purchase version, and have it ask what changes and why. The answers become a written field guide that lives next to the template.

Does voice dictation help with AI prompts?

On this build, typing speed was named as a bottleneck for prompting and email, so daily dictation practice was assigned. We did not measure the effect. The reason to try it is that speaking is faster than typing for most people, and a longer prompt gives Claude more to work with.

If your AI outputs, deal files or templates are scattered across projects, book a 30-minute AI follow-up and reporting audit. We look at where your brand, files and templates live and show you the one-home structure.