LEMMASYSTEMS

Capabilities

Four defined pieces of work.

Each is scoped in writing and priced fixed, with an out-of-scope list so there is no argument later about what was included. Most land under the micro-purchase threshold.

  1. 01

    Spreadsheet to system

    A workbook that started as one analyst's convenience and is now load-bearing: month-end depends on it, one person understands it, and nobody can say what it did last quarter. We replace it with a tested .NET or Python tool that produces the same numbers and can prove it.

    • Parity first — the new tool reproduces the spreadsheet's output before anything changes
    • Tests against known periods, so a wrong number surfaces in development rather than at close
    • A runbook, so running it is not a thing only one person can do
  2. 02

    Investment portfolio reporting

    Automated cash-flow, maturity-ladder, stress, and investment-policy compliance reporting for public treasury, pension, and housing-finance portfolios. The reporting a board or an auditor asks for, produced on a schedule instead of assembled by hand.

    • Cash-flow and maturity-ladder reporting across the portfolio
    • Stress and scenario runs, with the assumptions recorded alongside the results
    • Investment-policy compliance checks that flag a breach when it happens, not at quarter end
  3. 03

    AWS readiness & cost review

    A written assessment of a workload you already run or a migration you are planning: what the security posture actually is, where it will fall over, what to fix first, and what it will cost to run. A document you can hand to a board, not a sales call.

    • Security posture against the boundary you have to defend
    • Reliability gaps, ranked by what fails first and what it takes down
    • A cost model with the assumptions visible, so it can be argued with
  4. 04

    Modernization & integration

    Fixed-scope sprints against a system that works but is holding you back: .NET or Java upgrades, CI pipelines, containerization, or integrations with ServiceNow, data lakes, and market-data APIs. Bounded work with a defined end, not a rewrite.

    • Runtime and framework upgrades done incrementally, with the system staying up
    • Pipelines that build, test and scan rather than just deploy
    • Integrations that leave each system of record authoritative

Technical stack

What we work in.

Deliberately unexotic. These systems outlive the people who build them, so the technology has to be something you can still hire for.

Languages

C#/.NET, C++, TypeScript, Python, Java, R, T-SQL

AWS

Lambda, SQS, API Gateway, ECS, S3, RDS, Athena; Terraform, Docker

Data

SQL Server, MongoDB, ETL; Bloomberg, Intex and CoStar feeds

Practice

TDD, dependency injection, SAST/DAST, CI/CD, SSRS, LaTeX and Doxygen documentation

Next

How an engagement actually runs.

What a fixed price buys, what the out-of-scope list is for, and the work we turn down.

Our approach