Services
.NET development
Web applications in C# that are still maintainable in five years.
Most business applications do not break on the day they are delivered, but three years later — once whoever built it has moved on and nobody dares touch what is there. We build on .NET because the platform lasts and enough people know it. That is not a technical preference but a choice about risk.
What you get
- Blazor, MVC and APIs on C# and .NET 10
- Multi-tenant setup and integration with Identity or your own sign-in
- Background processing and event-driven integrations with other systems
- Migration of existing applications, in stages rather than in one go
- Source code, documentation and the pipeline that puts it live
When this fits
- Something runs on an old .NET version and nobody dares to update it.
- The work lives in spreadsheets that now matter more than the system does.
- You have a supplier who no longer responds, or no longer exists.
Taking over an existing codebase
We start with a week-long audit: what runs, where the risk sits, what is overdue and what is unsafe. That produces a plan with an order of work. Not a rebuild in one go — that is exactly the project that stalls halfway.
What you get when it is done
The source code is yours, sits in your repository and builds without us. That sounds obvious and is not: it is the most common reason a client ends up locked in to a supplier.
How a project runs
Scoping
We map what is there, what needs to be added, and where it goes wrong if we misjudge it.
Design
Screens, flows and components are settled before a line of code is written.
Build
Two-week sprints, each ending in something that runs and that you can try yourself.
Release
Live in stages, with monitoring that trips before a user picks up the phone.
Maintenance
The part that lasts longest. Updates, incidents, and the version after this one.
What we work with
Work in this service
Need any of this?
A single half-hour conversation is usually enough to work out whether this fits and roughly what it costs.