π Week-over-Week Calculator
This week vs last week, in percent.
Week-over-week change
Estimates for planning only, not financial advice.
This week $12,000 against last week's $10,000 is +20.0 percent week-over-week, an absolute gain of $2,000. Held for a year, that pace annualizes to about 13,100 percent, which is your reminder that weekly growth rates should never be annualized with a straight face.
How to Use This Calculator
Enter this week's value and last week's value for any metric: revenue, traffic, signups, anything countable. The calculator returns the percentage change, absolute change, and direction.
Enter the two weeks using identical definitions: same attribution, same week boundaries.
Read the percent change for the headline, the absolute change for the business impact.
Check 4-week averages before reacting: single weeks lie.
The Formula
Simple, which is both its virtue and its danger. Percentage change on small bases explodes: going from 2 to 6 signups is +200 percent and means nothing. Always pair the percent with the absolute number, and beware comparing weeks with different day counts (holiday weeks, partial weeks).
Worked Example
This week 12,000, last week 10,000. Change: (12,000 - 10,000) / 10,000 = 0.20 = +20.0 percent. Absolute: +2,000. If the prior four weeks were 9,800 / 10,200 / 10,000 / 12,000, the 4-week average is 10,500 and this week is 14 percent above trend: real momentum, not just a soft comp. If the prior weeks were 14,000 / 13,500 / 13,000 / 12,000, the +20 percent WoW is noise in a downtrend.
WoW vs YoY vs MoM
| Metric | Best for | Watch out |
|---|---|---|
| Week-over-week | Fast feedback, ops | Noisy, seasonal |
| Month-over-month | Growth tracking | Calendar effects |
| Year-over-year | True trend | Slow, lags turns |
Use WoW for operations (did the launch move the needle this week?), MoM for growth scorecards, YoY for the real trend. Year-over-year on weekly data (this week vs the same week last year) is the pro move: it keeps the speed of weekly data while killing seasonality. Our YoY calculator handles that comparison.
Smoothing Without Lying to Yourself
Legitimate smoothing: 4-week moving averages, same-weekday comparisons, excluding known one-offs (outages, viral spikes) with disclosure. Illegitimate: cherry-picking the base week, switching between WoW and YoY whichever looks better, or annualizing weekly rates. Set the rules before you see the numbers, or the numbers will choose the rules.
WoW for Operators and Creators
Week-over-week is the native cadence of operating dashboards: revenue, signups, traffic, and ad spend all get WoW treatment because a week matches how businesses actually run. Set up the dashboard right: compare complete weeks (Monday to Sunday, never partial), annotate known events (holidays, launches, outages), and pair every WoW figure with a 4-week average so one weird week does not drive decisions. Alert thresholds beat eyeballing: flag moves beyond two standard deviations of the last 12 weeks and ignore the rest.
Creators live on WoW too, with extra noise. YouTube views, newsletter subs, and sales all swing 20 to 30 percent week to week on publishing cadence alone; comparing a two-video week to a one-video week measures output, not growth. Normalize first (views per video, revenue per session), then compute WoW on the normalized metric. The creators who grow steadily are not the ones with the best weeks; they are the ones whose bad weeks keep getting less bad, which only shows up in smoothed WoW trends.
Know when WoW lies. Holiday weeks, with different day counts and behavior, make adjacent-week comparisons meaningless: compare to the same week last year instead. Businesses with strong intra-month cycles (payday spikes, month-end B2B closes) should prefer 4-week rolling comparisons. And never chain WoW percentages into a trend ("up 5 percent four weeks running"): compounding percentages without the base is how 2 percent weekly becomes a fictional 10.8 percent monthly. Use WoW for alerts, YoY for verdicts.
Fast Signal, Careful Reading
Week-over-week is your early-warning radar: fast, sensitive, and noisy. Use it on complete weeks with annotated events, smooth it with rolling averages, and switch to year-over-year whenever seasonality or holidays distort the comparison. The operators who master WoW do not react to every blip; they react to the pattern the blips form.
Build the WoW Habit
The teams that run on WoW share a ritual: same dashboard, same weekday, same definitions, every week. They annotate anomalies, track rolling averages alongside raw figures, and escalate only genuine breaks in trend. Adopt that discipline and WoW stops being noise and becomes your fastest feedback loop: what changed, by how much, and what are we doing about it.
Pair the weekly cadence with monthly and yearly reviews so short-term reactions never override long-term strategy. WoW tells you something moved; the slower metrics tell you whether it mattered. Speed of signal is WoW's gift; the discipline not to overreact to it is yours to develop.
One more guardrail: never present WoW without the absolute numbers beside it. "Up 50% WoW" on a base of 4 signups is 6 signups, not a breakout. Percentages persuade; absolutes inform. Show both, and your WoW reporting stays honest.
Estimates for planning only, not financial advice.
Frequently Asked Questions
How do you calculate week-over-week growth?
(This week - last week) / last week x 100. With $12,000 this week and $10,000 last: (12,000-10,000)/10,000 = +20%. Use identical week definitions and metrics for both periods. Monday-to-Sunday versus Sunday-to-Saturday definitions shift results, so lock one definition in your dashboard and never mix them mid-analysis.
What is WoW in business?
Week-over-week: the percentage change in a metric versus the prior week. It is the fastest standard growth cadence, used for operational dashboards, launch tracking, and early trend detection. Product teams watch WoW activation and retention; marketers watch WoW traffic and spend efficiency; founders watch WoW revenue like a pulse.
WoW vs YoY: which should I use?
WoW for speed (operations, experiments), YoY for truth (strategy, seasonality-free trends). Report both: WoW tells you what just happened, YoY tells you whether it matters. Same-week-last-year splits the difference. A launch that spikes WoW but shows flat same-week-last-year growth bought attention, not a trend.
Why is week-over-week so noisy?
Small samples, day-of-week effects, holidays, pay cycles, weather, and one-off events all swing weekly numbers. A single viral post or outage can dominate a week. Smooth with 4-week averages before drawing conclusions. B2B metrics swing hardest: one enterprise deal closing can make a week look heroic and the next look catastrophic, with nothing fundamental changing.
Can you annualize week-over-week growth?
Mathematically yes ((1+g)^52 - 1), practically no: +20% WoW annualizes to ~13,100%, an absurdity. Weekly rates compound too fast for annualization to mean anything. Annualize monthly or quarterly rates instead. The absurdity is instructive: sustained 20% weekly growth would 131x a business in a year, which no business does; weekly rates describe sprints, not years.
How do holidays affect WoW?
Enormously: holiday weeks collapse B2B metrics and spike retail. Compare against the same holiday week last year, or exclude and disclose. Never present a holiday-distorted WoW as a trend. Thanksgiving week can halve B2B signups and triple ecommerce revenue simultaneously; both readings are calendar artifacts, and honest reporting labels them as such.
What is a good WoW growth rate?
For early startups, 5-10% WoW sustained is excellent (it compounds ferociously). For mature businesses, 1-2% is strong. Context is everything: 5% on $1k revenue is $50; on $1M it is $50,000. Paul Graham's famous benchmark was 5-7% weekly for YC startups; even 2-3% sustained separates real traction from noise at the earliest stage.
Should I use revenue or units for WoW?
Both, and watch them diverge: revenue up with units flat means pricing/mix did it; units up with revenue flat means discounting did. The split diagnoses the growth's quality. Revenue growth from price increases is usually higher-margin and more durable; growth from discounting buys volume at the cost of profitability and trains customers to wait for sales.
How do you handle partial weeks?
Pro-rate or exclude: compare full comparable periods only. A week with a Monday holiday has 20% fewer business days; adjust expectations or use per-day averages before computing change. For always-on metrics like web traffic, partial weeks still work if you compare matching day-ranges; for sales-driven metrics with weekday patterns, per-business-day normalization is cleaner.
What tools track WoW automatically?
Any BI dashboard (Metabase, Looker, even spreadsheets) with week-period comparisons. The discipline matters more than the tool: fixed week definitions, disclosed exclusions, and absolute numbers alongside percents. A shared spreadsheet updated every Monday with annotated anomalies beats an expensive dashboard nobody trusts; consistency of method is what makes WoW data actionable.