From Spreadsheet to High-Complexity System Architecture

How early identification of a scope misalignment turned an unviable spreadsheet request into a robust, high-impact corporate software development project.

01 Overview

The Context: Initial demand requested by the client and passed down by company management to create advanced Excel spreadsheets packed with conditional calculations and variables.

My Role: Designer / Front-end (initial strategic scope work, dissecting the demand, followed by UI Design and Front-end Development during the execution phase).

The Impact: Early identification of a critical scope misalignment, conversion of an unviable spreadsheet request into a large-scale software development project, and successful contract expansion for two additional projects under the same model.

02 The Challenge and Client Pain Point

The client faced a high-complexity business scenario: they needed to consolidate and automate a series of calculations, variables, dynamic conditions, and financial/operational exceptions that directly impacted final values.

The Core Pain: The client needed to generate values and reports based on an infinity of highly specific business rules full of exceptions.

The Invisible Bottleneck: Neither the client nor the company partners could grasp the true scale of the demand. The initial request was merely to "organize this in Excel."

03 Critical Analysis and Strategic Pivot (Discovery)

Initial Investigation: I requested all available raw information. Upon analyzing it, I identified that the scope was undersized: that was not an "Excel case."

Systemic Vision and Collaboration: Even without holding a formal leadership position, I gathered the team I was part of, shared my analysis and doubts, and everyone agreed with my assessment.

Strategic Alignment: We presented our vision to the partner and requested a direct meeting with the client.

The Turning Point: In a meeting with the client, it became clear that the project was immense, much larger than any spreadsheet or initial system imagined. Absolute consensus: it was a case for developing a robust system from scratch.

04 Execution, Complexity, and Overcoming Challenges

The project proved to be of extreme magnitude and confidentiality:

Expanding Scope and Sensitive Data: Since it dealt with highly confidential matters (sensitive data), we could not access real data, which required reverse engineering the logic rules and generating dummy data for testing.

Team Management and Adaptation: The project required assembling and replacing team members throughout the process and went through many natural "refactorings" of a product that grew as the client themselves managed to identify and present their hidden rules.

My Contribution in the Execution Phase: Beyond preventing the project's failure by diagnosing the scope at the outset, I worked directly on Interface Design (UI) and Front-end development for the screens and complex flows generated by the system rules.

05 Results and Value Generated

Despite the extreme degree of complexity, open scope challenges, extended "refactoring" cycles, and confidential data constraints, the delivery was successful.

• Commercial Value: The solidity of the delivery and the trust built throughout the process resulted in expanding the contract for two additional projects under the same models.
• Risk Mitigation: We prevented the company from investing hundreds of hours building an unviable spreadsheet solution that would break after a short period of operation.
• Value Lesson (Soft Skills): The case proves the power of critical thinking in technology. A demand that looked like simple spreadsheet formatting turned into a strategic opportunity that reshaped the client's product and expanded the company's revenue.