LiverpoolSoftware · Mobile · Web · DesignMon–Fri 09:00–18:00

Financial software people can actually read.

Mitchell Finance & Technology Ltd designs, builds and supports web applications, mobile apps, client portals and reporting dashboards for finance teams and financial products. We make numbers legible and processes traceable. The regulated decisions stay with your qualified professionals.

Line 01 · Summary

The short version

We are an IT company. Our services are the familiar ones: software development, mobile and web applications, interface and experience design, publishing to app stores and the web, and ongoing support. What sets the work apart is the domain. Our attention goes to software that handles money, records and reports: reconciliation tools, client portals, approval workflows, statements and dashboards.

Financial software has a peculiar burden. It must be correct, explainable and auditable, and it must still be pleasant to use. We spend much of our effort on that second half, because unclear financial software is where costly mistakes begin.

Scope statement. We do not provide financial, investment, tax or credit advice, and we are not your compliance function. Where regulation applies, we build to the requirements your qualified advisers set.

Line 02 · Services

Itemised services

  • 02.1

    Web applications and portals

    Client portals for documents and messages, internal tools for operations, back-office systems with clear audit trails and role-based access.

    Detail
  • 02.2

    Mobile apps

    iOS and Android apps for budgeting, expenses, approvals and account information, integrated with authorised providers where money moves.

    Detail
  • 02.3

    Dashboards and reporting

    Reporting that reconciles to source, labels its assumptions and lets a reader trace a total back to its transactions.

    Detail
  • 02.4

    Interface and content design

    Research, prototypes and plain-English microcopy for screens where misunderstanding costs money.

    Detail
  • 02.5

    Publishing and releases

    App store submissions, accurate privacy declarations, hosting, change control and release notes.

    Detail
  • 02.6

    Support and maintenance

    Updates, fixes, dependency and security patching, with a referenced request for every issue.

    Detail
Line 03 · Demonstration

See a matching rule think

Reconciliation is where financial software earns or loses trust. Move the tolerances and watch which fictional lines match. The point is visible: a rule that is too generous quietly hides a 63p discrepancy.

We design matching so exceptions are surfaced to a person with the evidence beside them, never smoothed away.

Illustrative, fictional data

Reconciliation matcher

Adjust the tolerances to see how a matching rule treats a small set of fictional bank and ledger lines. Green rows match; coral rows go to review.

Bank feed
Ledger
-

Line 04 · Who it serves

Teams we build for

A

Finance and operations teams

Internal tools that replace fragile spreadsheets for approvals, reconciliations and month-end checklists.

B

Advisory and accountancy practices

Client portals for secure document exchange, task lists and status updates. The advice remains yours; the portal carries it.

C

Early fintech products

Prototypes and first releases built around authorised providers, ready for your compliance review.

D

Charities and membership bodies

Grant tracking, subscription records and reporting dashboards that trustees can read.

Line 05 · Interface design

Clarity is a numerical property

Good financial interfaces share habits. Figures align on the decimal point with tabular digits. Negative amounts are shown with a sign and a word, not colour alone. Every total has a route back to its parts. Dates state whether they are transaction or posting dates. Fees and charges are shown before a customer commits, not after.

We prototype these screens early and test them with real users, including people who are not confident with numbers. A screen that only works for the finance director does not work.

Our interface design approach

Abstract line illustration of translucent data layers above a geometric riverside skyline
Generated illustration. Data layers, not a real product.
Line 06 · Mobile and web

Layered so each reader sees the right depth

Most financial products have readers at different depths: a customer wants the balance and next payment; an operations user wants the transactions; an auditor wants the change history. We design products in layers, so every reader gets a complete answer at their own depth without wading through the others.

Web applications carry the heavy lifting. Mobile apps carry the moments: an approval on the train, a receipt captured at the till, a notification that something needs attention.

Line 07 · Delivery controls

Controls we apply to our own work

  • C1

    Written scope and acceptance criteria

    Agreed before each phase, including what is excluded.

    Each phase
  • C2

    Calculation tests

    Automated tests for every sum, rounding rule and currency conversion, with worked examples you supply.

    Every change
  • C3

    Audit trail by design

    Who changed what, when and why, stored in a form your auditors can read.

    From day one
  • C4

    Least-privilege access

    Roles, two-factor sign-in and separate environments for testing and live data.

    Always
  • C5

    Fortnightly demonstrations

    Working software, not slides, every two weeks.

    Fortnightly

Full delivery controls

Line 08 · Words

Check your own copy

Financial products often lose customers at the words. Paste a sentence from your product and see which terms most readers would need explained. It is a rough check, written for writers; it is not a regulatory review.

Runs in your browser

Plain-English checker

Paste help text, a product description or an onboarding screen. The checker flags long sentences and finance jargon that most customers will need explained.

-
    Line 09 · Publishing

    Released carefully, declared accurately

    Finance apps attract closer review from app stores. We prepare listings that describe exactly what the app does, privacy declarations that match the data actually collected, and the documentation reviewers ask for. Accounts are held by your organisation.

    For web releases, we use change control: a written change list, a staging test, a backup, a release, and a recorded check afterwards. Every release can be traced and, if needed, rolled back.

    Publishing and release process

    Line 10 · Questions

    Asked before engagement

    • Q1

      Can you tell us whether our product needs authorisation?

      No. That is a question for a qualified compliance professional or the regulator. We can build to whatever requirements they set.

      Advisers
    • Q2

      Do you hold or move client money?

      Never. Where money moves, we integrate an authorised provider of your choosing.

      Providers
    • Q3

      Can we start with a prototype?

      Yes. A clickable prototype is often the best way to brief your advisers and investors before building.

      Prototype
    • Q4

      Do you work outside Liverpool?

      Yes, remotely across the UK, with meetings arranged where useful.

      UK-wide
    Closing balance

    Send us one awkward process

    Describe one process that is slow, error-prone or hard to explain today. We will reply from fintech@mitchellfinancetechnology.trade during working hours with questions and, where it makes sense, a suggested first step.