Verified against Perplexity Pro · 2026-07-25
Map a trend across time with a dated citation for every data point, not a snapshot
A trend-analysis prompt that requires a chronological, dated citation table and an explicit split between a real structural shift and a one-off headline dressed up as a trend, plus a named reversal condition.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Analyze this as a trend over time, not a single current snapshot. Every data point needs its own date and citation — a trend claim with no dates attached to its evidence is not a trend claim, it's a description of the present moment wearing a trend's clothing. TREND TO ANALYZE Adoption of usage-based pricing among B2B SaaS companies TIME WINDOW 2021 to present MARKET / GEOGRAPHY North American mid-market SaaS METRIC TO TRACK % of new SaaS pricing pages listing usage-based tiers as the default option OUTPUT FORMAT 1. A chronological table: Date | Data point or event | Source. Sorted oldest to newest, so the shape of the change is visible at a glance rather than needing to be reconstructed from a narrative. 2. A short narrative distinguishing a real structural shift — sustained direction backed by multiple dated points across more than one source — from noise: a single headline, a one-off event, or a seasonal blip that superficially looks like a trend but isn't. Name specifically which rows in the table above are load-bearing for calling this a real trend versus which are just recent color. 3. Flag explicitly if the most recent one or two data points might be too new to confirm the trend is continuing, rather than extrapolating confidently off a single recent point that hasn't been corroborated by anything after it yet. 4. What would have to happen for this trend to reverse, based on what the sources say is actually driving it — not a generic "market conditions could change," but the specific mechanism (a regulatory action, a competitor move, a cost shift) that the sources themselves point to as the driver, and therefore also the plausible point of reversal. 5. If the available data has any obvious gap in coverage — a period with no data points, a source type that's missing entirely — name the gap instead of letting the table's smoothness imply more continuous coverage than actually exists.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Asked for a trend without structural constraints, a model tends to answer with the current state framed as if it were the whole trend, because the most recent and most abundant sources are about now, not about the shape of change over time, and retrieval naturally over-represents whatever is most recently published. Forcing every row of the output to carry its own date converts an impressionistic 'this is growing' into a chronological table a reader can actually eyeball for direction, gaps, and inflection points, rather than a narrative that asserts a slope without showing the points it was fit to. The explicit instruction to name which rows are load-bearing for the trend claim directly counters a specific and common error — treating a single recent headline as proof of a trend, when a genuine trend claim requires multiple dated points moving the same direction across more than one source, not one data point plus a confident narrative wrapped around it. Flagging the newest points as potentially unconfirmed also guards against the model's tendency to extrapolate a clean line through the most recent, least-verified data, which is exactly where a trend narrative is most likely to be wrong, since the newest data hasn't yet had time to be corroborated or contradicted by anything that comes after it. Naming a specific reversal mechanism rather than a generic hedge is what makes the analysis useful for planning rather than just descriptive — a reader who knows the trend depends on a specific driver can actually watch for that driver changing, where a vague 'this could change' gives them nothing concrete to monitor.
Verified against
Perplexity Pro Sonar Pro · 2026-07-25
Changelog
- 2026-07-25 — Initial publish, verified against Perplexity Pro Sonar Pro search.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
