The connected plan · capability

One model, forecast to markdown.

Every capability operates on the same numbers. Change one and it reconciles everywhere — no nightly extracts, no version drift.

Planning·Connected plan · SS27Last sync · just now

One model, forecast to in-season

Forecast, MFP, OTB, buy, allocate, replenish and in-season on a single versioned number — reconciled live, not at month-end.

Connected plan · SS27
7/7reconciled live
94%Reconciled
−$1.2MVariance
v6Versions
on 1Roles
One model, forecast to in-season
7
layers on one model
±2%
reconcile tolerance
live
not month-end
v6
versioned + audited
Reconciliation · by category
SS27 · live ›
Knitwear · SS27over +2.8%reconcile
Outerwear · SS27on track+0.9%
The numbers behind it

Why one model changes how the team plans.

14 pts

Full-price sell-through gap between retail leaders and the industry — most of it down to how the plan stays connected.

Source: Incisiv × WRC × Anaplan 2026

~53%

Share of unplanned markdown cost attributed to disconnected planning decisions upstream.

Source: Coresight industry research

+23%

Face the Future's full-price sell-through gain when forecast, plan and OTB worked from one model.

Source: Audited customer outcome

The problem today

What breaks before the connected plan runs to plan.

Planning·Month-end reconciliation · SS27
Systems in the stack
5
meet at month-end
Top-down vs bottom-up drift
$1.9M
widening weekly
Reconciled
Monthly
when the buy is set
Versions of 'the plan'
3
none authoritative
Variance found
month-end
too late to act
Two numbers, drifting apart · SS27
$1.9M drift by wk13
TOP-DOWN MFP vs BOTTOM-UP FORECAST · SS27 · $M$16M$17M$18M$19Mwk1wk4wk7wk10wk13$1.9Mdriftfound here — too latetop-down MFP · stalebottom-up forecast · climbing
Disconnected layers · own systems
Forecast
point tool · 34d old
drifted
MFP
Excel · stale
drifted
OTB
Excel
drifted
Buy
ERP
drifted
Allocation
sheet
drifted
The number nobody trusts
3 versions
reconciled in a meeting, six weeks stale
Diagnosis — five systems only agree at month-end; by then the buy is committed against the wrong numberSource: Incisiv × WRC × Anaplan benchmark 2026
How Tightly does it

Three steps from five systems to one model that reconciles live.

Tightly · Connected plan live· three stages from data to decisionLive
01One model
FIVE SYSTEMS → ONE 7-LAYER SPINE5 filesFcstv6MFPv6OTBv6Buyv6Allocv6Replv6Seasonv6

Five systems collapse into one

Forecast, MFP, OTB, buy, allocate, replenish and in-season stop being five files that meet at month-end. They become seven layers of one versioned model — every layer reads and writes the same number.

7 layers · one model
02Reconcile
RECONCILE · 4-STATE VERDICTTARGET · MFP$18.4MCOMMITTED · BUY$18.9MOVER-COMMITTED · gap +$0.5M (2.8%)On trackCoverage gapOver-committed

Reconcile live, with a verdict

Top-down and bottom-up sit on the same surface. Tightly reconciles the two continuously and returns a verdict — On track, Coverage gap or Over-committed — with the gap it found (committed minus target).

verdict · gap = committed − target
03One number
ONE NUMBER · EVERY ROLE · v6MPWorkingSCSubmittedJPSigned-offFinance & merchandising · one versioned number · $18.4M

Every role off one number

Finance and merchandising work the same versioned plan through Working → Submitted → Signed-off. Change the forecast and the plan moves; commit a buy and OTB draws down — for everyone, at once.

Working · Submitted · Signed-off
See it run

Change one number. The whole plan moves.

Every capability operates on the same numbers. Change one and it reconciles everywhere — no nightly extracts, no version drift.

