Lean Business Partner

Intuit is prioritising new customer acquisition alongside scaling its major growth initiatives, Chief Financial Officer Sandeep Singh Aujla said at the Goldman Sachs Technology Conference. The company's strategic bets — including upmarket QuickBooks expansion, fintech services, and assisted tax — have each grown over 30% and now represent nearly 30% of its revenue. Aujla said Intuit expects near-term pressure from investments in lower-priced tax and QuickBooks offerings but believes these will create higher customer lifetime value over time. The company is integrating AI into financial workflows using proprietary customer data, with potential monetisation through pricing, payments, and additional services. Intuit targets durable double-digit revenue growth and high-teens earnings-per-share growth. Aujla noted that assisted tax represents 88% of the market, presenting significant opportunity for expansion.

Intuit CFO targets end-to-end consumer platform. 12/09/2026 by Qodriyah Rosdi Tax Moves Intuit CFO Sandeep Aujla admits the company has lost market share in its consumer tax business in recent years, but he says he has a plan to win customers back. Speaking at the Goldman Sachs Communacopia and Technology Conference in Santa Clara, California, on Thursday, Aujla said Intuit has been building a platform to serve consumers from start to finish. That effort has been under way since Intuit's $8.1 billion acquisition of consumer credit tech firm Credit Karma back in 2020, he said. And it took a notable step forward two years ago, when Intuit put Credit Karma under the same leadership as TurboTax, the company's well-known, do-it-yourself tax software. Rebuilding the DIY funnel. "One of the focus areas is rebuilding that DIY funnel so we can retake share in tax," Aujla told attendees. "We are definitely not the best we could be, having lost share in the last couple of years." Drawing in new customers, and not just retaining existing ones, appears to be one area of focus to remedy that. Aujla noted that Intuit for the last several years had been making investments to "go upmarket" and to capture business in the fintech space. Those investments, he said, "did exceptionally well." But they may have come with an unintended side effect. "When we looked at the last year, we realized we were not the best we could be in growing new-to-the-franchise customers," he said. Scaling the platform. Going forward, Intuit aims to "meaningfully scale the platform, which comes down to scaling new-to-the-franchise customers." Free or lower-cost tax services could be one way to reach "price-sensitive consumers," Aujla said. But the aim is to go beyond that. The company sees revenue potential in checking accounts through Credit Karma, for example. "Tax is a very, very deep engagement, but two days a year," Aujla said. Another avenue for customer growth could come through QuickBooks. Aujla pointed to QuickBooks Free and QuickBooks Lite, a lower-cost version of the company's flagship accounting software. While such moves might not generate a lot of revenue to begin with, Aujla said there's ample opportunity to cross-sell other offerings to customers. Macroeconomic picture. The macroeconomic picture for small and midsize businesses remains stable, Aujla said. "The two metrics that are my favorite to look at are the cash reserves that these customers have, and the hours worked," he said. Both metrics are trending up, especially for medium-sized business customers, Aujla said. In the middle of this stability, Intuit is trying to become the central point for consumers' and businesses' financial needs, which could significantly impact how people manage their finances. Throughout the conversation, Aujla repeatedly referenced the "big bets" that Intuit has been chasing recently. One of those is for Intuit to become "the center of money for consumers and businesses," as laid out by Intuit Chairman and CEO Sasan Goodarzi in May. This goal indicates a significant shift in the company's strategy, focusing on providing a wide range of financial services to its customers. How those bets will play out in the long term isn't yet clear. Intuit did see an uptick in revenue in its 2026 fiscal year, which ended July 31. The company's full-year revenue grew 14% to $21.4 billion, with both its global business solutions unit and consumer units reporting double-digit revenue increases. In that same timeframe, though, Intuit also cut its workforce by 17%, laying off about 3,000 people. While the company has been heavily investing in and exploring artificial intelligence, Goodarzi told investors that the move was "not about AI." The company's efforts to build an end-to-end consumer platform and become the central point for financial needs will likely continue to shape its strategy and decisions in the coming years.

