From Spreadsheets to Interactive Diagrams Overnight

For a company of this scale — a Fortune 500 technology firm headquartered in the San Francisco Bay Area, with operations spanning forty countries and a market capitalisation in the tens of billions — the legal department was surprisingly lean. Twenty-two lawyers, six paralegals, and a small legal operations team managed everything from patent prosecution to regulatory compliance to the corporate housekeeping of a sprawling global entity structure. It was the entity management function that had become the department's most persistent headache.

The company's corporate structure comprised over 500 entities: operating subsidiaries, holding companies, dormant shells, joint ventures, and special-purpose vehicles accumulated over two decades of acquisitions, market entries, and corporate reorganisations. The entity data — incorporation details, registered agents, board compositions, ownership percentages, filing deadlines, and tax attributes — lived in a single Excel workbook maintained by one paralegal. The workbook had grown to over 150 tabs and regularly exceeded the limits of what Excel could handle. It crashed without warning, took several minutes to open on even the fastest machines, and had become so complex that the paralegal who maintained it was the only person in the organisation who understood its structure.

The risks of this arrangement were obvious to everyone. When the paralegal went on medical leave for three weeks, the department discovered that no one else could navigate the workbook well enough to answer basic questions about subsidiary ownership. When the board requested an updated corporate org chart for the annual report, producing it took a full week of manual work. When auditors from the company's external accounting firm asked questions about the ownership chain of a European subsidiary, the legal team spent two days piecing together answers from different tabs, cross-referencing with old board minutes, and making phone calls to local counsel in three countries.

The general counsel had been advocating for a dedicated entity management platform since her arrival at the company four years earlier. She had evaluated several options, but each had fallen short. Enterprise-grade entity management systems designed for company secretarial functions were expensive — six-figure annual licence fees were common — and required lengthy implementation projects that the lean legal operations team could not absorb. Simpler tools lacked the visual capabilities that the general counsel considered essential: she wanted the legal team and the business to be able to see the corporate structure, not just read about it in tabular form.

Juristic Structure entered the conversation through an unexpected channel. A junior lawyer on the corporate team had seen a demo at a legal innovation event in Austin and mentioned it to the legal operations manager, who in turn raised it with the general counsel. The combination of visual-first design, rapid implementation, and a pricing model that did not require board-level budget approval made it worth evaluating. The general counsel approved a pilot with a clear mandate: migrate the entity data and show me results within thirty days.

Migration was more straightforward than anyone had anticipated. The legal operations manager exported the entity data from the Excel workbook into a structured CSV format and imported it into Structure in a single batch. The process took less than a day. Within hours, the team had a fully interactive diagram of the entire corporate group — colour-coded by jurisdiction, with ownership percentages, director details, registration numbers, and filing deadlines attached to each node. The paralegal who had maintained the spreadsheet for years described the moment she saw the complete structure rendered visually as the first time she could actually see what they manage.

The immediate impact was one of visibility. For the first time, the legal team could see the full architecture of the corporate group in a single view. Patterns that had been hidden in the spreadsheet became immediately apparent: three holding companies in the Netherlands that appeared to serve identical functions, a chain of dormant entities in Singapore that had been maintained at cost for years without any apparent business purpose, and two subsidiaries in Brazil whose ownership percentages did not add up to 100% — a data error that had persisted in the spreadsheet for over a year without detection.

The ripple effects across the organisation were significant and rapid. Business unit leaders, who had previously emailed the legal team every time they needed to know which entity operated in a particular country, could now look up the information themselves through Structure's read-only shared views. The tax team, which had maintained its own separate and often inconsistent set of entity records, adopted the Structure workspace as its single source of truth. The treasury team used the ownership diagrams to trace intercompany funding flows and identify potential simplifications.

Board reporting underwent a transformation. The quarterly corporate structure update, which had previously been a week-long project involving manual diagram creation in PowerPoint, became a same-day task. The general counsel could export a current, accurate structure diagram from Structure at any time, annotated with whatever information the board had requested. When the board asked for a view of the company's APAC entities ahead of a strategic review, the diagram was produced and delivered within two hours — a turnaround that the board chair described as unprecedented.

The real test came six months into the deployment, when the company undertook a significant reorganisation of its EMEA holding structure. The restructuring involved consolidating twelve entities into five, changing the domicile of two intermediate holding companies, and unwinding a legacy joint venture in Germany. Under the old system, modelling the proposed changes would have required weeks of manual work in the spreadsheet, followed by the creation of before-and-after diagrams in PowerPoint for board approval. In Structure, the legal team duplicated the current workspace, modelled the proposed changes in the copy, and presented both versions to the tax team and the board within days.

The modelling exercise surfaced an issue that would almost certainly have been missed in the old workflow. One of the intermediate holding companies proposed for dissolution held a minority stake in a joint venture that had separate governance provisions requiring partner consent before any change in shareholder identity. The visual representation in Structure made the relationship immediately visible; in the spreadsheet, it had been recorded in a footnote on a tab that the restructuring team had not thought to consult. The issue was flagged, partner consent was obtained, and the restructuring proceeded without delay.

Training and adoption followed a pragmatic, role-based approach. The legal operations team received comprehensive training on data management, import and export workflows, and workspace administration. Lawyers received a lighter session focused on navigation, search, and the features most relevant to their day-to-day work: looking up entity details, tracing ownership chains, and exporting diagrams for client or board presentations. Business unit stakeholders were given access to read-only views with a brief orientation session. Adoption was essentially complete within six weeks, with minimal resistance.

A year into the deployment, the general counsel conducted a formal assessment of the impact. The team had reclaimed the equivalent of one full-time headcount's worth of hours previously spent on entity management busywork — data entry, diagram creation, responding to ad hoc queries, and reconciling inconsistent records across departments. The paralegal who had maintained the spreadsheet was reassigned to higher-value corporate governance work, a change she described as the most positive development in her career at the company.

The accuracy of entity data improved measurably. Under the old system, the legal team estimated that roughly five percent of entity records contained errors at any given time — outdated directors, incorrect ownership percentages, missing filing deadlines. Six months after migrating to Structure, a comprehensive audit found the error rate had dropped to less than one percent. The improvement was attributed to the visual nature of the tool: errors that were invisible in tabular data became obvious when rendered as a diagram.

The general counsel, reflecting on the project at an internal town hall, offered an assessment that resonated across the department: the migration to Structure was not merely a technology upgrade. It was a shift in how the legal team understood and communicated the company's corporate architecture. The structure diagram was no longer a deliverable produced on request; it was a living, always-current representation of the organisation that anyone could access at any time. That shift, she noted, had changed the legal department's relationship with the rest of the business — from a team that was asked questions to a team that provided answers before the questions were asked.