Planning·Connected plan · SS27 · KnitwearLive · one versioned model
Envelope
$18.4M
SS27 · Knitwear plan
Committed
$17.9M
buy + on-order
Gap
+2.8%
committed − target
Verdict
OVER-COMMITTED
guardrail tripped
Versions
v6
live · signed-off
The chain · one model, forecast to in-season
Reconcile the buy
LayerShare of envelopeNumberReconcile
Forecast
demand · rebuilt live
$18.4Mreconciled
MFP
top-down target
$18.4Mon target
OTB
open-to-buy · drawing down
$18.0Mguardrail
Buy
committed + on-order
$18.9Mover +2.8%
Allocate
by store cluster
$17.2Mon plan
Replenish
cover-based fill
$16.4Mon plan
In-season
actuals → forecast
$16.9Mfeeding back
One number · SS27 envelope
$18.4M
every layer reconciles to this
Committed$17.9M
Buy over-commit+$0.5M
Reconciled6 / 7
Guardrail · OTB

Buy is committing $0.5M above the OTB envelope — pull the last two POs or raise the target.

Change the forecast and the plan moves. Commit a buy and OTB draws down. One model.reconciled live · versioned + audited
Why teams change

What changes once every number reconciles live.

One number, all the way through

Demand forecast through to the markdown plan, on the same data, reconciled live. No second model, no spreadsheet reconciliation, no version drift.

Change one number, the rest reconcile

Lift the Q4 forecast and the OTB, the receipts, the allocation and the markdown plan update — with Tia explaining every move.

No nightly extracts

POS, e-com, ERP, supplier and inventory all stream into one governed model. The plan is never working off yesterday.

The system of record for the season

One place the team commits to the plan, and one place the agents work it. The plan stops being a deck and starts being the truth.

Your agents

Meet the Tightly agents

Specialist agents reconcile every line across your data and the plan — proposing, reconciling and acting under your policies.

Meet the agents
Tightly agent
just now · within your limits
Live

Re-forecast ready — 3 categories have drifted from plan this week. Want me to stage the moves for your review?

Drifted vs plan · this weekΔ wmape
Tailored Trousers+9%8%
Woolly Layers−12%11%
Activewear+5%9%
Rebalance 240u DC → SFRe-baseline OTB Q3Hold buy on OCN-072
Stage movesReview firstLogged · audit ready
Customer outcome
We used to spend Mondays reconciling Anaplan against the ERP. Now the team spends Mondays talking about what to do — because the numbers have already agreed.
Face the Future
Mark Till
MD, Face the Future
+23%

Full-price sell-through (audited)

What this replaces

The stack you run today, and the model Tightly delivers.

5 systems, reconciled monthly
THE PLAN · WHERE IT LIVESreconciled monthly
LayerSystemForecastpoint toolMFPExcelOTBExcelBuyERPAllocationsheet
five files, one planreconciled in a meetingstale by Mondaythree versions, no auditvariance at end-of-season
Forecast, MFP, OTB, buy and allocation each live in their own file, reconciled by hand in a monthly roll-up that’s stale by Monday. Three versions of “the plan,” no audit trail — and the variance only shows up at end-of-season, once the buy is long committed.
Tightly · one connected model · live
ONE MODEL · EVERY LAYER WRITES TO ITverdict live
Forecast → MFP → OTBreconciled
Buy → allocate → replenishreconciled
In-season → forecastfeeding back
Top-down ⇄ bottom-upgap +2.8%
one versioned numberreconciled live, with a verdictforecast rolls up to move the targetWorking → Live · all loggedgap flagged the instant it opens
One connected model the whole stack runs on. Every layer writes to it, top-down and bottom-up reconcile live with a verdict, and change a forecast and the target moves — every version logged and audited, so finance and merchandising work off one number, not five.
FAQ

Questions buyers ask, answered straight.

Something not covered here? Talk to the team.

How does this integrate with Anaplan / SAP / NetSuite / Shopify?

Tightly reads from your SoR and writes the proposed plan back. Most teams keep their existing ERP for record-keeping and move all planning into Tightly. No rip-and-replace.

What happens to our existing DP tool?

Most customers retire their DP tool inside the first cycle — once Tightly's forecast and plan are running live, the DP tool is a duplicate. You can run them in parallel for confidence.

How long does it take to onboard?

First useful forecast and plan in week one. Live reconciliation by week three. Full retirement of legacy DP/MFP tooling by end of first cycle (4-8 weeks).

Can different brands run on different policies?

Yes — each brand has its own model, policies and team. The group rolls up live (see /platform/scale).

One model. Forecast to markdown, reconciled live.

There's nothing to rip out. Tightly runs on your existing ERP, EDI, e-commerce and POS. Give us 30 minutes and we'll show it on your own categories.