ContactBook a call

Industries/ Finance and banking

Software your clients can trust, and your auditors can follow

We build client portals, onboarding journeys, reporting and AI tools for advisers, brokers, lenders, fintechs and in-house finance teams. Every build starts from the record it has to leave behind, so a reviewer can see who did what, when and why.

Four colleagues standing beside a large wall screen of colourful charts in a bright office with a city view, pointing at the figures and smiling

Overview

Finance and banking, today

Small and mid-sized financial firms are squeezed from two directions. Clients expect the experience of the big banking apps: open an account from the sofa, see a balance or a valuation whenever they like, get an answer without ringing. Regulators expect more evidence than ever that each customer was treated fairly, understood the product and was told the right things at the right time. Most firms meet both demands with the tools they have had for years: a core system, a CRM, shared drives, email and a great many spreadsheets, held together by careful people.

Software rarely needs to replace the core platform, and it should not try. The ledger, the policy administration system or the banking engine usually works; the trouble lives in the gaps around it. Onboarding forms that get re-keyed, client questions answered from memory, month-end packs rebuilt by hand, evidence for a file review gathered from a handful of inboxes. Those gaps are where a focused piece of software pays its way: a portal, a workflow, a report that builds itself, an assistant that searches the policy library. Each sits beside the systems you have and reads from them, rather than becoming another place for the truth to live.

Good looks quieter than the brochures suggest. A client finishes an application on the first attempt because the form asks one thing at a time and explains why. An adviser opens a file and sees the whole relationship on one screen. The finance director signs off numbers nobody had to assemble by hand. And when a regulator, an auditor or an enterprise client asks how a decision was reached, the answer comes from a log rather than from somebody's recollection. That last point shapes everything we build in this sector: if the software cannot show its working, it is not finished.

The pressures

What you are up against

What owners, operations leads and finance directors tell us when they describe a normal week.

  1. 01

    Applicants give up halfway

    People start the application and never finish it. Our form asks for everything at once, rejects the whole submission over one field, and then someone in operations rings to chase the missing documents. By the time identity and suitability are checked, the customer has often gone to a competitor who simply made it easier.

  2. 02

    Evidence takes days to gather

    When a file review, an audit or a complaint lands, somebody has to reconstruct what happened: which version of the terms applied, what the client was told, who approved the exception. It is all there somewhere, across the CRM, email and shared drives, but piecing it together takes our most experienced people away from clients.

  3. 03

    Month end is manual assembly

    Our qualified accountants spend the start of every month exporting, reconciling and reformatting rather than analysing. The board pack is rebuilt from the same workbook each time, the definitions drift between versions, and the one person who understands the macros is the one person who cannot be away when the deadline falls.

  4. 04

    Clients expect app-like service

    Our clients use banking apps that show everything instantly, then ring us to ask for a valuation, a statement or an update on their application. The team spends hours answering questions a screen could answer, and every call that goes unanswered makes a relationship we worked hard for feel a little more distant.

What we build

Software for finance

Six things we build for financial firms most often, each designed to sit beside your core platform rather than replace it.

Client portals

A secure login where clients see valuations, statements, documents and application status, upload what you have asked for, and sign or approve without a printer. Permissions are checked on the server for every request, and every view is logged.

Read more

Guided onboarding journeys

Application and onboarding flows designed around how customers think: one question at a time, errors explained where they happen, progress saved between visits, and identity and suitability checks handed to your chosen providers at the right step.

Read more

Automated management reporting

Ledger, CRM and operational data joined on agreed definitions, so the board pack and investor updates build themselves from the same numbers every month, with unusual movements flagged for a person to explain before anything is sent.

Read more

Policy and procedure search

An assistant that answers questions from your own policies, procedures, product terms and committee minutes, citing the document and the version it relied on, so staff stop guessing and reviewers can check the source for themselves.

Read more

Document reading and triage

Bank statements, payslips, claim forms, valuations and signed agreements read on arrival, key details extracted and checked against the client record, and anything ambiguous or above a set threshold routed to a person rather than processed automatically.

Read more

Secure cloud foundations

Hosting arranged so customer and account data are separated, encrypted and reachable only by the roles that need them, with access logged to storage nobody can quietly edit, and card details kept out of your own systems wherever possible.

Read more

What changes

From how it runs now to how it could

How familiar pieces of work run in most firms today, and how they run once the software is in place.

TodayWith the right software
Applications arrive as PDFs by email and are re-keyed into the core system by operations.Applicants complete a guided online form that checks each answer and writes straight to your records.
Clients ring for valuations, statements and application updates, then wait for someone to be free.Clients log in to see current valuations, documents and status, with a named person one click away.
Board packs are rebuilt by hand each month from exports, with definitions drifting between versions.The pack generates itself from agreed definitions, and the team spends its time explaining the movements.
Staff answer policy questions from memory, or ask the one colleague who knows where things live.Staff ask in plain English and get the answer with the policy, version and paragraph cited.
Evidence for a review is pieced together from inboxes, shared drives and people's recollections.Every action, approval and client message is logged as it happens, ready to export when asked.

In practice

What it looks like on the ground

Worked examples from our service pages that come up again and again with financial firms: the month-end pack, the application people abandon, and the compliance question that arrives with a deadline attached.

01 · Finance teams & CFO offices

Four days of month end that were never accounting

