Back-office software · Public finance
The back-office software public finance runs on.
Fixed-price engagements under $15,000, delivered by one senior engineer with twenty years in production systems and fourteen in fixed income.
A written scope, a fixed price, and an out-of-scope list — sized so a buyer can approve it alone. The engineer who scopes the work writes it, tests it, and hands it over.
What we build
Four things, scoped to a fixed price.
Each one is a defined piece of work with a written scope, not an open-ended engagement. Most land under the micro-purchase threshold.
Spreadsheet to system
Replace a fragile Excel, Access, or VBA process with a tested .NET or Python tool, delivered with a runbook.
Investment portfolio reporting
Automated cash-flow, maturity-ladder, stress, and investment-policy compliance reports for public treasury, pension, and housing-finance portfolios.
AWS readiness & cost review
A written assessment of a workload or a planned migration: security posture, reliability gaps, prioritized fixes, and a cost model.
Modernization & integration
Fixed-scope sprints: .NET or Java upgrades, CI pipelines, containerization, or integrations with ServiceNow, data lakes, and market-data APIs.
Why Lemma
Depth in the thing you are buying.
Fixed-income depth
Fourteen years of cash-flow and risk analytics for CLO, CMBS, and RMBS portfolios, including scenario analysis across a securitization's full capital structure.
Built for audit
Calculation routines documented in versioned LaTeX. Production interceptors capture every model input and output, so any prior result can be reproduced.
Sized for the purchase card
A fixed price with a written scope and an out-of-scope list, so a buyer can approve it alone. No handoffs: the engineer who scopes it writes, tests, and hands it over.
For contracting officers
Registered, and sized to be easy to buy.
Registration details, NAICS codes, socio-economic status and teaming posture are on one page — with a one-page capability statement you can drop straight into a file.
Have a spreadsheet holding up something important?
Tell us what it does, who depends on it, and what breaks when it is wrong. We will tell you honestly whether it is worth building properly.