Trade area brief for every new HubSpot site-acquisition deal

Build me an agent workflow that auto-briefs every new HubSpot deal in my Site Acquisition pipeline with a trade area read from Sites USA.

Trigger: HubSpot incoming webhook for deal creation. Only act when the new deal's pipeline matches my Site Acquisition pipeline. If a deal lands in any other pipeline, exit early without doing anything.

When a matching deal lands, do the following in order:

1. Read the deal. Use HubSpot Get Deal with the deal id from the webhook, requesting the property address, latitude, longitude, the deal's target tenant category (a custom property on the deal), and hubspot_owner_id. If latitude or longitude are missing, attach a one-line HubSpot note on the deal saying coordinates were not available and exit. Do not call Sites USA without coordinates.

2. Build the trade area. Call Sites USA Request Trade Area Boundaries with the deal's lat/long and a 3-mile radius ring. Keep the returned WKT polygon; every Sites USA call below reuses it.

3. Pull demographics. Call Sites USA Get Demographics by WKT for the ring polygon. Ask for current population, daytime population, household count, median household income, and 5-year population growth.

4. Pull competition. Call Sites USA Get Merchant Counts by WKT for the same polygon, filtered to the deal's target tenant category (e.g. coffee, fast casual, dollar store, urgent care). This is the competitive saturation gauge.

5. Pull the containing geographies. Call Sites USA Get KTA Info by Coordinates with the deal's lat/long so the note can reference the zip, city, county, and MSA the site sits inside.

6. Write the brief. Draft a concise trade area summary, 2 to 4 paragraphs, no fluff. Cover: location context (city, MSA, zip, county); demographics inside the 3-mile ring (population, daytime population, household count, median income, growth signal); competitive read for the tenant category (how many same-category merchants sit inside the ring, with a one-line read of whether the area looks under-served, balanced, or saturated); a short "what to dig into next" line for the deal owner. If the demographics call returns thin data (rural site, sparse coverage), say so explicitly. Do not invent numbers. Do not pad. No marketing voice.

7. Attach the brief. Call HubSpot Create Note with the brief as the note body, associated to the deal id.

8. Queue the review. Call HubSpot Create Task with subject "Review trade area brief", a due date 48 hours from now, associated to the deal, and assigned to the deal's owner using hubspot_owner_id from step 1. Use HubSpot Get Owner if you need to resolve the owner id.

Constraints: the brief should be short. Brokers and tenant reps skim. Read the target tenant category from the deal, do not hardcode a default. The note is the primary artifact and the task is the nudge; do not post anywhere else (no Slack, no email).

Additional information

What does this prompt do?

A demographics-and-competition summary lands on every new site-acquisition deal as a HubSpot note, ready before the first internal review.
A Review trade area brief task gets queued for the deal owner with a 48-hour due date, so nothing sits without a next step.
The brief covers population, median income, household count, growth signals, and same-category competitors inside a 3-mile ring around the site.
If the site is rural or the data thins out, the note says so plainly instead of inventing numbers.

What do I need to use this?

A HubSpot account with permission to read deals and create notes and tasks.
A site-acquisition pipeline in HubSpot whose deals carry a property address and latitude and longitude.
A Sites USA REGIS Online account with API access.

How can I customize it?

Swap the ring radius. 3 miles is the default, but brokers often want 1, 3, and 5 mile reads stacked.
Change the tenant category used for the competition count, like coffee, fast casual, dollar store, or urgent care.
Point the trigger at a different pipeline, or only fire on specific deal stages.

Frequently asked questions

Which HubSpot pipeline does this run on?

Whichever pipeline you point it at. Most teams use it on a pipeline called Site Acquisition or Site Selection, but the agent only acts on the pipeline you choose.

Does the deal need to carry coordinates?

Yes. The agent uses the latitude and longitude on the deal to anchor the trade area lookup. If your deals only store a street address, you can add a geocoding step at the start to fill them in.

What happens if the site is rural and demographic data is thin?

The note will say so explicitly. The agent is told to flag sparse coverage instead of fabricating numbers, which keeps the brief honest for sites outside dense markets.

Can I change the ring radius or use drive-time instead?

Yes. The 3-mile ring is the default. You can swap to a different radius, use a drive-time area, or stack multiple rings in the same brief.

Will this overwrite my own notes on the deal?

No. The agent creates a new note attached to the deal. Anything you or your team has already written stays untouched.