Use Farmhand to prepare a property brief before a client meeting

Start with the question your client has

A buyer wants to know whether a home fits the search you agreed on. A seller wants to discuss their property in the context of nearby listings. Give your AI that purpose before asking it to fetch anything. Otherwise, you get a long property summary and still have to decide which parts matter.

For a buyer meeting, name the property and supply the buyer's stated requirements. Include the features they have called essential. Keep your own assumptions out of that list. A request for a home office doesn't establish a bedroom count or a preferred neighborhood.

Check the connection once

Farmhand supplies property data to an AI tool that supports authenticated HTTP requests. You need an account and access to the records you plan to use. Its setup guides explain the available connection. The AI does the drafting; Farmhand supplies the property context.

Before starting the brief, ask your AI to identify the documented lookup it will use and the account permissions it needs. Store the API key in the connection's secret settings. Keep credentials out of the brief and the prompt you reuse.

Build a brief you can check

Keep asking price, a past sale price, and an estimate in separate fields. Your AI should preserve the meaning of each number even when the source uses a short label. A neat table won't help if it quietly turns an old sale into today's asking price.

1. Confirm the property by address and the identifier returned with its record. Resolve a unit or parcel mismatch before continuing.
2. Retrieve the available record. Keep its source and retrieval time with the facts you extract.
3. Separate the property facts from the buyer's preferences. Mark a missing fact as unknown.
4. Ask for a short meeting brief, then inspect the source record for any fact that affects the conversation.

A prompt to adapt

Prepare a property brief for my review.

Property: {{address and listing or parcel identifier}}
Meeting purpose: {{buyer showing or seller conversation}}
Client's stated requirements: {{requirements}}

Use the records available through my authorized Farmhand connection. Identify the property before retrieving details.

Return a concise overview and a fact table with source names and retrieval dates. Separate asking price, recorded sale price, and estimates. Connect relevant facts to the stated requirements. List missing information and questions I should resolve before the meeting.

Use only supported facts. Label your interpretations. Return a draft and wait for my review before sharing it.

Keep a conflict visible

For a fictional example, suppose a listing says 1,900 square feet and a second authorized record says 1,760. Keep both figures with their source labels. Ask which measurement the records describe and who can confirm it. Don't let the AI average them into a new number.

Use that same approach for an uncertain feature. If a client wants a separate entrance and the record doesn't address it, put it on the showing questions. Leave the feature out of the confirmed facts.

Save the format after you review the result

Keep a copy of the brief format and the prompt. On the next property, replace the inputs and retrieve the current record again. Old facts need a new check even when the document layout stays the same.

The directory lists Farmhand at $29/mo. Check your account's coverage and any data conditions before using this workflow. The connection price alone doesn't establish access to a particular MLS or field.