Give every vendor a market update worth reading

Routine vendor calls often start with the same ingredients: a portal result, an anecdote from the weekend and a broad statement about buyer activity. The numbers may be current, but they rarely answer the question a vendor actually has: what changed, and what should we discuss next?

A more useful workflow starts before the call. Give the agent a short, dated market snapshot for the relevant suburb and property type, show the recent context, and turn the evidence into questions for human review. The same snapshot can support every matching vendor record, so the agency does not need to buy or prepare a new report for each contact.

A four-month view changes the conversation

Here is a real example from Richmond, Victoria 3121: houses, across all bedroom counts. The snapshot was captured on 10 September 2026 and covers reporting periods through 31 August.

The August days-on-market reading fell by 16 days from July, a 39.0% decrease. At the same time, the reported Raw HtAG stock-on-market measure was unchanged at 20.

That combination is more useful than either number alone. It suggests a prompt for the agent: The latest reported sale-time measure moved lower while the stock measure held steady. Are we seeing stronger enquiry and cleaner campaigns, or is this a short-term movement that needs another month of evidence?

The four-month context matters. August’s 25-day reading is close to May’s 26 days. The data therefore does not prove a sustained acceleration. It gives the agent something concrete to investigate against inspection feedback, comparable campaigns and the circumstances of the vendor’s property.

The HtAG data dictionary defines Days on Market as the median time for a for-sale listing to reach a reported sale. This example displays the historical endpoint’s reported dom readings for each period. The stock figures are its raw som readings. Stock on Market Percentage (SoM%) is a separate ratio of listed dwellings to estimated dwellings; the values 15, 11, 20 and 20 here are numeric SoM readings.

For supply context, HtAG’s detailed Stock on Market methodology focuses on new unsold listings introduced during a period. Inventory includes listings carried over from earlier periods and expresses accumulated stock relative to the sales pace. Read them together to distinguish new-listing momentum from the depth of available stock. The demo retains the historical endpoint’s reported SoM values.

Prepare the next vendor conversation

A useful vendor-update screen puts the two four-month series beside a briefing note. The demo below illustrates a screen your CRM or agency workflow could provide. Switch between the two measures, select a month to inspect its reading, then add your own campaign context.

The first draft of the briefing might say:

Richmond’s reported days-on-market measure for houses moved from 41 days at 31 July to 25 days at 31 August, while HtAG’s stock-on-market measure remained at 20. The latest movement is worth discussing, but the four-month history does not yet establish a lasting change.

The agent should then review and add what the area-level data cannot know:

• How does the vendor’s property compare with recent campaigns in presentation, price range and buyer appeal?
• Did open-home attendance, enquiry quality or offer activity change during August?
• Are competing campaigns launching now, and how do they differ from the vendor’s likely campaign?
• Is the vendor’s timing or preparation plan affected, or is the evidence still too early to act on?

This division of labour is deliberate. The data supplies a consistent local baseline. The agent supplies property knowledge, campaign context and judgement. A suburb observation is not a prediction of how long a particular listing will take to sell.

View the demo screenshot

One market snapshot, reused across the vendor book

The cost-conscious design is simple: key each cached snapshot by locality, property type and bedroom selection. When several vendor records map to Richmond houses with the same selection, prepare the market context once and reuse it. Refresh the cache when a new reporting period appears, rather than making the same request for every contact or every screen view.

In this production example, four distinct REST operations were used. The calls returned one market-summary row, four days-on-market rows and four stock-on-market rows, plus three locality lookup matches. That is four requests and nine market rows, with three lookup records. Endpoint count, request count, returned rows and billable units are different concepts; consult current HtAG pricing before estimating production spend.

When the demo is loaded, readers make zero HtAG API calls because it uses a captured example. A live CRM or agency application would need its own authenticated data workflow, cache and refresh rules.

Keep the implementation small and reviewable

The workflow needs only four operations:

The Richmond house-market summary covers the period ending 31 August 2026 and carries HtAG’s High confidence rating.

Product teams should preserve the period end, filters and capture date beside the chart or note. They should also keep the source wording available in an explanation panel. Those small details help an agent distinguish observed area context from a property-specific claim.

A practical place to start

Start with one agency territory and one common property type. Cache a four-period snapshot, draft a two-sentence briefing, and require an agent to review it before it becomes part of a vendor check-in. Measure whether the screen saves preparation time or produces better questions before adding more markets or metrics.

The HtAG API documentation explains the available market data, while the REST reference covers request details. Developers can sign in to the self-service developer portal to test the workflow against their own authorised environment.