Intuit Entreprise Suite
#enterprise #AI-native #ERP
Intuit Enterprise Suite is Intuit's cloud-based financial management and light Enterprise Resource Planning (ERP) platform including multi-entity management.
My role: Multiple team collaboration co-Leading with "Agent Studio (ERP builder), and leading designs with "Project Shield", "Multi-entity Inter-company Elimination", etc.
Agent Studio:
AI-native ERP Builder
Agentic automation for mid-market financial workflows demands a delicate balance of precision and flexibility. While a small business using QuickBooks might only need an agent to categorize simple expenses, an Intuit Enterprise Suite (IES) mid-market customer requires a vastly more complex system. They need an agent capable of managing multi-entity expense allocations across dozens of subsidiaries, routing approvals based on strict departmental budget thresholds, flagging policy exceptions directly for the CFO, and accurately posting to the general ledger—all while maintaining rigid, SOX-compliant audit controls.
Every mid-market company operates on unique business rules, from their specific Chart of Accounts (CoA) structures to localized approval hierarchies and revenue recognition policies. These rules represent critical institutional knowledge. The true value of an AI-native ERP lies in transforming this knowledge into executable logic, empowering customers to build and customize agents that mirror exactly how their business runs.
Shifting the Paradigm
To address this complexity, the IES Agent Studio shifts the focus from rigid, one-size-fits-all software to user-customized AI agents. It offers a robust, no-code environment where financial teams can seamlessly build, test, deploy, and monitor their custom workflows.
The platform streamlines the entire agent lifecycle through five core pillars:
-
Natural Language Processing: Users describe complex workflows using plain, everyday language.
-
Visual Canvas: Teams visually map out and configure intricate financial logic.
-
Sandbox Simulations: Users run safe, isolated tests to validate logic before touching live data.
-
Governed Deployment: One-click deployment pushes agents into a fully auditable, compliant production environment.
-
Performance Tracking: Dashboards monitor execution, track system performance, and measure bottom-line business outcomes.
My Role
As a Product Designer on Agent Studio, I partnered closely with a Principal Designer to shape this native-AI ERP builder experience. While our engineering team focused on data extraction and technical feasibility, the design team focused on safeguarding and optimizing the end-user experience.
My responsibilities centered on bridging the gap between a complex technological vision and immediate, tactical execution:
-
Vision Exploration: I mapped out the long-term user journey for building and managing autonomous financial agents.
-
User Testing & Validation: I conducted iterative user research to ensure complex AI behaviors felt intuitive, transparent, and trustworthy to mid-market financial professionals.
-
Rapid Prototyping: I leveraged our existing design system to quickly build and deliver high-fidelity, shippable components—ensuring we provided immediate value to businesses transitioning from QuickBooks Online Advanced to a heavier, more sophisticated ERP solution.
Multi-entity Inter-company Elimination
Our Intercompany Eliminations initiative directly supports IES’s core mission: leveraging our AI-powered platform to drive customer productivity and profitability. By automating 95% of eliminations—while seamlessly handling unique edge cases—we will deliver a user experience that vastly outperforms legacy competitors like Sage Intacct and NetSuite.
Traditional manual and account-based methods lack the depth needed for accurate multi-entity or dimensional reporting. We solve this by providing CEOs and CFOs with dynamic, consolidated reports that offer granular, customizable insights. This is achieved through automated upstream processes that tie every intercompany transaction directly to its corresponding elimination. Ultimately, this foundational structure creates a closed-loop data set that will power our advanced AI to resolve even the most complex edge cases automatically.
Objective
Our Intercompany Eliminations strategy directly supports IES’s core mission to maximize efficiency and profitability via our AI-powered platform. We aim to automate 95% of intercompany eliminations while seamlessly handling unique edge cases and exceptions. This solution delivers a superior user experience that outpaces legacy competitors like Sage Intacct and NetSuite.
The Problem
Traditional account-based and manual elimination methods lack precision. This deficiency leads to inaccurate or distorted reporting when leadership attempts to filter data by specific entities or dimensions.
The Solution
We are transforming this process by engineering automated, upstream workflows to manage and eliminate transactions with pinpoint accuracy. This framework enables us to provide CEOs and CFOs with intuitive, consolidated dashboards that offer granular, customizable insights by both entity and dimension.
The Approach
We propose 1:1 transaction mapping, which directly links every intercompany transaction to its corresponding automatic or manual elimination entry. Building this rigorous data foundation will streamline current workflows and pave the way for advanced, AI-driven automation capable of resolving highly complex edge cases.
Project Sheild
Construction and Landscape is one of the primary industries supported by IES. As our team develops more robust features, we want to drive awareness and adoption across all project-related areas, including "Change Orders" and "Project Estimates." Below is an overview of the "Project Estimates" feature.
Objective
Currently there are two similar yet different functions called "Estimates" and "Project Estimates" in IES and QuickBooks Advanced. "Estimates" and "Project Estimates" are modeled as 2 separate forms. Project functionalities like Change orders, Budgets, Reports, etc. are built over Project Estimates and do not work with Estimates. The goal of this initiative was to increase the awareness and adoption of Project Estimates for project based business.
• Unlock key project offerings like change orders, budgets, reports and KPIs for the customer
• Drive overall projects adoption on the back of increasing project estimate adoption
• Build an end to end fully functional system to replace non-starters and lower end ISVs
Current Data
There are approximately 119,000 companies that create Estimates with projects (this is different from project estimates).
Only 27,600 users across all SKUs specifically used Project Estimates.
Breakdown of users across different SKUs that use Estimates with projects but not Project Estimates. The first 2 are huge opportunity areas.
○ IES: 257 companies. This is a potential opportunity to increase engagement of Project
Estimates by up to 13 pts (from 15% to 28%).
○ QuickBooks Advanced: 45K companies. This is a potential opportunity to increase engagement of Project Estimates.
○ QuickBooks Plus: 74,000 users (Project Estimates are not available in this SKU). This is a great
potential base to 1) Sell construction packs which will be packaged with all project functionalities and 2)
The Problem
User research revealed that "Estimates" and "Project Estimates" feel virtually identical to our users, causing confusion over why two separate access points exist. Instead, users expect "Project" to simply be a category within "Estimates." Until we can architecturally merge these two systems, we need an interim solution that smoothly supports user workflows without disruption, while still hitting our business goals.
The Solution
We will keep the most commonly used entry which is "Estimates". When users select a "Project type" client estimate, they will automatically land on "Project Estimates". We will highlights the page and its benefits while offering an option to revert to "Estimates". We will measure success by tracking usage and analyzing why users revert to guide future improvements.
UX polish: The zero-state screen under Project currently displays "Estimates". Changing this to 'Project Estimates' will align with user expectations and encourage more engagement.
