Enterprise Software Gap Report 2026: Where Off-the-Shelf Platforms Fall Short Across 6 Verticals

After analyzing G2 and Capterra reviews across 50+ enterprise platforms in six verticals — manufacturing, insurance, legal, commercial real estate, healthcare, and professional services — the same three gaps appear everywhere. Reporting can't cross module boundaries. Integrations sync records but not workflows. Compliance and audit processes require manual workarounds the platform vendor never built.

These aren't obscure edge cases buried in feature request backlogs. They're the specific, named complaints that show up review after review, on platforms with seven-figure enterprise contracts behind them. The pattern holds regardless of vertical, price point, or how long the platform has been on the market.

This report walks through what we found in each vertical, the cross-cutting pattern that repeats across all six, and the financial threshold at which building a custom system stops being a luxury and starts being the cheaper option.

What did this analysis cover?

We pulled one- and two-star reviews from G2 and Capterra for the leading platforms in six verticals: manufacturing ERP, insurance agency management, legal practice management, commercial real estate (CRE) property management, healthcare EHR, and professional services automation. Fifty-plus platforms, several thousand reviews.

We excluded generic complaints about support response time and pricing — those exist for every SaaS product and don't tell you anything about the platform's structural fit. We kept complaints that named a specific feature gap, a specific workaround the user built, or a specific integration failure. Those are the complaints that indicate a hole in the product, not a hole in the support team.

For each vertical, we looked at the two or three platforms with the largest review volume — a proxy for market share — and mapped every recurring, specific gap against how many reviews mentioned it and whether any vendor in that space had actually closed it.

Where do manufacturing ERPs fall short?

Epicor Kinetic reviewers describe custom reporting as a project in itself. Anything beyond the canned reports requires either Crystal Reports or a BAQ (Business Activity Query) built by someone who understands Epicor's internal schema. There's no single view that combines shop floor production data with financial data without that custom work — a plant manager and a controller are, in practice, looking at two different systems.

NetSuite's manufacturing module reads, in reviews, like it was bolted onto a financial system rather than built around a production floor. Multi-level bill of materials changes and routing updates that should take minutes require SuiteScript customization, and every customization is billed separately by an implementation partner.

Fishbowl users in mixed-unit-of-measure environments — a manufacturer that buys in pounds, produces in units, and ships in cases — describe inventory accuracy breaking down at the conversion boundaries. The workaround in most reviews is a parallel spreadsheet that reconciles what the ERP can't.

We've built inside this exact gap. A manufacturing cost estimator we shipped for an enterprise client replaced a costing process that lived across three spreadsheets and one ERP export, and it now runs as the client's system of record for quote-to-cost accuracy — the ERP stayed in place; the gap around it didn't.

Where do insurance platforms fall short?

Applied Epic reviews describe a reporting silo between policy data and commission data. Agencies reconcile carrier commission statements against their book of business by exporting both sides to Excel — the platform holds the data but won't cross-reference it natively.

Vertafore AMS360 reviewers report the same pattern for agencies writing across multiple carriers: commission reconciliation across carrier statements with different formats is a manual monthly task, and it scales linearly with the number of carrier relationships an agency holds.

Guidewire is the strongest core platform in the set — reviewers rarely question its underlying architecture. The complaint is access: building a niche endorsement workflow or a custom rating algorithm for a specialty line requires a certified Guidewire implementation partner and a statement of work sized for a carrier, not a managing general agent (MGA) running a narrower book.

Where do legal practice management tools fall short?

Clio reviewers are largely satisfied with intake, calendaring, and standard hourly billing. The gap shows up at custom fee arrangements: blended rates, capped fees, and alternative fee arrangements require a manual override on every invoice rather than a rule the system applies automatically.

MyCase reviews describe conflict checking as shallow once a firm handles more than one practice area — a check that's reliable for a single-matter-type firm misses cross-practice relationships (the same client on one file, opposing party on another) that multi-practice firms need caught automatically.

PracticePanther reviewers running trust accounting across more than one state bar jurisdiction report that the platform's trust reports don't reconcile automatically against jurisdiction-specific rules — each jurisdiction's three-way reconciliation gets built and checked by hand.

Where do CRE platforms fall short?

Yardi Voyager's reporting engine is powerful and, by reviewer consensus, has a learning curve steep enough that most custom reports get built by a paid Yardi consultant rather than in-house staff. The platform can technically do what's asked; the cost is in who's allowed to ask it.

AppFolio reviewers managing commercial (not residential) portfolios describe lease abstraction and CAM (common area maintenance) reconciliation as manual work the platform was never built around — AppFolio's strength is residential unit management, and commercial lease complexity exposes that boundary quickly.

MRI Software reviewers running both property management and investment or fund accounting describe the two modules as requiring middleware to talk to each other cleanly — data that should flow from a lease event to a fund-level return doesn't, without a connector most teams build themselves.

Where do healthcare EHR systems fall short?

Epic is the deepest platform in the set and the hardest to customize on your own timeline. Specialty clinics building a workflow outside Epic's standard specialty templates report build cycles measured in months, gated by the availability of Epic-certified analysts rather than by the complexity of the actual workflow.

athenahealth reviewers running multi-location practices describe cross-location reporting as not rolling up cleanly — a metric that's accurate per-location doesn't aggregate to a single, trustworthy practice-wide number without an export-and-rebuild step each reporting cycle.

eClinicalWorks reviewers describe interoperability with health information exchanges (HIEs) as surface-level: data comes in, but tracking whether a referral loop actually closed — the patient saw the specialist, the specialist sent notes back — is a manual follow-up task, not something the platform tracks as a workflow.

What patterns repeat across all verticals?

Strip away the vertical-specific language and three gap types repeat in every single category we analyzed. The table below maps each gap type against a named example from each vertical.

Every one of these is a workaround problem, not a feature-request problem. Nobody in these reviews is asking for something new. They're describing the spreadsheet, the consultant, or the manual reconciliation they built to compensate for something the platform should already do.

The second table below scores the platforms we analyzed on how exposed they are to these gaps, based on review frequency and the severity of the workaround users describe.

When does custom development make more financial sense?

Custom development wins the moment the workaround costs more per year, loaded, than the system that would remove it — and in every vertical above, that threshold is lower than most teams assume, because the workaround cost is a recurring headcount cost, not a one-time build cost.

An agency spending one full-time role reconciling carrier commissions is spending $60,000-$90,000 a year, indefinitely, on a problem a custom reconciliation layer solves once. A manufacturer running a parallel costing spreadsheet is exposed to the same error the spreadsheet exists to catch, every time someone forgets to update it. Neither of these costs shows up on a line item labeled "software gap" — they show up as headcount, as errors, and as the person who quietly knows how the workaround works and hasn't documented it.

We built an enterprise workflow platform for Tejas Networks that replaced a paper-based approval process running across procurement, engineering, and finance. Paper approvals dropped 90%. That number came from removing exactly this kind of gap — a process too specific to any single off-the-shelf platform's module boundaries, and too costly to keep running manually at Tejas's transaction volume.

The decision isn't platform versus custom build in the abstract. It's whether the specific gap costs more to keep patching than to close. If the workaround touches one report once a quarter, live with it. If the workaround is a recurring role, a recurring reconciliation cycle, or a recurring compliance risk, the math already favors building the system that removes it — the platform stays in place either way; what changes is whether the gap around it keeps costing money indefinitely.

Our enterprise software team builds the systems that close these specific gaps around the platforms already in place, and our custom ERP team does the same for manufacturing and operations workflows specifically.