Founder & CEO

Three decades inside enterprise planning, and the same four gaps every time.

Ashutosh Bansal spent his career selling, designing and delivering planning systems at PwC, IBM, SAP and GitaCloud. The systems did what they promised. The decisions above them kept losing value in the same four places. He built VYAN to close them.
The quarter that kept repeating

Every function hit its number. The enterprise still lost.

A plant rated at 1,000 units a day was planned at 700, because nobody trusted the number. A key supplier confirmed late, by email, after the plan was locked. Sales hit its bookings target while the business missed its profit. Six months later, nobody could say why the commitment had been made.

I saw versions of that quarter in high-tech, industrial and consumer businesses, on systems I had sold and implemented myself. The planning systems were not failing. Nobody was deciding for the enterprise as a whole, across the range of what could happen.

Illustrative concept: PwC · IBM Led supply chain planning practices SAP High-Tech Industry Leader GitaCloud Led an implementation partner for planning systems VYAN Founder and CEO: the decision layer above the planPwC · IBMLed supply chain planning practicesSAPHigh-Tech Industry LeaderGitaCloudLed an implementation partner forplanning systemsVYANFounder and CEO: the decision layerabove the plan
The four gaps

What I kept seeing, and what VYAN does about each.

01
Gap 1

Functional targets conflict

Sales maximizes volume, operations maximizes utilization, procurement minimizes price and finance protects cash. Each wins its own scorecard while the enterprise gives value away.
One enterprise objective: economic profit (EVA)
02
Gap 2

Uncertainty is squeezed into one number too early

A range of possible demand becomes one forecast, and buffer is added afterward wherever it feels safe. The plan looks precise and breaks at the first surprise.
Ranges kept; plan and protection chosen together
03
Gap 3

Commitments are made outside the plan

A supplier confirms by email, a customer moves an order by phone, and the plan learns about it after the money is committed.
Partners respond inside one governed flow
04
Gap 4

The reasoning disappears

What was known, which alternatives were weighed and who approved what live in inboxes and slides. The next decision starts from scratch.
Every run kept, so the next decision starts from the last
Illustrative concept: DECISION LAYER VYAN Leadership decides together, across the futures it could face, within the limits it sets SYSTEM OF PLANNING Planning systems What the plan says SYSTEM OF RECORD ERP What is trueDECISION LAYERVYANLeadership decides together, across the futures itcould face, within the limits it setsSYSTEM OF PLANNINGPlanning systemsWhat the plan saysSYSTEM OF RECORDERPWhat is true
Why the planning stack stays

I spent years putting planning systems in. VYAN does not ask anyone to take them out.

Planning systems coordinate well, run optimization and scenarios, and remain the system of planning. What was missing sat above them: a place where leadership decides together, across the futures it could face, within the limits it sets.

VYAN connects the functional plans an enterprise already has and adds that executive decision layer. From S&OP to a decision lab for the C-suite.

Background

Where the judgment comes from.

▤

Consulting

Supply chain planning practice leader at PwC and at IBM.
◆

Enterprise software

High-Tech Industry Leader at SAP.
⚙

Implementation

Led GitaCloud, an implementation partner for enterprise planning systems.
◎

Education

Mechanical engineering at IIT Bombay; industrial management at IIT Madras. Based in the San Francisco Bay Area.
Writing

Working notes on deciding before the facts are in.

∑

Every function delivered. Enterprise value didn't.

Why operating decisions destroy economic profit when nobody prices the trade-offs.
Perspective
Read ↗
≈

Planning was never the top of the stack

Everyone is accelerating the plan. The advantage sits in the layer above it.
Perspective
Read ↗
⇢

Speed of response is not the same as quality of response

Faster decisions on the same assumptions are the same blind spots, automated.
Perspective
Read ↗
◷

You're judging decisions by how they turned out. That's backwards.

A good outcome is often luck. Grade the call made before the world showed its hand.
Perspective
Read ↗
Compare notes

Deciding something you cannot easily undo? I would like to hear about it.

Write to ashutosh@vyan.ai or connect on LinkedIn. Every PULSE workshop request comes to me, and I reply after reviewing your request.
Book a PULSE workshop ↗