The problem
Management accounts mean exporting from the accounting package, reconciling against the sales and operations systems, rebuilding the same workbook, and reformatting the board pack: every month, under time pressure, with the qualified accountant doing data entry.
What we build
Ledger, sales and operational data joined automatically, the pack generated from agreed definitions with variance against budget and prior year, and a checking step that flags anything unusual before the file is produced.
What changes
The pack is ready on day two rather than day six, the arithmetic is identical every month, and the finance team spends its time explaining the numbers instead of assembling them.
More on automated reporting
Financial services & fintech

02 · Financial services & fintech

The application people abandon at step four

The problem
An onboarding flow that asks for everything at once, explains none of it, and then rejects the whole submission over one badly formatted field. Drop-off concentrates at precisely the point where the customer had already decided to buy.
What we build
The flow is broken into steps that follow how the customer thinks rather than how the database is arranged, questions are asked only when they become relevant, errors are explained where they happen, and progress is saved so a return visit resumes instead of restarting.
What changes
More applications finished on the first attempt, and fewer abandoned half-records for the operations team to chase by phone.
More on product design
Regulated financial services

03 · Regulated financial services

Which rule applied on the day the decision was made

The problem
Compliance questions arrive with a deadline attached: what did our policy say in March, which version of the procedure was live, where is the evidence we followed it. Reconstructing that from a document library takes days, and the answer has to stand up to somebody else's scrutiny.
What we build
Policies, procedures, regulatory correspondence and committee minutes indexed with effective dates and version history, so questions can be asked about a point in time. Every answer returns the document, the version and the dates it applied between.
What changes
Evidence-gathering that used to take days becomes an afternoon, and answers arrive with citations a reviewer or a regulator can follow without having to take anyone's word for it.
More on knowledge search

Handled with care

The details that matter here

Financial software is judged on the day something is questioned. These are the things we handle with particular care, working alongside your compliance lead and advisers rather than in place of them.

  • Audit trails by default

    Every login, view, change and approval is recorded with who, what and when, in storage that cannot be edited after the fact. We agree with your compliance lead what must be kept and for how long, so the log answers the questions your reviewers and auditors actually ask, not the ones a developer imagined.

  • Card and account data

    Wherever possible, card details travel straight from the customer to your payment provider and never touch your servers, which keeps the PCI DSS scope small. Account numbers and identity documents are encrypted, kept only as long as they are needed, and visible only to the roles whose work requires them.

  • Access that matches the job

    Advisers see their own clients, operations sees the queue, and nobody sees everything by accident. Roles, two-factor sign-in and single sign-on are designed with your team, removing access is part of the leaving process, and regular access reviews are built into the system rather than left to someone's calendar.

  • AI that shows its working

    Where we use AI, it reads, searches and drafts; a person decides. Every answer cites its source, anything touching advice, credit or a customer outcome goes to a human for approval, and we document how each tool behaves so your compliance lead can assess it against the rules you work under.

Good first projects

Where to start

Good first projects: small enough to run alongside the day job, useful on their own, and a fair test of whether we are the right partner for the bigger work.

Guides

Worth reading first

Questions

What finance teams ask us

Can you replace our core banking, lending or policy administration system?

Generally no, and we would be wary of anyone who says yes lightly. Core platforms such as a ledger, a payments engine or a lending decision system carry years of regulatory scrutiny, and their track record matters to your auditors and your regulator. If an established product already fits your process, we will tell you to buy it. Where we are useful is everything around the core: the portal, the onboarding journey, the reporting, the integrations and the internal tools your team uses all day, all reading from the platform you already trust.

Who is responsible for meeting FCA, SEC or PCI DSS requirements?

Your firm is, through its policies, people and suppliers together, so no developer can hand compliance over in a box, and we do not claim to. What we do is build with the relevant requirements in mind from the first conversation: data minimisation under GDPR, keeping card data out of your systems for PCI DSS, access control and logging that support a SOC 2 audit, and the record keeping your compliance lead specifies. We work alongside your compliance lead or external adviser, document our decisions as we go, and give them the evidence they need for their own assessments.

How do you handle our clients' personal and financial data during the project?

With the same care we expect the finished system to show. We work from anonymised or synthetic data wherever we can, and when real records are genuinely needed for testing or migration, access is limited to named people, logged, and removed when the work is done. We are happy to sign your confidentiality terms and data processing agreement, complete your supplier due diligence questionnaire, and agree where data is hosted before anything is built, including keeping it within a particular region if your obligations require that.

Can AI be used safely in a regulated firm?

Yes, for the right jobs and with a person in charge. AI is good at reading documents, finding the relevant paragraph in a policy library and drafting a first version of a letter or a file note. It should not be making credit decisions, giving advice or telling a customer something nobody has checked. We design tools so the AI proposes and a person approves, every answer cites its source, and inputs and outputs are logged. Your compliance lead sees exactly how it works before it goes anywhere near a customer.

Will it work with the systems we already use?

Almost always. Most financial firms run a core platform, a CRM, an accounting package and a document store, and most of those offer some way to read and write data, whether a modern interface or a scheduled export. We map which system owns each piece of information before anything is built, so the new software reads from your records instead of becoming another copy of them. Where a supplier makes integration awkward, we will say so early and suggest a practical way round it.

Show us the spreadsheet that runs the firm

Book a free first call and walk us through the process that costs your team the most time. We reply within 48 hours, and we will tell you honestly whether software is the answer.