Skip to main content

Keene Systems, Inc.

How to Choose an ASP.NET Development Company

To choose an ASP.NET development company, match the size of the firm to the size of your project, confirm who will own the source code, ask who will actually do the work, and find out what happens after launch. Technical skill matters, but most ASP.NET firms have it. Projects usually go wrong on fit, ownership and continuity. This guide covers the questions to ask, the warning signs and the kinds of firm you will meet.

Seven questions to ask any ASP.NET development company

  1. Who owns the source code? The answer should be you, in writing, with no conditions. Ask to see the clause.
  2. Who will do the work, and will they stay on it? Ask whether the people you meet are the people who build, and what happens if one leaves.
  3. How long have you worked with ASP.NET? A firm that has lived through Web Forms, MVC and ASP.NET Core can maintain what you have as well as build what you need.
  4. What size of project is normal for you? A firm built for enterprise programs will not give a mid-sized system its best people. A one-person shop cannot cover holidays or illness.
  5. How do you find out what we need? Look for written requirements in plain English before any code. Skipping this step is the most common cause of failed projects.
  6. What happens after launch? Ask whether support requires a monthly contract, and whether the same people will handle it.
  7. Can we see comparable work? Ask for case studies and a client list in businesses like yours.

Business professionals shaking hands at the start of a meeting

Before you contact anyone, have these ready

  • A one-page description of the business problem, in your own words.
  • A rough idea of who will use the system and how many of them there are.
  • A list of the other systems it must exchange data with.
  • For an existing application: where the source code is and what version of .NET it runs on.
  • The name of the person on your side who can make decisions.

Warning signs

  • A fixed price offered before anyone has asked how your business works.
  • Vague answers about who owns the code or where it is kept.
  • No one on the call who can talk about your business as well as the technology.
  • A proposal that recommends rebuilding everything without having looked at what you have.
  • Support offered only as a long-term contract you pay for whether you use it or not.

The kinds of ASP.NET development company you will meet

Firms that do ASP.NET work differ far more in size and focus than in technical skill. Knowing the types makes a shortlist easier to build.

  • Large international software firms. Thousands of staff, many technologies, and a .NET practice among them. They are built for enterprise programs that need dozens of developers at once. A mid-sized project is a small account to them.
  • Digital agencies. Design, marketing and development under one roof, usually working on a .NET content management system. A good fit for a marketing website, less so for the software that runs your operations.
  • Staffing and augmentation companies. They supply individual developers who work under your direction. This works when you have a technical manager in-house to lead them.
  • Independent developers. Often very capable and good value for a small job. The risk is continuity: one person cannot cover illness, holidays or a better offer.
  • Specialist business-application firms. Companies whose whole business is custom software for running a company, built and then looked after for years. Keene Systems is one of these: founded in 1987, building on ASP.NET since 2002, with a team of 50+ professionals.

Which kind of firm fits which project

  • A very large program with dozens of developers: a large international firm has the bench for it.
  • A marketing website on a .NET content management system: an agency that combines design, marketing and development is the natural fit.
  • Extra hands for a team you already manage: staff augmentation. See hiring ASP.NET developers.
  • A business application that runs part of a mid-sized company: a firm that specializes in custom business software and will still know your system in ten years.
  • An existing ASP.NET application whose developer has gone: a firm that takes over other people’s code as routine work. See ASP.NET application support and takeover.

The last two are what Keene Systems does. Our ASP.NET development services page sets out how we work, and our client list and case studies show who we have done it for.

A sensible way to run the selection

  1. Shortlist three firms whose normal project size matches yours.
  2. Have the same conversation with each. Use the seven questions above and note how specific the answers are.
  3. Read the contract terms early. Code ownership and support terms should be settled before price.
  4. Start with a small, defined piece of work. A requirements document or a system review shows how a firm works before you commit to the whole project.

The next step is a short, no-pressure conversation. Schedule an ASP.NET project exploration call or use the form on this page.

Frequently asked questions

How do I choose an ASP.NET development company?

Match the firm’s usual project size to yours, confirm in writing that you will own the source code, ask who will do the work and whether they will stay on it, and find out how support works after launch. Then start with a small defined piece of work before committing to the whole project.

What should I ask an ASP.NET developer before hiring?

Ask who owns the source code, who will do the work, how long they have worked with ASP.NET, what size of project is normal for them, how they gather requirements, what happens after launch, and whether you can see comparable work.

Should I hire a freelancer or a company for ASP.NET development?

A freelancer can suit a small, short project. For an application the business depends on, a company gives you continuity: more than one person knows the system, and work continues through holidays, illness and staff changes.

Who should own the source code?

The client. Insist on a contract clause that states you own the intellectual property of everything produced for you, and make sure the code is kept in a repository you can reach.

Does the size of the ASP.NET company matter?

Yes. A firm much larger than your project tends to assign it junior staff, and a firm much smaller cannot provide cover. Look for one whose typical client looks like you.

Schedule a Project Exploration Call

This free session is your fastest path to improved business productivity.