7 things to know before commissioning a web application

Commissioning a web application can turn into a process that eats up both budget and time if it isn't started the right way. I have gathered the most important lessons from projects I developed for clients in Canada and Turkey (an operations panel for a dealer network, a football league management site, desktop accounting software) into 7 points you should know before hiring someone. This article is especially for business owners commissioning a web application or SaaS product for the first time.

1. Write the problem first, the feature list later

Instead of saying "I need a panel", describe the real problem, such as "We collect appointments from our dealers over the phone, and finance approvals get lost in email." A good developer listens to the problem and comes up with the scope that solves the most with the fewest features. Web application projects that start with a feature list usually end up bigger and more expensive than necessary.

Coming to the first meeting with answers to the following questions speeds up the process a lot:

2. Start with an MVP

The first version should contain only the features essential for the work to run: user login, the main workflow and a simple admin panel. Add-ons such as reports, notification settings and multiple languages are added after real user feedback arrives. Thanks to the MVP approach, you have a working web application within a few weeks and spend your budget on features that are actually used.

3. Decide from the start who sees what

Admin, employee, dealer, customer... The role and permission structure is the hardest part to change later. Clarifying in the first meeting which role sees which screen and approves what prevents a rewrite later. For example, in an appointment system, the customer creating a record, the finance team approving it and the technical team closing the job means three separate roles.

4. Technology choice determines maintenance cost

When common, well-documented tools such as Next.js, Supabase/PostgreSQL and Vercel are chosen, development gets faster and continuing later with another developer becomes easier. A correctly set up web application can run with only a few hours of maintenance a month. An infrastructure that is little known or dependent on a single person, however, creates extra cost with every change.

5. Split the payment into stages

Define stages such as analysis and design, development, testing and going live, and ask for a demo at the end of each stage. Paying only for the stage you have approved protects both you and the developer and makes progress transparent. Paying everything upfront in one go, or paying entirely at the end of the job, is risky for both sides.

6. The source code and accounts must be yours

The code should be in your GitHub account, and the domain name and server should be in your name. Discuss this from the start and put it in writing so you aren't dependent on the developer when the project ends. A short user guide at delivery and the handover of admin passwords to you are also part of this point.

7. Post-delivery support should be discussed

In the first weeks after going live, small bugs and improvement needs will certainly come up. Discuss the free support period after delivery and how monthly maintenance will be priced afterwards from the start. That way your web application stays safe after it goes live too.

How long does it take to commission a web application?

A small MVP with a clear scope can usually go live within 3-6 weeks. Systems with multiple roles, payments and integrations can take 2-3 months. What lengthens the time most is not technical difficulty but delayed decisions and constantly changing scope.

What does the cost of a web application depend on?

The main factors determining the price are the number of user roles, the number of screens, integration with external systems such as payments or ERP, the need for reporting, and how custom the design will be. That is why, to get a sound quote, a short analysis meeting should be held first and the scope put in writing. As the scope becomes clearer, both the price and the delivery date become more reliable.

Conclusion

With the right scope, staged progress and transparent communication, a web application can go live within a few weeks. While planning your project, you can use these 7 points as a checklist; you can send me any questions you have through serbestis.