Scope of work

Develop the .NET system your business already relies on

I develop existing applications, build new features and help regain control of ASP.NET Core, MVC, WebForms, APIs, Windows services and SQL databases. The scope can be one module, regular product development or a staged modernisation of the system.

Does this sound familiar?

  • The feature backlog grows without an experienced person to implement it safely.
  • Deployments are stressful and failures emerge in production.
  • The system depends on old libraries or one person's knowledge.
  • Every change touches many areas and is difficult to estimate.
  • Tests, documentation and monitoring are missing.

What the work can include

New features and modules

Develop ASP.NET Core, MVC and WebForms applications, APIs, business workflows, dashboards and integrations.

Audit and modernisation plan

Map architecture, dependencies, risks and deployment. Deliver priorities and a first-stage plan with quotation assumptions and acceptance criteria.

Staged migration to ASP.NET Core

Assess library compatibility and .NET Framework dependencies. Separate selected processes, define module communication and replace older components gradually.

Code and architecture

Clarify module responsibilities, refactor and update .NET and libraries within an agreed scope, checking existing functionality.

Data and SQL performance

Diagnose queries and locks, improve models and indexes and plan migrations with consistency checks. Measure representative operations before and after.

Integrations and background processes

Develop APIs, Windows services, imports and scheduled jobs with errors, retries and duplicate handling so operations can be traced and resumed.

Tests and predictable deployment

Protect critical paths, organise environments and automate publishing. Include data migration, rollback conditions and deployment instructions.

Monitoring and knowledge transfer

Add logs, alerts and measurements. Document important decisions, startup and diagnostics and explain changes to the maintenance team.

Explore the related terms →

See the process in practice

1. Stabilise what already works

Identify critical processes, reproduce startup and add tests and diagnostics. The current application and database establish a baseline.

Move on when the team can reproduce and verify the main operations.

2. Separate one module

Move an agreed process into a new .NET module while the old application handles the rest. Define communication, permissions and read/write ownership.

Move on when the new module meets acceptance criteria and existing workflows still pass their checks.

3. Extend based on results

Choose the next area after verifying the first. Retire replaced components only after confirming functionality and data consistency.

Measurements and business needs should justify the next stage. Agree downtime, cutover and rollback before deployment.

Three starting points

  • Product development: a new workflow, customer portal or integration with clear acceptance criteria.
  • Staged modernisation: assess dependencies, separate a module and verify it before moving the next area.
  • Stabilisation: address incidents, slow operations, critical-path tests and repeatable deployment.

Deployment is more than publishing code

  • Before: process tests, a verified backup, migration plan and rollback conditions.
  • During: a controlled sequence, configuration checks and verification of critical operations.
  • After: monitor errors and timings, compare the baseline and hand over documentation.
Ongoing technical support →

After an audit, you know the next step

Start with a problem description, technology details and agreed access to code or an environment. Missing documentation can be reconstructed during diagnosis. Deliverables include the system and dependency map, risks and priorities, and a first-stage plan with scope, assumptions and acceptance criteria.

From diagnosis to a working system

01

Your needs

Describe the problem, system and desired result.

02

Workshop or audit

Data, risks, feasibility and measurement.

03

PoC or plan

A small scope that validates the solution.

04

Implementation

Integration, tests, monitoring and documentation.

05

Support

Measure results and continue improving.

Frequently asked questions

Does an old .NET system need a complete rewrite?

Not always. Assess dependencies, risks and change costs first. Stabilisation, selective upgrades and module separation are often safer starting points.

What does an audit deliver?

A dependency and risk map, technical priorities, modernisation options, a recommended first stage and information needed to estimate further work.

Can modernisation happen while the business keeps working?

Often, in stages. Each change needs suitable tests, deployment arrangements, monitoring and rollback; the actual plan depends on architecture and data.

Can we develop WebForms while preparing migration?

Yes, when responsibilities can be separated. Moving to ASP.NET Core requires assessing UI, business logic, session state, permissions and dependencies; it is more than changing a project version.

Can I commission just one feature?

Yes: a screen, module, integration, performance improvement or deployment work. We first establish dependencies and acceptance criteria to contain the scope.

Contact me

Do you have a process or system that needs a sound implementation?

Briefly describe the situation. I will recommend a sensible first step — without a sales pitch or obligation.

Describe your problem