Banking & Financial Services

Fourteen years inside the same operational environment, across five employers.

Most of my career has been spent working on systems that support banking and financial-services operations — not as a series of unrelated contracts, but as a continuous thread through workforce planning, document processing and backend integration work, largely within and around Lloyds Banking Group's operational environment. Employers changed around that work more than once; the operational context and the standards I held myself to didn't. Delivery is provided directly by Jamie Page on a 100% remote basis.

Where this experience comes from

I started inside Lloyds Banking Group's operations, not in an IT function looking in. As sole developer, I built a workforce-planning and capacity-management tool from scratch in Excel/VBA, addressing fragmented spreadsheet-led planning and inconsistent forecasting across operational teams. It began as a site-level fix and grew into tooling used across most of UK Group Operations — I gathered requirements directly from planners and managers, ran stakeholder demonstrations, and supported rollout, training and adoption across multiple UK sites.

From there I moved into document processing and ECM at Communisis, supporting and developing capture and inbound-processing systems used in high-volume banking and financial-services production environments across multiple UK operational sites — OpenText Captiva workflows (including a Captiva 7 to 7.5 migration), Microsoft Graph integration, manifest generation, custom import services, SQL-driven routing, and scanner configuration and troubleshooting on ImageTrac and Kodak platforms.

At Tech Mahindra I moved further into backend delivery — C#/.NET, SQL Server, Entity Framework, REST APIs, Microsoft Graph and Microsoft Information Protection — across banking, insurance and operational workflow environments, with production support and root-cause investigation as a constant thread.

What continuity looks like from the inside

Lloyds' inbound-processing services changed supplier more than once during my time on them — Communisis, then Tech Mahindra, then Paragon Customer Communications, then SPS. At one point I worked for three companies in a single year because of transfers I had no control over. Each time, the work that actually mattered was making the transition invisible to the client: correct access and groups in place from day one, documentation that reflected reality rather than tribal knowledge, and enough visibility that nobody's continuity depended on one person remembering the right thing. That's a habit now, not a one-off effort.

Typical challenges

• Workforce planning or capacity-management tooling that has outgrown its original spreadsheet or ad-hoc design
• Document and message ingestion workflows that have become difficult to trace or maintain
• Scanner and capture environments that need investigation, reconfiguration or more resilient handling of modern inputs
• Backend integrations (SQL Server, REST APIs, Microsoft Graph) that need production support or reliability improvements
• Supplier or team transitions where operational continuity and documented handover matter
• Systems where the operational context is at least as important as the code itself

Where I draw the line

This experience is operational and technical, not regulatory. I've supported compliance-related workflows without owning regulatory responsibility for them, and I'd expect any banking or financial-services engagement to work the same way: I fit around your compliance and risk functions rather than replace them. If a piece of work needs regulatory sign-off, that stays with the people whose job it is — my role is making the systems underneath it reliable and understandable.

How PageTech helps

• Workforce planning & capacity-management tooling
• Document processing & ECM support
• Backend integration & production reliability
• Transition and handover continuity
• Documentation and knowledge transfer

The aim isn't to sound bigger than a founder-led practice is. It's to bring the same operational discipline I used inside Lloyds' environment for over a decade to whatever system you need stabilised, improved or maintained.

Explore related areas

Explore Document Processing & ECM · Explore Business Process Outsourcing · Explore Operational Systems · Explore Business Operations · Explore Production Reliability

Discuss a banking or financial-services challenge

If you're dealing with an operational system, document-processing workflow or backend integration in a banking or financial-services environment, a short conversation is usually the best place to begin. Delivery is 100% remote.