A mid-sized financial advisory practice built its business on trust and consistency, but the back office told a different story. Behind every client review sat a tangle of manual tasks: tracking schedules by memory, drafting documents from scratch and chasing down files scattered across folders with no shared system. There was no clear roadmap for how automation could help, and growth meant more admin, not less.

Through Colleague-as-a-Service, Denova embedded an automation specialist into the practice to find out where the friction actually lived, not just where it appeared to live. After consultation with the client, we delivered a structured discovery process that turned a vague wish to “be more efficient” into a working set of automated systems built around how the business actually operated.

The Challenge

With operations running on manual effort, there was less time for the organisation’s relationships with their clients.

• Administrative overload: Review tracking, reminder emails, document preparation and file organisation all relied on individual effort rather than a shared process. 

• Undocumented processes: Knowledge of how reviews were conducted lived with individuals rather than in any documented system, making the business harder to scale or hand off. 

• Time away from clients: Hours spent on repetitive admin work were hours not spent on client-facing advisory activity, the part of the business that actually drove value. 

• Inconsistent documentation: Annual review letters, the core output of the practice, were built manually each time, increasing the risk of inconsistency and error. 

• No clear automation roadmap: Leadership recognised the inefficiency but lacked the internal expertise to identify where automation could realistically help. 

• Scaling constraints: Without standardised workflows, taking on more clients meant taking on proportionally more administrative strain. 

These weren’t dramatic failures. They were the quiet, accumulating costs of a business that had simply outgrown its own processes. 

The Solution

Denova’s consultant started with discovery, treating the engagement as a diagnostic exercise before it transitioned into a build. 

• Discovery-first approach: Multiple sessions were held to map existing workflows, identify pain points and understand the practice’s day-to-day rhythms before any solution was proposed. 

• Translating goals into metrics: An initial ambition to “reduce admin and improve efficiency” was refined into concrete objectives: automate review tracking and communication, improve document management, standardise workflows and reduce manual letter preparation. 

• Designing around the business, not against it: Solutions were built on the practice’s existing Microsoft 365 environment (SharePoint Online, OneDrive, Power Automate and Outlook), minimising disruption while still improving the underlying process. 

• Prototyping to build confidence: Because the client found it difficult to visualise automation in the abstract, working prototypes and demonstrations were used to validate ideas and build buy-in. 

• Managing scope through communication: As new ideas emerged mid-project, the consultant balanced responsiveness with discipline, communicating clearly about what could realistically be delivered within the agreed timeline. 

• Prioritising adoption over complexity: Every solution was designed to be simple enough for a non-technical user to adopt without feeling disruptive to daily operations. 

Weekly catch-ups, usually  fifteen to thirty minutes, kept delivery on track. The team rolled out an annual review reminder automation, automated email workflows for client follow-ups, a document generation tool for the practice’s annual review letters, and a SharePoint-based system to organise and tag client files automatically. User guides and training materials accompanied the build, giving the practice something to rely on long after the project wrapped.

The Results

Beyond the immediate time savings, the engagement gave standardised, automated workflows that could support future growth without a proportional rise in admin. The practice also gained confidence in its own systems, along with the groundwork needed to scale operations as client numbers increase.

What We’ve Learned

Understand before you automate The most valuable phase of the engagement wasn’t the build, it was the discovery. Mapping the actual business problem before proposing solutions ensured the automation that followed addressed real pain points rather than assumed ones. 

Design takes longer than delivery, and that’s fine Planning and design consistently took more time than the technical build itself, and that investment paid off in the relevance and adoption of the final solution. 

Documentation outlives the engagement A clear user guide gives clients something durable to rely on long after a project ends, particularly when the audience isn’t naturally tech-savvy.