WHAT IF Settings — Full System Logic

1. Architectural Role

WHAT IF Settings is the central scenario engine of the system.
It is not just a configuration panel.

It performs six core functions:

• Captures strategic intent
• Converts intent into structured scenario inputs
• Recalculates cross-functional dependencies
• Generates a coherent business forecast
• Creates a strategic execution plan
• Synchronizes all canvas blocks in real time

It connects:

Goal → Marketing → Finance → Sales → Inventory → Operations → Execution

2. GOAL Section — Strategic Intent Layer

What It Represents

The GOAL section displays the active goal for the selected timeframe (day / week / month).

If no scenario is active:

• It reflects actual current performance

If a scenario is active:

• It reflects the projected target created via WHAT IF

Two Ways to Define a Goal

1. Manual Goal Input

The user manually defines a goal value.

This assumes:

• The user is confident in achieving it
• No structural constraints are considered

⚠ This does not automatically validate operational feasibility.
This mode is direct and static.

2. Scenario-Based Goal (Recommended)

When a user moves a slider:

• The system interprets the change as a strategic objective
• A new goal is created automatically
• Dependencies are recalculated
• A realistic scenario is constructed

This ensures:

• Logical consistency
• Operational feasibility
• Financial balance

3. Metric Structure & Hierarchy

Sliders are grouped by organizational logic.

TOTAL Layer (Outcome Layer)

• Total Sales
• Net Profit
• ROI

These are result metrics.

Changing them triggers recalculation across:

• Marketing budgets
• Inventory flow
• Capital allocation
• Operational speed

CMO Layer (Growth Engine)

• Total Marketing Budget
• Amazon Ads Budget
• Amazon Attribution Budget
• Organic
• BSR Rank (target position)

These define demand generation mechanics.

If Sales increases:

• Marketing investment must adjust
• Organic ranking must improve
• Conversion pressure increases

CFO Layer (Capital Constraints)

• Available Capital
• Frozen Capital
• COGS

These define financial feasibility.

If marketing increases:

• Capital requirements increase
• Frozen capital may expand
• COGS scaling impacts margin

The model ensures:

• Profit growth cannot exceed capital capacity
• ROI respects cost structure

COO Layer (Execution Capacity)

• DOI Available
• Lead Time

These define operational constraints.

If sales increase:

• Inventory turnover must increase
• Lead time must support velocity
• DOI must remain stable to avoid stockout

The system prevents artificial profit growth without supply readiness.

4. Interdependency Logic

All sliders are mathematically linked.

Key Rule:
No metric can change in isolation.

Example:

If Net Profit increases:

→ Sales must increase
→ Marketing must increase
→ Inventory must increase
→ Capital must support scaling
→ Operational speed must adjust

The system recalculates:

• Volume requirements
• Margin structure
• Cost ratios
• Inventory flow velocity
• Capital utilization

The scenario remains economically and operationally coherent.

5. Real-Time Recalculation Engine

When any slider changes:

• Current state is captured
• Delta is calculated
• Dependency graph is triggered
• All affected metrics recalculate
• UI sliders reposition automatically
• Forecast timeline updates
• Canvas blocks sync instantly

This prevents unrealistic combinations such as:

• Higher profit with lower sales
• Faster growth with unchanged inventory
• Higher ROI with uncontrolled COGS

6. Forecast Distribution Logic

After recalculation, projections are displayed across:

• Sales Performance Chart
• Executive Summary
• Inventory Performance
• COO Tab
• Advertising / Organic / Attribution
• P&L

The system shows:

Retroactive simulation
(How it would have looked if applied earlier)

Forward projection
(How performance evolves over time)

Both past and future enable strategy validation.

7. Goal Creation & Strategic Plan Generation

When a slider is adjusted:

• A new goal is created (named after the primary metric changed)
• The user selects the timeframe for achieving it
• The system constructs a structured strategic plan

Activate Plan Logic

When the user clicks Activate Plan:

• The scenario becomes active
• The Strategic Plan block restructures
• A phased roadmap is generated

Tasks are distributed:

• By phase
• By day
• By operational priority

Dependencies between tasks are defined.

The forecast becomes execution.

8. Continuous Adaptation Logic

If performance deviates:

• The user adjusts sliders again
• A new goal recalculates
• The plan regenerates
• Tracking updates on the Sales Performance Chart

The system supports iterative strategy refinement.

9. Cross-Block Synchronization

All blocks remain aligned by:

• Timeframe (day / week / month)
• Scenario state
• Metric selection
• View mode

All columns remain structurally consistent across levels.
There is no fragmentation between departments.

10. Strategic Philosophy Behind the System

WHAT IF is built on three principles:

• Realism — no isolated metric manipulation
• Interdependency — finance, marketing, and operations are connected
• Execution-driven forecasting — every scenario can become a plan

It transforms:

Static reporting
→ Predictive modeling
→ Structured execution
→ Measurable progress tracking

Executive Perspective

The Dashboard is not designed for monitoring metrics.

It is designed for managing:

• Capital
• Growth speed
• Risk exposure
• Profit sustainability

It is your operational command center.