--- title: "The Headcount Trap: Scaling Fund Ops Without Payroll | Next Matter" description: "Hiring more analysts used to be how fund administrators scaled. In 2026 it's the slowest, riskiest option on the table. Here's the governed orchestration alternative." lang: en json-ld: | [ { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://nextmatter.com/#organization", "name": "Next Matter", "legalName": "Daizy NM Limited", "url": "https://nextmatter.com", "logo": "https://nextmatter.com/__l5e/assets-v1/aab354c2-e169-46fe-8e9b-0e78438471d3/nextmatter-logo.svg", "description": "Next Matter is the orchestration platform for regulated financial operations - purpose-built for asset managers, fund administrators, and wealth and wealthtech firms, not a generic workflow tool - combining AI agents, your existing systems and human approvals with governance and a complete audit trail.", "sameAs": [ "https://www.linkedin.com/company/nextmatter", "https://www.daizy.com" ] }, { "@type": "WebSite", "@id": "https://nextmatter.com/#website", "url": "https://nextmatter.com", "name": "Next Matter", "publisher": { "@id": "https://nextmatter.com/#organization" }, "inLanguage": "en" } ] }, { "@context": "https://schema.org", "@type": "Article", "headline": "The Headcount Trap: Why Scaling Fund Ops No Longer Means Scaling Payroll", "author": { "@type": "Person", "name": "Jonty Hurwitz", "jobTitle": "Founder" }, "publisher": { "@id": "https://nextmatter.com/#organization" }, "datePublished": "2026-07-30", "mainEntityOfPage": "https://nextmatter.com/opinions/headcount-trap-fund-ops", "inLanguage": "en" }, { "@context": "https://schema.org", "@graph": [ { "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://nextmatter.com" }, { "@type": "ListItem", "position": 2, "name": "Opinions", "item": "https://nextmatter.com/opinions" }, { "@type": "ListItem", "position": 3, "name": "Headcount Trap", "item": "https://nextmatter.com/opinions/headcount-trap-fund-ops" } ] } ] } ] --- [![Next Matter Logo](/__l5e/assets-v1/aab354c2-e169-46fe-8e9b-0e78438471d3/nextmatter-logo.svg)](/) - [Solutions](/solutions) [ grid\_view Solutions Overview Personas, capabilities, and proof ](/solutions)[ smart\_toy AI Orchestration Coordinate agents across your stack ](/solutions/ai-orchestration)[ library\_books Workflow Library Remix production-ready workflows ](/remix) Case Studies [ ![Ocorian](https://cdn.prod.website-files.com/69a7f71677d8045f0f2d982a/69a7f71677d8045f0f2da4e8_Ocorian_trustbar.svg) Ocorian 1,800 Employees • Fund Administrator ](/case-studies/ocorian)[ ![Trade Republic](https://cdn.prod.website-files.com/69a7f71677d8045f0f2d982a/69a7f71677d8045f0f2da4e9_traderpublic_trustbar.svg) Trade Republic 10M Customers • Online Trading Platform ](/case-studies/trade-republic)[ ![b2Venture](/__l5e/assets-v1/40232f5e-b66d-45f6-8d04-8be40304d172/b2venture-logo.png) b2Venture $800mn AUM • Venture Capital Firm ](/case-studies/b2venture)[ ![Swan](/__l5e/assets-v1/ef4919d4-3042-430f-b1a2-10b7da14c889/swan-logo.webp#lh=1500x401) Swan BaaS leader • Embedded Banking Platform ](/case-studies/swan) - [Platform](/platform) [ hub Platform Overview Built for Fund Operations ](/platform)[ build Workflow Builder Build long-running orchestrations ](/workflow-builder)[ smart\_toy AI & Automation Agents, models and guardrails ](/ai-and-automation)[ extension Integrations Core Ledger & Ecosystem Connectivity ](/integrations)[ verified\_user Governance & Audit Approvals and a full audit trail ](/governance-and-audit)[ shield Security SOC 2, data residency ](/security) - Resources [ forum Ask a Technical Question Chat with the docs AI assistant ](https://help.nextmatter.com/docs/integrate-across-tools?assistant)[ campaign Opinions Perspectives from our team ](/opinions) [Sign in](https://app.nextmatter.com/login) [Apply](/book-a-demo) [Home](/) chevron\_right [Opinions](/opinions) chevron\_right Headcount trap Opinion · Fund administration # The Headcount Trap: why scaling fund ops no longer means scaling payroll If you ask ten Heads of Operations at fund administrators how they're planning to handle next year's growth, nine will give you the same three words: hire more people. Here's why that plan is already running out of road. volume\_up Listen to this piece [menu\_book Start reading](#article) ![Jonty Hurwitz](https://cdn.prod.website-files.com/69a7f71677d8045f0f2d982a/69b9321a07c5323a0c817c07_Jonty.png) Written by Jonty Hurwitz Founder Read time 8 min Published Jul 2026 F or decades, fund administration scaled the same way a restaurant scales: more covers, more staff. Win a new mandate, launch a new sub-fund, add three analysts. It worked because volume grew in a straight line and so did the team. That straight line is gone. Transaction volumes, asset classes, and regulatory obligations are compounding, but fees are flat and the market for fund accountants is painfully tight. Firms that keep solving a software problem by hiring people are about to find out how expensive that mistake is. 01 · The trap ## Why more headcount doesn't buy you more capacity Adding people to an operations team doesn't scale capacity in a straight line - it scales coordination overhead. Every new analyst is another person who needs onboarding, another set of handoffs, another inbox to copy on the capital call chase. A bigger team spends more of its week chasing missing documents and reconciling who-did-what, not less. When the logic of how your fund operates lives in two senior specialists' heads instead of a governed system, you're one resignation away from a frozen onboarding pipeline. That's not a staffing problem. That's a single point of failure wearing a headcount costume. ### The ceiling built into legacy workarounds Most fund administrators are still running on the same three coping mechanisms: The inbox as a workflow tool Shared mailboxes become the default place to track, assign, and chase capital call notices, subscription documents, and KYC updates - with no system of record behind any of it. Spreadsheet orchestration Brittle Excel trackers hold together multi-step processes like LP onboarding or the NAV sign-off checklist, one broken formula away from silent failure. Manual re-entry Analysts copy investor data out of a PDF subscription agreement into the CRM, then do it again for the transfer agency platform - twice the effort, twice the chance of a typo that becomes a compliance finding. As fund structures get more complex - hybrid vehicles, co-investments, more jurisdictions - this patchwork doesn't bend. It breaks. Error rates climb, client reporting slips, and the team you just grew starts absorbing the rework instead of the growth it was hired for. 02 · The framework ## What actually deserves automation first Not every process is equally worth fixing. The processes that eat the most hours and carry the most compliance risk should move first - everything else can wait. Automation priority tiers Tier 1 Investor / LP onboarding & KYC/AML Constant back-and-forth, high compliance exposure. Tier 1 Capital calls & distributions Volume-heavy, deadline-driven execution. Tier 2 Reconciliations & data ingestion Repetitive checking with real NAV risk if it slips. Tier 2 NAV calculation & distribution Highly structured, but a valuation error here is critical, not cosmetic. Later Ad-hoc client reporting Variable and custom by nature. Worth automating eventually, not first. Fix Tier 1 and Tier 2 and you've removed the majority of the manual load without touching the processes that are genuinely bespoke. 03 · The fragile fix ## Why RPA scripts and generic workflow tools quietly fail The instinct, once you've picked your priority processes, is to reach for whatever automation tool is already licensed. That instinct is usually wrong. RPA bots are built on the assumption that user interfaces never change. The moment an investor portal tweaks its layout or a tax authority updates an online form, the script snaps - and it usually fails silently. Nobody notices until there's a multi-day backlog sitting behind it. Generic workflow tools and Kanban boards have a different problem: they were never built for regulated finance. They don't enforce maker-checker controls natively, and they can't produce the kind of immutable, timestamped record you'd hand an auditor during an ISAE 3402 review. A generic tool can tell you a task is marked "done." It cannot tell you who verified the underlying data, which systems were touched, or who actually signed off. 04 · The blueprint ## Orchestration, with humans still holding the pen The fix isn't more automation bolted onto the same fragile foundation. It's a different architecture entirely - one operating layer that coordinates your people, your existing systems, and your AI agents, instead of leaving your ops team to play human middleware between them. One operating layer, two sides of the stack Core Ledger Books & records Orchestration Layer State · controls · audit trail CRM & Portals Investor-facing AI Agents Repetitive data ingestion Human Experts Four-eyes review & approval AI agents handle the repetitive work Reading incoming mail, extracting data from PDF subscription documents, drafting the first version of a record. Integration removes double entry Data moves between the ledger, the CRM, and the KYC provider over secure APIs, not copy-paste. Humans stay in the loop At a KYC sign-off or a capital call distribution, the system halts and routes it to the right person as a structured maker-checker task. Automation handles the grunt work. People keep the authority. That trade is the whole point - and it's also what makes the resulting audit trail worth something. Scaling through automation eventually brings a knock on the door from auditors, and proving compliance is nearly impossible when the process history is scattered across scripts, inbox folders, and chat threads. An orchestration layer built for this generates that record by default: exactly when a file arrived, how the AI classified it, which analyst completed the sign-off, and the precise moment the ledger updated. That's the difference between handing a regulator a link and handing them a war room. 05 · The architecture choice ## Where the available tools actually fit Next Matter · regulated ops orchestration Built specifically for financial operations, with native maker-checker controls and immutable audit trails from day one. Lives in days or weeks, not quarters, without heavy IT lift. Doesn't try to be your ledger. Duco · specialised reconciliation Excellent at transaction matching. Doesn't orchestrate the broader human-in-the-loop process around it, like onboarding or capital calls. Appian · enterprise low-code Powerful and endlessly customisable, if you have the developer headcount and the multi-year timeline to match. Built for a different kind of buyer. ServiceNow · enterprise ticketing Strong for IT service management. No native financial governance, no maker-checker model - you're building that yourself, from scratch, in a tool that wasn't designed for it. 06 · Getting there ## How the teams that pull this off actually roll it out 1 Augment the stack, don't replace it Ripping out a core ledger or investor portal is a multi-year risk project nobody wants to own. Put an orchestration layer on top, connect it by API, and the legacy tools underneath become part of one workflow instead of five disconnected ones. 2 Put operations in the driver's seat If every process tweak needs an IT ticket, the whole initiative stalls. The people who understand the workflow should be the ones adjusting it - with governance built into the platform, not bolted on afterward, so speed and control stop being a trade-off. 3 Prove it on one process before you scale it Don't try to automate the whole back office at once. Pick the highest-friction candidate - LP onboarding or capital call tracking are usually it - and build that first. Proof point · Ocorian 300+ fund specialists Rather than a multi-year IT programme, Ocorian's own operations specialists configure and adapt workflows on Next Matter in days. The platform now runs behind more than 300 of Ocorian's fund specialists, managing high-consequence processes at scale without a parallel increase in engineering headcount. [Read the case study](/case-studies/ocorian) The firms that get this right stop treating growth and payroll as the same line on the budget. Assets under administration keep climbing. The team doesn't have to climb with it. On this piece [01   The trap](#s1)[02   The framework](#s2)[03   The fragile fix](#s3)[04   The blueprint](#s4)[05   The architecture choice](#s5)[06   Getting there](#s6) Share [share ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fnextmatter.com%2Fopinions%2Fheadcount-trap-fund-ops) [alternate\_email ](https://twitter.com/intent/tweet?url=https%3A%2F%2Fnextmatter.com%2Fopinions%2Fheadcount-trap-fund-ops&text=The%20Headcount%20Trap%3A%20why%20scaling%20fund%20ops%20no%20longer%20means%20scaling%20payroll) [mail ](mailto:?subject=The%20Headcount%20Trap%3A%20why%20scaling%20fund%20ops%20no%20longer%20means%20scaling%20payroll&body=https%3A%2F%2Fnextmatter.com%2Fopinions%2Fheadcount-trap-fund-ops) Keep reading ## See what orchestration looks like on your stack A working session with our team, on your real processes. [Book a demo](/book-a-demo) [More opinions](/opinions) [ Answer Why fund admins need an orchestration layer Your ledger owns the books. Something else has to own the process, approvals and audit trail. ](/answers/why-fund-admins-need-orchestration-layer)[ Opinion The Automation Trap Why APIs and workflows won't fix fund operations - and what the third option actually is. ](/opinions/automation-trap)[ Opinion Investor onboarding & KYC How to automate LP onboarding end to end without losing the audit trail. ](/opinions/investor-onboarding-kyc-audit-trail)[ Opinion The hidden cost of DIY AI Why wrapping an API around an LLM quietly becomes a million-dollar science experiment. ](/opinions/diy-ai) ![Next Matter](/__l5e/assets-v1/aab354c2-e169-46fe-8e9b-0e78438471d3/nextmatter-logo.svg) [](https://www.linkedin.com/company/nextmatter) Case studies - [Ocorian](/case-studies/ocorian) - [Trade Republic](/case-studies/trade-republic) - [Swan](/case-studies/swan) - [b2Venture](/case-studies/b2venture) - [All case studies](/case-studies) Solutions - [Solutions overview](/solutions) - [AI Orchestration](/solutions/ai-orchestration) - [Workflow library](/remix) Platform - [Platform overview](/platform) - [Workflow Builder](/workflow-builder) - [AI & Automation](/ai-and-automation) - [Integrations](/integrations) - [Governance & Audit](/governance-and-audit) - [Security](/security) - [System status](https://status.nextmatter.com/) Capabilities - [AI Financial Reporting](/ai-financial-reporting) - [Operational Intelligence](/operational-intelligence) - [Exception Handling](/exception-handling) - [Team Interfaces](/team-interfaces) - [Guest Interfaces](/guest-interfaces) - [Manager Dashboard](/manager-dashboard) - [Builder Toolbox](/builder-toolbox) Company - [About](/about) - [Careers](/careers) - [Opinions](/opinions) - [Answers](/answers) - [Documentation](https://help.nextmatter.com/docs/integrate-across-tools) - [Ask a Technical Question](https://help.nextmatter.com/docs/integrate-across-tools?assistant) Certified Secure [![AICPA SOC 2 for Service Organizations](https://cdn.prod.website-files.com/69a7f71677d8045f0f2d982a/69a7f71677d8045f0f2da55f_logo_SOC2.svg)](https://app.drata.com/trust/d62cb1a1-96df-4741-8058-97ecbc4ff345/) [![GDPR compliant](https://cdn.prod.website-files.com/69a7f71677d8045f0f2d982a/69a7f71677d8045f0f2da561_logo_GDPR.svg)](https://app.drata.com/trust/d62cb1a1-96df-4741-8058-97ecbc4ff345/) [![SOC 2 Type 2 compliant 2025](https://cdn.prod.website-files.com/69a7f71677d8045f0f2d982a/69eb389eff4de1586e1d2f14_Daizy%20SOC%202%20Type%202.png)](https://app.drata.com/trust/d62cb1a1-96df-4741-8058-97ecbc4ff345/) © 2026 Daizy NM Ltd. All rights reserved. A Daizy company [Terms of Service](/terms-of-service) [Privacy Policy](/privacy-policy) [Data Processing Agreement](/data-processing-agreement) Solutions - [Solutions Overview](/solutions) - [AI Orchestration](/solutions/ai-orchestration) - [Workflow Library](/remix) Case Studies - [Ocorian](/case-studies/ocorian) - [Trade Republic](/case-studies/trade-republic) - [b2Venture](/case-studies/b2venture) - [Swan](/case-studies/swan) Platform - [Platform Overview](/platform) - [Workflow Builder](/workflow-builder) - [AI & Automation](/ai-and-automation) - [Integrations](/integrations) - [Governance & Audit](/governance-and-audit) - [Security](/security) Resources - [Ask a Technical Question](https://help.nextmatter.com/docs/integrate-across-tools?assistant) - [Opinions](/opinions) [Sign in](https://app.nextmatter.com/login) [Talk to us](/book-a-demo)