Project №4 · INNOVA · Enterprise Transformation
Business Systems Transformation
A research-led roadmap for moving from a fragmented Zoho environment to Salesforce, NetSuite, and Slack—with CPQ at the center.
Product LeadScope
Strategy · Architecture · CPQ
The decision
Change systems—or change how the company operates?
The business had reached the limits of its existing stack, especially around complex configuration and quoting. A simple tool comparison would not answer the real question: which operating model could support growth without recreating the same fragmentation in more expensive software?
I led the research for ownership, translating platform capabilities, financial implications, data dependencies, and organizational change into a practical decision framework and phased roadmap.
One transformation, four platform decisions
The target stack was evaluated as a connected business system spanning demand, configuration, finance, operations, and collaboration.
Zoho CRM → Salesforce
Customer, sales, service, and product workflows consolidated around a scalable commercial platform.
Zoho Books → NetSuite
Financial and operational processes evaluated against growth, control, reporting, and integration requirements.
Zoho Cliq → Slack
Cross-functional communication redesigned for clearer ownership, faster escalation, and connected workflows.
CPQ as the core
Compatibility, pricing, discounts, quantities, accessories, and commercial rules managed as governed product logic.
The product core
CPQ turns product complexity into sales confidence.
CPQ was the decisive capability. I owned the product logic that connects what can be built, what can be sold, under which conditions, at what quantity, and with which price and discount controls.
Product and accessory compatibility
Quantity and dependency rules
Discount levels and approval paths
Market-specific pricing logic
Generation and configuration constraints
Quote accuracy and sales guidance
My contribution
From research to an executable roadmap.
The work connected executive decision-making with the operational detail required to implement the change responsibly.
- 01
Current-state audit
Mapped systems, workflows, data ownership, limitations, manual work, and operational risk.
- 02
Business case
Prepared decision notes explaining expected value, trade-offs, implementation effort, and organizational impact.
- 03
Scenario budgeting
Compared platform, implementation, integration, migration, training, and ongoing operating-cost scenarios.
- 04
Target architecture
Designed the exchange of commercial, product, manufacturing, vendor, and logistics data across the future stack.
- 05
Transition roadmap
Structured the change into controlled stages with dependencies, validation gates, ownership, and adoption work.
- 06
CPQ ownership
Defined the rules and governance needed to turn complex product knowledge into reliable quoting logic.
Connected operations
The system extends beyond company walls.
The future architecture had to synchronize not only CRM and finance, but also the Italian factory, product development, external vendors, manufacturing, warehousing, and logistics.
That required clear source-of-truth ownership, stable identifiers, controlled product rules, interface boundaries, validation, and an operating cadence for resolving data exceptions.
Transformation principles
A platform strategy grounded in operations.
No isolated migration
Each platform decision was evaluated as part of one operating model, not as a standalone software replacement.
Product truth stays governed
Factory and engineering sources remain authoritative while CRM and CPQ deliver usable commercial logic.
Value before complexity
Capabilities were compared against total cost, implementation risk, adoption effort, and measurable operational value.
Phased change
Data, integrations, rules, and teams move through testable stages to protect business continuity.
Not a software replacement.
A scalable operating system for the business.