
sidebar.wechat

sidebar.feishu
sidebar.chooseYourWayToJoin

sidebar.scanToAddConsultant
"Every weekend, sales drop."
"Our peak season is always Q3."
"At the beginning of each month, customer traffic has a small surge."
People in business always have a vague sense of these "patterns." But feelings are feelings, data is data.
The question cycle analysis answers is: Are these "patterns" real cyclical modes or coincidental random fluctuations?
AskTable's cycle analysis skill does exactly this: identifies cycles from data, quantifies patterns, restores trends - helping you distinguish "real trends" from "false fluctuations."
Mistake 1: Treating Seasonal Fluctuations as Trends
December sales increased 30% compared to November!
Is it really growing? Not necessarily.
If December is always peak season every year (Double 12, pre-New Year restocking),
then this 30% increase is just seasonal "normal performance."
True trends need to be viewed after excluding seasonality.
Mistake 2: Treating Trend Changes as Fluctuations
"Customer traffic has been declining these past few weeks, must be off-season."
But if deseasonalization shows traffic declining for 12 consecutive weeks,
this isn't "off-season" - it's a trending decline -
possibly competitors took share, or mall foot traffic is decreasing.
Ignoring trend changes has more serious consequences than misjudging seasonality.
AskTable's cycle analysis approaches from three time dimensions:
Short-term cycles (day/week): Weekdays vs weekends, intra-day peaks and troughs
Mid-term cycles (month/quarter): Seasonality, holiday effects, paydays
Long-term cycles (year/multi-year): Economic cycles, product life cycles, industry cycles
Each cycle level has different identification methods and business significance.
AskTable uses statistical methods to automatically identify cycle signals in data:
Analysis method: Aggregate by day of week / hour, calculate average and variance
Example: Weekly cycle for a certain store
┌─────────┬────────────┬──────────────┐
│ Day │ Daily Sales │ Seasonal Index │
├─────────┼────────────┼──────────────┤
│ Monday │ ¥42,000 │ 0.85 │
│ Tuesday │ ¥50,000 │ 1.02 │
│ Wednesday│ ¥52,000 │ 1.06 │
│ Thursday│ ¥53,000 │ 1.08 │
│ Friday │ ¥58,000 │ 1.18 │
│ Saturday│ ¥48,000 │ 0.98 │
│ Sunday │ ¥38,000 │ 0.78 │
└─────────┴────────────┴──────────────┘
Findings:
- Friday is the highest sales day (18% above average)
- Sunday is the lowest (22% below average)
- Cycle intensity: highest/lowest = 1.53x
Analysis method: Aggregate by month/quarter, calculate seasonal index
Example: Annual seasonality for an e-commerce platform
┌─────────┬──────────────┬──────────────┐
│ Month │ Seasonal Index│ Note │
├─────────┼──────────────┼──────────────┤
│ Jan │ 0.75 │ Off-season │
│ Feb │ 0.70 │ CNY off-season│
│ Mar │ 0.85 │ Recovery │
│ Apr │ 0.95 │ Normal │
│ May │ 1.00 │ Normal │
│ Jun │ 1.20 │ 618 peak │
│ Jul │ 1.05 │ Normal-high │
│ Aug │ 1.00 │ Normal │
│ Sep │ 0.95 │ Normal │
│ Oct │ 1.10 │ National Day │
│ Nov │ 1.30 │ Double 11 peak│
│ Dec │ 1.15 │ Double 12/year-end│
└─────────┴──────────────┴──────────────┘
Findings:
- Peak seasons concentrated in June and November (e-commerce promotions)
- Off-season in January-February (around Chinese New Year)
- Peak/off-season ratio: 1.30 / 0.70 = 1.86x
Analysis method: Moving average + trend line fitting
Example: User growth for a SaaS product
- Past 24 months: rapid rise → growth slowdown → plateau
- Trend line fitting: R² = 0.92, fits S-curve growth model
- Current stage: maturity, monthly growth rate dropped from 15% to 3%
The seasonal index is the core tool of cycle analysis. Its meaning is: how much a certain cycle deviates from the average level.
Seasonal Index = Cycle Average / Overall Average
Index > 1: This cycle is above average (peak season)
Index = 1: This cycle equals average
Index < 1: This cycle is below average (off-season)
AskTable automatically calculates and visualizes seasonal indices, letting you see cycle patterns at a glance.
This is the most valuable step in cycle analysis.
Original Data = Trend Component + Seasonal Component + Random Fluctuation
After deseasonalization:
Deseasonalized Data = Original Data / Seasonal Index
Example: A store's November sales ¥1.3 million
Without deseasonalization:
"November ¥1.3M, up 30% from October's ¥1M! Great!"
After deseasonalization:
- November seasonal index: 1.30 (Double 11 peak)
- Deseasonalized: 1.3M / 1.30 = ¥1M
- Actual trend: flat with October, no growth
Conclusion: November's "growth" is entirely a seasonal effect.
The business's actual trend hasn't improved.
The value of deseasonalized analysis: shows you "what the true business trend is after removing cyclical factors like holidays, peak seasons, and promotions."
User Question: "This month's sales grew 25% from last month - is the trend improving?"
📊 Cycle Analysis Report
Raw Data:
- October: ¥1M
- November: ¥1.25M (+25%)
Seasonal Analysis:
- November seasonal index: 1.25 (Double 11 peak)
- October seasonal index: 1.00 (normal month)
Deseasonalized Data:
- October deseasonalized: ¥1M / 1.00 = ¥1M
- November deseasonalized: ¥1.25M / 1.25 = ¥1M
Conclusion:
After deseasonalization, actual trend is flat, no growth.
November's "growth" is entirely a seasonal effect.
User Question: "Does our business have a clear weekly cycle?"
📊 Weekly Cycle Analysis
Significant weekly cycle found (intensity 1.53x):
Recommended Scheduling:
- Friday, Thursday: Full staff (peak days)
- Monday, Sunday: Reduce staff by 30% (trough days)
- Tuesday, Wednesday: Normal scheduling
With this plan, labor costs can be reduced by about 12%,
while maintaining service quality (trough day traffic is already lower).
User Question: "When is the best time for marketing?"
📊 Cycle + Marketing Effectiveness Analysis
Best Marketing Timing:
1. Wednesday-Thursday: User browsing intent rising, but not yet at shopping peak
→ Suitable for seeding, warm-up
2. Friday: Sales peak → Suitable for conversion, promotions
3. Sunday: Sales trough → Suitable for inventory clearance, discounts
Avoid:
- Monday: Users just back to work rhythm, low attention
- Holiday days: Natural traffic already high, marketing incremental limited
"Why do sales drop every weekend?"
"Does our business have clear seasonality?"
"Help me find any patterns in the data"
"What's our true trend after removing seasonal factors?"
"Analyze the weekly cycle"
"Look at the annual seasonality"
"Make a deseasonalized trend chart for me"
Cycle Analysis (identify cycles, deseasonalize to see trends)
↓
Anomaly Detection (after excluding cyclical factors, detect true anomalies)
↓
Prediction Trends (incorporate seasonal patterns, improve prediction accuracy)
Cycle analysis is the "infrastructure" for other skills - understanding cycles, anomaly detection won't misidentify "weekend troughs" as anomalies, and prediction trends can incorporate seasonal factors into models.
Pain Point: Every weekend, customer traffic dropped, making store managers anxious. They increased marketing efforts with poor results. Meanwhile, weekdays were understaffed, degrading service quality.
Solution: Deploy cycle analysis skill, identify weekly and intra-day cycle patterns, optimize scheduling and marketing strategy.
Results:
"We always thought there was a problem with weekends, so we拼命 did promotions. Cycle analysis told us: weekend decline is normal cyclical fluctuation, not a problem. The real problem was weekday understaffing. Once our thinking shifted, the solution was completely different." — Operations Director, A Chain Restaurant
The core value of the cycle analysis skill isn't "finding patterns," but:
The ultimate goal of cycle analysis isn't telling you "there's a pattern," but telling you "which are patterns, which are trends, and which are just noise."
sidebar.noProgrammingNeeded
sidebar.startFreeTrial