> ## Documentation Index > Fetch the complete documentation index at: https://clearskies.cc/docs/llms.txt > Use this file to discover all available pages before exploring further. # Market Trends > A weekly read on what's changing in buyer priorities, drawn from your own conversations. The shift shows up in what buyers say months before it shows up in your win rate. Win rate is a lagging indicator. By the time it moves, the change in the market happened two quarters ago and you are reacting to it. What buyers care about, what they compare you against, what they suddenly need before they can buy, all of it is being said out loud on your calls every week. Market trends reads your own conversations as a signal about the market: what is coming up more than it was, what has fallen away, and what is being said now that nobody was saying a month ago. ## Data Sources | Category | Required | Recommended | | :--------------- | :------- | :---------- | | Calls | ✓ | | | CRM | ✓ | | | Email + Calendar | | ✓ | | Messaging | | ✓ | **Starter** (required only): what buyers are raising across your calls, and how that has shifted against the previous period. **Full** (required + recommended): the same, plus what arrives in writing. Budget language, procurement requirements, and organizational changes tend to show up over email rather than on a call. This report reads your own conversations. It is a read on the market you are actually selling into, not a market research report drawn from outside sources. See the [Context Graph](/docs/unifying-gtm-data/customer-context-graph) for how each source feeds the report. ### Choose your path | Path | Best for | Output is delivered | | :------------------------- | :---------------------------------------------------------------------------- | :------------------------------------ | | Build in Clearskies | Leaders and product marketing who want a standing weekly read | To Slack DMs or channels | | Build in Claude or ChatGPT | Digging into a specific shift, or a longer window than the weekly read covers | In the Claude or ChatGPT conversation | ## Build in Clearskies Weekly is the point. A quarterly read tells you what already happened; a weekly one catches a shift while you can still respond to it. ### The Workflow In the Clearskies app, open the workflow builder and describe what you want in plain language: ```text theme={null} Every Monday at 8am, review the customer calls and emails from the last 7 days. Report what buyers are prioritizing: the problems they lead with, the requirements they name, what they compare us against, and what they say about their own budget and timing. Compare it to the previous four weeks and call out what is rising, what is falling, and what is new. Post the report to the #gtm channel. ``` The app configures the schedule, the conversations in scope, and the destination. Scheduled workflows have no meeting context, so the conversations come from a record lookup over a date range. Record lookups cap at 100 records per step, so scope the window or the segment rather than sweeping everything. Expect the first few runs to be noisy. A weekly read on a small conversation volume will surface things that are variance rather than signal. The value builds once there is enough history to compare against, which is the reason the four-week comparison is in the prompt from the start. ### Deploy to Slack Once published, the channel gets the weekly read: ```text theme={null} Market Trends — week of Aug 10 41 customer conversations · 23 accounts Rising • Consolidation. Buyers leading with "we have too many tools" rather than a capability gap, in 11 conversations this week against 4 a month ago. The pitch they respond to is replacing three things, not adding one. • Internal capacity as the constraint. 9 conversations named their own team's bandwidth as the reason a decision waits, up from 3. This is now the most common stated reason a timeline moves. Falling • Build-versus-buy. 3 conversations, down from 12 four weeks ago. Buyers who were scoping an internal build in July are not raising it now. New this week Two conversations independently asked whether we would be acquired. Both were enterprise, both raised it during security review rather than with the champion. Worth watching rather than acting on. What buyers are comparing us against Incumbent tooling in 14 conversations. A named competitor in 6. Doing nothing in 9, which is the largest single alternative and the one least often treated as one. Budget and timing language "Next fiscal year" appeared in 7 conversations, all in the same segment. Two accounts moved a decision out of the quarter for stated budget reasons rather than product ones. The read Two things moved together: consolidation is up and build-versus-buy is down. The same buyer who was planning to build in July now wants fewer tools. That is a positioning opportunity this quarter, not next. ``` ### Customize the rollout * Set the cadence weekly, and change the comparison window as history accumulates * Scope by segment, region, or product line, since these trends rarely move together across all of them * Ask for the things your market moves on: budget language, org changes, regulatory pressure, competitive alternatives * Route it to a GTM channel, product marketing, or a leadership DM * Chain it with [objection trends](/docs/use-cases/objection-trends) and [competitive intel](/docs/use-cases/competitive-intelligence-from-your-own-data), which read the same conversations for different signals ## Build in Claude or ChatGPT Better for the longer window and the specific question. A weekly report tells you consolidation is rising; a conversation tells you what those eleven buyers actually said. ### The Prompt Open Claude or ChatGPT with the Clearskies MCP connected and paste this (or modify to your needs). ```text theme={null} Using the Clearskies Context Graph, tell me what has changed in buyer priorities over the last 90 days. Cover: - The problems buyers lead with, and how that has shifted across the period - Requirements they name that they were not naming before - What they compare us against, including doing nothing - What they say about their own budget, timing, and internal capacity - Anything being said now that nobody was saying three months ago Compare the most recent 30 days against the 60 before it. Quote buyers directly. Distinguish a real shift from a small-sample fluctuation, and say which one you think each finding is. ``` The last instruction is the one that keeps this honest. On a weekly cadence with modest call volume, most week-to-week movement is noise, and a report that cannot say so will manufacture a trend every week. ### Make it yours * Add `Show me the quotes behind the consolidation finding` to get from the trend to the language. * Add `Only [segment]` when you suspect the shift is not uniform across your market. * Add `Which of these shifts show up in deals we lost` to connect a trend to an outcome. * Add `What should change in how we position against this` when the output is going into messaging work. Want this packaged for your team? [**Reach out**](mailto:support@clearskies.cc) and we'll help you customize this into a skill for your workflow. ## The Plugin **Ready to make this part of your team's workflow?** We'll set up the Clearskies plugin with you. Clearskies workflows, Claude skills, all tailored to how your team works. [**Book 15 minutes →**](https://calendly.com/pouyan/new-meeting) ## Next steps 1. [Sign in to Clearskies](https://app.clearskies.cc/) 2. Connect your data sources 3. Get your [Clearskies MCP server](/docs/building-with-clearskies/mcp-server) and try with [Claude](/docs/building-with-clearskies/mcp-clients/claude) or [ChatGPT](/docs/building-with-clearskies/mcp-clients/chatgpt)