
You have an ASP.NET application that works, built years ago. The person who coded it has gone, and every change feels risky. You need someone to take it over, maintain it and perhaps modernise it. These are the questions I'd ask before trusting anyone with the system, myself included.
Freelancer, agency or employee?
- A freelancer fits when you need one experienced person who reads the code, makes the calls and answers you directly. You talk to the person doing the work.
- An agency fits a large project needing several profiles at once, if you accept dealing with a go-between.
- Hiring fits when the system provides full-time work for years.
Eight questions before you sign
- Have you taken over code you didn't write? Ask for a specific example. Maintaining someone else's system is a different craft from coding from scratch.
- How do you audit before quoting? The right answer includes reading the code, the database and the server logs. A price given without seeing anything is a guess.
- What do you know about SQL Server beyond writing queries? Execution plans, indexes, Query Store. In most of the slow systems I see, that's where the problem is.
- Do you migrate everything at once or in stages? For an application in production, Microsoft recommends the incremental method. Be wary of "it all has to be rewritten".
- How do you test, and how do you roll back? A copy to test on, a backup before every change and a plan if something goes wrong.
- Who owns the code and the access? You do, always: the source code, the database and the credentials, with a minimum of documentation.
- Do you know the support dates? In 2026, .NET 8, .NET 9 and SQL Server 2016 all reached end of support. Whoever maintains your system should know that without looking it up.
- Who will I be talking to, in what language and during which hours?
An example of what question 3 is after
On my Parcelas Patagonia portal, one page loaded every listing in the database on each visit, with descriptions in five languages. It worked, until traffic grew. The fix wasn't in the server but in the query: count and page on the SQL Server side.
The same diagnosis showed something else: the listing query had run 22,168 times, almost always for bots crawling every combination of filters. The solution was an index and a robots.txt rule, not more hardware.

Warning signs
- They propose rewriting everything without having read the code.
- They give a fixed price before the audit.
- They don't ask about backups or the server.
- They can't show any system they've maintained for years.
What to have ready
- The source code, or at least a copy of the published site.
- A database backup.
- The versions: Windows Server, IIS, .NET and SQL Server.
- The list of what must not fail: payments, invoicing, outgoing email.
- Known problems and what has already been tried.
My profile, so you can compare
- More than 25 years in .NET, freelance since 2007, with clients in France, the UK and Chile.
- High-traffic sites: I've worked with French platforms such as Taratata, SeLoger.com and Promovacances.com.
- ASP.NET in every era: Web Forms, MVC and ASP.NET Core, with C# and SQL Server.
- Three languages: English, French and Spanish. I live in Chile and work remotely: my mornings overlap with the European afternoon.
- Proper invoicing: I'm registered as self-employed in France.
I work the way I describe above: a free audit, a staged plan at a fixed price and direct support. You can see my experience, my projects and my .NET migration and modernisation page, or write to me directly.
Got a .NET or SQL Server application to modernise?
Free audit and a staged plan at a fixed price. I reply in English, French or Spanish.
Ask for my free auditMessage me on WhatsApp