How Vertex Capital Cut Quarterly Reporting Hours by 60%

Problem

Every quarter, Vertex Capital's analyst team lost the first two weeks to a single task: manually assembling client reports. That meant pulling data from four internal systems into spreadsheets, then formatting each one by hand across 180+ client accounts — several hundred hours of repetitive, error-prone work squeezed into a hard deadline every single quarter.

The Director of Analytics was clear about the constraint that mattered most: this wasn't a "move fast and accept some errors" project. A wrong number in a client's financial report isn't a minor bug — it's a trust and compliance problem. Whatever we built had to be faster and provably as accurate as the manual process, not one traded off against the other.

Research

We spent the first two weeks mapping every client's report customizations before writing a line of the templating engine — some clients wanted specific benchmarks included, others required additional risk disclosures, a few had formatting requirements tied to their own internal compliance needs. Retrofitting that customization logic after the fact would have meant rebuilding the templating system from scratch, so we treated this mapping phase as non-negotiable groundwork rather than a step to compress.

Strategy

Given what's at stake in financial reporting, we scoped this as a human-in-the-loop system from day one — not an eventual safeguard, but the core design constraint. Full automation of data assembly and formatting, with a mandatory analyst sign-off before any report reaches a client. Speed was the goal, but not at the cost of removing the human check entirely.

Design

Rather than one generic report layout, we built a rules-based template system so each client's specific formatting and disclosure requirements are met automatically, without an analyst manually re-editing anything after generation. The review dashboard was designed around a single question: can an analyst tell, at a glance, whether a report looks different from what they'd expect — not just whether it's technically well-formed.

Implementation

The pipeline is built in Python, pulling from Vertex's four data sources into PostgreSQL, with a templated PDF generation layer and a review queue analysts work through before anything sends. Approved reports go out automatically via Resend, closing the loop from data pull to client delivery without a manual handoff at the end.

Challenges

The hardest problem was proving accuracy before go-live, not building the pipeline itself. Spreadsheet-based manual reporting had its own inconsistencies built up over years, so "match the old process exactly" wasn't actually the right bar — some manual reports had small legacy errors baked in that nobody had caught. We had to work with Vertex's analysts to identify which discrepancies were pipeline bugs versus which were the automated version correctly fixing a long-standing manual mistake.

Solutions

We ran two full quarters in parallel — the existing manual process and the new automated pipeline side by side — comparing every generated report line-by-line against its manually produced counterpart before cutting over. That comparison surfaced the legacy-error question directly: each discrepancy got individually reviewed and signed off by Vertex's team as either a fix or a bug, rather than us making that call unilaterally.

Results

The system went live at the start of a new quarter, with the full analyst team trained on the review dashboard a week ahead of the first automated cycle. Analyst hours spent on report assembly dropped 60% in the first live quarter, and — the number Vertex cared about most — there have been zero calculation errors across three full quarters since launch. After the first live quarter, we also streamlined the review queue to flag only reports with unusual variances for detailed review, rather than requiring line-by-line sign-off on every single report.

Lessons Learned

The two-quarter parallel-testing phase added real time to the timeline, and it was worth every day of it. In a domain where an error has real financial and trust consequences, "we're pretty confident it's accurate" isn't good enough — you need a side-by-side comparison you can point to.

Future Improvements

Vertex and SmartFlow AI are scoping a second phase extending the same pipeline to monthly interim reports, a smaller but higher-frequency version of the same problem that surfaced as a natural next step once the quarterly system proved out.