KPMG’s “vibe coding” pilot signals a new operating model for tax technology delivery
KPMG US’s six-week “vibe coding” pilot—pairing roughly 30 tax professionals with software engineers in small, coach-led squads—reads less like an internal experiment and more like a preview of how professional services may build software going forward. The core idea is straightforward: move prototyping closer to the domain, enabling tax practitioners to translate regulatory logic and workflow nuance directly into working tools, even with minimal formal coding background.
What makes the development noteworthy is not simply that prototypes were produced, but the type of work automated: tax and compliance workflows that historically depend on manual compilation, cross-system reconciliation, and spreadsheet-heavy analytics. By building prototypes that aggregate data across systems and generate analytics previously assembled by hand, the pilot demonstrates a practical path to compressing the cycle from “requirement” to “working artifact.”
For clients, the immediate implication is faster time-to-value—tools can be shaped in near-real time by the people who understand the edge cases. For KPMG, the pilot suggests a scalable way to embed technology creation inside service lines, rather than treating engineering as a separate downstream function. The firm’s intent to institutionalize multidisciplinary teams to co-create AI-powered solutions aligns with a broader industry movement: the boundary between practitioner and developer is becoming porous, especially in high-regulation domains like tax.
From low-code to domain-native prototyping: why “vibe coding” changes the build cycle
“Vibe coding” can be understood as a convergence of low-code/no-code platforms, agile teaming, and AI-assisted development—but with a crucial twist: it elevates domain logic (tax rules, compliance thresholds, exception handling) to first-class input in the software lifecycle. Instead of domain experts writing long specifications and waiting for software sprints, they participate directly in shaping functional prototypes.
This approach can materially alter the mechanics of delivery:
- Reduced hand-off latency: fewer translation steps between “what the business needs” and “what engineers implement.”
- Earlier discovery of edge cases: tax and compliance work is defined by exceptions; surfacing them during prototyping reduces downstream rework.
- Democratized algorithmic design: practitioners can encode decision rules and workflow steps without waiting for scarce engineering capacity.
- A layered pipeline emerges: citizen-built prototypes can feed into professional engineering workflows for hardening, security review, performance tuning, and scalability.
The technological trajectory becomes even more consequential when paired with AI. As AI-driven code generation, automated testing, and assisted debugging mature inside low-code environments, prototypes can become more sophisticated faster—compressing what used to be distinct phases (requirements → build → test → iterate) into a tighter loop. The strategic question shifts from “Can non-engineers build?” to “How quickly can the organization convert prototypes into governed, production-grade assets?”
That conversion step is where many initiatives succeed or fail. The pilot’s squad model—tax professionals supported by engineers acting as coaches and integrators—implicitly acknowledges the need for guardrails: architecture standards, secure-by-design patterns, and disciplined data handling. In other words, vibe coding is not a replacement for engineering; it is a reallocation of engineering effort toward enablement and industrialization.
Productivity, margins, and the rise of the “10x consultant” in professional services
The economic logic behind embedding technical capability inside consulting and tax teams is compelling in a labor market where specialized skills are expensive and demand for digital delivery keeps rising. If domain experts can prototype automations that remove manual effort, firms can improve both productivity and the client experience—while also creating new monetizable digital offerings.
Several margin and growth levers stand out:
- Faster time-to-value for clients: on-demand tool creation can shorten implementation timelines and accelerate measurable outcomes.
- Higher-value utilization of domain experts: shifting practitioners from manual compliance assembly to solution design and oversight can raise effective billable impact.
- Lower friction in innovation: ideation and prototyping can be done by the people closest to the work, reducing coordination overhead.
- New revenue streams: bespoke analytics, workflow automations, and compliance tooling can evolve into repeatable offerings.
KPMG’s framing—echoing the “10x engineer” concept—points to an emerging archetype: the “10x consultant” or proto-developer whose leverage comes from combining subject-matter mastery with rapid tool-building capability. This is not merely a talent story; it is an operating architecture story. When practitioners can build, engineers can focus on what only engineers should do: security, scalability, reliability, integration, and platform governance.
In a slower-growth macro environment with intensifying regulatory complexity, the ability to “do more with existing talent” becomes a competitive differentiator. Vibe coding offers a mechanism to unlock latent capacity inside specialist teams—particularly in tax, where rule density and frequent change make traditional software backlogs perpetually vulnerable to reprioritization.
The governance and platform play hiding in plain sight: reuse, controls, and retention
Beyond productivity, the pilot hints at less obvious second-order effects that could shape how large firms build internal platforms and retain talent.
- Internal marketplace dynamics: if citizen-built prototypes are cataloged, templated, and reused, firms can reduce duplicated effort across practice areas and geographies. The prize is not one-off automation; it is compound reuse.
- Data governance at the source: when tax experts pull live data into prototypes, privacy, retention, and compliance controls can be embedded early—reducing costly remediation later.
- Upskilling as a retention anchor: a structured pathway from practitioner to proto-developer can strengthen career narratives in high-demand domains, potentially reducing attrition.
The strategic risk is equally clear: without a disciplined center of excellence—standards, templates, ROI measurement, and a clear prototype-to-product pathway—organizations can accumulate a fragmented landscape of tools that are hard to secure, hard to maintain, and difficult to audit. The firms that win will be those that pair democratized building with enterprise-grade governance, using engineers not as gatekeepers but as force multipliers.
KPMG’s pilot suggests that the next phase of digital transformation in professional services will not be defined by a single platform or model, but by how effectively firms fuse domain expertise with engineered rigor—turning regulatory complexity from a cost center into a software-driven advantage.
By
By
By