Building an agentic Disaster Recovery assistant with Amazon Bedrock. September 7, 2026 - * - Nino - Senior Tech Editor Disaster recovery (DR) at enterprise scale remains one of the most stressful challenges in software engineering. When an AWS region experiences degradation or a core storage layer suffers corruption, on-call engineers are tasked with executing complex, multi-step runbooks under extreme pressure. A single mistyped command during a live regional failover can turn a minor outage into a catastrophic data corruption incident. To solve this, Intuit developed EWOK Agent (Emergency Workflow Operator Kit), an agentic disaster recovery assistant built on Amazon Bedrock. EWOK allows on-call SREs to initiate, monitor, and validate production failovers using plain-language requests - all while ensuring every operation remains deterministic, fully audited, and strictly policy-compliant. When evaluating high-availability AI infrastructure to back critical SRE automation workflows, enterprise teams often combine Amazon Bedrock with multi-provider aggregators like n1n.ai to ensure cross-model redundancy and low-latency API access. The architecture of EWOK: bridging LLM intelligence with deterministic safety. The fundamental challenge of using Large Language Models (LLMs) in site reliability engineering is non-determinism. Infrastructure failover requires 100% predictable execution. Intuit bridged this gap by decoupling the LLM's role as a high-level orchestrator and intent parser from the underlying execution and policy evaluation engine. +-+ | User Interface | (Slack / CLI / Web Command Interface) | +-+ | v +-+ | Amazon Bedrock Agent Layer | - Intent Extraction (Claude 3.5 Sonnet) | - Context & Parameter Resolution | - Plan Generation | +-+ | v +-+ | Deterministic Guardrail & Policy Engine | - OPA (Open Policy Agent) Rules | - IAM / RBAC Role Verification | - Pre-flight Readiness Checks | +-+ | v +-+ | Execution Layer (Orchestration) | - AWS Step Functions / Lambda / Systems Manager | - Multi-Region Traffic Switching (Route 53 / ALB) | +-+ | v +-+ | Telemetry & Audit Pipeline | - Immutable Audit Logs (DynamoDB / CloudWatch) | - Real-time Slack Status Updates | +-+ Key components breakdown: * Intent Parsing & Reasoning: Powered by Amazon Bedrock (utilizing models such as Anthropic Claude 3.5 Sonnet), the agent parses natural text like "Failover TurboTax tax calculation service from us-east-1 to us-west-2 due to elevated latency." * Tool / Action Groups: The agent calls predefined AWS Lambda tool hooks mapped to specific infrastructure tasks (e.g., draining connection pools, rerouting DNS, promoting read replicas). * Policy Guardrails: Before any AWS API is invoked, the proposed actions pass through an independent Open Policy Agent (OPA) layer and Bedrock Guardrails. If the RTO (Recovery Time Objective) or compliance parameters are violated, execution halts instantly. * Human-in-the-Loop (HITL) Authorization: Destructive operations (e.g., DNS rerouting or active database promotions) require interactive cryptographic authorization from a secondary incident commander. Step-by-Step implementation: building Bedrock Action Groups for DR. To implement an agentic DR assistant, developers configure Amazon Bedrock Agents with explicit JSON schemas for tool calling. Below is an example of an OpenAPI specification for a regional failover tool group, followed by the Python Lambda handler executing the validated action. 1. Defining the OpenAPI schema for Bedrock Agent. { "openapi": "3.0.0", "info": {"title": "Disaster Recovery Failover API", "version": "1.0.0"}, "paths": {"/failover/execute": { "post": { "summary": "Trigger regional service failover", "description": "Executes traffic shift and database promotion for a target microservice.", "operationId": "executeFailover", "requestBody": { "required": true, "content": { "application/json": { "schema": { "type": "object", "properties": { "service_name": { "type": "string", "description": "The identifier of the service, e.g., turbotax-calc"}, "source_region": {"type": "string", "description": "Current primary region, e.g., us-east-1"}, "target_region": {"type": "string", "description": "Destination region for failover, e.g., us-west-2"}, "reason": {"type": "string", "description": "User-provided rationale for initiating failover"}}, "required": ["service_name", "source_region", "target_region", "reason"]}}}}, "responses": {"200": { "description": "Failover workflow successfully initiated"}}}}}} 2. AWS Lambda action group handler with security controls. import json import boto3 import os step_functions = boto3.client('stepfunctions') STATE_MACHINE_ARN = os.environ.get("DR_STATE_MACHINE_ARN") ALLOWED_SERVICES = \{"turbotax-calc