Market Pulse
This page is shared openly with fellow SF agents. If what you are seeing in the field supports or contradicts the working hypothesis, the Feedback tab is exactly for that. Better shared information makes everyone a better advisor.
Every subdistrict is placed by its own single-family data (price, overbid intensity, and how house-heavy it is), not by its district as a whole. The top of the market splits in two: Luxury areas price to value and barely overbid, while Prestige areas list low and overbid hard.
The sparkline carries the shape of the last ten years in the width of a word; the endpoints carry the numbers. Read the level, not the wiggle; single-year counts are small.
Houses vs condos, ten-year price paths, the cash fingerprint, and the top of the market. Pick a view.
{{ marketTabs }} {{ marketBody }} {{ nextCTA }}Should a seller bring a listing on now, in the summer, or hold for after Labor Day? Ten and a half years of closings, grouped by the month each one hit the market, say the folklore is mostly wrong, and that the launch date matters more than the season.
{{ season }} {{ nextCTA }}POTM stands for Pulse On Today’s Market. POTM Command is the engine behind Paulo’s Pulse: it pulls San Francisco’s MLS closed-sale records into one consistent dataset that runs back a decade, refreshed each cycle so the figures stay current rather than months old. Every number traces to a specific closed sale, by neighborhood and housing type.
Governed means it runs on fixed rules, not one-off spreadsheets: one source of truth, single-family kept separate from condos and TICs, thin samples flagged, and nothing typed in by hand.
Each cycle it does the same four things:
Claudio is Paulo’s agentic assistant, built on Claude AI. Under Paulo’s direction, Claudio does the heavy lifting: cleaning and reconciling the records, building the maps, charts, and tables, and drafting the first read of what the data shows. The AI makes the work faster and more consistent. It does not decide what is true, and it does not speak for Paulo.
What Claudio does to build and run Paulo’s Pulse:
Paulo sets the questions, checks every number against its source, and adds the part no dataset carries: what he is actually seeing in live deals. The line this site keeps between measured (what the sales records prove) and observed (what agents see in the field) is his rule, and observed is never dressed up as measured.
Final judgment, interpretation, and accountability are Paulo’s. The AI is a tool; the standard of honesty and the responsibility for every claim are his. If a number here is wrong, it is Paulo’s to correct, which is what the Feedback tab is for.
The exact rules behind every number here, the data sources, definitions, comparison windows, sample-size discipline, and the limits, live on the Methodology page.
This guide gets better with your eyes on it. Flag anything that looks wrong: a figure that does not match what you see in the field, a subdistrict misclassified, or a metric you wish existed. It routes straight to Paulo so it can be corrected or built.
{{ feedback }}From the POTM Blog