Doc 360
Building an intelligent document hub for Post-Sales and GTM
Problem
Zscaler’s customer lifecycle documents were scattered across a sprawling Google Drive environment with inconsistent permissions, orphaned folders, empty directories, and years of accumulated file-management debt. Planning documents, technical designs, architecture records, presentations, meeting notes, support logs, and contractual deliverables had no account-level home in Salesforce.
Even employees who had access often could not find the right document. Enterprise search helped only when someone already knew what they were looking for, and it could not surface files the user lacked permission to view. Executives faced the same problem when trying to understand their customers.
The sharpest workflow failure involved Matik-generated documents. A deck created for a customer landed in a global folder, forcing Professional Services and Technical Success users to find it in Google Drive, copy its link, return to Salesforce, and manually attach it to the appropriate engagement. Depending on downstream automations, that process could take 5 to 10 minutes for every document.
Context
A new customer lifecycle framework was standardizing how GTM, Professional Services, Technical Success, and Support planned, designed, implemented, operated, and optimized customer engagements. Updating the documents to align with that framework solved the content problem, but not the discoverability, access, workflow, or governance problems surrounding them.
The issue had already surfaced repeatedly through product intake, user research, interviews, and the advisory group when C-suite frustration turned it into an executive mandate.
Rather than treat this as a search feature, I defined Doc360 as shared account-level infrastructure spanning Zscaler’s GTM and Post-Sales Salesforce workspaces. It would provide one contextual interface for customer documents while preserving Google Drive as the authoritative system of record for both files and permissions.
The roadmap began with document access, governance, and workflow automation. It then expanded to AI-generated document summaries and a future phase focused on editing documents directly from Salesforce.
The issue had already surfaced repeatedly through product intake, user research, interviews, and the advisory group when C-suite frustration turned it into an executive mandate.
Rather than treat this as a search feature, I defined Doc360 as shared account-level infrastructure spanning Zscaler’s GTM and Post-Sales Salesforce workspaces. It would provide one contextual interface for customer documents while preserving Google Drive as the authoritative system of record for both files and permissions.
The roadmap began with document access, governance, and workflow automation. It then expanded to AI-generated document summaries and a future phase focused on editing documents directly from Salesforce.
My Role
As Director of Business Systems Product Management, I owned the product vision and end-to-end strategy for Doc360, including discovery, build-versus-buy evaluation, experience design, information architecture, governance, integrations, roadmap, delivery, launch, and measurement. I made the decision to build internally and defined the required Google Drive access outcomes, while IT, Engineering, Salesforce, BI, and business partners owned their respective execution responsibilities.
Strategy & Process
- 1Frame It as InfrastructureDefined Doc360 as shared account-level infrastructure for GTM and Post-Sales, not as an isolated document widget or another search interface.
- 1Evaluate Build Versus BuyAssessed dedicated document-management platforms and Salesforce’s native Files, Content Libraries, and CRM Content capabilities. Third-party platforms were cost-prohibitive at Zscaler’s scale, while Salesforce’s native stack lacked the required workflow automation, advanced search, OCR, and lifecycle-management capabilities while still carrying significant storage costs.
- 2Rebuild the Information ArchitectureDesigned a new account-level folder hierarchy to cut through years of orphaned folders, empty directories, and inconsistent organization in Google Drive.
- 3Preserve the System of RecordBuilt bidirectional synchronization so Salesforce became the destination where users could find and view documents in the context of the customer account, while Google Drive remained the authoritative system of record for files and permissions. This avoided duplicate storage and prevented Doc360 from becoming another disconnected repository.
- 3Fix Permissions at the FoundationDefined the required access outcomes and directed an overhaul of the Google Drive permission model before attempting to solve discoverability through search or AI. Doc360 inherited Google Drive permissions instead of creating a second authorization layer.
- 3Embed Governance in the WorkflowConnected Doc360 to the existing adoption-plan and Professional Services offering logic in Salesforce and Certinia. Required deliverables could be evaluated against the relevant support SKU or services offering, making missing evidence visible where teams already managed customer work.
- 3Eliminate the Matik HandoffRedesigned the Matik workflow so one action generated the customer document, placed it in the correct account folder, and made it immediately available in Doc360.
- 3Add AI UnderstandingDelivered AI-generated document summaries in Phase 2, enabling employees to understand the contents of a customer artifact without first opening and reading the full file.
- 4Create a Connected AI ArchitectureMade Doc360’s customer-document context available to Agent Z, extending the repository’s value beyond document management into Zscaler’s broader multi-product AI ecosystem.
Key Decisions
- 1Build InternallySelected a ground-up internal product after neither dedicated platforms nor Salesforce’s native document stack could meet Zscaler’s requirements at an acceptable cost.
- 1Keep Google Drive AuthoritativePreserved Google Drive as the system of record for documents and permissions, avoiding duplicate storage costs and preventing Doc360 from becoming another disconnected repository.
- 1Solve Structure Before SearchPrioritized folder architecture, permissions, and governance before adding advanced search or AI. Better retrieval would not have fixed inaccessible, duplicated, or poorly organized source material.
- 1Operate at the Account LevelDesigned the experience around the customer account rather than around a global document library, ensuring users saw the right artifacts in the context of the work they were performing.
- 2Prioritize the Daily Pain PointPulled the Matik integration into Phase 1 because it was the most visible and frequently reported workflow failure for Professional Services and Technical Success users.
- 3Replace Checklists With EvidenceShifted governance from manually completed closure checklists toward verification that required documents actually existed and remained findable.
Impact
- 1Document Creation Became One ClickReduced the Matik workflow from 5 to 10 minutes of manual handling to a single action that generated the document, filed it correctly, and made it immediately available in Salesforce.
- 2Capacity Returned at ScaleContextual inquiry indicated approximately five minutes saved per Matik document, while product telemetry showed an average of five documents generated per enabled TSM each week. Across 565 Matik-enabled TSMs, that equated to an estimated 11,771 hours of annual capacity returned, or approximately 294 forty-hour workweeks.
- 2Adoption Reached Across Post-SalesAchieved approximately 85% measured adoption across Zscaler’s 1,500-person Post-Sales organization, representing roughly 1,275 users across Support, Technical Success, Professional Services, and Customer Success Engineering.
- 2Customer Documents Became GovernableReplaced inconsistent manual checklist completion with evidence-based visibility into whether required customer deliverables existed and remained findable.
- 2Duplicate Storage Costs Were AvoidedDelivered an account-level Salesforce experience without storing the same documents in two platforms or establishing a second permission system.
- 2GTM and Post-Sales Gained Shared InfrastructureCreated a single account-level document experience spanning multiple Salesforce workspaces and integrating outputs from Matik, Momentum, support logs, customer logs, and other automation products.
- 2AI Summaries ShippedExpanded Doc360 from document retrieval into AI-assisted understanding, allowing employees to quickly interpret customer artifacts without opening and reading every document.
- 3The Enterprise AI Stack Gained ContextSupplied account-level document context to Agent Z and established foundational capabilities aligned with Zscaler’s broader Enterprise Knowledge Management strategy.
Lessons Learned
Run-the-business products do not always produce one clean financial ROI figure. The broad value of making customer documents accessible across GTM and Post-Sales was clear, but measuring every minute previously lost to document search would have required an expensive study with limited additional decision value.
The better approach was to use the strongest evidence available for each part of the story: instrumented Matik usage and observed handling time for workflow capacity, BI measurement for adoption, and qualitative evidence for the broader strategic and employee-experience value.
Doc360 also reinforced that enterprise AI products are only as useful as the information architecture beneath them. AI summaries and agent access became valuable because the team first solved the less glamorous foundational problems: folder structure, permissions, account context, governance, integration, and system-of-record ownership.
That sequencing was the product strategy. Search and AI were not the foundation. They were capabilities made possible by fixing the foundation first.
The better approach was to use the strongest evidence available for each part of the story: instrumented Matik usage and observed handling time for workflow capacity, BI measurement for adoption, and qualitative evidence for the broader strategic and employee-experience value.
Doc360 also reinforced that enterprise AI products are only as useful as the information architecture beneath them. AI summaries and agent access became valuable because the team first solved the less glamorous foundational problems: folder structure, permissions, account context, governance, integration, and system-of-record ownership.
That sequencing was the product strategy. Search and AI were not the foundation. They were capabilities made possible by fixing the foundation first.
