Custom software · US · Canada · EU · Middle East
Engineering teams for regulated and mid-market companies. Every figure on this site carries the method behind it — what was measured, over what window, and how — so you can test the claim before you trust the company.
A senior engineer replies within one business day.
The standard
No client logo we cannot evidence. No statistic without a named owner and a source. No case study without the measurement method printed beside the number.
Four company figures are defined in our content model and withheld until each is signed off. You are seeing the gap on purpose.
The stack
What we reach for first. The full inventory — including what we maintain rather than choose — is published in one place, grouped by the decision it belongs to.
Where to start
A product that does not exist yet, or a first version that needs to become a platform. The risk is usually in the assumption nobody has tested, so that is what we build first.
Scope a new buildA system that works but is getting more expensive to change, slower than it should be, or running on infrastructure nobody wants to talk about. We start by measuring, not rewriting.
Scope modernisationWhat we do
E-commerce and long-term maintenance sit inside custom software rather than getting their own page. Splitting them out would make the list look longer without telling you anything more.
Capabilities
The four services are how work is bought. These are the disciplines it gets built with — and each one says where it sits, so nothing here is a fifth service quietly added to the menu.
Retrieval over your own documents, classification and extraction on the workflows currently done by hand, and agents that are allowed to act only where a wrong answer is recoverable. Every model ships behind an evaluation set, so a regression is caught by the pipeline rather than by a customer.
Re-platforming and refactoring systems that were built for a rack. We move the parts that get cheaper or safer in the cloud and leave the rest, because a lift-and-shift of an application that was never designed to scale horizontally buys a bigger bill and the same bottleneck.
Pipelines, environments and release governance, described in code. The goal is a deployment that is boring enough to happen on a Friday, and an environment that can be rebuilt from the repository rather than from the memory of whoever set it up.
Automated coverage where the cost of a defect is highest, load testing against a number someone has committed to, and accessibility checked in the pipeline rather than audited at the end. We will tell you which parts of a suite are worth keeping and which are only slowing the build down.
Threat modelling on the design, dependency and secret scanning in the pipeline, and remediation work on the findings a penetration test comes back with. We do not sell the penetration test itself: an independent party should run it, and we will work to their report.
The layer between the systems you keep — public and partner APIs, webhooks, single sign-on, and the middleware that lets a bought product and a built one agree on what a customer is. Versioned, documented, and built to survive the upgrades of everything either side of it.
Ingestion, fleet state and the operator interface for hardware that reports from the field. Most of the difficulty is not the device: it is a network that drops, a clock that drifts, and a payload schema that has to change without bricking what is already deployed.
Discovery, a riskiest-assumption build, and then iterations that each end with something deployed. Where a proof of concept is the right first step we scope it as one, with an explicit decision point at the end rather than a slide deck and an invoice.
Interface and interaction design delivered as components rather than as flat files, with accessibility treated as a requirement at AA. The design system and the code review are the same review, which is what stops a library drifting from the product it describes.
Engineers who join your standups, your repository and your on-call rota, under your technical direction. No subcontracting: everyone on the engagement is ours, and you meet each of them before they start.
Proof
Each of these states what was measured, over what period, and how — so you can judge whether the number means what it appears to mean.
Saltea
Every price change at Saltea needed an engineering release, and mid-cycle plan changes were priced three different ways. We moved pricing out of the application and rebuilt the billing surface on top of it.
Mirolens
Screening sites were typing patient identifiers into camera consoles and sending graded outcomes on as documents. We made capture pull from a worklist and exposed the outcomes over a FHIR API.
Zafarin
Zafarin's daily safeguarding reconciliation produced a queue of breaks that finance operations cleared by hand every evening, and the queue grew with transaction volume. We rebuilt the partner feeds, the ledger and the break workbench underneath it.
Vertigem
Receipts captured outside mobile coverage were dropped without anyone noticing, on shared handsets that killed the app mid-upload. Our engineers worked inside Vertigem's squads on the capture path and the reconciliation queue.
How we work
We read the code and talk to the people operating it before proposing anything. Where nothing exists yet, we build the riskiest assumption first.
Two-week iterations, each ending with something deployed to a real environment. Nothing accumulates in a branch for a quarter.
Instrumentation goes in before optimisation, so improvements can be attributed rather than asserted.
Your engineers run the last deployments while ours watch. If they cannot, the engagement is not finished.
Industries
We publish an industry page only where we can point at delivered work in that vertical. Three, for now.
Payments, banking, and trading systems where correctness and latency are both non-negotiable and the regulator is a stakeholder.
Discuss a FinTech projectClinical and patient-facing systems where availability is a safety property and data residency is usually not negotiable.
Discuss a healthcare projectMulti-tenant products where the engineering problems are activation, tenancy isolation, and the cost of serving a customer.
Discuss a SaaS projectEnquiry
Three fields. A senior engineer replies within one business day, and if we are not the right people for it we will say so in that first reply.
Coming from a specific service or industry page? Open the full enquiry page and the form carries that context with it.
That did not go through. We need a name, a work email we can reply to, and a description of the problem. Nothing else was lost — the fields below are empty because the form posts rather than storing a draft. If it fails again, write to hello@riseforge.io and it reaches the same people.
If a form is the wrong shape for what you are dealing with, write to us directly and a senior engineer will pick it up.
